[Fiware-cloud] FI-WARE WP4 functions and capabilities - draft for review & discussion

[FERNANDO LOPEZ AGUILAR]

Dear Alex et all,

We just extend the section about PaaS with the following context in order to talk about it during the PhC today:

PaaS:

-  application/service definition (extensions to OVF to support platform concepts).

-  Deployment design (establish the concrete structure of the application deployment: number of VMs, software in each VM, final network structure, etc.

-  Provisioning and deployment: Configuring and passing of information to the different elements in the PaaS to prepare and later deploy the application/service into the IaaS.
During the deployment phase different components need to be orchestrated: the configuration interfaces of the services offered integrated into the Platform (e.g. database services), configuration of the monitoring and accounting system, configuration of the VM (drive the creation of the VM with the application components inside), etc.

-  IaaS/NaaS control layer, which interacts with the IaaS provider to deploy the VM, install and configure the software into the different VMs.

-  Adaptation and scalability of the application/services deployed. Based on rules defined by the service provider or to enforce the SLAs in place.


BR, Fernando.-

Fernando López Aguilar
Cloud Computing
fla at tid dot es
+34 914 832 729
Telefónica I+D (R&D)
Ronda de la Comunicación s/n
Distrito C, Edificio Oeste 1, Planta 5
28050 Madrid, Spain


[cid:image001.jpg at 01CB21A4.CCF8C640] <http://www.tid.es/>
<http://www.tid.es/>

El 13/05/2011, a las 16:44, Alex Glikson escribió:


All,

Based on the WP description in the DoW and the discussion we had during the
kickoff, I've tried to outline the main functions and capabilities of Cloud
Hosting, as well as few other aspects (scenarios, users, non-functional
aspects). I'm sure there are many things missing -- please, review and
comment.

Hopefully, this list can become the outline of our chapter in the High
Level Description that we need to deliver by June, 20th.

During the upcoming conference call on Tuesday (let me know if you don't
have the call details), we can review the latest version of this list (with
your updates and comments), and decide on responsibilities to elaborate on
each of the items in the HLDesc.

Regards,
Alex

P.S. it is still not clear to me how to 'partition' the list below into
small number of 'generic enablers'.. However, I'm also not sure it is
strictly necessary, as long as we provide the necessary details to
understand what this WP is about to provide., Juanjo, others -- any
thoughts?

------------------------------

Object store

Management fabric
- communication, synchronization, health monitoring, persistent store

Node deployment engine

Resource management -- Single 'compute' target ("node"), Group of 'compute'
targets ("cluster"), Group of clusters (cloud)
- request orchestration and dispatching
- capacity management & admission control
- placement optimization (for multiple targets)
- QoS management & resource allocation guarantees
- resource reservation (for certain time period)
- storage control (internal, shared)
- network control (internal, external)

Storage management

Network connectivity management

Image repository

Service management
- request orchestration and dispatching
- catalog
- elasticity governance
- SLOs (management, enforcement)
- metering

PaaS

Cloud Proxy

Interfaces (APIs, portal, toolkit)
- Admin interface
- User interface

------

E2E Scenarios
- catalog browsing
- provisioning & deployment management
- monitoring & metering
- SLO-driven capacity overbooking & elasticity governance
- cloud administration

Non-functional Aspects
- Security: e.g., user authentication & authorization,
compute/network/storage isolation, OVF certificate validation, etc
- Scalability
- Performance
- Resiliency
- APIs
- etc

Users of Cloud Hosting
  admin of the IaaS provider, managing the IaaS infrastructure
  admin of the PaaS provider, managing the PaaS infrastructure
  IaaS user, directly consuming IaaS infrastructure and services (Note:
  could be the UC Project developer, which uses hosted VMs to perform
  development/testing or to deploy in 'production' a UCP
  product/application)
  PaaS user (e.g., UC Project developer), directly consuming PaaS
  infrastructure and services to build a 3rd part application/service
  End-user of the application hosted in the cloud -- Not a Direct User!?


_______________________________________________
Fiware-cloud mailing list
Fiware-cloud at lists.fi-ware.eu<mailto:Fiware-cloud at lists.fi-ware.eu>
http://lists.fi-ware.eu/listinfo/fiware-cloud


________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20110517/bddb0f6c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6541 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20110517/bddb0f6c/attachment.jpg>