We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Roadmap of Cloud Hosting - FIWARE Forge Wiki

Roadmap of Cloud Hosting

From FIWARE Forge Wiki

Revision as of 11:31, 30 May 2014 by Jkennedyie (Talk | contribs)
Jump to: navigation, search

Contents

Introduction

The Cloud chapter in FI-WARE provides a next generation Cloud solution that will be open, scalable, resilient, standardised, and secure, and will enable Future Internet applications by providing service-driven IaaS and PaaS functionalities and extending the reach of the cloud infrastructure to the edge of the networks, much closer to end users.

You can learn more about the Cloud Chapter by reading the FI-WARE Architecture and Open Specifications. Following is a description of the Technical Roadmap planned for the chapter, which will be developed through subsequent Releases of the FI-WARE Platform. Please also check the Releases and Sprints numbering, with mapping to calendar dates.


Third Major Release

Following is a description of the major features that will be supported in the third major release of FI-WARE. These features will be implemented by a number of FI-WARE GEs implementing the Reference Architecture of the Cloud Chapter. The third release of FI-WARE introduces 1 new GEs, and significantly extends the capabilities of the rest.

IaaS Data Center Resource Management

  • OpenDayLight integration in Openstack
  • Scheduler overcommit support
  • Scheduler advanced proximity support
  • Upgrade to Openstack's Havana release
  • Document the User & Programmers Guide
  • Document the Installation and Administration Guide
  • Document the Unit Testing report
  • Use agile development methodologies

IaaS Service Management

Deprecated, some functionalities was translated to the Cloud Portal and other one was translated to the PaaS Management. The functionalities related to the autoscalability was translated to a new GE (Scalability Manager).

Scalability Manager

The roadmap of this new component is the following:

  • Choose Rule Engine based on analysis of different Rule Engines available.
  • Define the scalability API of the new GE.
  • Define the scalability rule format.
  • Define the architecture of the GEi.
  • Generate documentation of the GE architecture.
  • Implement Rest interface to collect data from the Monitoring GE in HA based on NGSI-10
  • Implement Rest interface to process the subscription to the GE in order to evaluate the scaling up and down of a server.
  • Implement the Rule Engine based on the selected framework.
  • Document the User & Programmers Guide.
  • Document the Installation and Administration Guide.
  • Document the Unit Testing report.
  • Management of security access to the information following the same schema of the rest of OpenStack service.

Object Storage

The roadmap of this component for release 3 is the following:

  • Add the ability for users to encrypt/decrypt specific objects on upload to/retrieval from the Object Storage system.
  • Add the ability for users to compress/decompress specific objects on upload to/retrieval from the Object Storage system.
  • Create client side libraries/utilities to consume CDMI interface.
  • Expose differentiated storage hardware capabilities for multi-tier storage.
  • Integrate with Object Storage benchmarking, monitoring and metrics.

Cloud Proxy

Please refer to the Roadmap of Interface to Networks and Devices

PaaS Management

The roadmap of this component for the release 3 is the following:

  • The management of blueprint templates
  • The existence of a blueprint template catalogue
  • The existence of abstract blueprint templates catalogue and its management (including the introduction of new ones)
  • The integration with resource management integration v2
  • The creation and management of networks
  • The configuration of blueprint templates
  • The management of application

Software Deployment And Configuration

The roadmap of this component for the release 3 is the following:

  • Introduction in metadata in the sofware catalogue
  • The software catalogue management
  • The inclusion of puppet as configuration engine for software recipes
  • The insertion of software in the SDC and chef-server automatically
  • Cookbooks to be included in the software catalogue

Monitoring

The main goal of the 3rd release will be:

  • Ability to monitor VM instances and publish the metrics via "Publish-Subscribe Context Broker" GE provided by the "Data/Context" chapter using NGSI API (which can be consumed by the Portal, SM, etc)
  • Advanced monitoring capabilities provided by this GE "as a service".
  • Extend the architecture in order to incorporate new probes like Nagios, openNMS and perfSONAR.
  • Provide federation capabilities to the architecture (developed by XiFi project).
  • Management of security mechanism as openstack services.

