Cloud Management in the Cloud Computing.ppt

Cloud management in cloud computing involves the administration and control of cloud environments, ensuring the efficient use of resources, secure operations, cost optimization, and compliance with regulatory standards. As businesses increasingly migrate to the cloud to take advantage of scalability, flexibility, and cost savings, effective cloud management becomes critical to ensuring the sustainability of cloud infrastructure.

### Key Aspects of Cloud Management

1. **Resource Allocation and Optimization:**
Managing cloud resources effectively involves the dynamic allocation of resources such as CPU, memory, and storage based on workload demands. Automated scaling mechanisms can be employed to adjust resources in real-time to prevent over or under-utilization. Proper resource management helps in reducing wastage and improving the overall performance of applications running on the cloud.

2. **Performance Monitoring and Analytics:**
Continuous monitoring of the cloud infrastructure is essential for ensuring optimal performance and availability of services. Cloud monitoring tools, such as AWS CloudWatch, Microsoft Azure Monitor, and Google Cloud Operations Suite, help track key performance metrics like CPU utilization, memory consumption, network traffic, and uptime. Performance analytics can provide insights into areas of improvement, and alert systems notify administrators in case of anomalies or failures.

3. **Security and Data Privacy:**
Security is a critical aspect of cloud management, as cloud environments can be vulnerable to various cyber threats. Security management involves implementing encryption protocols, securing data in transit and at rest, enforcing identity and access management (IAM) policies, and regular security audits to ensure that the cloud environment remains protected against unauthorized access or data breaches. Multi-factor authentication (MFA), role-based access control (RBAC), and the principle of least privilege are some of the measures employed to enhance security.

4. **Automation and Orchestration:**
Automation simplifies repetitive tasks such as backups, scaling, patch management, and disaster recovery. Cloud automation tools streamline processes, reducing human intervention and errors. Orchestration further extends automation by managing complex workflows across multiple cloud services, often across hybrid or multi-cloud environments. For example, in a multi-cloud setup, orchestration tools can automatically deploy applications across multiple cloud platforms (AWS, Azure, Google Cloud) while maintaining consistent configurations and policies.

5. **Cost Management and Optimization:**

1. Cloud Management in Cloud Computing

Cloud computing management is maintaining and controlling the cloud services and
resources be it public, private or hybrid. Some of its aspects include load balancing,
performance, storage, backups, capacity, deployment etc. To do so a cloud managing
personnel needs full access to all the functionality of resources in the cloud. Different
software products and technologies are combined to provide a cohesive cloud
management strategy and process.

Need of Cloud Management :

Cloud is nowadays preferred by huge organizations as their primary data storage. A
small downtime or an error can cause a great deal of loss and inconvenience for the
organizations. So as to design, handle and maintain a cloud computing service specific
members are responsible who make sure things work out as supposed and all arising
issues are addressed.

2. Cloud Management Tasks :
The below figure represents different cloud management
tasks :

3. UNIT – III (Service Management and Resource Management in Cloud computing)

3.1 CLOUD SERVICE MANAGEMENT

3.1.1 SLO (SERVICE LEVEL OBJECTIVES):

Whenever a Consumer – Provider scenario is in picture, and services are metered or paid services then
service management is a major and important role player.

When services are metered services then there should be contract or agreement from Provider and
Consumer sides so as to agree on certain points, pricing measures, quality of services etc.

The SLA (Service Level Agreement) served this purpose in cloud computing. In SLA, pricing of services,
service availability factor, other quality related factors are included. Service level agreements play an
important role to guide outsourcing vendors to understand customers’ business need. Normally
outsourcing vendors have to ensure that the agreed service level agreements are met. Therefore, it is
necessary to be able to effectively develop service level agreements to avoid resource failures.

There is no as such fixed format for this SLA, but it is a signed document or a formal contract between
service provider and a consumer

4. 
3.1 CLOUD SERVICE MANAGEMENT

3.1.1 SLO (SERVICE LEVEL OBJECTIVES) (CONTINUED…) :

Why SLA is needed?

The SLA helps to develop trust to SP(Service provider)

Helps SP to understand business requirements of consumers

Helps consumers to select appropriate SP by comparing their SLAs

Bound SP to provide the promised services

Helps to maintain quality of services

Helps consumer and SP for billing of services

SLA contains SLO (Service Level Objectives) :

Services in SLA are objectively measurable conditions and hence every SLA

SLOs helps to tailor product/ user/ requirement specific goals and to target
realistic performance.

A Service Level Objective (SLO) serves as a benchmark for indicators,
parameters, or metrics defined with specific service level targets. The objectives
may be an optimal range or a specific value for each service function or
process that constitutes a cloud service.

5. 
3.1 CLOUD SERVICE MANAGEMENT

3.1.1 SLO (SERVICE LEVEL OBJECTIVES) (CONTINUED…) :

The SLO is measurable characteristic.

It consists of shared performance goals in it’s structure.

E.g. The requirement availability for the peak time is 90%, then the allowed down-time per
year could be 36.5 days OR 72 hours per months OR 16.8 hours per week

