CLOUD INFRASTRUCTURE & CLOUD

Unit-4
RESOURCE MANAGEMENT
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

➢Cloud Computing , which is one of the demanding technology of the current

time and which is giving a new shape to every organization by providing on
demand virtualized services/resources.
➢ Starting from small to medium and medium to large, every organization use
cloud computing services for storing information and accessing it from
anywhere and any time only with the help of internet.
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

➢Transparency, scalability, security and intelligent monitoring are some of the

most important constraints which every cloud infrastructure should experience.
➢Current research on other important constraints is helping cloud computing
system to come up with new features and strategies with a great capability of
providing more advanced cloud solutions.
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

Cloud Computing Architecture :

The cloud architecture is divided into 2 parts i.e.
1.Frontend
2.Backend
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

Architecture of cloud computing is the combination of both SOA (Service Oriented

Architecture) and EDA (Event Driven Architecture).
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

1. Frontend :

Frontend of the cloud architecture refers to the client side of cloud computing system.
Means it contains all the user interfaces and applications which are used by the client to
access the cloud computing services/resources. For example, use of a web browser to
access the cloud platform.

•Client Infrastructure – Client Infrastructure is a part of the frontend component. It

contains the applications and user interfaces which are required to access the cloud
platform.
•In other words, it provides a GUI( Graphical User Interface ) to interact with the cloud.
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

2. Backend :
Backend refers to the cloud itself which is used by the service provider. It contains the
resources as well as manages the resources and provides security mechanisms. Along
with this, it includes huge storage, virtual applications, virtual machines, traffic control
mechanisms, deployment models, etc.

Application –
Application in backend refers to a software or platform to which client accesses. Means it
provides the service in backend as per the client requirement.

Service –
Service in backend refers to the major three types of cloud based services like SaaS, PaaS
and IaaS. Also manages which type of service the user accesses.
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

Runtime Cloud-
Runtime cloud in backend provides the execution and Runtime platform/environment to the
Virtual machine.
Storage –
Storage in backend provides flexible and scalable storage service and management of stored
data.
Infrastructure –
Cloud Infrastructure in backend refers to the hardware and software components of cloud
like it includes servers, storage, network devices, virtualization software etc.
Management –
Management in backend refers to management of backend components like application,
service, runtime cloud, storage, infrastructure, and other security mechanisms etc.
ARCHITECTURAL DESIGN OF STORAGE AND COMPUTE CLOUD

Security –
Security in backend refers to implementation of different security mechanisms in the
backend for secure cloud resources, systems, files, and infrastructure to end-users.
Internet –
Internet connection acts as the medium or a bridge between frontend and backend and
establishes the interaction and communication between frontend and backend.
Database– Database in backend refers to provide database for storing structured data, such
as SQL and NOSQL databases. Example of Databases services include Amazon RDS, Microsoft
Azure SQL database and Google CLoud SQL.
Networking– Networking in backend services that provide networking infrastructure for
application in the cloud, such as load balancing, DNS and virtual private networks.
Analytics– Analytics in backend service that provides analytics capabillities for data in the
cloud, such as warehousing, bussness intellegence and machine learning.
BENEFITS OF CLOUD COMPUTING ARCHITECTURE :

❖ Makes overall cloud computing system simpler.

❖ Improves data processing requirements.
❖ Helps in providing high security.
❖ Makes it more modularized.
❖ Results in better disaster recovery.
❖ Gives good user accessibility.
❖ Reduces IT operating costs.
❖ Provides high level reliability.
❖ Scalability.
LAYERED CLOUD ARCHITECTURE DEVELOPMENT :

➢ Layered cloud architecture development refers to the process of designing and implementing
a cloud computing infrastructure with multiple layers of abstraction and functionality.

➢ This approach helps in organizing and managing various components of the cloud
environment to optimize performance, scalability, and security.
LAYERED CLOUD ARCHITECTURE DEVELOPMENT :

❑ Physical Infrastructure Layer:

❑ This is the foundational layer that includes the actual hardware components, such as
servers, storage devices, and networking equipment. In a cloud context, this layer may
involve data centers and server farms.
❑ Network Layer:
❑ The network layer is responsible for managing the communication between different
components within the cloud infrastructure. It includes elements like routers, switches,
load balancers, and firewalls.
❑ Compute Layer:
❑ This layer involves the virtualization of resources, including virtual machines (VMs) or
containers. It allows for the efficient allocation and management of computing power to
run applications and services.
LAYERED CLOUD ARCHITECTURE DEVELOPMENT :

❑ Storage Layer:
❑ The storage layer deals with data storage and retrieval. It includes various storage
solutions such as object storage, block storage, and file storage. This layer ensures data
durability, availability, and scalability.
❑ Platform Layer:
❑ The platform layer provides tools and services that simplify the development,
deployment, and management of applications. This may include platform-as-a-service
(PaaS) offerings, development frameworks, and application hosting environments.
❑ Service Layer (SaaS, PaaS, IaaS):
❑ This layer offers cloud services to end-users or developers. It includes Software-as-a-
Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS). SaaS
delivers software applications over the internet, PaaS provides a platform for application
development, and IaaS offers virtualized computing resources.
LAYERED CLOUD ARCHITECTURE DEVELOPMENT :

❑ Identity and Access Management (IAM) Layer:

❑ IAM is crucial for securing the cloud environment. This layer manages user identities,
permissions, and access controls, ensuring that only authorized users can interact with
resources.
❑ Security and Compliance Layer:
❑ Security is a critical consideration in cloud architecture. This layer includes features such
as encryption, intrusion detection/prevention, security information and event
management (SIEM), and compliance monitoring.
❑ Monitoring and Management Layer:
❑ This layer involves tools and services for monitoring the performance, health, and
utilization of resources. It includes logging, monitoring, and management solutions to
ensure optimal operation and to troubleshoot issues.
LAYERED CLOUD ARCHITECTURE DEVELOPMENT :

❑ Automation Layer:
❑ Automation is essential for efficient cloud management. This layer includes tools for
orchestrating and automating tasks, such as provisioning and scaling resources
dynamically.
❑ Governance and Compliance Layer:
❑ This layer focuses on enforcing policies, managing compliance, and ensuring that the
cloud environment adheres to regulatory requirements and organizational standards.
❑ Integration Layer:
❑ The integration layer facilitates the seamless connection of different components, both
within the cloud environment and with external systems. It includes APIs, middleware,
and integration services.
DESIGN CHALLENGES :

❑ Designing a robust and efficient cloud architecture comes with its own set of challenges.

❑ These challenges need to be carefully considered and addressed to ensure that the cloud
environment meets the requirements of scalability, performance, security, and reliability.
DESIGN CHALLENGES :

➢ Scalability:
➢ Challenge: Ensuring that the cloud architecture can scale horizontally to handle
increasing workloads and demand.
➢ Solution: Implementing auto-scaling mechanisms, load balancing, and designing
applications for distributed architectures.
➢ Security:
➢ Challenge: Protecting data, applications, and infrastructure from security threats and
unauthorized access.
➢ Solution: Implementing strong identity and access management, encryption, network
security measures, and regularly updating security policies.
➢ Data Management:
➢ Challenge: Efficiently managing and storing large volumes of data while ensuring data
integrity and availability.
➢ Solution: Implementing effective data storage solutions, considering data lifecycle
management, and leveraging appropriate database technologies.
DESIGN CHALLENGES :

➢ Compliance and Legal Issues:

➢ Challenge: Adhering to regulatory requirements and legal considerations specific to the
industry and geographic location.
➢ Solution: Regularly auditing and updating policies to ensure compliance, collaborating
with legal experts, and choosing cloud providers with strong compliance frameworks.
➢ Interoperability and Integration:
➢ Challenge: Ensuring seamless integration with existing on-premises systems and other
cloud services.
➢ Solution: Using standardized APIs, middleware, and integration tools to facilitate
interoperability, and designing systems with modularity in mind.
➢ Reliability and High Availability:
➢ Challenge: Ensuring that the cloud architecture is reliable and available even in the face
of failures or disruptions.
➢ Solution: Employing redundancy, geographic distribution, and fault-tolerant design
principles. Implementing backup and disaster recovery plans.
DESIGN CHALLENGES :