Self-Service Interfaces

The roadmap of the Self-Service Interface component for release 3 is the following:

  • The management of blueprint templates
  • The existence of a blueprint template catalogue
  • The existence of abstract blueprint templates catalogue and its management (including the introduction of new ones)
  • The integration with IdM GE, including OAuth authentication
  • The creation and management of networks in Grizzly version
  • The management of networks within Blueprint templates

Edgelets Management

  • First public release of the Edgelets GEi, previous one had to be postponed
  • Ability to manage the slave nodes via API
  • Ability to manage the edgelets on the slave nodes via API
  • Catalogue of existing edgelets software

Job Scheduler

  • Ability to offer the User Dataspace (requirement for multitenancy).
  • Ability to access User and Global Dataspaces through RESTful API
  • Ability to integrate with the Identity Management GE Keystone for users authentication
  • Ability to manange Nova IaaS Nodesources by handling the interaction with IaaS DCRM GE
  • Improve the Java APIs for protocols communication management or troubleshooting

For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release:


FI-WARE GE Supported Features Epics under analysis

IaaS Data Center Resource Management

Release 3.1


Release 3.2

Release 3.3

Scalability Manager

Release 3.1

Release 3.2

Release 3.3

Object Storage

Release 3.1

Release 3.2

Release 3.3

Cloud Proxy

Please refer to the Roadmap of Interface to Networks and Devices

 

PaaS Management

Release 3.1

Release 3.2

Release 3.3

FIWARE.Feature.Cloud.PaaSManager.APIs.OVFPlusPlus FIWARE.Feature.Cloud.PaaSManager.StartStopEnvironmentMgmt FIWARE.Feature.Cloud.PaaSManager.AppMonitoring FIWARE.Feature.Cloud.PaaSManager.PaaSScaling FIWARE.Epic.Cloud.PaaSManager.Backup FIWARE.Epic.Cloud.PaaSManager.Lifecycle FIWARE.Feature.Cloud.PaaSManager.EnvironmentConfiguration FIWARE.Feature.Cloud.PaaSManager.AutomaticInstaller FIWARE.Feature.Cloud.PaaSManager.StartStopEnvironmentMgmt

Software Deployment And Configuration

Release 3.1


Release 3.2

Release 3.3

FIWARE.Feature.Cloud.SwDeployConfig.SWStartStop FIWARE.Feature.Cloud.SwDeployConfig.SWUpdate FIWARE.Epic.Cloud.SwDeployConfig.Backup FIWARE.Epic.Cloud.SwDeployConfig.Lifecycle FIWARE.Feature.Cloud.SwDeployConfig.ArtifactRetirement

Monitoring

Release 3.1

Release 3.2

Release 3.3

Self-Service Interfaces

Release 3.1:

Release 3.2:

Release 3.3:


Edgelets

Release 3.2

Release 3.3

Job Scheduler

Release 3.1

Release 3.2

Release 3.3


Future Releases

Following is a description of features that will be supported in future releases of FI-WARE after the second release:


IaaS Data Center Resource Management

  • Ability to keep low labor cost while growing the cloud, by automating administrative tasks (e.g., failure recovery, upgrade, etc)
  • Ability to efficiently schedule resources across compute, storage and network
  • Ability to provide QoS guarantees for services hosted in the cloud (compute, storage and network)
  • Ability to support heterogenous hardware configurations, optimized for different classes of workloads
  • Ability to access advanced administration capabilities related to resource management via CLI and Web portal: health, capacity, etc
  • Ability to support cross-cloud deployments (via federation and/or cloud brokerage)

Object Storage

Materializing_Cloud_Hosting_in_FI-WARE#Scalability_Manager

  • Management of scalability policies related to tier.

Cloud Proxy

The third release of Cloud Proxy will be focusing on 'productization' of Cloud Proxy as an industrial appliance.

PaaS Management

PaaS GE in the third release of FI-WARE will be focusing on bringing the full capabilities of the PaaS plaatform developed in the 4CaaSt project, as well as enhancements needed to address additional, more advanced, PaaS platforms:

  • Lifecycle management of applications and environments.
  • Start/Stop functionality.
  • Monitoring probes configuration
  • Backup and recovery.
  • Software updates.