The SLA (Service Level Agreement): Life-cycle

There are 3 major phases – ACQUISITION, OPERATION, TERMINATION

[A] Cloud service lifecycle: Acquisition

A prospective cloud customer can use service offerings published by the cloud service
provider to check whether it meets her/his requirements, for example, security, personal
data protection, performance etc., and see how one offering compares with another in
the market. Why is it important? This phase is crucial for establishing an SLA between the
cloud customer and the cloud service provider

6. 
3.1 CLOUD SERVICE MANAGEMENT

3.1.2 SLA(SERVICE LEVEL OBJECTIVES) (CONTINUED…) :

[A] ACQUISITION -

[A.1] Assessment – Any relationship starts with pre-assessing what one would like,
why, when and with whom (for instance one or more CSPs), so does the first
Cloud SLA lifecycle phase, Assessment. This includes for instance doing market
intelligence, checking specific needs, offerings, CSPs, performance of CSPs and
setting up a business case

[A.2] Preparation – This second Cloud SLA lifecycle phase, includes for instance,
the first contact and conversation with possible CSPs, further assessment, pre-
evaluation and fine-tuning goals and assumptions

[A.3] Negotiation and contracting - This phase can include preparing for
negotiation and the actual negotiation and deal making with one or more CSPs,
including sharing concerns, discuss in-scope and out-of-scope (cloud) services,
debating about trade-offs and finding common grounds, reaching agreement,
double-checking needs, goals and assumptions, and of course documenting
the contractual arrangements, and signing thereof

7. 
3.1 CLOUD SERVICE MANAGEMENT

3.1.2 SLA(SERVICE LEVEL OBJECTIVES) (CONTINUED…) :

[B] OPERATION -

[B.1] Execution and Operation– This phase includes the actual start of setting up the
cloud services, populating the respective cloud service with relevant data, on
boarding and training users, setting up communication channels and further
operational activities while using the respective cloud services

[B.2] Updates and amendments – This phase includes updated or otherwise amended
needs, goals and assumptions by the Cloud Service Customer during the term of the
ongoing cloud services arrangements, as well as improved or added cloud services
by the CSP there under. It also includes optimization of the respective cloud services
by CSP as per (contractual or other) non-compliance, breaches and other incidents
during that term

[B.3] Escalation - This phase deals with contractual or other) non-compliance,
breaches and other incidents during the term of the ongoing cloud services
arrangements that have resulted in a dispute that needs escalation, (perhaps even
litigation as a last resort), negotiation and resolution, either by parties themselves or by
arbitration, court or otherwise

8. 
3.1 CLOUD SERVICE MANAGEMENT

3.1.2 SLA(SERVICE LEVEL OBJECTIVES) (CONTINUED…) :

[C] TERMINATION -

[C.1] Termination and consequences of termination – This phase deals with the
end of the relationship between CSP and CSC, including the end of the legal
relationship even though the latter will generally continue for several years after
any termination as per mandatory laws and legislation. This last phase for
instance includes the assessment of alternatives, settlement and termination
arrangements, cloud services transition projects and services, data export,
customer and (end)use care and diligence, and adequate data deletion

14. 3.1.2 Types of SLA
 It consists details of type and quality of services that has been
agreed upon used for individual customer and it consists of all
relevant services that she/he may need into a single contract.
Customer based
 It consists of
one identical
type of
service
for all of its
customers
It is more
straightforwa
rd and
based upon
standards
Service based
 all
gen
eral
issu
es
are
cov
ere
d
her
e,
whic
h
are
ap
plic
abl
e to
enti
re
org
aniz
atio
n.
It
has
3
sub
-
cat
eg
orie
s:
Cor
por
ate
lev
el,
cus
tom
er
lev
el,

serv
ice
lev
el.
Multi-level

15. )
 No frequent updates are applicable to end-
users
(a) Corporate
Level
Applicable to specific group of customers
(less usage )
(b) Customer
Level
 all
att
rib
ut
es
ar
e
ap
pli
ca
bl
e
to
sp
ec
ific
cu
sto
m
er
gr
ou
p

