Tools and Mechanisms (Module 3) Xen: paravirtualization

• Xen is an open source hypervisor based on paravirtualization.

• Xen
• Most popular application of paravirtualization.
• VMWare • Used for
• Microsoft Hyper-V • Desktop virtualization
• Server virtualization,
• Cloud computing solutions by means of Xen Cloud Platform (XCP).
• Xen has been extended to compatible with full virtualization
using hardware-assisted virtualization.
• It enables high performance execution of guest OS
– Eliminates the performance loss while executing instructions
that require special management.
• By modifying portions of the guest operating systems run by Xen with
reference to the execution of such instructions
• This supports x86, which is the most used architecture on
commodity machines and servers.
Tthe architecture of Xen and its mapping onto a classic x86
privilege model
Xen Architecture
Xen: paravirtualization Xen
• Xen-based system is managed by the Xen hypervisor, which runs in the highest privileged • Four different security levels in x86
mode and controls the access of guest OS to the underlying hardware. – Ring 0 , for the kernel code, represent the level with the highest privileges
• Guest OSes are executed within domains, which – Ring 3 : for user application and nonprivileged OS code, the level with the
lowest ones.
represent virtual machine instances. • Ring 0 - Xen executes the hypervisor
• Domain 0:
• Ring 1 - Domain 0, and all the other domains running guest
– specific control software, which has privileged access to the host and controls all the operating systems—generally referred to as Domain U
other guest operating systems, is executed in a special domain called Domain 0. • Ring 3 - User applications are run
• Using hypercalls,
– This is the first one that is loaded once the virtual machine manager has completely
booted, – Domains will use hypercalls to request privileged operations like updating
pagetables
– It hosts a HyperText Transfer Protocol (HTTP) server that serves requests for virtual – Xen hypervisor is able to catch the execution of all the sensitive instructions, manage
machine creation, configuration, and termination. them, and return the control to the guest operating system by means of a supplied
handler
– operating systems need to be changed in their implementation, and the sensitive
system calls need to be reimplemented with hypercalls, which are specific calls
exposed by the virtual machine interface of Xen. handler.
Xen Xen: Components in detail:
• Paravirtualization needs the operating system codebase to be modified, and hence not • Components in detail:
alloperating systems can be used as guests in a Xen-based environment. • The Xen Project Hypervisor
• Open-source operating systems such asLinux can be easily modified, since their code is – software layer that runs directly on the hardware and is responsible formanaging
publicly available and Xen provides full support for their virtualization, CPU, memory, and interrupts.
– whereas components of the Windows family are generally not supported by Xen unless – It is the first program running after the bootloader exits.
hardware-assisted virtualization is available. • Guest Domains/Virtual Machines
– virtualized environments, each running their own operating system and
applications.
– Guest VMs are totally isolated from the hardware:
– no privilege to access hardware or I/O functionality.
– called as unprivileged domain (or DomU).
• Xen enabled OS:
– Domain 0 requires a Xen enabled kernel.
– Paravirtualized guests require a PV-enabled guest.
– Linux distributions that are based on Linux kernels newer than Linux 3.0 are Xen
Project-enabled and usually include packages that contain the hypervisor and Tools
(the default Toolstack and Console).
Xen: Components in detail …
• The Control Domain (or Domain 0) VMware: full virtualization
– specialized Virtual Machine that has special privileges like the capability to access
the hardware directly, handles all access to the system’s I/O functions and interacts
with the other Virtual Machines. • Vmware
– The Xen Project hypervisor is not usable without Domain 0, – full virtualization
which is the first VM started by the system.
•underlying hardware is replicated and made available to
– Dom0 contains the following functions: the guest operating system
• System Services: such as XenStore/XenBus (XS) for managing settings, the • VMware implements full virtualization
Toolstack (TS) exposing a user interface to a Xen based system, Device
Emulation (DE) which is based on QEMU in Xen based systems
– In the desktop environment, by means of Type II
hypervisors(hosted),
• Native Device Drivers: Dom0 is the source of physical device drivers and thus
native hardware support for a Xen system – In the server environment, by means of Type I
• Virtual Device Drivers: Dom0 contains virtual device drivers (also called hypervisors (bare-metal).
backends). • Full virtualization is done by
• Toolstack: allows a user to manage virtual machine creation, destruction, and
configuration. The toolstack exposes an interface that is either driven by a – direct execution (for nonsensitive instructions) and
command line console, by a graphical interface or by a cloud orchestration stack
such as OpenStack or CloudStack. Note that several different toolstacks can be
– binary translation (for sensitive instructions), thus allowing the virtualization of
architecture such as x86.
used with Xen
VMware: full virtualization VMware: full virtualization
VMware: full virtualization VMware: full virtualization
• Full virtualization and binary • Virtualization solutions
translation
– End-user (desktop) virtualization
– Server virtualization
– Infrastructure virtualization and cloud
computing solutions
 End-user (desktop)virtualization
End-user (desktop) virtualization
Virtualization of end-user computing environments
• VMware supports virtualization of operating system environments and single applications include
on end-user computers. • VMware Player, VMware ACE, and VMware ThinApp.
• Virtualization of operating system environments
– VMware Player is a reduced version of VMware Workstation that allows creating and
– Allows installing a different operating systems and applications in a completely playing virtual machines in a Windows or Linux operating environment.
isolated environment from the hosting operating system.
– VMware ACE, a similar product to VMware Workstation, creates policy-wrapped virtual
– VMware Workstation, for Windows operating systems, and VMware Fusion, for Mac machines for deploying secure corporate virtual environments on end-user computers.
OS X environments – VMware ThinApp is a solution for application virtualization. It provides an isolated
• Installed in the host operating system to create virtual environment for applications in order to avoid conflicts due to versioning and
incompatible applications.
machines and manage their execution.
• Allow a guest operating system to use the resources of the
host machine
End-user (desktop) virtualization
Server virtualization Server virtualization
• VMware GSX server,
– Replicates the approach used for end-user
computers
– Remote management and scripting capabilities.
– Serve the virtualization of Web servers.
– A daemon process, called serverd, controls and
manages VMware application processes.
– These applications are then connected to the virtual machine instances by means of
the VMware driver installed on the host operating system.
– Virtual machine instances are managed by the VMM

– User requests for virtual machine management and provisioning are routed from the
Web server through the VMM by means of serverd.
 Infrastructure virtualization
Server virtualization
and cloud computing solutions
• vSphere

– A pool of virtualized servers is tied together and remotely managed as a whole.

– virtual compute services

– Virtual file system, virtual storage, and virtual network constitute the core of the
infrastructure;

– application services, such as virtual machine migration, storage migration, data

recovery, and security zones, complete the services offered by vSphere.
Infrastructure virtualization Infrastructure virtualization
and cloud computing solutions and cloud computing solutions
• vCenter:
– The management of the infrastructure is operated by Vmware
– Provides centralized administration and management of vSphere installations
in a data center environment. by VMware vCloud, which
• vCloud:
– Turns a collection of virtualized data centers are turned into a IaaS cloud
– allows service providers to make available to end users virtual computing
environments on demand on a pay-per-use basis.
– A Web portal provides access to the provisioning services of ,
– End users can self-provision virtual machines by choosing from availabletemplates
and setting up virtual networks among virtual instances.
• vFabric : application development
– A set of components used for the development of scalable Web applications on top of a
virtualized infrastructure.
– vFabric is a collection of components for application monitoring, scalable data
management, and scalable execution and provisioning of Java Web applications.
• Zimbra, a solution for office automation, messaging, and collaboration that is
completely hosted in the cloud and accessible from anywhere.
Infrastructure virtualization
Microsoft Hyper-V
and cloud computing solutions
• Infrastructure virtualization solution
• For server virtualization.
• Hypervisor-based approach to
hardware virtualization
• Component of Windows Server 2008R2.
Microsoft Hyper-V Microsoft Hyper-V
Microsoft Hyper-V Microsoft Hyper-V
Parent Partition/root partition:
• Hyper-V supports multiple andconcurrent execution of guest operating systems by means of
partitions. – Hyper-V takes control of the hardware, and the host operating system becomes a
virtual machine instance with special privileges, called the parent partition.
• A partition is a completely isolated environment in which an operating system is installed
and run. – only one that has direct access to the hardware.

– It runs the virtualization stack,

– hosts all the drivers required to configure guest
operating systems
– creates child partitions through the hypervisor

– hosts an instance of the Windows Server 2008 R2, which manages the
virtualization stack made available to the child partitions.
Microsoft Hyper-V Microsoft Hyper-V
Child partitions Hypervisor : Directly manages the underlying hardware(processors and memory). It is
• Host guest OS logically defined by thefollowing components:
• Do not have access to the underlying hardware • Hypercalls interface.
• Isolated environments that allow secure and controlled – This is the entry point for all the partitions for theexecution of sensitive
instructions.
execution of guests.
– The parent partition also uses this interface to create child
• Interaction with hardware is controlled by either the
partitions.
parent partition or the hypervisor itself • Memory service routines (MSRs).
• Two types of child partition exist, – Controls the memory and its access from partitions.
– Enlightened partitions • Advanced programmable interrupt controller (APIC).
• Hypervisor-aware – This component represents the interrupt controller,
• can benefit from Enlightened I/O – which manages the signals coming from the underlyinghardware when some
– Unenlightened partitions event occurs (timer expired, I/O ready, exceptions and traps).

