Page 157 - Cloud computing: From paradigm to operation

Framework and requirements for cloud computing 1

For the establishment of a contract, this logical component needs to create a cloud SLA document by using
CSP's SLA and notifies it to the contracted CSC. This logical component registers an agreed service level to the
service management logical component to guarantee the contracted service quality. If the cloud service fails to
meet the service level, this logical component enforces remedies for failures to meet the terms of the SLA.

6.4.4 Service access management

A service access management logical component requests to launch a contracted cloud service to the
designated CSP. This logical component also manages access information of cloud services. In order to use to
a cloud service, a CSC requires to get access information. After a CSP launches a cloud service, the CSP
provides access information to a cloud service broker and this logical component manages the information
and delivers the access information to the CSC.
NOTE – The access information is required for a CSC to access a cloud service. The access information may include an
access point such as Internet protocol address or uniform resource locator (URL) of the cloud service and authentication
methods such as a certificate or identification (ID) and password to access the cloud service.
6.4.5 Service management
A service management logical component manages the controls and status of running cloud services. This
logical component delivers control requests for the running cloud services to CSPs in order to stop, resume
and terminate them on behalf of a CSC. This logical component also checks the status of running cloud
services by monitoring and enforces the service level agreed in a SLA. If a cloud service fails to meet the
service level, this logical component needs to take an action to handle the situation by interacting with a
contract management logical component.

7 Functional requirements of cloud service brokerage

7.1 Functional requirements for workspace
– Authentication and authorization for workspace: It is required that a CSN: cloud service broker
have authentication and authorization mechanisms to authorize CSPs and CSCs access to workspace.
– Account management: It is required that a CSN: cloud service broker manage the accounts of CSCs
and CSPs.
– User interface for CSCs: It is recommended that a CSN: cloud service broker provide a user interface
for CSCs to search, select, request, launch, monitor, manage and pay for the cloud services from the
multiple CSPs.
– User interface for CSPs: It is recommended that a CSN: cloud service broker provide a user interface
for CSPs to register information about the CSPs and cloud services to a CSN: cloud service broker.
NOTE – The information about a CSP includes a name of the CSP, entry point URL of the CSP at which a CSN:
cloud service broker gains access to and communicates with the CSP, geographical location of the CSP, access
account to the CSP and so on.

7.2 Functional requirements for product catalogue management

– Registration of cloud service: It is required that a CSN: cloud service broker provide registration of
cloud services in the product catalogue.
NOTE 1 – Depending on the service models, the subject and way of registration are different. For a cloud
service aggregation model, cloud services in CSPs are registered in a product catalogue. For cloud service
integration and customization models, a CSN: cloud service broker registers new cloud services to a product
catalogue by integrating the registered cloud services according to the broker and CSC's requirements,
respectively.
– Cloud service deregistration: By the agreement between a CSP and a CSN: cloud service broker, it
is required that the CSN: cloud service broker deregister the cloud services in a product catalogue.
NOTE 2 – The deregistration of a cloud service includes disabling the cloud service from the product catalogue,
notifying the deregistration of the cloud service to related CSCs, stopping all running cloud services and
deleting the cloud service from the product catalogue.

149