Chapter 10: Managing the

Cloud Infrastructure
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 CRICOS Code: 00161E
RTO Code: 90458 TEQSA Provider Number: PRV12051
Version 2 – 18th December 2015
Prescribed Text:
Roger McHaney, (2021), Cloud Technologies, Kansas State University,
Manhattan USA, John Wiley & Sons, Ltd

Kavis, M. (2014) Architecting the Cloud, John Wiley, Hoboken, NJ

Erl,T. Puttini, R. Mahmood, Z. (2013) Cloud Computing: Concepts,

Technology & Architecture, Pearson Higher Ed USA

Additional Text:

Bond, J. (2015) The Enterprise Cloud - Best Practices for

Transforming Legacy IT, O’Reilly Media

Rafaels, R. (2015) Cloud Computing: From Beginning to End,

available online CreateSpace Independent Publishing Platform

Kent Institute Australia Pty. Ltd.

ABN 49 003 577 302 CRICOS Code: 00161E
RTO Code: 90458 TEQSA Provider Number: PRV12051
Managing the Cloud - Cloud Monitoring
• Complexity and Mission Criticalness of Cloud
• Scale and diversity of the infrastructure
• Servers, network devices, storages, etc.
• Hundreds, even thousands of machines
• Massive number of user applications
• Catastrophic consequence of failure / security breach / performance degradation

• Monitoring is indispensable
• Availability, failure detection
• Performance, provisioning
• Security, anomaly detection
• Application-level monitoring
Managing the Cloud - Cloud Monitoring
• Delivering Monitoring-as-a-Service
• Similar to other cloud services
• Database service (e.g. SimpleDB, Datastore)
• Storage service (e.g. S3)
• Application service (e.g. AppEngine)

• Various benefits
• End-to-end support, easy to use
• Well maintained, reliable service
• Sharing of implementation (template implementation)
A high-level view of the cloud monitoring service
State Monitoring
• State Monitoring
• Monitoring the state of a system / application / service
• State definition: a scalar value describes a certain state, V
• E.g. CPU utilization, average response time, etc.
• Violation: V > T
Distributed State Monitoring
• Distributed State Monitoring
• State value V is aggregated across multiple objects
• Monitor and coordinator
• An example of web server monitoring (average CPU utilization)
Architecture
• Architecture
• Monitor Server
• Coordinator Server
 Challenges at System Level
• Efficient Scalability • Massive Scale
Supporting tens of thousands of • Many monitoring tasks are inherently large scale
monitoring tasks • E.g. SLA monitoring
• A large number of users
Cost effective: minimize resource • Infrastructure monitoring
usage • Application monitoring
• Monitoring tasks with high cost
• E.g. Distributed heavy hitter detection based on
• Monitoring QoS netflow data

Multi-tenancy environment
• Cost Effectiveness
Minimize resource contention • Monitoring is a facilitating service
between monitoring tasks • Use few machines as possible
Budget-Aware Monitoring
• Allow dynamic monitoring resolution based on available budget

• Cloud and “Pay-as-You-Go”

• Directly associate computing cost with monetary cost
• Allow flexible provisioning based on available budget

• Overhead in Cloud Monitoring

• Violation processing cost
• E.g. provisioning new servers when detects performance degradation
• Also consumes cloud users’ budget
Budget-Aware Monitoring
• Why we need a new interface?
• Web application auto-scaling
• Dynamically adding/removing servers
based on performance
• Given a budget, how should we configure
the monitoring task?
Budget-Aware Monitoring
• How does budget-aware monitoring work?
• Determine monitoring resolution based on available
budget
• When budget is abundant
• Using fine monitoring resolution
• Detect both trivial and important violation

• When budget is limited

• Using coarse monitoring resolution
• Detect less but important violation
Managing the Cloud Infrastructure Introduction
• A technical definition is a computing capability that provides :

o an abstraction between the computing resource and its underlying

technical architecture (e.g., servers, storage, networks)

o enabling convenient ondemand network access to a shared pool of

configurable computing resources that can be rapidly provisioned and
released with minimal management effort or service provider interaction.
Principles of Cloud Computing
• Virtualization and automation
• Interchangeable (fungible) resources such as servers, storage and network
• Management of these resources as a single fabric
• Elastic capacity (scale up or down) to respond to business demands.
• Applications (and the tools to develop them) that can truly scale out
Architectural layers of Cloud Computing
• Cloud computing is typically divided into
three levels of service offerings as showed
in Fig.
1) Software as a Service (SaaS),
2) Platform as a Service (PaaS),
3) Infrastructure as a service (IaaS).

These levels support virtualization and

management of differing levels of the
solution stack.
Understanding Infrastructures as a Service (IaaS)
• Infrastructure as a Service is a form of hosting!
It includes network access, routing services and storage.

The IaaS provider will generally provide the hardware and administrative
services needed to store applications and a platform for running applications.
Scaling of bandwidth, memory and storage are generally included,
And vendors compete on the performance and pricing offered on their dynamic
services.

Resources: Sushil Bhardwaj and Etal, IJEIT 2010, 2(1), 60-63 International Journal of Engineering and Information Technology Vol 2 , No. 1
ISSN 0975-5292 (Print) IJEIT 2010, 2(1), 60-63 ISSN 0976-0253 (Online)
Understanding Infrastructures as a Service (IaaS)