• Hypervisor-unaware
• executed by leveraging hardware emulation from the hypervisor.
Microsoft Hyper-V Microsoft Hyper-V
• Scheduler. Enlightened I/O and synthetic devices

– Schedules the virtual processors to run onavailable physical processors.

• Enlightened I/O perform I/O operations using
interpartition communication channel
– The scheduling is controlled by policies that areset by the parent partition.
• Address manager. • There are three fundamental components:
– VMBus : implements the channel and defines the protocol
– Manage the virtual network addresses that are
for communication between partitions.
allocated to each guest operating system.
– Virtual Service Providers (VSPs) : VSPs are kernel-level drivers that are deployed in the
• Partition manager. parent partition and provide access to the corresponding hardware devices.

– Performs partition creation, finalization, – Virtual Service Clients (VSCs) : represent the virtual device drivers (also called
synthetic drivers) seen by the guest operating systems in the child partitions.
destruction, enumeration, and configurations.
Microsoft Hyper-V Microsoft Hyper-V
Cloud computing and infrastructuremanagement Cloud computing and infrastructuremanagement ….
• Windows Server Core is new version of WindowsServer 2008 • System Center Virtual Machine Manager (SCVMM)
• Windows Server Core
2008. (provides advanced management of VMs)
– reduced set of features and a smaller footprint.
– Management portal for the creation and management ofvirtual instances
– No GUI component and other bulky components such as the .NET Framework and – Virtual to Virtual (V2V) and Physical to Virtual (P2V)
all the applications developed on top of it (for example, PowerShell). conversions
– Advantages – Delegated administration
• Reduced maintenance (i.e., fewer software patches), – Library functionality and deep PowerShell integration
• Reduced attack surface – Intelligent placement of virtual machines in the managed
• Reduced management, environment
• Less disk space – Host capacity management
 Module 4

• Cloud Infrastructure Mechanism: Cloud Storage, Cloud Usage Monitor, Resource

Replication – Readymade Environment
• Specialized Cloud Mechanism: Load Balancer, SLA Monitor, Pay-per-use Monitor,
Audit Monitor -Failover System Hypervisor - Resource Cluster.

Cloud Computing Mechanism

Module 4
 Cloud Storage Device
• The cloud storage device
• Cloud Infrastructure Mechanisms
– Cloud Storage Device – Designed specifically for cloud-based
• Cloud Storage Levels provisioning.
• Network Storage Interfaces
• Object Storage Interfaces – Can be virtualized
• Database Storage Interfaces
• Relational Data Storage – Fixed-increment capacity allocation in
• Non-Relational Data Storage support of the pay-per-use mechanism.
• Case Study Example
– Cloud Usage Monitor – Can be remotely accessed via cloud
• Monitoring Agent storage services.
• Resource Agent
• Polling Agent
• Case Study Example
– Resource Replication
• Case Study Example
– Readymade Environment
Cloud Storage Device Cloud Storage Device
Cloud Storage Levels
• Issues and Challenges
Different logical units of data storage are
– Security, integrity, and confidentiality ofdata • Files
– Collections of data are grouped into files that are located in
– Legal and regulatory implications folders.
• Blocks
• Since data are stored across geographical ornational boundaries.
– a block is the smallest unit of data that is still individually
– Performance of large databases accessible.
– lowest level of storage and the closest to the hardware
• Increase in latency
• Datasets
– Sets of data are organized into a table-based, delimited, or
record format.
• Objects
– Data and its associated metadata are organized as Web-basedresources.
Different cloud service consumers utilize differenttechnologies to interface with
virtualized cloud storage devices. Cloud Storage Device

• Different cloud service consumers utilizedifferent technologies to interface with virtualized

cloud storage devices.

– File : Internet Small Computer System Interface (iSCSI), Fibre Channel (FC) , Fibre
Channel Over Ethernet Logical Unit Numbers FCoE LUNs,

– Block: Portable Operating System InterfaceNetwork File System, Common Internet

File System (POSIX NFS, CIFS)

– Object : create, read, update, and delete (or CRUD) operations via HTTP ( Hyper Text
Transfer Protocol)eg: Cloud Data Management Interface (CDMI)

