Page 158 - Cloud computing: From paradigm to operation

1 Framework and requirements for cloud computing

– Automation of service deregistration: It is recommended that a CSN: cloud service broker provide
automatic cloud service deregistration to perform deregistration procedures conveniently and safely.
– Notification of service deregistration: It is required that a CSN: cloud service broker provide the
notification of the service deregistration to CSCs not to use the deregistered service.
– Request for maintaining cloud service: It is recommended that a CSN: cloud service broker request
the related CSP to maintain the deregistered service until the CSCs finish using the cloud service.
– Providing cloud service requirement template: It is recommended that a CSN: cloud service broker
provide a template for service requirements to CSCs for receiving CSC's requirements.
NOTE 3 – The requirement template reflects information about CSC's requirements.
NOTE 4 – The CSC's requirement includes SLA information of the cloud service such as quality, price of cloud
service, remedies for failures to meet the terms of the SLA and so on. The CSC's requirement also includes
information about specifications of the cloud service such as virtual machine, operating system (OS) type,
applications, etc.
– Cloud service requirement validation: It is recommended that a CSN: cloud service broker provide
validation of the contents in the cloud service requirement template.
– Cloud service search: It is required that a CSN: cloud service broker provide searching a cloud service
in the product catalogue to meet the requirements of CSCs.
NOTE 5 – The requirements of a CSC are used as search criteria that include specifications and service level of
a cloud service that a CSC wants to use.
– Providing the best matched cloud service: It is recommended that a CSN: cloud service broker
provide CSCs with the best matched cloud services and information about the CSPs who provide the
cloud services reflecting the CSC's requirements.

– Cloud service alteration: It is recommended that a CSN: cloud service broker request CSPs to alter
registered services for cloud service customization.
– Cloud service substitution for integrated cloud service: It is recommended that a CSN: cloud service
broker provide alternative cloud services in a product catalogue for an integrated cloud service.
NOTE 6 – Based on the alternative cloud services in a product catalogue, a CSN: cloud service broker provides
the substitution of cloud service as a member of an integrated cloud service.
– Equivalent cloud service selection: It is recommended that a CSN: cloud service broker provide an
equivalent cloud service in the product catalogue with the registered service to migrate to keep
service equivalence after migration.

7.3 Functional requirements for contract management
– Cloud service charging: It is recommended that a CSN: cloud service broker provide billing
information to CSCs by reorganizing billing information gathered from related CSPs.
NOTE 1 – The billing information is used to generate invoices for the usage of a cloud service. The billing
information includes business information related to payment, such as methods for payment and biller and
costs for the usage of the cloud service based on price and metering.
– Configuration of cloud service for contract: It is recommended that a CSN: cloud service broker
configure a cloud service through selecting elements of the cloud service by a CSC.
NOTE 2 – Examples of elements for cloud service specification are virtual machines, OS type, applications, etc.
– Service level objectives (SLO) selection: It is recommended that a CSN: cloud service broker provide
selection of service level objectives to a CSC according to business requirements of the CSC.
– SLA document management: It is recommended that a CSN: cloud service broker provide
generation of a SLA document according to the agreement to share the SLA document with the
related CSC.
– SLA description model: It is recommended that a CSN: cloud service broker provide a SLA
description model to describe terms and conditions.
NOTE 3 – Examples of terms and conditions are guaranteed service levels and remedies for failures to meet
the terms of the SLA.

150