Cloud 3
Cloud Service Management
The management of cloud infrastructure products and services is cloud
management. Public clouds are operated by public cloud service providers,
which provide the servers, storage, networking and data centre operations of
the public cloud environment. With a third-party cloud management tool, users
can also choose to manage their public cloud services.
Public cloud service users can typically choose from three categories of specific
cloud provisioning:
User self-provisioning: Users, usually via a web form or console
interface, buy cloud services directly from the provider. On a per-
transaction basis, the client pays.
Advanced provisioning: A pre-determined sum of services scheduled in
advance of operation is contracted in advance by customers. A flat fee or
a monthly fee is charged by the consumer.
Dynamic provisioning: When the client requires them, the provider
allocates resources, and then decommissions them when they are no
longer required. On a pay-per-use basis, the client is paid.
,The purpose and scope of the management of cloud services are listed below:
Purpose: Establish suitable techniques for managing and running cloud-
based services. Insert cloud service management techniques into current
frameworks for IT creation and support.
Scope: Oversight of cloud-based service design, development and
change. Cloud-based service management and operation.
Characteristics of Cloud service
Management
In a design for handling cloud environments, cloud management incorporates
applications and technologies. With a range of cloud management platforms
and instruments, software developers have responded to the management
challenges of cloud computing. These solutions include native tools provided by
public cloud providers, as well as third-party tools designed by various cloud
providers to provide consistent functionality. With access to various native
features within individual cloud platforms, administrators must balance the
conflicting requirements of efficient consistency across various cloud platforms.
The need for transparent cross-platform management is motivated by
increasing public cloud adoption and increased multi-cloud use. For those
technical professionals responsible for maintaining IT systems and facilities, the
rapid adoption of cloud services presents a new set of management challenges.
In the following categories, cloud-management systems and instruments should
be able to have minimum functionality.
Service request: receiving and fulfilling user requests to access and
deploy cloud services.
Cost management and optimization: Cloud spending monitors and
accurate sizes and aligns resources and efficiency with real demand.
Security and compliance: handling cloud providers' role-based access
and implementing security settings.
Inventory and classification: discover and maintain pre-existing cloud
infrastructure in the brownfield plus track and handle modifications.
Service level agreements in Cloud computing
A Service Level Agreement (SLA) is the bond for performance negotiated between the cloud services
provider and the client. Earlier, in cloud computing all Service Level Agreements were negotiated between a
client and the service consumer. Nowadays, with the initiation of large utility-like cloud computing
providers, most Service Level Agreements are standardized until a client becomes a large consumer of cloud
services. Service level agreements are also defined at different levels which are mentioned below:
2
, Customer-based SLA
Service-based SLA
Multilevel SLA
Few Service Level Agreements are enforceable as contracts, but mostly are agreements or contracts which
are more along the lines of an Operating Level Agreement (OLA) and may not have the restriction of law. It
is fine to have an attorney review the documents before making a major agreement to the cloud service
provider. Service Level Agreements usually specify some parameters which are mentioned below:
1. Availability of the Service (uptime)
2. Latency or the response time
3. Service components reliability
4. Each party accountability
5. Warranties
In any case, if a cloud service provider fails to meet the stated targets of minimums then the provider has to
pay the penalty to the cloud service consumer as per the agreement. So, Service Level Agreements are like
insurance policies in which the corporation has to pay as per the agreements if any casualty occurs.
Microsoft publishes the Service Level Agreements linked with the Windows Azure Platform components,
which is demonstrative of industry practice for cloud service vendors. Each individual component has its
own Service Level Agreements. Below are two major Service Level Agreements (SLA) described:
1. Windows Azure SLA – Window Azure has different SLA’s for compute and storage. For
compute, there is a guarantee that when a client deploys two or more role instances in
separate fault and upgrade domains, client’s internet facing roles will have external
connectivity minimum 99.95% of the time. Moreover, all of the role instances of the client
are monitored and there is guarantee of detection 99.9% of the time when a role
instance’s process is not runs and initiates properly.
2. SQL Azure SLA – SQL Azure clients will have connectivity between the database and
internet gateway of SQL Azure. SQL Azure will handle a “Monthly Availability” of 99.9%
within a month. Monthly Availability Proportion for a particular tenant database is the ratio
of the time the database was available to customers to the total time in a month. Time is
measured in some intervals of minutes in a 30-day monthly cycle. Availability is always
remunerated for a complete month. A portion of time is marked as unavailable if the
customer’s attempts to connect to a database are denied by the SQL Azure gateway.
Service Level Agreements are based on the usage model. Frequently, cloud providers charge their pay-as-
per-use resources at a premium and deploy standards Service Level Agreements only for that purpose.
Clients can also subscribe at different levels that guarantees access to a particular amount of purchased
resources. The Service Level Agreements (SLAs) attached to a subscription many times offer various terms
and conditions. If client requires access to a particular level of resources, then the client need to subscribe to
a service. A usage model may not deliver that level of access under peak load condition.
3
, SLA Lifecycle
Steps in SLA Lifecycle
1. Discover service provider: This step involves identifying a service provider that can
meet the needs of the organization and has the capability to provide the required service.
This can be done through research, requesting proposals, or reaching out to vendors.
2. Define SLA: In this step, the service level requirements are defined and agreed upon
between the service provider and the organization. This includes defining the service level
objectives, metrics, and targets that will be used to measure the performance of the
service provider.
3. Establish Agreement: After the service level requirements have been defined, an
agreement is established between the organization and the service provider outlining the
terms and conditions of the service. This agreement should include the SLA, any
penalties for non-compliance, and the process for monitoring and reporting on the service
level objectives.
4. Monitor SLA violation: This step involves regularly monitoring the service level
objectives to ensure that the service provider is meeting their commitments. If any
violations are identified, they should be reported and addressed in a timely manner.
5. Terminate SLA: If the service provider is unable to meet the service level objectives, or if
the organization is not satisfied with the service provided, the SLA can be terminated.
This can be done through mutual agreement or through the enforcement of penalties for
non-compliance.
4
Cloud Service Management
The management of cloud infrastructure products and services is cloud
management. Public clouds are operated by public cloud service providers,
which provide the servers, storage, networking and data centre operations of
the public cloud environment. With a third-party cloud management tool, users
can also choose to manage their public cloud services.
Public cloud service users can typically choose from three categories of specific
cloud provisioning:
User self-provisioning: Users, usually via a web form or console
interface, buy cloud services directly from the provider. On a per-
transaction basis, the client pays.
Advanced provisioning: A pre-determined sum of services scheduled in
advance of operation is contracted in advance by customers. A flat fee or
a monthly fee is charged by the consumer.
Dynamic provisioning: When the client requires them, the provider
allocates resources, and then decommissions them when they are no
longer required. On a pay-per-use basis, the client is paid.
,The purpose and scope of the management of cloud services are listed below:
Purpose: Establish suitable techniques for managing and running cloud-
based services. Insert cloud service management techniques into current
frameworks for IT creation and support.
Scope: Oversight of cloud-based service design, development and
change. Cloud-based service management and operation.
Characteristics of Cloud service
Management
In a design for handling cloud environments, cloud management incorporates
applications and technologies. With a range of cloud management platforms
and instruments, software developers have responded to the management
challenges of cloud computing. These solutions include native tools provided by
public cloud providers, as well as third-party tools designed by various cloud
providers to provide consistent functionality. With access to various native
features within individual cloud platforms, administrators must balance the
conflicting requirements of efficient consistency across various cloud platforms.
The need for transparent cross-platform management is motivated by
increasing public cloud adoption and increased multi-cloud use. For those
technical professionals responsible for maintaining IT systems and facilities, the
rapid adoption of cloud services presents a new set of management challenges.
In the following categories, cloud-management systems and instruments should
be able to have minimum functionality.
Service request: receiving and fulfilling user requests to access and
deploy cloud services.
Cost management and optimization: Cloud spending monitors and
accurate sizes and aligns resources and efficiency with real demand.
Security and compliance: handling cloud providers' role-based access
and implementing security settings.
Inventory and classification: discover and maintain pre-existing cloud
infrastructure in the brownfield plus track and handle modifications.
Service level agreements in Cloud computing
A Service Level Agreement (SLA) is the bond for performance negotiated between the cloud services
provider and the client. Earlier, in cloud computing all Service Level Agreements were negotiated between a
client and the service consumer. Nowadays, with the initiation of large utility-like cloud computing
providers, most Service Level Agreements are standardized until a client becomes a large consumer of cloud
services. Service level agreements are also defined at different levels which are mentioned below:
2
, Customer-based SLA
Service-based SLA
Multilevel SLA
Few Service Level Agreements are enforceable as contracts, but mostly are agreements or contracts which
are more along the lines of an Operating Level Agreement (OLA) and may not have the restriction of law. It
is fine to have an attorney review the documents before making a major agreement to the cloud service
provider. Service Level Agreements usually specify some parameters which are mentioned below:
1. Availability of the Service (uptime)
2. Latency or the response time
3. Service components reliability
4. Each party accountability
5. Warranties
In any case, if a cloud service provider fails to meet the stated targets of minimums then the provider has to
pay the penalty to the cloud service consumer as per the agreement. So, Service Level Agreements are like
insurance policies in which the corporation has to pay as per the agreements if any casualty occurs.
Microsoft publishes the Service Level Agreements linked with the Windows Azure Platform components,
which is demonstrative of industry practice for cloud service vendors. Each individual component has its
own Service Level Agreements. Below are two major Service Level Agreements (SLA) described:
1. Windows Azure SLA – Window Azure has different SLA’s for compute and storage. For
compute, there is a guarantee that when a client deploys two or more role instances in
separate fault and upgrade domains, client’s internet facing roles will have external
connectivity minimum 99.95% of the time. Moreover, all of the role instances of the client
are monitored and there is guarantee of detection 99.9% of the time when a role
instance’s process is not runs and initiates properly.
2. SQL Azure SLA – SQL Azure clients will have connectivity between the database and
internet gateway of SQL Azure. SQL Azure will handle a “Monthly Availability” of 99.9%
within a month. Monthly Availability Proportion for a particular tenant database is the ratio
of the time the database was available to customers to the total time in a month. Time is
measured in some intervals of minutes in a 30-day monthly cycle. Availability is always
remunerated for a complete month. A portion of time is marked as unavailable if the
customer’s attempts to connect to a database are denied by the SQL Azure gateway.
Service Level Agreements are based on the usage model. Frequently, cloud providers charge their pay-as-
per-use resources at a premium and deploy standards Service Level Agreements only for that purpose.
Clients can also subscribe at different levels that guarantees access to a particular amount of purchased
resources. The Service Level Agreements (SLAs) attached to a subscription many times offer various terms
and conditions. If client requires access to a particular level of resources, then the client need to subscribe to
a service. A usage model may not deliver that level of access under peak load condition.
3
, SLA Lifecycle
Steps in SLA Lifecycle
1. Discover service provider: This step involves identifying a service provider that can
meet the needs of the organization and has the capability to provide the required service.
This can be done through research, requesting proposals, or reaching out to vendors.
2. Define SLA: In this step, the service level requirements are defined and agreed upon
between the service provider and the organization. This includes defining the service level
objectives, metrics, and targets that will be used to measure the performance of the
service provider.
3. Establish Agreement: After the service level requirements have been defined, an
agreement is established between the organization and the service provider outlining the
terms and conditions of the service. This agreement should include the SLA, any
penalties for non-compliance, and the process for monitoring and reporting on the service
level objectives.
4. Monitor SLA violation: This step involves regularly monitoring the service level
objectives to ensure that the service provider is meeting their commitments. If any
violations are identified, they should be reported and addressed in a timely manner.
5. Terminate SLA: If the service provider is unable to meet the service level objectives, or if
the organization is not satisfied with the service provided, the SLA can be terminated.
This can be done through mutual agreement or through the enforcement of penalties for
non-compliance.
4