– Dataset : DBMS API SQL or NoSQL , (Database Management System Application

Programming Interface, Structured Query Language,
Cloud Storage Device… Cloud Storage Device…
Small Computer System Interface
Network Storage InterfacesServer Message Block Object Storage Interfaces
• Legacy network storages Common Internet File System • Object storage is a data storage architecture for storing unstructured data, which sections
• Uses industry standard protocols, Network File System data into units— object.
– SCSI for storage blocks • Each object includes the data, metadata, and a unique identifier that applications can use
– SMB, CIFS, NFS for file and network storage. for easy access and retrieval.
• File:
• Objects can be accessed via REST, HTTP.
– Stores individual data in separate files of different sizes and
• Many data and media types are supported
formats
– Organized into folders and subfolders.
– When modified Original files are often replaced by the new files
– Data searching and extraction performance is suboptimal.
• Block
– Uses fixed format - data block,
– Data Block- which is the smallest unit that can be stored and Representational State Transfer (REST)
accessed and the storage format closest to hardware.
– Uses LUN (logical unit number) or virtual volume block-level
storage
– Better performance than file-level storage.
Cloud Storage Device… Cloud Storage Device…
Relational Data Storage
• Data is stored using relational databases or relational database
Database Storage Interfaces
management systems (RDBMSs).
• Support a query language in addition tobasic storage operations.
• Tables
• Storage management is done
– To organize similar data into rows and columns.
– Using a standard API
– Have relationships with each other to give the data increased structure, to protect data
– Using an administrative user interface. integrity, and to avoid data redundancy (which is referred to as data
• Two categories based on storagestructure normalization).

– Relational Data Storage

• Structured Query Language (SQL) is used to work with relational
data
– Non-Relational Data Storage • Eg: IBM DB2, Oracle Database, Microsoft SQL Server, and MySQL.
• Challenges
– Scaling a relational cloud storage device vertically can be more
complex and cost-ineffective
– Performance: Large Databases with complex relationships has higher processing overhead
and latency, when accessed remotely.
Cloud Storage Device… Cloud Storage Device…
Non-Relational Data Storage Non-Relational Data Storage ….
• NoSQL storage • Advantages:
• “looser” structure for stored data – Provides scalability and availability of storeddata
• No relationships and data over multiple server environments.
normalization. – More scalable than relational storage
• Limited schemas or data models. – Less complexity and processing overhead.
• Transactions or joins are not
supported. • Problem :
– Portability: Non-relational storage mechanismsare proprietary and so limit data
portability.
Cloud Storage Device… Cloud Storage Device…
cloud storage device based onan object storage interface
Cloud storage device based on an object storage interface
• A company provides cloud consumers access to a cloud storage device based on an object
storage interface

(3) Consumer uses the cloud

storage device UI to interact
(1) create a cloud storage
directly with the data objects. device and define access
control policies
 Cloud storage device based on
an object storage interface

(1) The cloud consumer interacts with the usage and administration portal to create a
cloud storage device anddefine access control policies.
(2)The usage and administration portal interact with the cloud storage software to create (2) The usage and administration portal interact with the cloud storage software to create the
cloud storage device instance and apply the required access policy to its data objects.
the cloud storage device instance and apply access policy to its data objects
– Each data object is assigned to a cloud storage device and all of the data objects are
stored in the same virtual storage volume.
(3) The cloud consumer uses the proprietary cloud storage
device UI to interact directly with the data objects.
• Access control
– Granted on a per-object basis
– Separate access policies are used for creating, reading from, andwriting to each
data object.
– Only read-only access is given for Public access
Cloud storage devices via a The creation of cloud storage devices viaa block storage network interface

block storage network interface

• A company offers a cloud service that enables the creation of cloud storage devices via a block The cloud consumer uses the
storage network interface usage and administration portal to
The cloud consumer remotely logs
create and assign a cloud storage
into the virtual server directly (3a)
to access the cloud storage device device to an existing virtual server
(3b).

The usage and administration

portal interacts with the VIM
software

VIM software creates

and configures the
appropriate LUN
The creation of cloud storage devices viaa block storage network interface

Cloud Usage Monitor

• The cloud consumer uses the usage and administration portal to create and assign a
cloud storage device to an existing virtual server (1).
• The usage and administration portal interacts with the VIM software (2a),
• Which creates and configures the appropriate LUN (2b).
• Each cloud storage device uses a separate LUN controlled by the virtualization platform. • Lightweight and autonomous software program
• The cloud consumer remotely logs into the virtual server directly (3a) to access the cloud • Collects and process IT resource usage data.
storage device (3b).
• Three categoris (based on the type of usage metrics
collected and implementation )

– Monitoring Agent

– Resource Agent

– Polling Agent
 Cloud Usage Monitor

Cloud Usage Monitor Monitoring Agent

(3a)before allowing it to continue to
the cloud service
(1) A cloud service consumer sendsa (3b)The monitoring agent stores the
Monitoring Agent request message to a cloud service collected usage data in a log database
• Intermediary, event-driven program (2) The monitoring agent interceptsthe
message to collect relevant usage data
• Existing on communication paths
• Transparently monitors and analyzes dataflows.
• Measures network traffic and message metrics.
 Cloud Usage Monitor Cloud Usage Monitor
(4) The cloud service replies with a response message
Monitoring Agent
(5) that is sent back to the cloud service consumer without beingintercepted by the
monitoring agent
Monitoring Agent
(1) A cloud service consumer sends a request message to a cloud
service
(2) The monitoring agent intercepts the message to collect relevant
usage data
(3a)before allowing it to continue to the cloud service
(3b)The monitoring agent stores the collected usage data in a log
database
(4) The cloud service replies with a response message
(5) that is sent back to the cloud service consumer without being
intercepted by the monitoring agent.
 Cloud Usage Monitor Cloud Usage Monitor

Resource Agent Resource Agent

The resource agent is actively monitoring a
virtual server and detects an increase in usage (1).
• Collects usage data on resources
• Event-driven program
• Activated each time resource software is initiated ,
suspended, resumed, and scaled.
 Cloud Usage Monitor Cloud Usage Monitor

Resource Agent
The resource agent receives a notification fromthe underlying
Resource Agent
resource management program that the virtual server is being • The resource agent is actively monitoring a virtual server and
scaled up and stores the collected usage data in a log database, as detects an increase in usage (1).
per its monitoring metrics (2).
• The resource agent receives a notification from the underlying resource management
program that the virtual server is being scaled up and stores the collected usage data in a
log database, as per its monitoring metrics (2).
 Cloud Usage Monitor Cloud Usage Monitor

Polling Agent Polling Agent

A polling agent monitors the status of a cloud service hosted by a
virtual server by sending periodic polling request messages and
• Collects cloud service usage data by polling IT receiving polling response messages that report usage status“A” after a
resources. number of polling cycles, until it receives a usage status of “B” (1)
• Monitors IT resource status (e.g. uptime and
downtime)
 Cloud Usage Monitor Cloud Usage Monitor

Polling Agent upon which the polling agent records the

Polling Agent
new usage status in the log database (2).

• A polling agent monitors the status of a cloud service hosted by a virtual server by
sending periodic polling request messages and receiving polling response messages that
report usage status “A” after a number of polling cycles, until it receives a usage status of
“B” (1), upon which the polling agent records the new usage status in the log database
(2).
 Cloud Usage Monitor Cloud Usage Monitor
Case Study
The resource agent is designed with logic and metrics that are based
on the following rules:
• A company has recently adopted cloud computing and wants to collect accurate usage 1. Each resource usage event that is generated by the VIM
data. software can contain the following data:
• Virtual servers of varying performancelevels need to be leased and billed hourly. • Event Type (EV_TYPE) – Generated by the VIM platform, there are
five types of events:
• A resource agent that relies on the resource usage events generated by the VIM platform is – VM Starting (creation at the hypervisor)
implemented to calculate the virtual server usage data.
– VM Started (completion of the boot procedure)
– VM Stopping (shutting down)
– VM Stopped (termination at the hypervisor)
– VM Scaled (change of performance parameters)
• VM Type (VM_TYPE) – type of virtual server (based on performance
parameters.
• Unique VM Identifier (VM_ID) – This identifier is provided by the VIM
platform.
• Unique Cloud Consumer Identifier (CS_ID) – Another identifier provided by the VIM
platform to represent the cloud consumer.
• Event Timestamp (EV_T) – An identification of an event occurrencethat is expressed in date-
time format, with the time zone of the data center and referenced to UTC as defined in RFC
3339 (as per the ISO 8601 profile).
 Cloud Usage Monitor Cloud Usage Monitor

2. Usage measurements are recorded for every virtual server

that a cloud consumer creates.
3. Usage measurements are recorded for a measurement period whose length is defined by
two timestamps called tstart and tend. .
4. Usage measurements are recorded at each minute of usage. The virtual server usage • The total usage, Utotal, for each virtual server during the measurement period is calculated
measurement period starts when the virtual server is created at the hypervisor and stops at using the following resource usageevent log database equations:
its termination.
– For each VM_TYPE and VM_ID in the log
5. Virtual servers can be started, scaled, and stopped multiple times during the measurement
period. The time interval between each occurrence i (i = 1, 2, 3,...) of these pairs of database:
successive events that are declared for a virtual server is called a usage cycle that is
known as Tcycle_i:
– As per the total usage time that is measured for each VM_TYPE, the vector of usage
for each VM_ID is Utotal: Utotal = {type 1, Utotal_VM_type_1, type 2,
Utotal_VM_type_2, ...}
 Cloud Usage Monitor Cloud Usage Monitor
The resource agent interacting with the VIM’s eventdriven API

virtual infrastructure manager (VIM)

 Cloud Usage Monitor
Resource Replication

• Creating of multiple instances of the same IT

• The cloud consumer (CS_ID = CS1) requests the creation of a virtual server resource.
(VM_ID = VM1) of configuration size type 1 (VM_TYPE = type1) (1).
• Replication is done when an IT resource’s
• The VIM creates the virtual server (2a). availability and performance need to be improved.
• The VIM’s event-driven API generates a resource usage event with timestamp • Technology used is Virtualization.
= t1, which the cloud usage monitor software agent captures and records inthe resource
usage event log database (2b).
• Virtual server usage increases and reaches the auto-scaling threshold (3).
• The VIM scales up Virtual Server VM1 (4a) from configuration type 1 to type
2 (VM_TYPE = type2).
• The VIM’s event-driven API generates a resource usage event with timestamp
= t2, which is captured and recorded at the resource usage event log database
by the cloud usage monitor software agent (4b).
• The cloud consumer shuts down the virtual server (5).
• The VIM stops Virtual Server VM1 (6a)
• and its event-driven API generates a resource usage event with timestamp = t3, which the
cloud usage monitor software agent captures and records at the log database (6b).
• The usage and administration portal accesses the log database and
calculates the total usage (Utotal) for Virtual Server Utotal VM1 (7).
 Resource Replication Resource Replication
The hypervisor replicates several instances of a Case Study
virtual server, using a stored virtual server image.

• Hypervisor • A company establishes a set of high-availability virtual servers that can be

– Creates many instances of a virtual server using a virtual server image automatically relocated to physical servers running in different data centers in response
– Deploy and replicate ready-made environments and entire applications to severe failure conditions.
• A virtual server that resides on a physical server running at
one data center experiences a failure condition.
• VIMs from different data centers coordinate to overcome theunavailability by reallocating the
virtual server to a differentphysical server running in another data center.
Resource Replication

A high-availability virtual server is running in Data Center A. VIM instances in Data Centers A and B are
executing a coordination function that allows detection of failure conditions. Stored VM images are replicated
between data centers as a result of the high-availability architecture.
Resource Replication

The virtual server becomes unavailable in Data Center A. The VIM in Data Center B detects the failure condition
and starts to reallocate the highavailability server from Data Center A to Data Center B.
Resource Replication

A new instance of the virtual server is created and made available

in Data Center B.
Ready-Made Environment Ready-Made Environment
• Pre-defined, cloud-based platform comprised of a • A ready-made environment has
set of already installed IT resources
– SDK (software development kit)
• Ready to be used and customized by a cloud
• provides cloud consumers with programmatic access to the development technologies
consumer.
that comprise their preferred programming stacks.
• Pre-installed IT resources are
– Middleware
– Databases
• For multitenant platforms to support the development and deployment of Web
– Middleware applications.
– Development tools – Runtime execution environments
– Governance tools.
• Cloud consumers can remotely develop and deploytheir own services and applications
within a cloud.
Ready-Made Environment Ready-Made Environment
• A cloud consumer accesses a ready-made environment
hosted on a virtual server.
 the development and deployment environment
Ready-Made Environment of Part Number Catalog application.
Case Study The developer uses the provided SDK to
develop the Part Number Catalog Web
• A company developed and deployed Java-based Part Number Catalog Web application,
Ready-Made Environment application
using leased PaaS environment, used for the switches and routers they manufacture.
• The application logic was split into front-end and back-end
processing logic.
– The front-end logic was used to process simple queries and
updates to the catalog.
– The back-end part contains the logic required to render the complete catalog and
correlate similar components and legacy part numbers.

The application is made available

for usage and one end-user
accesses its front-end instance
 Ready-Made Environment
The development and deployment environment of partnumber catalog application

• The developer uses the provided SDK to develop the Part

Number Catalog Web application (1).
• The application software is deployed on a Web platform that was established by two ready-
The software running in the made environments called the frontend instance (2a) and the back-end instance (2b).
front-end instance invokes a • The application is made available for usage and one end-user
long-running taskat the back- accesses its front-end instance (3).
end instance that corresponds to • The software running in the front-end instance invokes a long-running task at the
provides persistent storage the processing required by the back-end instance that corresponds to the processing required by the end-user (4).
end-user (4) • The application software deployed at both the front-end andback-end instances is backed by a
of the application data cloud storage device that provides persistent storage of the application data (5).
 Ready-Made Environment Other Use Cases … Ready-Made Environment
Other Use Cases
Learning Management System (LMS):
Front-end: Students can access course materials, take assessments, and interact with
Library Management System:
Front-end: Users can search for books, manage their instructors.
accounts, and request holds or renewals. Back-end: Delivers course content, manages enrollments, and grades assessments. Tracks
Back-end: Handles complex queries based on author, genre, or availability. Manages user student progress and facilitates communication between instructors and students. Integrates
accounts, loan periods, and overdue fines. Integrates with barcode scanners and other library with third-party learning tools and resources.
management systems.
Customer Relationship Management (CRM) System:
E-commerce Platform:
Front-end: Users can browse products, add items to cart, Front-end: Sales teams can manage contacts, leads, and opportunities. Customer service
and checkout securely. representatives can access customer information and support requests.
Back-end: Handles product information, inventory management, and order processing. Back-end: Stores customer data, tracks sales activities, and automates workflows. Generates
Integrates with payment gateways and fulfillment centers. Recommends similar products reports and analytics for sales performance and customer trends. Integrates with email
and displays personalized promotions.
marketing and other communication tools.

Content Management System (CMS):

Front-end: Content editors can create, edit, and publish web content.
Back-end: Manages content versions, user permissions, and website configuration. Delivers
content to the front-end and ensures website functionality. Integrates with analytics tools
and third-party content sources.
 Ready-Made Environment Ready-Made Environment

• https://www.intellinetsystem.com/int eli-catalogue-oem.htm
Ready-Made Environment
Ready-Made Environment

Cloud Computing Mechanism

- Specialized Cloud Mechanism

Module 4
 • Case Study Example
– 8.10 State Management Database
• Case Study Example

• 8: Specialized Cloud Mechanisms

– 8.2 Load Balancer
• Case Study Example
– 8.3 SLA Monitor
• Case Study Example
• SLA Monitor Polling Agent
• SLA Monitoring Agent
– 8.4 Pay-Per-Use Monitor
• Case Study Example
– 8.5 Audit Monitor
• Case Study Example
– 8.6 Failover System
• Active-Active
• Active-Passive
• Case Study Example
– 8.7 Hypervisor
• Case Study Example
– 8.8 Resource Cluster
• Case Study Example
– 8.9 Multi-Device Broker
Specialized cloud mechanisms Load Balancer

• cloud technology architecture following • Balance a workload across two or more IT resources to increase performance and capacity
specialized cloud mechanisms beyond what a single IT resource can provide.
– Load Balancer • Runtime agent, Does Horizontal scaling
– SLA Monitor • Exists on the communication path between the IT resources generating the workload and
the IT resources performing the workload processing
– Pay-Per-Use Monitor
• Load Balancer functions are
– Audit Monitor
– Failover System 1. Asymmetric Distribution
– Hypervisor • larger workloads are issued to IT resources with higher processing
– Resource Cluster capacities
– Multi-Device Broker 2. Workload Prioritization
– State Management Database • workloads are scheduled, queued, discarded, and distributed workloads
according to their priority levels
3. Content-Aware Distribution
• requests are distributed to different IT resources as dictated by the
request content
 Load Balancer
A load balancer implemented as a service agent transparently
distributes incoming workload request messages across two redundantcloud service Load Balancer
implementations, which in turn maximizes performance for the cloud service consumers.
• A load balancer has
– Performance and qos rules
– Parameters
• Objectives of load balancer
– Optimizing IT resource usage
– Avoiding overloads
– Maximizing throughput.
• The load balancer mechanisms can exist as a:
– Multi-layer network switch
– Dedicated hardware appliance
– Dedicated software-based system (in server OS)
– Service agent
 Load Balancer Load Balancer
New instances of the cloud services are automatically created to meet increasing usage
Case Study requests. The load balancer uses round- robin scheduling to ensure that the traffic is
distributed evenlyamong the active cloud services.

• The Part Number Catalog cloud service has peak usageperiods during the first few days of
every month that coincide with the preparatory processing of heavy stock control routines at
the factories.
• The company upgraded the cloud service to be highly scalable
in order to support the anticipated workload fluctuations.
– Peak workloads are 1,000 times greater than their average
workloads
SLA Monitor SLA Monitor
The SLA monitor polls the cloud service by sending
over polling request messages (MREQ1 to MREQN).
• Observes the runtime performance of cloud services to ensure QoS requirements are The monitor receives polling response messages
fullfilled (MREP1 to MREPN) that report that the service was
– QoS requirements are in SLAs
“up” at each polling cycle (1a).
The SLA monitor stores the “up” time—time period
• SLA management system
of all polling cycles 1 to N—in the log database (1b).
– Process the data collected and aggregate them into SLA
reporting metrics.
• The system can proactively repair or failover cloud services when exceptional conditions occur
(eg, when cloud service is “down”)
 The SLA monitor polls the cloud service thatsends polling request
SLA Monitor messages (MREQN+1 to MREQN+M). Polling response messages are not The SLA monitor sends a polling request message
SLA Monitor (MREQN+M+1) and receives the polling response message
received (2a).
The response messages continue to time out, sothe SLA monitor stores the (MREPN+M+1) (3a).The SLA monitor stores the “up” time in
“down” time—time period of all polling cycles N+1 to N+M—in the log the log database (3b).
database (2b).
 SLA Monitor
SLA Monitor

• The SLA monitor polls the cloud service by sending over

polling request messages (MREQ1 to MREQN).
• The monitor receives polling response messages (MREP1 to MREPN) that report that the
service was “up” at each polling cycle (1a).
• The SLA monitor stores the “up” time—time period of all
polling cycles 1 to N—in the log database (1b).
• The SLA monitor polls the cloud service that sends polling request messages (MREQN+1 to
MREQN+M). Polling response messages are not received (2a).
• The response messages continue to time out, so the SLA monitor stores the “down” time—
time period of all polling cycles N+1 to N+M—in the log database (2b).
• The SLA monitor sends a polling request message (MREQN+M+1)
and receives the polling response message (MREPN+M+1) (3a).
• The SLA monitor stores the “up” time in the log database (3b).
 SLA Monitor SLA Monitor
Case Study Example Case Study Example …
• The standard SLA for virtual servers in a company’s leasing agreements defines a minimum
IT resource availability of 99.95%, which is tracked using two SLA monitors: 1) one based on
SLA Monitoring Agent
a polling agent 2) Another based on a monitoring agent
• Event-driven API
• SLA Monitor Polling Agent • Generates three events:
– Runs in the external perimeter network to detect physical server – VM_Unreachable – the VIM cannot reach the VM
timeouts. – VM_Failure – the VM has failed and is unavailable
– Can identify data center network, hardware, and software failuresthat result in – VM_Reachable – the VM is reachable
physical server non-responsiveness. • The events are
– After three consecutive timeouts of 20-second polling periods an IT – Generated by the agents have timestamps
resource is declared as unavailable – Logged into an SLA event log database
– Used by the SLA management system to calculate ITresource availability.
Three types of events are generated:
– PS_Timeout
• the physical server polling has timed out
– PS_Unreachable – the physical server polling has consecutively
timed out three times
– PS_Reachable – the previously unavailable physical server becomesresponsive to
polling again
the steps taken by SLA monitors during a data center network failure and recovery.
SLA Monitor the steps taken by SLA monitors during a data center network failure and recovery.
SLA Monitor
At timestamp = t1, a
firewall cluster has
failed and all of the IT
resources in the data
center become
unavailable (1).
the steps taken by SLA monitors during a data center network failure and recovery.
SLA Monitor the steps taken by SLA monitors during a data center network failure and recovery.
SLA Monitor
The SLA monitor polling
agent stops receiving
responses from physical
servers and starts to issue
PS_timeout events (2).
The SLA monitor polling
agent starts issuing
PS_unreachable events
after three successive
PS_timeout events.
The timestamp is now t2
(3).
the steps taken by SLA monitors during a data center network failure and recovery.
SLA Monitor the steps taken by SLA monitors during a data center network failure and recovery.
SLA Monitor

