Page 489 - Cloud computing: From paradigm to operation

Cloud Computing management 2

Provisioning
Management
system(s) Assurance
Charging/billing

Cloud
provider
resource view

Application

Cloud
virtualized
resources

Network
virtualized
Cloud service resources
provider
Y.3520(13)_F02

Figure 2 – Cloud resource management system (OSS and BSS)

6.4.1 Software enabled services

The software enabled services (SES) management approach enables both traditional service providers as well
as Internet content and media service providers to leverage the opportunities and service marketplace that
are presented by the convergence of networking and IT. Specifically, the SES management approach provides
a means to allow consistent end to end management and metering of services exposed by and across
different service providers' domains and technologies.

Operations, administration and management interfaces for cloud services today are structured in silos per
technology, standardized by specific standards development organizations or implemented by vendors as
proprietary implementations. This presents a challenge in the rendering of consistent management of
services sourced from different domains.
The SES management approach proposes a mechanism to allow consistent access to the software
components information as well as management operations. This consistent access is achieved by
incorporating the management interface in addition to the functional interface (FI) definition that is part of
software component creation. The SES approach enables reusability of services in different environments,
including that of cloud computing by manipulating the SES lifecycle management metadata which is
supporting the service management interface (SMI) operations.

For further information about SES and SMI concepts, please refer to Appendix III.
The SES pattern is defined to also handle those cases where the composed service is not able to manage all
of the management dependencies by means of the logic which is triggered by the SMI operations. In this
case, the lifecycle management metadata associated with the SMI is providing a recipe which describes how
to manage the composition members.

Protocol neutral interface information models and class models of the SMI, along with corresponding
statements of interface information requirements and interface information use cases, can then be defined
[b-TMF TR198].

In order for implementation of SESs to be as useful as possible, the following requirements should be
addressed:

481