➢ Cost Management:
➢ Challenge: Controlling and optimizing costs associated with cloud resources.
➢ Solution: Implementing cost monitoring, utilizing resource auto-scaling efficiently,
optimizing usage, and leveraging cost-effective pricing models.
➢ Performance Optimization:
➢ Challenge: Achieving optimal performance for applications and services running in the
cloud.
➢ Solution: Fine-tuning configurations, optimizing code, leveraging content delivery
networks (CDNs), and using performance monitoring tools.
➢ Network Complexity:
➢ Challenge: Managing the complexity of cloud networks, especially in a hybrid or multi-
cloud environment.
➢ Solution: Implementing well-defined network architectures, utilizing software-defined
networking (SDN), and employing network monitoring and management tools.
DESIGN CHALLENGES :

➢ Cost Management:
➢ Challenge: Controlling and optimizing costs associated with cloud resources.
➢ Solution: Implementing cost monitoring, utilizing resource auto-scaling efficiently,
optimizing usage, and leveraging cost-effective pricing models.
➢ Performance Optimization:
➢ Challenge: Achieving optimal performance for applications and services running in the
cloud.
➢ Solution: Fine-tuning configurations, optimizing code, leveraging content delivery
networks (CDNs), and using performance monitoring tools.
➢ Network Complexity:
➢ Challenge: Managing the complexity of cloud networks, especially in a hybrid or multi-
cloud environment.
➢ Solution: Implementing well-defined network architectures, utilizing software-defined
networking (SDN), and employing network monitoring and management tools.
DESIGN CHALLENGES :

➢ Cost Management:
➢ Challenge: Controlling and optimizing costs associated with cloud resources.
➢ Solution: Implementing cost monitoring, utilizing resource auto-scaling efficiently,
optimizing usage, and leveraging cost-effective pricing models.
➢ Performance Optimization:
➢ Challenge: Achieving optimal performance for applications and services running in the
cloud.
➢ Solution: Fine-tuning configurations, optimizing code, leveraging content delivery
networks (CDNs), and using performance monitoring tools.
➢ Network Complexity:
➢ Challenge: Managing the complexity of cloud networks, especially in a hybrid or multi-
cloud environment.
➢ Solution: Implementing well-defined network architectures, utilizing software-defined
networking (SDN), and employing network monitoring and management tools.
INTER CLOUD RESOURCE MANAGEMENT :

➢ “inter-cloud” or “cloud of clouds.” combining numerous various separate clouds

into a single fluid mass for on-demand operations

➢ Simply put, the inter-cloud would ensure that a cloud could utilize resources
outside of its range using current agreements with other cloud service providers.
There are limits to the physical resources and the geographic reach of any one
cloud.
NEED OF INTER-CLOUD :

Due to their Physical Resource limits, Clouds have certain Drawbacks:

❖ When a cloud’s computational and storage capacity is completely depleted, it is

unable to serve its customers.

❖ The Inter-Cloud addresses these circumstances when one cloud would access the
computing, storage, or any other resource of the infrastructures of other clouds.
NEED OF INTER-CLOUD :

Due to their Physical Resource limits, Clouds have certain Drawbacks:

❖ When a cloud’s computational and storage capacity is completely exhausted, it is

unable to serve its customers.

❖ The Inter-Cloud addresses these circumstances when one cloud would access the
computing, storage, or any other resource of the infrastructures of other clouds.
BENEFITS OF INTER-CLOUD :

✓ Avoiding vendor lock-in to the cloud client

✓ Having access to a variety of geographical locations, as well as enhanced

application resiliency.