PS_Timeout – the physical server polling has timed out

PS_Unreachable – the physical server polling hasconsecutively
timed out three times
PS_Reachable – the previously unavailable physical
server becomes responsive to polling again
the steps taken by SLA monitors during a data center network failure and recovery.

Case Study - 2

SLA Monitor
• The steps that are taken by the SLA monitors during the failure and subsequent recovery
of a physical server that is hosting three virtual servers (VM1, VM2, VM3).
Case Study Example …

• The IT resource becomes operational at timestamp = t3 (4).

• The SLA monitor polling agent receives responses from the physical servers and issues
PS_reachable events. The timestamp is now t4 (5).
• The SLA monitoring agent did not detect any unavailability since the communication
between the VIM platform and physical servers was not affected by the failure (6).
• The SLA management system uses the information stored in
the log database to calculate the period of unavailability as t4
– t2, which affected all of the virtual servers in the data
center.
The steps that are taken by the SLA monitors during the failure and subsequent recovery of a physical
server that is hosting three virtual
servers (VM1, VM2, VM3).

At timestamp = t2, the SLA for each of the failed host server’s three
At timestamp = t1, the physical host server has failed and becomes unavailable (1). virtual servers (3a).
monitoring agent captures a
VM_failure event that isgenerated

The SLA monitor polling agent stops The SLA monitoring agent captures a
receiving responses from the host VM_unreachable event that is generated for • VM_Unreachable – the VIM cannot reach the VM
serverand issues PS_timeout events eachvirtual server in the failed host server (2a) • VM Failure – the VM has failed and is unavailable
(2b).
• VM_Reachable – the VM is reachable