Software Deployment And Configuration

The implementation of this GE in the third release of FI-WARE will be focusing on bringing the full capabilities developed in the 4CaaSt project, as well as enhancements associated with the emerging 'devops' and configuration management tools for the cloud (such as Chef).

  • New types of recipes for lifecycle management (upgrades, backups, start/stop, monitoring configuration, etc.).

Monitoring

Self-Service Interfaces

  • Ability to access advanced administration capabilities related to resource management via CLI and Web portal: health, capacity, etc
  • Ability to compose new services in Web Portal


Edgelets Management

The main goal of the 3rd release will be to support large-scale deployments, involving large number of distributed Cloud Proxy devices that will be used to host Edgelets.

Job Scheduler

  • Ability to offer the User Dataspace (requirement for multitenancy).
  • Ability to access User and Global Dataspaces through RESTful API

Planned:

  • Ability to integrate with the Identity Management GE Keystone for users authentication
  • Ability to enable several communication protocols
    • baseline enhancements in troubleshooting, by offering a ping mechanism forced with a given protocol or the possibility to disable dynamically a protocol.
  • Ability to integrate Object Storage GE

Previous Releases

Second Major Release (2Q 2013)

Following is a description of the major features that will be supported in the second major release of FI-WARE. These features will be implemented by a number of FI-WARE GEs implementing the Reference Architecture of the Cloud Chapter. The second release of FI-WARE introduces 5 new GEs, and significantly extends the capabilities of the rest.

IaaS Data Center Resource Management

This GE provides a very complex, distributed and highly scalable system, comprising an entire cloud infrastructure. The capabilities are largely based on OpenStack, as well as several additional baseline assets provided by IBM (such as System Pools for resource management, HSLT for building scalable meadleware fabric, and DOVE for network virtualization). The development of this GE includes contribution to each of the above assets (including contributions to the OpenStack open source community, as well as contribution of features to the proprietary assets), as well as integration (e.g., enhancements to OpenStack Nova leveraging HSLT assets, integration between DOVE and OpenStack Quantum) and customization for the needs of FI-WARE and FI-PPP (e.g., to meet the multi-tenancy needs of the Open Innovation Lab).

  • Ability to achieve high resource utilization (by using a new resource scheduler component providing efficient resource pooling, optimization and resource over-commit). High resource utilization is the effect of several combined extensions to the GE baseline including :
    • a placement engine that optimizes the initial placement of VMs at provisioning time
    • a resource scheduler that dynamically adjusts over-commit ratios to the VM workloads and live-migrates VMs to maximize utilization
  • Support for VM groups and placement policies (e.g., HA, security, etc)
Initial placement and scheduling are enhanced so that they can leverage VM hints to solve placement problems
  • Ability to scale to thousands of physical machines (by leveraging hierarchical approach using OpenStack "Cells") [Note: will not be deployed in the FI-WARE testbed]
  • Enhanced availability of VM instances by automated recovery of VMs from a failed host
Disaster-recovery functionality extensions
  • SDN-style virtual networking with policy-based connectivity services
Support for multi-tenancy in the cloud by network isolation

IaaS Service Management

The implementation of this GE is based on Claudia -- the baseline asset developed by Telefonica. Hence, this roadmap is tightly coupled with the roadmap of Claudia, and focuses on integration aspects as well as enhancements developed in FI-WARE.

  • Ability to provision and manage the life cycle of Virtual Appliances.
  • Ability to allocate virtual network as part of a Virtual Appliance.
  • Ability to allocate volume resources associated to a Virtual Appliance.
  • Ability to invoke DCRM capabilities via OpenStack APIs.
  • Ability to specify placement policy rule associated to a Virtual Appliance.

Object Storage

Object Storage capabilities in FI-WARE are built on OpenStack Swift, exposed through an implementation of the CDMI interface. The FI-WARE team is contributing directly to the OpenStack open source community, and also works on value-add capabilities which are not yet available. The work is also leveraging results of the VISION Cloud project.

  • Pluggable Front-end Architecture
    • Arbitrary in-band filters can be plugged into the data path
  • Integrated Object Storage Security
    • Integration with shared security infrastructure