• The service provider owns the equipment and is responsible for housing,
running and maintaining it.
• IaaS can be purchased with either a contract or on a pay-as-you-go basis.
• However, most buyers consider the key benefit of IaaS to be the flexibility of
the pricing, since you should only need to pay for the resources that your
application delivery requires..

Resources: Sushil Bhardwaj and Etal, IJEIT 2010, 2(1), 60-63 International Journal of Engineering and Information Technology Vol 2 , No. 1
ISSN 0975-5292 (Print) IJEIT 2010, 2(1), 60-63 ISSN 0976-0253 (Online)
Understanding Infrastructures as a Service (IaaS)

• Characteristics and components of IaaS include:

Utility computing service and billing model.
Automation of administrative tasks.
Dynamic scaling.
Desktop virtualization.
Policy-based services.
Internet connectivity

Resources: Sushil Bhardwaj and Etal, IJEIT 2010, 2(1), 60-63 International Journal of Engineering and Information Technology Vol 2 , No. 1
ISSN 0975-5292 (Print) IJEIT 2010, 2(1), 60-63 ISSN 0976-0253 (Online)
Inside Cloud Infrastructure
• Cloud infrastructures employ a virtualization layer to ensure resource
isolation and abstraction.

• They are designed to provide restricted visibility to both users and IaaS
providers.

• The Virtual Machine (VM) instances are blocked from looking down into the
infrastructure and the IaaS providers are not allowed to look inside the running
VM instance.

• In cloud environments, it is not clear that who is responsible for fixing

problems. Some of the cloud providers run online support forum, example -
Amazon EC2 Online forum. Most of VM problems in cloud infrastructure are
due to configuration events.
Infrastructure Management
• Cloud infrastructure is provided to the users in a more scalable and elastic way
by IaaS providers through pay-per-use business model in the form of virtual
machine.

• The problem is how to manage and monitor the IT infrastructure in the cloud.

• The concerns are; vendor lock-in, security, availability, portability etc.

• To overcome these problems, different infrastructure management

models/projects are developed.

Resources: Cloud Infrastructure Service Management – A Review A. Anasuya Threse Innocent Department of Computer Science and Engineering, SCT Institute of Technology,
Visvesvaraya Technological University
T.Swathi et al, International Journal of Computer Science and Mobile Computing, Vol.3 Issue.5, May- 2014, pg. 540-546
Infrastructure Management RESTful Cloud Management System (CMS)

• REpresentational State Transfer (REST) was introduced by Roy Fielding in the

year 2000 [9].
• REST, architectural style for distributed hypermedia systems describing the
software engineering principles and the interaction constraints.
• Fundamental principles of REST are:
i. Each resource is referenced using a uniform resource identifier (URI),
ii. Resources are manipulated by only four major HTTP methods; GET, PUT,
DELETE, and POST,
iii. Each interaction with a resource is stateless.

Resources: Cloud Infrastructure Service Management – A Review A. Anasuya Threse Innocent Department of Computer Science and Engineering, SCT Institute of Technology,
Visvesvaraya Technological University
T.Swathi et al, International Journal of Computer Science and Mobile Computing, Vol.3 Issue.5, May- 2014, pg. 540-546
Infrastructure Management RESTful Cloud Management System (CMS)

• REST can enhance existing management systems since resources in REST can
model managed elements such as computing/network/storage resources, and
the four methods in REST can replace full operation of management systems.
• It also allows management systems to be easily decentralized because
management information can modelled as a resource, which is identified by a
URI.
• RESTful Cloud Management System (CMS) [10] is composed of a GUI or
external systems, a REST-based manager and a REST-based agent in the
infrastructure element side.

• CMS fully utilizes fundamental Web technologies such as, HTTP and URIs, to
perform infrastructure management through REST-based manager and agent.
Integrated Multi-Cloud Management Services
• The cloud platforms must evolve from just infrastructure delivery to
automated service to satisfy the full automation requirements demanded by
service providers and it should be able to provide all the services through one
gateway.

• Four goals to be accomplished for this are:

1) Appropriate service abstraction level
2) Automatic scalability
3) Smart scaling
4) Avoiding vendor lock-in.

Resources: Cloud Infrastructure Service Management – A Review A. Anasuya Threse Innocent Department of Computer Science and Engineering, SCT Institute of Technology,
Visvesvaraya Technological University
T.Swathi et al, International Journal of Computer Science and Mobile Computing, Vol.3 Issue.5, May- 2014, pg. 540-546
Integrated Multi-Cloud Management Services
• Cloud projects such as, DeltaCloud, and RightScale are some of the examples.

• DataCloud is an open source project, providing one common API for a wide
range of service providers.

• RightScale provides management tools to manage the cloud infrastructure

over multiple public cloud providers.

• Few of the models providing muti-cloud platform or multi-service platform are

discussed in the following sections. .

Resources: Cloud Infrastructure Service Management – A Review A. Anasuya Threse Innocent Department of Computer Science and Engineering, SCT Institute of Technology,
Visvesvaraya Technological University
T.Swathi et al, International Journal of Computer Science and Mobile Computing, Vol.3 Issue.5, May- 2014, pg. 540-546
 kent.edu.au
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 ● CRICOS Code: 00161E ● RTO Code: 90458 ● TEQSA Provider Number: PRV12051

25