events after three successive

The SLA monitor polling agent PS_timeout events at timestamp =
startsto issue PS_unreachable t3 (3b).
The steps that are taken by the SLA monitors during the failure and subsequent recovery of a physical
server that is
hosting three virtual servers (VM1, VM2, VM3) ….

The host server becomes operational at timestamp = t4 (4).

PS_Reachable – the previously unavailable physical server
becomes responsive to polling again
VM_Reachable – the VM is reachable

The SLA monitor polling agent receives At timestamp = t6, the SLA monitoring agent
responses from the physical server and issues captures a VM_reachable event that is generated for
PS_reachable events at timestamp =t5 (5a). each virtual server (5b).

t5

5a 5b

The SLA management system calculates the unavailability

period that affected all of the virtual servers as t6 – t2.
 SLA Monitor SLA Monitor

Case Study Example … Case Study Example …

• At timestamp = t1, the physical host server has failed • The host server becomes operational at timestamp = t4 (4).
and becomes unavailable (1). • The SLA monitor polling agent receives responses from the
• The SLA monitoring agent captures a VM_unreachable event that is generated for each physical server and issues PS_reachable events at timestamp
virtual server in the failed host server (2a). = t5 (5a).
• The SLA monitor polling agent stops receiving responses from the host server and issues
PS_timeout events (2b). • At timestamp = t6, the SLA monitoring agent captures a VM_reachable event that is
generated for each virtual server (5b).
• At timestamp = t2, the SLA monitoring agent captures a VM_failure event that is
generated for each of the failed host server’s three virtual servers (3a). • The SLA management system calculates the unavailability
• The SLA monitor polling agent starts to issue PS_unreachable events after three period that affected all of the virtual servers as t6 – t2.
successive PS_timeout events at timestamp = t3 (3b).
 Pay-per-use monitor implemented as a resource agent used to determine
the usage period of a virtual server
Pay-Per-Use Monitor Resource Agent: Collects usage data on resources, Event-driven program, Activated each time Pay-Per-Use Monitor
resource software is initiated , suspended, resumed, and scaled.

• Measures cloud-based IT resource usage The IT resource is instantiated and the pay-per- use
– Based on predefined pricing parameters monitor receives a “start” event notification from the
resource software (2).
• Generates usage logs for fee calculations andbilling purposes.
• Monitoring metrics:
– Request/response message quantity
– Transmitted data volume (size)
– Bandwidth consumption (bps)
• Billing management system process the collected data and calculates the payment fees

A cloud consumer requests the creation of a The pay-per use monitor stores the value
new instance of a cloud service (1). timestamp in the log database (3).

The payper-use monitor receivesa “stop” event

The cloud consumer later requests that the notification from the resource software (5)
cloud service instance be stopped (4).
 Pay-Per-Use Monitor
Pay-per-use monitor implemented as a resource agent
The pay-peruse monitor stores the value timestamp in the log used to determine the usage period of a virtual server …

database (6). • A cloud consumer requests the creation of a new instance of a cloud service (1).
• The IT resource is instantiated and the pay-per- use monitor receives a “start” event
notification from the resource software (2).
• The pay-peruse monitor stores the value timestamp in the log database (3).
• The cloud consumer later requests that the cloudservice instance be stopped (4).
• The payper-use monitor receives a “stop” event notification from the resource software (5)
• The pay-peruse monitor stores the value timestamp in the log database (6).
A pay-per-use monitor designed as a monitoring agent Pay-Per-Use Monitor A pay-per-use monitor designed as a monitoring agent Pay-Per-Use Monitor
Monitoring Agent Monitoring Agent
Intermediary, event-driven program; Existing on communication paths; Transparently monitors Intermediary, event-driven program; Existing on communication paths; Transparently monitors
and analyzes dataflows; Measures network traffic and message metrics. and analyzes dataflows; Measures network traffic and message metrics.
A pay-per-use monitor designed as a monitoring agent Pay-Per-Use Monitor Pay-Per-Use Monitor
Monitoring Agent Case Study Example
Intermediary, event-driven program; Existing on communication paths; Transparently monitors
and analyzes dataflows; Measures network traffic and message metrics.
• A company decides to invest in a commercial system capable of generating invoices based
• A cloud service consumer sends a request message to the cloud service (1). on events pre-defined as “billable” and customizable pricing models.

• The pay-per-use monitor intercepts the message (2), • The installation of the system results in two proprietary databases: the billing event
database and the pricing scheme database.
• Forwards the message to the cloud service (3a),
• Runtime events are collected via cloud usage monitors that are implemented as extensions
• Pay-per-use monitor stores the usage information in accordance with itsmonitoring
to the VIM platform using the VIM’s API.
metrics (3b).
• The pay-per-use monitor agent periodically supplies the
• The cloud service forwards the response messages back to the cloud service
billing system with billable events information.
consumer to provide the requested service (4).
 The steps that are taken by pay-per-use
Case Study Example …
• A separate monitoring agent provides furthersupplemental billing-related data, such as:
monitor during a typical usage event.
– Cloud Consumer Subscription Type
• Eg: pre-paid subscription with usage quota, post-paid subscription with
maximum usage quota, and post-paid subscription with unlimited usage.
• Identifies the type of pricing model for usage fee
calculations.
– Resource Usage Category –
• normal usage, reserved IT resource usage, and
premium (managed) service usage.
• The billing management system uses this to identify
the range of usage fees
– Resource Usage Quota Consumption
• When usage contracts define IT resource usage quotas, usage event conditions
are typically supplemented withquota consumption and updated quota limits.
The steps that are taken by pay-per-use The steps that are taken by pay-per-use
monitor during a typical usage event. monitor during a typical usage event.
• The cloud consumer (CS_ID = CS1) creates and starts a virtual server (VM_ID = VM1) of
configuration size type 1 (VM_TYPE = type1) (1).
• The VIM creates the virtual server instance as requested (2a). The VIM’s eventdriven API
generates a resource usage event with timestamp = t1, which is captured and forwarded to
the pay-per-use monitor by the cloud usage monitor (2b).
• The pay-per-use monitor interacts with the pricing scheme database to identify the
chargeback and usage metrics that apply to the resource usage.
• A “started usage” billable event is generated and stored in the billable event log database (3).
• The virtual server’s usage increases and reaches the auto-scaling threshold (4).
• The VIM scales up Virtual Server VM1 (5a) from configuration type 1 to type 2 (VM_TYPE
= type2). The VIM’s event-driven API generates a resource usage event with timestamp =
t2, which is captured and forwarded to the pay-per-use monitor by the cloud usage monitor
(5b).
• The pay-per-use monitor interacts with the pricing scheme database to identify the
chargeback and usage metrics that apply to the updated IT resource usage. A “changed
usage” billable event is generated and stored in the billable event log database (6).
• The cloud consumer shuts down the virtual server (7) and the VIM stops Virtual Server
VM1 (8a).
• The VIM’s event-driven API generates a resource usage event with timestamp = t3, which is
captured and forwarded to the payper- use monitor by the cloud usage monitor (8b).
• The pay-per-use monitor interacts with the pricing scheme database to identify the
chargeback and usage metrics that apply to the updated IT resource usage.
• A “finished usage” billable event is generated and stored in the billable event log database (9).
• The billing system tool can now be used by the cloud provider to access the log database
and calculate the total usage fee for the virtual server as (Fee(VM1)) (10).
 Audit Monitor