Cloud Proxy

The implementation of the Cloud Proxy GE is based on the baseline asset developed by Technicolor. The main goal of the second (and third) release is to develop a production-ready industrial appliance with the Cloud Proxy capabilities, as well as to further develop it with additional capabilities, as outlined below.

  • Image management for cloud edge virtual appliances
  • Extending trusted compute pools to cloud edge devices
  • Resource allocation guarantees for cloud edge appliances
  • Better integration of the Cloud Proxy with the cloud applications
  • Richer interface to the Cloud Proxy
  • OSGi machines in the Cloud Proxy (legacy apps support)
  • Enhanced resource management for virtual appliances hosted on cloud edge devices
  • Availability of the Cloud Proxy as a HW box (with embedded SW)

PaaS Management

This is the first release of FI-WARE providing PaaS capabilities. The implementation of this GE is based on the results of the 4CaaSt project, and the roadmap below is focusing on integration of the capabilities into FI-WARE platform.

  • Ability to maintain a catalogue of PaaS components
  • Ability to deploy PaaS environments comprising sets of components in the catalogue.
  • Ability to deploy applications on already deployed PaaS environments.
  • Interface with the Service Manager
  • Security features (CORS, Keyston authentication, tokens).

Software Deployment And Configuration

This is the first release of this GE. The implementation of this GE is based on the baseline assets developed in 4CaaSt project, as well as open source engine called Chef. Hence, the roadmap is tightly coupled with the roadmap of the baseline assets, and focuses on integration aspects as well as enhancements developed in FI-WARE. Please, refer to the documentation of the baseline assets for more details of their roadmap.

  • Automated installation and configuration of software packages on virtual machines.
  • Installation and configuration of application components on the installed products.
  • Management of recipes and a catalogue of supported products.
  • Integration with the security mechanisms (CORS, tokens, Keystone).

Monitoring

This is the first release of FI-WARE providing these capabilities. The implementation of this GE is based on the results of the 4CaaSt project, and the roadmap below is focusing on integration of the capabilities into FI-WARE platform.

  • Ability to monitor VM instances and publish the metrics via collectd.
  • Storage of the metrics in a monitoring database, accessible through the TCloud monitoring API.

Self-Service Interfaces

The main goal of the second release of this GE is to provide advanced service management capabilities (provided by IaaS Service Management GE) via Web portal, including Virtual Data Center, Services, storage/network resources, quotas.

Edgelets Management

This is the first release of FI-WARE introducing the capability to host 'edgelets' (lightweight runtime components) on Cloud Edge devices.

  • Ability to manage the slave nodes via API
  • Ability to manage the edgelets on the slave nodes via API
  • Ability to add edgelets to the edgelets catalogue
  • First version of the development framework for the edgelets
  • Monitoring API for the nodes and the edgelets

Job Scheduler

This release includes a preview of the Job Scheduling GE, delivered as virtual appliance. The implementation of this GE is largely based on the ProActive suite, hence the baseline for the current roadmap is the capabilities inherited from the baseline asset, as well as new capabilities developed as part of the development cycle of the baseline asset (with major contributions by the FI-WARE team).

  • Ability to schedule, manage and submit computational jobs on heterogeneous resources via RESTful API
  • Ability to monitor and manage computing nodes via RESTful API
  • Ability to provision computing nodes according with user criteria (i.e. specific operating system, available resources or licenses)
    • baseline enhancements in securing internally unauthorized selection scripts execution.
  • Ability to access to the Job Scheduler GE implementation, hosted in a VM available from the testbed.
  • Basic capabilities relevant for Development & Test usage will be also available via the Integrated Development Environment, provided by the "Developer Tools" chapter.

For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release:


FI-WARE GE Supported Features Epics under analysis

IaaS Data Center Resource Management

Release 2.1

Release 2.2


Release 2.3

