Page 487 - Cloud computing: From paradigm to operation
P. 487
Cloud Computing management 2
to be instantiated and become available for use by the cloud service users. In other words, a cloud application
needs to be executed to make one or more cloud services available.
Cloud service providers need to increasingly offer multi-cloud platform solutions to support the above
scenarios. Such solutions will need to be flexible and effective in managing resources across multiple cloud
service providers [ITU-T Y.3501].
These solutions can be realized using cloud services, delivered through cloud computing capabilities with
reusable services. Cloud service providers need to develop a deep insight into, and understanding of, the run-
time aspects of service delivery as well as the management of these services and the resources required to
deliver them.
Therefore, there is a need for a common concept for end to end resource management across multiple cloud
service providers.
Complex, media-rich, composite services use a variety of both telecommunication and information
technology (IT) infrastructures and are composed of individual service components that may be acquired
from, or exposed to, third parties.
6.2 Service delivery management structure
The framework described in this Recommendation can be used to enable the delivery of cloud services,
independent of the underlying software or network technologies. This framework, which is a service delivery
management structure, needs to address the full cloud services lifecycle, covering such important use cases
as service composition, aggregation and service catalogues.
Management of cloud services needs to provide a framework for the essential building blocks required to
manage the delivery of cloud services and foster the basis for detailed service delivery management.
One objective is to provide a means to allow consistent end to end management, including accounting, of
services exposed by and across, domains and platforms of different cloud service providers. A standard
framework and best practices are needed to support business practices associated with multiple provider
cooperation throughout the lifecycle of the service and to foster wide adoption of the standard artefacts in
any architecture, technology environment and service domain.
Achieving consistent maintenance of cloud services sourced from different domains is a challenging task. To
address this challenge, an approach that enables and supports consistent management access to the cloud
services is desired. Such an approach is desired to complement the service capabilities exposed by the
software component's interfaces with additional lifecycle management operations. This approach should
also enable reusability of services in different environments, especially in cloud computing.
Frameworks, architecture, design patterns and best practices are required to realize the above objectives for
the cloud service providers. The interfaces of individual service components are not the primary focus as the
actual interfaces may vary across different implementations, vendor technologies and operator
requirements. Standard design principles and frameworks are required to allow for the rapid development,
deployment and management of composite multi-cloud services provided by the telecommunication
industry.
This provides a framework to guide architects and developers of cloud services regarding the end to end
management of cloud computing resources.
6.3 Difference between cloud computing and the traditional form of computing
There are two principal differences between cloud computing and the traditional form of computing that
make the problem of managing resources associated with cloud services more difficult. One difference is the
virtualization of the computing and network resources in the cloud computing reference architecture
[ITU-T Y.3502]. The other difference is that multiple cloud service provider domains are increasingly involved
in the delivery of cloud services and this environment greatly complicates end to end resource management.
479