Audit Monitor An audit monitor implemented as a monitoring agent that intercepts “login” requests and
stores the requestor’s security credentials, as wellas both failed and successful login
attempts, in a log database for future audit reporting purposes.
• Collects audit tracking data for networksand IT resources
• This data support regulatory and
contractual obligations.
• Audit Monitor
– Intercepts “login” requests
– Stores following details in a log databases
• Requestor’s security credentials
• Failed and successful login attempts,
– The stored details will be used for futureaudit
reporting purposes.
 Audit Monitor
Audit Monitor Case Study Example

• A cloud service consumer requests access to a cloud service by • A key feature of Innovartus’ role-playing solution is its unique userinterface.
sending a login request message with security credentials (1). • However, the advanced technologies used for its design have imposed licensing restrictions
• The audit monitor intercepts the message (2) and forwards it to the that legally prevent Innovartus from charging users in certain geographical regions for
authentication service (3). usage of the solution.
• The authentication service processes the security credentials. • Innovartus’ legal department is working on getting these issues resolved.
• A response message is generated for the cloud service consumer, in • But in the meantime, it has provided the IT department with a list of countries in which
addition to the results from the login attempt (4). the application can either not be accessed by users or in which user access needs to be free
• The audit monitor intercepts the response message and stores the entire collected login event of charge.
details in the log database, as per the organization’s audit policy requirements (5). • In order to collect information about the origin of clients accessing the application,
Innovartus asks its cloud provider to establish an audit monitoring system.
• Access has been granted, and a response is sent back to the cloud
service consumer (6). • The cloud provider deploys an audit monitoring agent to intercept each inbound message,
analyze its corresponding HTTP header, and collect details about the origin of the end-
user.
• As per Innovartus’ request, the cloud provider further adds a log database to collect the
regional data of each end-user request for future reporting purposes.
• Innovartus further upgrades its application so that end-users from selectcountries are able
to access the application at no charge
 Audit Monitor Audit Monitor

Case Study Example … Case Study Example …

 Audit Monitor
Failover System

Case Study Example …

• Failover is the ability to switch automatically and seamlessly to a
reliable backup system
• An end-user attempts access to the Role Player cloud • A failover system is configured to automatically switch over to a redundant or standby
IT resource instance whenever the currentlyactive IT resource becomes unavailable.
service (1).
• An audit monitor transparently intercepts the HTTP request message and analyzes the • Failover system uses resource replication mechanism
message header to determine the geographical origin of the enduser (2). • A failover system can span more than one geographical region
• The audit monitoring agent determines that the end- user is from a region that • Used in
Innovartus is not authorized to charge a fee for access to the application.
• The agent forwards the message to the cloud service (3a) and generates the audit track – Mission-critical programs
information for storage in the log database (3b). – Reusable services that can introduce a single point of failure for
• The cloud service receives the HTTP message and multiple applications.

grants the end-user access at no charge (4). • Adv

– Increases the reliability and availability of IT resources
– Provides redundant implementations.
• https://www.druva.com/glossary/what-is-a-failover-definition-and-related-faqs/
 Active-Active
Failover System … The failover system monitors the operational
status of Cloud Service A.

Failover systems come in two basic

configurations:
Active-Active, Active-Passive
1. Active-Active
– Redundant implementations of the IT resource
actively serve the workload synchronously
– Load balancing among active instances is
required.
– When a failure is detected, the failed instance is
removed from the load balancing scheduler
– Whichever IT resource remains operational when
a failure is detected takes over the processing
 Active-Active
When a failure is detected in one Cloud Service A implementation, the failover system Active-Active
commands the load balancer to switch over the workload to the redundant CloudService A The failed Cloud Service A implementation is recovered or replicated into an operational cloud
implementation. service. The failover systemnow commands the load balancer to distribute the workload again.
 Active-Passive
Failover System … The failover system monitors the operational status of Cloud Service A. The Cloud Service A
implementation acting as the active instance is receiving cloud service consumer
requests.
2. Active-Passive
– A standby or inactive implementation isactivated to take over the processing from the IT
resource that becomes unavailable,
– The corresponding workload is redirected to the instance taking over the operation
 Active-Passive
The Cloud Service A implementation acting as the active instance
The failed Cloud Service A implementation is recovered or
Active-Passive
encounters a failure that is detected by the failover system, which subsequentlyactivates the
inactive Cloud Service A implementation and redirects the workload toward it. The newly replicated an operational cloud service, and is now positioned as thestandby instance,
invoked Cloud Service A implementation now assumes the role of active instance. while the previously invoked Cloud Service A continues to serve as the active instance.
 Failover System …
Failover System …
Case Study Example

• Some failover systems are designed to redirect workloads to active IT resources that rely on
specialized load balancers that detect failure conditions and exclude failed IT resource • DTGOV creates a resilient virtual server to support the allocation of virtual server
instances from the workload distribution. instances that are hosting critical applications, which are being replicated in multiple
• This type of failover system is suitable for IT resources that do not require execution state data centers.
management and provide stateless processing capabilities.
• The replicated resilient virtual server has an associated active-passive failover system.
• In technology architectures that are typically based on clustering and virtualization
technologies, the redundant or standby IT resource implementations are also required to • Its network traffic flow can be switched between the IT resource instances that are residing at
share their state and execution context. different data centers, if the active instance were to fail.
• A complex task that was executed on a failed IT resource can
remain operational in one of its redundant implementations.
 A resilient virtual server is established by replicating the virtual server instanceacross two
different data centers, as performed by the VIM that is running at both data centers. The SLA monitors detect when the active virtualserver instance becomes unavailable.
active instance receives the network traffic and is vertically scaling in response, while the
standby instance has no workload and runs at the minimum configuration.

Failover System …
The failover system is implemented as an event-driven software agent that intercepts the
message notifications the SLA monitors send regarding server unavailability. In response, The failed virtual server instance is revived and scaled down tothe minimum standby instance
the failover system interacts with the VIM and network management tools to redirect all of the configuration after it resumes normal operation.
network traffic to the now-activestandby instance.
 Hypervisor
Hypervisor Virtual servers are created via individual hypervisor on
individual physical servers.
All three hypervisors are jointly controlled by the same VIM.
• Fundamental part of virtualization infrastructure
• Used to generate virtual server instances of a physical server.
• A hypervisor
– Limited to one physical server
– Can create virtual images of that server
– Assign virtual servers to resource pools that reside on the same
underlying physical server.
– A hypervisor has limited virtual server management features, such as increasing the
virtual server’s capacity or shutting it down.
– Is installed directly in bare-metal servers.
– Provides features for controlling, sharing and scheduling the usage of hardware
resources, such as processor power, memory, and i/o (these resources can appear to each
virtualserver’s os as dedicated resources)
• The VIM provides a range of features for administering multiple hypervisors across
physical servers.
 Hypervisor Hypervisor
Case Study Example A virtual server capable of auto-scaling
Case Study Example… experiences an increase in its workload
• A company has established a virtualization platform in which the same hypervisor
software product is running on all physical servers.
(1).
• The VIM coordinates the hardware resources in each data center so that virtual server The VIM decides that the virtual server
instances can be created from the most convenient underlying physical server.
• As a result, cloud consumers are able to lease virtual
cannot scale up because its underlying
servers with autoscaling features. physical server host is being used by
• The company’s virtualization platform provides live VM migration of virtual servers among
physical servers inside the same data center. other virtual servers (2).
– where a virtual server live-migrates from one busy physical server to another that is
idle, allowing it to scale up in response to an increase in its workload.
Hypervisor

Case Study Example…

Case Study Example…

• A virtual server capable of auto-scaling experiences an

increase in its workload (1).
• The VIM decides that the virtual server cannot scale up because its underlying physical
server host is being used by other virtual servers (2).
• The VIM commands the hypervisor on the busy physical server to suspend execution of the
virtual server (3). The VIM then commands the instantiation of the virtual server on the
idle physical server.
• State information (such as dirty memory pages and processor registers) is synchronized
via a shared cloud storage device (4).
• The VIM commands the hypervisor at the new physical server to resume the virtual server
processing (5).
Resource Cluster Resource Cluster
• Cloud-based IT resources that are geographically diverse can be logically combined into • Resource cluster architectures rely on high-speed dedicated network connections, or cluster
nodes, between IT resource instances to communicate about
groups to improve their allocation and use.
– workload distribution,
• The resource cluster mechanism is used to group multiple IT resource instances so that – task scheduling,
they can be operated as a single IT resource. – data sharing,
• Improves – system synchronization.
– computing capacity, • cluster management platform is
– A distributed middleware runs in all of the cluster nodes
– load balancing, and
– Responsible for workload distribution, task scheduling,
– availability of the clustered IT resources
data sharing, system synchronization
– coordination function: allows distributed IT resources toappear as one IT
resource,
– Executes IT resources inside the cluster.
 Resource Cluster Resource Cluster