FIWARE.Epic.Cloud.ResourceManager.MgmtFabric FIWARE.Epic.Cloud.ResourceManager.Capacity, FIWARE.Epic.Cloud.ResourceManager.Mobility, FIWARE.Epic.Cloud.ResourceManager.Network, FIWARE.Epic.Cloud.ResourceManager.Placement, FIWARE.Epic.Cloud.ResourceManager.Metrics

IaaS Service Management

Release 2.1

Release 2.2


Release 2.3

FIWARE.Feature.Cloud.ServiceManager.Security, FIWARE.Feature.Cloud.ServiceManager.Template

Object Storage

Release 2.1

Release 2.2

Release 2.3

FIWARE.Epic.Cloud.ObjectStorage.API FIWARE.Epic.Cloud.ObjectStorage.Security FIWARE.Feature.Cloud.ObjectStorage.Security.EnhancedMultiTenancy

Cloud Proxy

Release 2.3

 

PaaS Management

Release 2.2:

Release 2.3:

FIWARE.Feature.Cloud.PaaSManager.ApplicationMgmt FIWARE.Feature.Cloud.PaaSManager.APIs.OVFPlusPlus FIWARE.Feature.Cloud.PaaSManager.BlueprintTemplateCatalogueMgmt FIWARE.Feature.Cloud.PaaSManager.EnvironmentConfiguration FIWARE.Feature.Cloud.PaaSManager.StartStopEnvironmentMgmt FIWARE.Feature.Cloud.PaaSManager.NetworkManagement FIWARE.Feature.Cloud.PaaSManager.InsertAbstractEnvironment FIWARE.Feature.Cloud.PaaSManager.AppMonitoring FIWARE.Feature.Cloud.PaaSManager.PaaSScaling FIWARE.Feature.Cloud.PaaSManager.Federation FIWARE.Epic.Cloud.PaaSManager.Backup FIWARE.Epic.Cloud.PaaSManager.Lifecycle

Software Deployment and Configuration

Release 2.2:


Release 2.3:

FIWARE.Feature.Cloud.SwDeployConfig.SWStartStop FIWARE.Feature.Cloud.SwDeployConfig.SWUpdate FIWARE.Epic.Cloud.SwDeployConfig.Backup FIWARE.Epic.Cloud.SwDeployConfig.Lifecycle FIWARE.Feature.Cloud.SwDeployConfig.PuppetAware FIWARE.Feature.Cloud.SwDeployConfig.Cookbooks FIWARE.Feature.Cloud.SwDeployConfig.InsertSoftwareCatalogue FIWARE.Feature.Cloud.SwDeployConfig.SWMetadata FIWARE.Feature.Cloud.SwDeployConfig.SWStartStop FIWARE.Feature.Cloud.SwDeployConfig.SWUpdate

Monitoring

Release 2.2

Release 2.3


FIWARE.Epic.Cloud.Monitoring.SourceMetrics FIWARE.Epic.Cloud.Monitoring.Distribution FIWARE.Epic.Cloud.Monitoring.Storage FIWARE.Epic.Cloud.Monitoring.APIs

Self-Service Interfaces

Release 2.1:

Release 2.2:

Release 2.3:


Edgelets

Not officialy released in this release

Job Scheduler

Release 2.1

Release 2.2

Release 2.3


First Major Release (3Q 2012)

Following is a description of the major features that were supported in the first major release of FI-WARE. These features were implemented by a number of FI-WARE GEs implementing the Reference Architecture of the Cloud Chapter:

July 2012

A number of basic capabilities for basic management of resources on datacenter were supported:

  • Ability to provision virtual machines and the associated compute, storage and network resources, via a standardized API and trough a Web-based Portal available to Application Providers
  • Ability to provide basic QoS guarantees (CPU and memory allocation guarantees)
  • Ability to scale to hundreds of physical machines (capable to host thousands of virtual machines)
  • Cloud Proxy availability (as a PC software with a basic level of features)

Besides, ability to provision virtual appliances on cloud edge devices, via a remote API, will be supported.

For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features were supported for each FI-WARE GE:


FI-WARE GE Supported Features