( i
ns
ur
an
ce
ser
vic
e)-
>
s/
w
+
A
pp
s
=>
Cl
ou
d
(M
or
e
us
ag
e)
(c) Service Level
3.1.2 Types of SLA (Multilevel

16. 
3.1.2 SLA Management in Cloud

Service Level Management, or SLM, is defined as being “responsible for ensuring
that all its service management processes, operational level agreements, and
underpinning contracts, are appropriate for the agreed-upon service level
targets. SLM monitors and reports on service levels, and holds regular customer
reviews.”

In other words, the key criteria for any information to be contained within a
Service Level Agreement (SLA) are that it must be measurable, with all language
used is clear and concise in order to aid understanding.

Understanding SLM is one of the steps in getting an ITIL certification. The IT
Infrastructure Library (ITIL) certification is a globally recognized IT service
management certification, distributed by Axelos. There have been several
versions of ITIL, with the latest one being ITIL v4 2018. The ITIL
Certification course is an entry-level qualification in the field of IT service
management, granting Foundation certification to those who complete the
studies.

17. 
.1.2 SLA Sample format –

A typical SLA document may include,

An introduction to the SLA, what does this agreement propose

A Service description, what service this SLA supports, and details of the
service

Mutual responsibilities, who’s responsible for what part of the service

Scope of SLA

Applicable service hours, from what time till what time is the service
available according to the agreement

Service availability, how much is the service available during the service
window and outside of the service window

Reliability

Customer support arrangements

Contact points and escalation; a communication matrix

Service performance

Security

Costs and charging method used

18. 
3.1.2 SLA Management and mitigation example –

Suppose, a cloud (CSP – XYZ) guarantees service availability for 99% of
time. Say an customer – c1 application run on cloud for 15 hours per
day(for 30 days in a month). At the end of the month it is found that the
service outage was total 10.75 hours.

Can we say it is SLA violation / violation of initial availability assurance?

% availability = {1 – (Outage duration / available duration)} * 100

25. 
.1.3 Cloud Economics –

Economic point of view –

Common infrastructure (CSP -> )

Location independence

Online connectivity

Utility pricing (pay per use)

On-demand resources (Elasticity)(4/5) (++ 25) (Scalability)

Whether it is beneficial to deploy on a cloud or not ?

The cloud pricing is function of time and hence always dependent on time
period over which service is consumed.

Financial feasibility for cloud use

26. What is Cloud Economics?
 
Cloud economics is the study of the economic and cost benefits of cloud computing. It examines the
business and technology aspects of cloud computing services, such as IaaS, PaaS, SaaS.
 
It also looks at the financial implications of cloud computing, including the cost-effectiveness of
cloud-based services, the cost savings associated with cloud computing, and the potential for
scalability and flexibility. Finally, it requires comprehending the cloud’s total cost of ownership
(TCO), its advantages over on-premises models, and cost-saving techniques to maximize the return
on your cloud investment.
Benefits Of Cloud Economics
Cost Savings:
 
Cloud economics makes it possible to reduce costs through more efficient resource
utilization and economies of scale. Cloud services can be scaled up or down as needed, and users
only pay for what they use. This helps organizations optimize their infrastructure expenses and trim
IT budgets.
Increased Efficiency:
 
Cloud economics enables businesses to save time and money by eliminating
the need for manual tasks associated with traditional Infrastructure. Automation and virtualization
can reduce manual processes, resulting in increased efficiency.
Flexibility:
 
Cloud economics makes it possible to quickly scale up or down based on the changing
needs of the business. This can help organizations remain agile and responsive and better meet
customer demands.

27. Key Considerations Of Cloud Economics

Cloud Total Cost of Ownership (TCO): 

Cloud TCO measures the total financial cost of a cloud computing solution, including the initial capital
expenditure (CAPEX) and the ongoing operational expenditure (OPEX). In addition, it considers both
the direct and indirect costs associated with deploying and running a cloud solution. This includes
hardware, software, licenses, maintenance, bandwidth, storage, and other related costs.
 

CAPEX to OPEX Switch: 

The CAPEX to OPEX switch is a common strategy for moving from on-premises services to cloud
computing. It involves shifting from a CAPEX model, where upfront capital expenditure is required to
purchase hardware and software, to an OPEX model, where operational expenditure is incurred for
the ongoing usage of the cloud. This switch can help reduce the upfront cost of cloud adoption and
allow organizations to benefit from the scalability and agility ( quickly develop, test, and launch
applications in a cloud-based environment) of cloud services.

On-Demand Pricing:
 

On-demand pricing is a pricing model in which customers pay only for the resources and services they
use. This model is popular in cloud computing, where costs depend on the amount and type of usage.
With on-demand pricing, customers can scale their usage up or down as needed, allowing them to
adjust their costs to match their needs quickly. Thus, your costs become elastic. This implies that
they could soon become out of hand if you don’t frequently monitor your cloud costs and make data-
driven decisions.

30. 
3.2 Cloud Resource Management –

Resources in cloud

Types of Resources in Cloud –

Physical Resources

Logical Resources

Cloud Resource Management –

Requires complex policies and decisions for multi-objective optimization.

It is challenging - the complexity of the system makes it impossible to have
accurate global state information.

Affected by unpredictable interactions with the environment, e.g., system
failures, attacks.

Cloud service providers are faced with large fluctuating loads which challenge
the claim of cloud elasticity. / load balancing

32. 
3.2 Cloud Resource Management –

Cloud resource management (CRM) policies – policy -broad guidelines/ statements to
achieve particular objective(s)

1.Admission control prevent the system from accepting workload in violation of high-level
system policies.

[a] for login –

[b] for task allocation to proc

[c] cloud interface

2.Capacity allocation allocate resources for individual activations of a service.

3.Load balancing distribute the workload evenly among the servers.

4.Energy optimization minimization of energy consumption.

5. Quality of service (QoS) guarantees ability to satisfy timing or other conditions specified by
a Service Level Agreement. (assurance of functionalities / standards / certifications)