Resource Cluster Types

• Server Cluster
– Physical or virtual servers are clustered to increase performance and availability.
– Virtual servers are able to live migrate from one to another
Loosely Coupled vs tightly coupled servers
• Database Cluster
• The cluster nodes in high availability cluster architectures need to access and share
– Designed to improve data availability
common storage IT resources.
– Synchronization feature maintains the consistency of data being stored at different
• This can require two layers of communication between the nodes—one for accessing the
storage devices used in the cluster. storage device and another to execute IT resource orchestration
• Large Dataset Cluster • Some resource clusters are designed with more loosely coupled IT resources that only
– Data partitioning and distribution is implemented so that the target datasets can be require the network layer
efficiently partitioned without compromising data integrity or computing accuracy.
 A loosely coupled server cluster that incorporates a load
Load balancing and resource replication are implemented through a cluster-enabled balancer. There is no shared storage.
hypervisor. A dedicated storage area network is used to connect the clustered storage and the Resource replication is used to replicate cloud storage devices
clustered servers, which are able to share common cloud storage devices. This simplifiesthe through the network by the cluster software.
storage replication process, which is independently carried out at the storage cluster.
Two basic types of resourceclusters
• Load Balanced Cluster Case Study Example

– Distributes workloads among cluster nodes to

increase IT resource capacity • DTGOV is considering introducing a clustered virtual server to run in a high-availability
cluster as part of the virtualization platform
– Provides centralization of IT resource • The virtual servers can live migrate among the physical servers, which are pooled in a
high- availability hardware cluster that is controlled by coordinated cluster-enabled
management. hypervisors.
• HA Cluster (high-availability cluster )
• The coordination function keeps replicated snapshots of the running virtual servers to
– Maintains system availability in the event of multiple node failures, facilitate migration to other physical servers in the event of a failure.
– Provides redundant implementations ofclustered IT resources.
– A failover system monitors failure conditions and automatically redirects the
workload away from any failed nodes.
An HA virtualization cluster of physical servers is deployed using acluster-enabled hypervisor, which guarantees that the
physical servers are constantly in sync.
Every virtual server that is instantiated in the cluster is automatically
replicated in at least two physical servers.
All of the virtual servers that are hosted on a physical server
experiencing failure are automatically migrated to other physical
servers.
Multi-Device Broker
Multi-Device Broker …
• A multi-device broker contains the mapping logic necessary to transform data exchanges
between a cloud service and different types of cloud service consumer devices
• An individual cloud service may need to be accessed by a range of cloud service
consumers differentiated by their hosting hardware devices and/or communication
requirements.
– To overcome incompatibilities between a cloud service and a disparate cloud service
consumer, mapping logic needs to be created to transform (or convert) information that
is exchanged at runtime.
– The multi-device broker mechanism is used to facilitate runtime data transformation so
as to make a cloud service accessible to a wider range of cloud service consumer
programs and devices.

A multi-device broker contains the mapping logic necessary to transform data exchanges between a cloud service and different types
of cloud service consumer devices.This scenario depicts the multi- device broker as a cloud service with its own API.This mechanism
canalso be implemented as a service agent that intercepts messages at runtime to perform necessary transformations.

Multi-Device Broker …
• Multi-device brokers commonly exist as gateways or incorporate gateway components,
such as:

1. XML Gateway – transmits and validates XML data

2. Cloud Storage Gateway – transforms cloud storage protocols and encodes storage
devices to facilitate data transfer and storage

3. Mobile Device Gateway – transforms the communication protocols used by mobile

devices intoprotocols that are compatible with a cloud service
Multi-Device Broker … Multi-Device Broker
Case Study Example
• The levels at which transformation logic can be created include:
• Innovartus has decided to make its role-playing application available to various mobile and
– transport protocols smartphone devices. A complication that hindered Innovartus’ development team during
– messaging protocols the mobile enhancement design stage was the difficulty in reproducing identical user
experiences across different mobile platforms. To resolve this issue, Innovartus implements a
– storage device protocols multi-device broker to intercept incoming messages from devices, identify the software
– data schemas/data models platform, and convert the message format into the native, server-side application format.

• A multi-device broker may contain mapping logic that coverts both transport and
messaging protocols for a cloud service consumer accessing a cloud service with a mobile
device.
 The cloud service processes the request and responds using the same standard format
(3).
The multi-device broker transforms the response message into the format required bythe source device and delivers the message (4).

Case Study Example

The multi-device broker intercepts incoming messages and detects the platform (Web
browser, iOS,Android) of the source device (1).
The multidevice broker transforms the message into the standard format required by
the Innovartus cloud service (2).
State Management Database State Management Database
• Storage device that is used to temporarilypersist
state data for software programs.
• An alternative to caching state data in
memory
• Software programs
– off-load state data to the database in order to reduce the amount of runtime memory
they consume.
– By doing so, the software programs become more scalable.
• Used by long-running runtime activities.
 State Management Database

State Management Database

During the lifespan of a cloud service instance it may be required to
remain stateful and keep state data cached in memory, even when
idle.
 State Management Database

By deferring state data to a state repository, the cloud service is able to transition to a stateless condition (or a partially Case Study Example
statelesscondition), thereby temporarily freeing system resources. • ATN is expanding its ready-made environment architecture to allow for the deferral of state
information for extended periods by utilizing the statemanagement database mechanism.
• Following figures demonstrates how a cloud service consumer working with a ready-made
environment pauses activity,causing the environment to off-load cached state data.
State Management DatabaseCase Study Example The cloud consumer accesses the ready-made environment and requires three virtual
…
servers to perform all activities (1).
The cloud consumer pauses activity. All of the state data needs to be preserved for
future access to the ready-made environment (2).
The underlying infrastructure is automatically scaled in by reducing the number of
virtual servers.
State data is saved in the state management database and one virtual server remains
active to allow for future logins by the cloud consumer (3).
At a later point, the cloud consumer logs in and accesses the ready-made environment to continue activity (4).
The underlying infrastructure is automatically scaled out by increasing the number of virtual servers and by retrieving the
statedata from the state management database (5).
State Management Database

Case Study Example …

• The cloud consumer accesses the ready-made environment

and requires three virtual servers to perform all activities (1).
• The cloud consumer pauses activity. All of the state data needs to be preserved for future
access to the ready-made environment (2).
• The underlying infrastructure is automatically scaled in by
reducing the number of virtual servers. Cloud Management Systems
• State data is saved in the state management database and one virtual server remains Multi Device Broker - State Management Database , Cloud
active to allow for future logins by the cloud consumer (3). Management Mechanism
• At a later point, the cloud consumer logs in and accesses the
ready-made environment to continue activity (4).
• The underlying infrastructure is automatically scaled out by increasing the number of Module 5
virtual servers and by retrieving thestate data from the state management database (5).
Module 5

• Multi Device Broker - State Management Database –

• Cloud Management Mechanism: Remote Administration System, Resource Management
System, SLA Management System, Billing Management System.
• 9: Cloud Management Mechanisms
– 9.1 Remote Administration System
• Case Study Example
– 9.2 Resource Management System
• Case Study Example
– 9.3 SLA Management System
• Case Study Example
– 9.4 Billing Management System
• Case Study Example
Cloud Management Mechanisms Remote Administration System

• Cloud-based IT resources need to be set up,

configured, maintained, and monitored. • Provides tools and user-interfaces for external cloud resource administrators to configure and
administer cloud-based IT resources.
• The following management-related mechanisms are
used in Cloud
– Remote Administration System
– Resource Management System
– SLA Management System
• A remote administration system can establish a portal for access to administration and
– Billing Management System management features of variousunderlying systems,
• These systems typically provide integrated APIs – Resource management,
and can be offered as – SLA management,
– individual products – Billing management systems
– custom applications, or
– combined into various product suites or multifunction
applications.
The remote administration system abstracts underlying management systems to
expose and centralize administration controls to external cloud resource
administrators.
The system provides a customizable user console, while programmatically
interfacing with underlying management systems via their APIs.
Remote Administration System … Remote Administration System …

• Two primary types of portals that are createdwith the remote administration system:
• Usage and administration portal
– Centralizes management controls to different cloud-based IT resources
– Further provide IT resource usage reports.
• Self-service portal
– Allows cloud consumers to search an up-to-date list of cloud services and it resources
that are available from a cloud provider.
– The cloud consumer submits its chosen items to
the cloud provider for provisioning.
Remote Administration System … Remote Administration System …

a scenario involving a remote administration system and both

usage and administration and self-service portals

