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

[Alex Glikson]

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!?