✓ Better service level agreements (SLAs) to the cloud client.

✓ Expand-on-demand is an advantage for the cloud provider.

TYPES OF INTER-CLOUD :

1.Federation Clouds:

➢ A federation cloud is a kind of inter-cloud where several cloud service providers willingly link
their cloud infrastructures together to exchange resources.

➢ Cloud service providers in the federation trade resources in an open manner.

➢ With the aid of this inter-cloud technology, private cloud portfolios, as well as government
clouds (those utilized and owned by non-profits or the government), can cooperate.
TYPES OF INTER-CLOUD :

2.Multi-Cloud:

➢ A client or service makes use of numerous independent clouds in a multi-cloud.

➢ A multi-cloud ecosystem lacks voluntarily shared infrastructure across cloud service

providers. It is the client’s or their agents’ obligation to manage resource supply and
scheduling.

➢ This strategy is utilized to use assets from both public and private cloud portfolios. These
multi-cloud kinds include services and libraries.
TOPOLOGIES USED IN INTER-CLOUD ARCHITECTURE :

1. Peer-to-Peer Inter-Cloud Federation:

❖ Clouds work together directly, but they may also

utilize distributed entities as directories or
brokers. Clouds communicate and engage in
direct negotiation without the use of
intermediaries. The peer-to-peer federation
intercloud projects are RESERVOIR (Resources
and Services Virtualization without Barriers
Project).
TOPOLOGIES USED IN INTER-CLOUD ARCHITECTURE :

2. Centralized Inter-Cloud Federation:

➢ In the cloud, resource sharing is carried out or

facilitated by a central body. The central entity
serves as a registry for the available cloud
resources. The inter-cloud initiatives Dynamic
Cloud Collaboration (DCC), and Federated Cloud
Management leverage centralized inter-cloud
federation.
TOPOLOGIES USED IN INTER-CLOUD ARCHITECTURE :

3. Multi-Cloud Service:

➢ Clients use a service to access various clouds.

The cloud client hosts a service either inside or
externally. The services include elements for
brokers. The inter-cloud initiatives OPTIMUS,
contrail, MOSAIC, STRATOS, and commercial
cloud management solutions leverage multi-
cloud services.
TOPOLOGIES USED IN INTER-CLOUD ARCHITECTURE :

4. Multi-Cloud Libraries:

➢ Clients use a uniform cloud API as a library to

create their own brokers. Inter clouds that
employ libraries make it easier to use clouds
consistently. Java library J-clouds, Python library
Apache Lib-Clouds, and Ruby library Apache
Delta-Cloud are a few examples of multiple
multi-cloud libraries.
RESOURCE PROVISIONING :

➢ In traditional computing, whenever a new server (or virtual server) is required to support
certain workload, it takes lots of efforts and time of administrator to install and supply the
server.

➢ Current age computing needs rapid infrastructure provisioning facility to meet the varying
demands of the consumers.

➢ With the emergence of virtualization technology and cloud computing IaaS model, it is now
just a matter of minutes to achieve the same provided required volume of resources are
being available.
RESOURCE PROVISIONING :

➢ Thus, provisioning of a new virtual machine saves lots of time and effort in cloud. One can
create a virtual server through a self-service interface which is considered as one of the
most attractive feature of cloud.

➢ Flexible resource provisioning is a key requirement in cloud computing. To achieve this

flexibility, it is essential to manage the available resources intelligently when required. The
orchestration of resources must be performed in a way so that resources can be
provisioned to applications rapidly and dynamically in a planned manner.
RESOURCE PROVISIONING :THE AUTONOMIC WAY

➢ Resource provisioning in cloud is the allocation of a cloud provider’s resources directly to

the consumers or to the applications.

➢ When a consumer asks for resource, cloud provider must create appropriate number of
virtual machines (VMs) in order to support the demand and should also allocate physical
resources accordingly.

➢ This provisioning is an automated process in cloud which is designed by applying artificial

intelligence and is known as autonomic resource provisioning.
RESOURCE PROVISIONING :THE AUTONOMIC WAY