new
Remote Administration System … Remote Administration System …
Tasks performed by cloud consumers via a remote
administration console:
• A cloud resource administrator uses the usage and administration portal to configure an • Configuring and setting up cloud services
already leased virtual server (not shown) to prepare it for hosting (1).
• The cloud resource administrator then uses the self- service portal to select and request the • Provisioning and releasing IT resource for on-demand cloud
provisioning of anew cloud service (2). services
• The cloud resource administrator then accesses the usage and administration portal again • Monitoring cloud service status, usage, and performance
to configure the newly provisioned cloud service that is hosted on the virtual server (3).
• Monitoring qos and SLA fulfillment
• Throughout these steps, the remote administration system interacts with the necessary
management systems to perform the requested actions (4). • Managing leasing costs and usage fees
• Managing user accounts, security credentials, authorization,
and access control
• Tracking internal and external access to leased services
• Planning and assessing IT resource provisioning
• Capacity planning
 Remote Administration System …
Remote Administration System
…

Depending on:
– The type of cloud product or cloud delivery model the cloud
consumer is leasing or using from the cloud provider,
– The level of access control granted by the cloud provider to the
cloud consumer, and
– Which underlying management systems the remote
administration system interfaces with
 Remote Administration System
…
Standardized APIs published by remote administration systems from different clouds
• Advantage of standardized APIs over Propreitary Uis
enable a cloud consumer todevelop a custom portal that centralizes a single IT resource
management portal for both cloud-based and onpremise IT resources. – A cloud consumer can create own front-end late it can be reused if it decides to move
to another cloud provider that supports the samestandardized API.
– The cloud consumer would be able to centrally administer IT resources from multiple
cloud providers and/or IT resources residing in cloud and on-premise environments.
– User-interface provided by the remoteadministration system will tend to be proprietary to
the cloud provider
Remote Administration System …
Resource Management System
Case Study Example
DTGOV has been offering its cloud consumers a user-friendly remote administration system
for some time, and recently determined that upgrades are required in order to accommodate the
growing number of cloud consumers and increasing diversity of requests.
DTGOV is planning a development project to extend the remote • Helps coordinate IT resources in response
administration system to fulfill the following requirements: – to management actions performed by both cloud
– Cloud consumers need to be able to self-provision virtual consumers and cloud providers
servers and virtual storage devices. • Core to this system is the virtual infrastructure manager (VIM)
– A single sign-on mechanism needs to be incorporated to centrally authorize and
control cloud consumer access. – VIM coordinates the server hardware so that virtual server instances can be created
from the mostexpedient/convenient underlying physical server.
– An API that supports the provisioning, starting, stopping, releasing, updown scaling,
and replicating of commands for virtual servers and cloud storage devices needs to be – A VIM manages a range of virtual IT resources acrossmultiple physical servers.
exposed. – A VIM creates and manages multiple instances of a hypervisor across different physical
In support of these features, a self-service portal is developed and the feature-set of DTGOV’s servers or allocate a virtual server on one physical server to another (or to a resource
existing usage and administration portal is extended. pool).
Resource Management System Resource Management System

• A resource management system encompassing a VIM • Tasks that are typically automated and implemented
platform and a virtual machine image repository. through the resource management system include:
• The VIM may have additional repositories, including one – Managing virtual IT resource templates that are used to create pre-built instances, such
as virtual server images
dedicated to storing operational data.
– Allocating and releasing virtual IT resources into the available physical
infrastructure in response to the starting, pausing, resuming, and termination of
virtual IT resource instances
– Coordinating IT resources in relation to the involvementof other mechanisms, such as
resource replication, load balancer, and failover system
– Enforcing usage and security policies throughout the
lifecycle of cloud service instances
– Monitoring operational conditions of IT resources
Resource Management System Resource Management System

• Resource management system functions can be accessed by cloud resource

administrators employed by the cloud provider or cloud consumer.
– Cloud resource administrators employed by the cloud provider can access the resource
management system’s native console.
– Cloud resource administrators employed by the cloud consumer can access usage and
administration portals built using APIs of Resource management systems .

The cloud consumer’s cloud resource administrator accesses a usage and administration portal externally to administer a leased
 Resource Management System Resource Management System
IT resource(1).
The cloud provider’s cloud resource administrator uses the nativeuser-interface provided by the VIM to perform internal Case Study Example
resource management tasks (2).
The DTGOV resource management system is an extension of a new VIM product it purchased,
and provides the following primary features:
– Management of virtual IT resources with a flexible allocation of pooled IT resources
across different datacenters
– Management of cloud consumer databases
– Isolation of virtual IT resources at logical perimeter
networks
– Management of a template virtual server image inventory
available for immediate instantiation
– Automated replication (“snapshotting”) of virtual server
images for virtual server creation
– Automated up-down scaling of virtual servers according to
usage thresholds to enable live VM migration among
physical servers
Resource Management System
Case Study Example … SLA Management System
The DTGOV resource management system is an extension of a new VIM product it purchased,
and provides the following primary features ….
• Provides features like administration, collection, storage, reporting, and runtime
• An API for the creation and management of virtual servers notification of SLA data
and virtual storage devices
• An SLA management system has
• An API for the creation of network access control rules
• An API for the up-down scaling of virtual IT resources – An SLA manager
• An API for the migration and replication of virtual IT resources across multiple data – A QoS measurements repository.
centers
• Interoperation with a single sign-on mechanism through an LDAP (lightweight directory
access protocol) interface
• Custom-designed SNMP (simple network management protocol) command scripts are
further implemented to interoperate with the network management tools to establish
isolated virtual networks across multiple data centers.
 SLA Management System

SLA Management System

• An SLA management system has
– A repository used to store and retrieve collected
SLA data
• Done based on pre-defined metrics and reporting
parameters.
– One or more SLA monitor mechanisms
• To collect the SLA data that can then be made available in near-real time to
usage and administration portals to provide on-going feedback regarding active
cloud services.
• The metrics monitored for individual cloud services are aligned with the SLA guaranteesin
corresponding cloud provisioning contracts.
SLA Management System SLA Management System
• A cloud service consumer interacts with a cloud service Case Study Example …
(1). • DTGOV implements an SLA management system that interoperates with its existing
• An SLA monitor intercepts the exchanged messages, evaluates the interaction, and VIM. This integration allows DTGOV cloud resource administrators to monitor the
collects relevant runtime data in relation to quality-of-service guarantees defined in the availability of a range of hosted IT resources via SLA monitors. DTGOV works with the
cloud service’s SLA (2A). SLA management system’s report design features to create the following pre-defined
• The data collected is stored in a repository (2B) that is reports that are made available via custom dashboards:
part of the SLA management system (3). – Per-Data Center Availability Dashboard – Publicly accessible, dashboard shows the
• Queries can be issued and reports can be generated for an external cloud resource overall operational conditions of each group of IT resources at each data center, in
administrator via a usageand administration portal (4) or realtime.
• for an internal cloud resource administrator via the SLA – Per-Cloud Consumer Availability Dashboard – This dashboard displays realtime
operational conditions of individual IT resources. Information about each IT resource
management system’s native user-interface (5).
can only be accessed by the cloud provider and the cloud consumer leasing or
owning the IT resource.
– Per-Cloud Consumer SLA Report – This report consolidates and summarizes SLA
statistics for cloud consumer IT resources, including downtimes and other
timestamped SLA events.
Billing Management System Billing Management System
• Collects and processes usage data
• A billing management system comprised of
– For cloud provider accounting
– A pricing and contract manager
– For cloud consumer billing.
– A pay-per-use measurements repository.
• Billing management system
– Uses pay-peruse monitors to gather
runtime usage data
– This usage data is stored in a repository
– Then this usage data is retrieved for
billing, reporting, and invoicing purposes.
Billing Management System

Billing Management System

• A cloud service consumer exchanges messageswith a cloud service (1).
• A pay-per-use monitor keeps track of the usage and collects data relevant to billing (2A),
• which is forwarded to a repository that is part of the billing management system (2B).
• The system periodically calculates the consolidated cloud service usage fees and generates
an invoice for the cloud consumer (3).
• The invoice may be provided to the cloud consumer through the usage and administration
portal (4).
Billing Management System Billing Management System
• Pricing models
Case Study Example
– Traditional pay-per-use models,
– Flat-rate DTGOV decides to establish a billing management system that enables them to create
– Pay-per-allocation modes, invoices for custom-defined billable events, such as subscriptions and IT resource volume
– Combinations usage. The billing management system is customized with the necessary events and
– Custom pricing models on a per cloud consumer pricing scheme metadata.
and/or per IT resource basis It includes the following two corresponding proprietary databases:
• Payments
–billable event repository
– Pre-usage and post-usage payments.
– Post-usage payments –pricing scheme repository
• Has pre-defined limits
– Usage quotas.
– Usage is blocked if quotas are exceeded.
• Unlimited usage
Billing Management System …

Case Study Example …

• Usage events are collected from pay-per-use monitors that are implemented as extensions to
the VIM platform.
–Thin-granularity usage events, such as virtual server starting, stopping, up-down
scaling, and decommissioning, are stored in a repository managed by the VIM
platform.
• The pay-per-use monitors report billable events periodically
• Either a standard or customized pricing model is applied to cloud consumer contracts.