IaaS Data Center Resource Management

FIWARE.Epic.Cloud.OCCIResourceManager.API, FIWARE.Epic.Cloud.OCCIResourceManager.Compute, FIWARE.Feature.Cloud.OCCIResourceManager.API, FIWARE.Feature.Cloud.OCCIResourceManager.Compute, FIWARE.Feature.Cloud.OCCIResourceManager.ImageRegistry, FIWARE.Feature.Cloud.OCCIResourceManager.EssentialManagement, FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler, FIWARE.Feature.Cloud.ResourceManager.Capacity.SimpleDaytraderOvercommitStandalone FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration, FIWARE.Feature.Cloud.ResourceManager.Capacity.MultiVmWithConstraintsOvercommitStandalone

IaaS Service Management

FIWARE.Feature.Cloud.ServiceManager.APIs.OCCI, FIWARE.Feature.Cloud.ServiceManager.APIs.OpenStackAPI, FIWARE.Feature.Cloud.ServiceManager.APIs.OCCIProvisioning, FIWARE.Feature.Cloud.ServiceManager.ActionSystem,FIWARE.Feature.Cloud.ServiceManager.QuerySystem, FIWARE.Feature.Cloud.ServiceManager.MonitoringQueryManager, FIWARE.Feature.Cloud.ServiceManager.Provisioning, FIWARE.Feature.Cloud.ServiceManager.QueryManager,FIWARE.Feature.Cloud.ServiceManager.ActionSwitch, FIWARE.Feature.Cloud.ServiceManager.DistributedQuerySystem, FIWARE.Feature.Cloud.ServiceManager.RulesEngine

Object Storage

Not in this release

Cloud Proxy

FIWARE.Feature.I2ND.CE.HomeResourceAbstractionLayerFirstRelease FIWARE.Feature.I2ND.CE.Images FIWARE.Feature.I2ND.CE.Instances FIWARE.Feature.I2ND.CE.PlatformFeatures

PaaS Management

Not in this release

Monitoring

Not in this release

Self-Service Interfaces

FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal,

FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Instances,

FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Images,

FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Flavors,

FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI,

FIWARE.Feature.Cloud.SelfServiceInterfaces.CloudLibraryImplementation


September 2012

The following enhancements and additions to the above capabilities were delivered in the September 2012 release:

  • Ability to provision 'premium' virtual machines with enhanced hardware-supported trust
  • Ability to maintain a library of pre-configured virtual machine images that can be used for fully-automated provisioning of new virtual machines
  • Ability to maintain high availability of certain components of the cloud management stack in presence of hardware failures
  • Ability to deploy virtual data centers, services and servers inside organizations
  • Ability to store opaque objects in assigned containers with associated metadata, via a standardized Object Storage API (CDMI)


Most of these functions were also available to Application Providers through extensions of the Web-based Cloud Portal.

For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features were supported for each FI-WARE GE:


FI-WARE GE Supported Features

IaaS Data Center Resource Management

FIWARE.Feature.Cloud.ResourceManager.MgmtFabric.DistributedScalableServices FIWARE.Feature.Cloud.ResourceManager.MgmtFabric.Resiliency FIWARE.Epic.Cloud.ResourceManager.Compute

IaaS Service Management

FIWARE.Feature.Cloud.ServiceManager.VDCManagement, FIWARE.Feature.Cloud.ServiceManager.Volumes

Object Storage

FIWARE.Feature.Cloud.ObjectStorage.API.ObjectManipulation, FIWARE.Feature.Cloud.ObjectStorage.API.ContainerManipulation

Cloud Proxy

No new feature

PaaS Management

Not in this release

Monitoring

Not in this release

Self-Service Interfaces

FIWARE.Feature.Cloud.SelfServiceInterfaces.GenerateFileFormat, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Monitoring, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.Volumes, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.ServiceAutoScalling, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserPortal.VDCManagement, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI.Monitoring, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI.Volumes, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI.ServiceAutoScalling, FIWARE.Feature.Cloud.SelfServiceInterfaces.UserInterface.UserCLI.VDCManagement


Personal tools
Create a book