➢ The purpose of autonomic resource provisioning is to automate the allocation of resources

so that the overall resource demand can be managed efficiently by minimum amount of
resources.

➢ One resource is allotted to different applications or consumers.

➢ This becomes possible since application loads varies with time.

➢ Through autonomic approach, computing resources can be rapidly provisioned and

released with minimal management effort from a shared pool of configurable resources as
on demand.
RESOURCE PROVISIONING : ROLE OF SLA

➢ Consumers typically enter into contract with cloud providers which describes the expected
requirements of computing resource capacity being required for their applications.

➢ This contract is known as service level agreements (SLAs). A cloud provider, after combining
all such SLAs, can plan for the total amount of physical resources they have to keep as
prepared to support all of its consumers so that those can be allocated to users when their
applications would run.

➢ This allocation is done dynamically by some provisioning algorithms that map virtual
machines (VMs) running end-user applications into physical cloud infrastructure (compute
nodes).
RESOURCE PROVISIONING : RESOURCE PROVISIONING APPROACHES

➢ Efficient resource provisioning is a key requirement in cloud computing. Cloud consumers

do not get direct access to physical computing resources.

➢ Physical resources can be assigned to the VMs using two types of provisioning approaches
like static and dynamic.

➢ In static approach, VMs are created with specific volume of resources and the capacity of
the VM does not change in its lifetime.

➢ In dynamic approach, the resource capacity per VM can be adjusted dynamically to match
work-load fluctuations.
RESOURCE PROVISIONING : STATIC APPROACH

➢ Static provisioning is suitable for applications which have predictable and generally
unchanging workload demands. In this approach, once a VM is created it is expected to
run for long time without incurring any further resource allocation decision overhead on
the system. Here, resource-allocation decision is taken only once and that too at the
beginning when user’s application starts running.
RESOURCE PROVISIONING : STATIC APPROACH

➢ Although static provisioning approach does not bring about any runtime overhead it has
major limitations also. This provisioning approach fails to deal with un-anticipated changes
in resource demands. When resource demand crosses the limit specified in SLA document
it causes trouble for the consumers.

➢ Again from provider’s point of view, some resources remain unutilized forever since
provider arranges for sufficient volume of resources to avoid SLA violation. So this method
has drawback from the viewpoint of both provider as well as for consumer.
RESOURCE PROVISIONING : DYNAMIC APPROACH

➢ With dynamic provisioning, the resources are allocated and de-allocated as per
requirement during run-time.

➢ This on-demand resource provisioning provides elasticity to the system. Providers no more
need to keep a certain volume of resources unutilized for each and every system separately,
rather they maintain a common resource pool and allocate resources from that when it is
required.

➢ Resources are removed from VMs when they are no more required and returned to the
pool. With this dynamic approach, the processes of billing also become as pay-per-usage
basis.
RESOURCE PROVISIONING : DYNAMIC APPROACH

➢ Dynamic provisioning technique is more appropriate for cloud computing where

application’s demand for resources is most likely to change or vary during the execution.
But this provisioning approach needs the ability of integrating newly-acquired resources
into the existing infrastructure. This gives provisioning elasticity to the system.

➢ Dynamic provisioning allows system to adapt in changed conditions at the cost of bearing
run-time resource allocation decision overhead.

➢ This overhead leads some amount of delay in system but this can be minimized by putting
upper limit on the complexity of provisioning algorithms.
PLATFORM DEPLOYMENT :

➢ Platform deployment in cloud computing refers to the process of hosting and managing
software applications or platforms on cloud infrastructure instead of on-premises servers.

➢ This deployment model offers numerous advantages, including scalability, flexibility, cost-
effectiveness, and reduced administrative overhead.

➢ Here's an overview of the steps involved in platform deployment in cloud computing:

PLATFORM DEPLOYMENT :

1.Selecting a Cloud Provider: Choose a cloud service provider (CSP) that best fits your
requirements. Major players in the market include Amazon Web Services (AWS),
Microsoft Azure, Google Cloud Platform (GCP), IBM Cloud, and others. Consider factors
such as pricing, availability, security, compliance, and geographic locations of data
centers.

2.Designing the Architecture: Determine the architecture of your platform deployment.

This includes decisions about the type of services to use (e.g., Infrastructure as a Service
(IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS)), the number and
configuration of servers, networking setup, data storage solutions, and security
measures.
PLATFORM DEPLOYMENT :

3.Developing or Migrating Applications: Develop new applications or migrate

existing ones to the cloud platform. Ensure that your applications are designed to
be cloud-native, taking advantage of cloud-specific features like auto-scaling, load
balancing, and distributed computing.

4.Containerization or Virtualization: Containerization technologies like Docker or

virtualization technologies like VMware are often used to package applications and
their dependencies into portable, isolated units. This ensures consistency across
different environments and simplifies deployment.
PLATFORM DEPLOYMENT :

5.Automating Deployment: Use automation tools like Ansible, Chef, Puppet, or Terraform
to automate the deployment process. Infrastructure as Code (IaC) practices enable you to
define your infrastructure in code, making it easier to replicate and manage.

6.Testing: Conduct thorough testing of your platform before deploying it to production.

This includes functional testing, performance testing, security testing, and disaster
recovery testing.

7.Deployment: Once testing is complete, deploy your platform to the cloud environment.
This may involve provisioning virtual machines, containers, databases, networking
components, and other resources as required.
PLATFORM DEPLOYMENT :

8.Monitoring and Management: Implement monitoring and management tools to track

the performance, availability, and security of your platform. Cloud-native monitoring
solutions like AWS CloudWatch, Azure Monitor, or GCP Stackdriver provide insights into
resource utilization, application performance, and potential issues.

9.Scaling: Configure auto-scaling policies to automatically adjust the capacity of your

platform based on demand. This ensures that your applications can handle fluctuations
in traffic without manual intervention.

10.Optimization: Continuously optimize your platform for cost, performance, and

security. This may involve rightsizing instances, optimizing resource utilization,
implementing caching mechanisms, and applying security best practices.
GLOBAL EXCHANGE OF CLOUD RESOURCES :

➢ The global exchange of cloud resources refers to the distribution and sharing of
computing resources, such as storage, processing power, and software
applications, across multiple geographic locations via cloud computing
infrastructure.

➢ This exchange enables organizations to access and utilize computing resources on-
demand without the need for investing in and maintaining physical hardware and
infrastructure.

➢ Key aspects of the global exchange of cloud resources include:

GLOBAL EXCHANGE OF CLOUD RESOURCES :

Geographical Distribution: Cloud computing providers operate data centers in

various regions around the world. This allows organizations to deploy their
applications and store data closer to their end-users, reducing latency and improving
performance.

Scalability: Cloud resources can be scaled up or down according to demand. This

elasticity enables organizations to efficiently manage their computing resources,
ensuring optimal performance while minimizing costs.

Resource Sharing: Cloud providers often utilize virtualization and multi-tenancy

techniques to maximize resource utilization. This means that multiple users or
organizations can share the same physical infrastructure while maintaining isolation
and security.
GLOBAL EXCHANGE OF CLOUD RESOURCES :

➢ Overall, the global exchange of cloud resources enables organizations to leverage the
benefits of cloud computing, including flexibility, scalability, and cost-efficiency,
to support their business operations and innovation initiatives on a global scale.
GLOBAL EXCHANGE OF CLOUD RESOURCES :
GLOBAL EXCHANGE OF CLOUD RESOURCES :

➢ Cloud Exchange (CEx) serves as a market maker, bringing service providers

and users together.

➢ The University of Melbourne proposed it under Intercloud architecture

(Cloudbus). It supports brokering and exchanging cloud resources for scaling
applications across multiple clouds.

➢ It aggregates the infrastructure demands from application brokers and

evaluates them against the available supply. It supports the trading of cloud
services based on competitive economic models such as commodity
markets and auctions.
ADMINISTRATING THE CLOUD :

➢ Cloud management software provides capabilities for managing faults,

configuration, accounting, performance, and security; this is referred to as
FCAPS.

➢ Many products address one or more of these areas, and through network
frameworks, you can access all five areas. Framework products are being
repositioned to work with cloud systems.
ADMINISTRATING THE CLOUD :

➢ The explosive growth in cloud computing services has led many vendors to
rename their products and reposition them to get in on the gold rush in the
clouds.

➢ What was once a network management product is now a cloud management

product.

➢ Nevertheless, this is one area of technology that is very actively funded, comes
replete with interesting startups, has been the focus of several recent strategic
acquisitions, and has resulted in some interesting product alliances.
ADMINISTRATING THE CLOUD :

➢ These fundamental features are offered by traditional network management

systems:

l Administration of resources
l Configuring resources
l Enforcing security
l Monitoring operations
l Optimizing performance
l Policy management
l Performing maintenance
l Provisioning of resources
ADMINISTRATING THE CLOUD :

➢ These fundamental features are offered by traditional network management

systems:

l Administration of resources
l Configuring resources
l Enforcing security
l Monitoring operations
l Optimizing performance
l Policy management
l Performing maintenance
l Provisioning of resources
CLOUD MANAGEMENT PRODUCTS :

Figure shows
IBM Tivoli
Service
Automation
Manager,
a framework
tool for
managing
cloud
infrastructure.
CLOUD MANAGEMENT PRODUCTS :

Intune is
Microsoft’s
cloud-
based
manageme
nt service
for
Windows
systems.
CLOUD MANAGEMENT PRODUCTS : LIFECYCLE MANAGEMENT

➢ Cloud services have a defined lifecycle, just like any other system
deployment.

➢ A management program has to touch on each of the six different

stages in that lifecycle:
CLOUD MANAGEMENT PRODUCTS : LIFECYCLE MANAGEMENT

1.The definition of the service as a template for creating instances

Tasks performed in Phase 1 include the creation, updating, and deletion of service
templates.

2. Client interactions with the service, usually through an SLA (Service Level Agreement)
contract

This phase manages client relationships and creates and manages service contracts.

3. The deployment of an instance to the cloud and the runtime management of instances

Tasks performed in Phase 3 include the creation, updating, and deletion of service offerings.
CLOUD MANAGEMENT PRODUCTS : LIFECYCLE MANAGEMENT

4.The definition of the attributes of the service while in operation and performance of
modifications of its properties

The chief task during this management phase is to perform service optimization and
customization.

5. Management of the operation of instances and routine maintenance

During Phase 5, you must monitor resources, track and respond to events, and perform
reporting and billing functions.

6. Retirement of the service

End of life tasks include data protection and system migration, archiving, and service
contract termination.
CLOUD MANAGEMENT PRODUCTS :
CLOUD MANAGEMENT PRODUCTS :
CLOUD MANAGEMENT PRODUCTS :
EMERGING CLOUD MANAGEMENT STANDARDS :

➢ As it stands now, different cloud service providers use different technologies for creating and
managing cloud resources.

➢ As the area matures, cloud providers are going to be under considerable pressure from large
cloud users like the federal government to conform to standards and make their systems
interoperable with one another.

➢ No entity is likely to want to make a major investment in a service that is a silo or from which
data is difficult to stage or to extract.

➢ To this end, a number of large industry players such as VMware, IBM, Microsoft, Citrix, and HP
have gotten together to create standards that can be used to promote cloud interoperability.
EMERGING CLOUD MANAGEMENT STANDARDS :

➢ Another effort just getting underway has been started by CA (the company
formerly known as Computer Associates) in association with Carnegie Mellon
called the Cloud Commons.

➢ This effort is aimed at creating an industry community and working group, and
promoting a set of monitoring standards that were part of CA’s cloud technology
portfolio but are now open sourced.
EMERGING CLOUD MANAGEMENT STANDARDS
: DMTF CLOUD MANAGEMENT STANDARDS

➢ The Distributed Management Task Force (DMTF; see http://www.dmtf.org/) is an industry

organization that develops industry system management standards for platform
interoperability.

➢ Its membership is a “who’s who” in computing, and since its founding in 1992, the group
has been responsible for several industry standards, most notably the Common
Information Model (CIM).

➢ The DMTF organizes itself into a set of working groups that are tasked with specifying
standards for different areas of technology.
EMERGING CLOUD MANAGEMENT STANDARDS
: DMTF CLOUD MANAGEMENT STANDARDS

➢ A recent standard called the Virtualization Management Initiative (VMAN) was

developed to extend CIM to virtual computer system management.

➢ VMAN has resulted in the creation of the Open Virtualization Format (OVF), which
describes a standard method for creating, packaging, and provisioning virtual appliances.

➢ Since OVF was announced in 2009, vendors such as VirtualBox, AbiCloud, IBM, Red Hat,
and VMWare have announced or introduced products that use OVF.
EMERGING CLOUD MANAGEMENT STANDARDS
: DMTF CLOUD MANAGEMENT STANDARDS

➢ It was, therefore, a natural extension of the work that DMTF does in virtualization to
solve management issues in cloud computing.

➢ DMTF has created a working group called the Open Cloud Standards Incubator (OCSI) to
help develop interoperability standards for managing interactions between and in
public, private, and hybrid cloud systems.

➢ The group is focused on describing resource management and security protocols,

packaging methods, and network management technologies. The Web site of the Cloud
Management group (http://dmtf.org/standards/ cloud) is shown in Figure.
EMERGING CLOUD MANAGEMENT STANDARDS
: DMTF CLOUD MANAGEMENT STANDARDS
EMERGING CLOUD MANAGEMENT STANDARDS :CLOUD COMMONS AND SMI

➢ CA Technologies (http://www.ca.com), the company once known as Computer Associates,

has taken some of its technologies in measuring distributed network performance
metrics and repositioned its products as the following:

❖ l CA Cloud Insight, a cloud metrics measurement service

❖ l CA Cloud Compose, a deployment service

❖ l CA Cloud Optimize, a cloud optimization service

❖ l CA Cloud Orchestrate, a workflow control and policy based automation service

Taken together, these products form the basis for CA’s Cloud Connected Management Suite
(http://www.ca.com/us/cloud-solutions.aspx)
EMERGING CLOUD MANAGEMENT STANDARDS :CLOUD COMMONS AND SMI

➢ At the heart of CA Cloud Insight is a method for measuring different cloud metrics that
creates what CA calls a Service Measurement Index or SMI.

➢ The SMI measures things like SLA compliance, cost, and other values and rolls them up
into a score. To help allow SMI to gain traction in the industry, CA has donated the
core technology to the Software Engineering Institute at Carnegie Mellon as part of
what is called the SMI Consortium.

➢ This same group is responsible for the Capability Maturity Model Integration (CMMI)
process optimization technology and other efforts. The second CA initiative is the
funding of an industry online community called the Cloud Commons (http://www.
cloudcommons.com/), the home page of which is shown in Figure
EMERGING CLOUD MANAGEMENT STANDARDS :CLOUD COMMONS AND SMI
EMERGING CLOUD MANAGEMENT STANDARDS :CLOUD COMMONS AND SMI

➢ The Service Measurement Index (SMI) is based on a set of measurement

technologies forming the SMI Framework that CA donated to the SMI
Consortium. It measures cloud-based services in six areas:
▪ Agility
▪ Capability
▪ Cost
▪ Quality
▪ Risk
▪ Security

➢ These form a set of Key Performance Indicators (KPI) that can be used to
compare one service to another. Figure shows the different characteristics that
make up each of the KPIs of the Service Measurement Index.
EMERGING CLOUD MANAGEMENT STANDARDS :CLOUD COMMONS AND SMI