Module 4

Fundamental Cloud Architectures

Workload distribution architecture, resource pooling architecture, dynamic
scalability architecture, elastic resource capacity architecture, service load
balancing architecture, cloud bursting architecture, elastic disk provisioning
architecture, redundant storage architecture, Cloud operations: Migration,
static and dynamic Scheduling

06/11/ 1
2023
Workload Distribution Architecture
• IT resources can be horizontally scaled via the addition of one or more
identical IT resources.
• Load balancer provides runtime logic capable of evenly distributing
the workload among the available IT resources.
• The resulting workload distribution architecture reduces both IT
resource over-utilization and under-utilization to an extent.
• Load Balancing can be applied to any IT resource, with workload
distribution commonly among the distributed virtual servers, cloud
storage devices, and cloud services.
06/11/ 2
2023
Workload Distribution Architecture

06/11/ 3
2023
Workload Distribution Architecture
• The below listed components are involved in workload distributed
architecture:
1. Audit Monitor
2. Cloud Usage Monitor
3. Hypervisor
4. Logical Network Perimeter
5. Resource Cluster
6. Resource Replication
06/11/ 4
2023
Resource Pooling Architecture
• A resource pooling architecture is grouping of identical IT resources
and maintained by a system that automatically ensures that they
remain synchronized.
• Physical server pools are composed of networked servers that have
been installed with operating systems and other necessary programs
and/or applications and are ready for immediate use.
• Virtual server pools are configured with several available templates
chosen by the cloud consumer during provisioning.

06/11/ 5
2023
Resource Pooling Architecture
• Storage pools, or cloud storage device pools, consist of file-based or
block-based storage structures.
• Network pools (or interconnect pools) are composed of different
preconfigured network connectivity devices. For example, a pool of
virtual firewall devices or physical network switches can be created
for redundant connectivity, load balancing, or link aggregation.
• CPU pools are ready to be allocated to virtual servers and are typically
broken down into individual processing cores.

06/11/ 6
2023
Resource Pooling Architecture
• Pools of physical RAM can be used in newly provisioned physical
servers or to vertically scale physical servers.
• Resource pools can become highly complex, with multiple pools
created for specific cloud consumers or applications.
• A hierarchical structure can be established to form parent, sibling, and
nested pools in order to facilitate the organization of diverse resource
pooling requirements.
• In typical case the IT resources pools can spread out over different
data centers.
06/11/ 7
2023
 Resource Pooling Architecture

Fig: Pools B and C are sibling pools that

are taken from the larger Pool A, which
has been allocated to a cloud consumer.
This is an alternative to taking the IT
resources for Pool B and Pool C from a
general reserve of IT resources that is
shared throughout the cloud.

06/11/ 8
2023
 Resource Pooling Architecture

Fig: Nested Pools A.1 and Pool A.2 are

comprised of the same IT resources as
Pool A, but in different quantities. Nested
pools are typically used to provision cloud
services that need to be rapidly
instantiated using the same type of IT
resources with the same configuration
settings.

06/11/ 9
2023
Resource Pooling Architecture
• Audit Monitor
• Cloud Usage Monitor
• Hypervisor
• Logical Network Perimeter
• Pay-Per-Use Monitor
• Remote Administration System
• Resource Management System
• Resource Replication
06/11/ 10
2023
Dynamic Scaling Architecture
• The dynamic scalability architecture model is based on a system of
pre- defined scaling conditions that trigger the dynamic allocation of
IT resources from resource pools.
• Dynamic allocation enables variable utilization as dictated by usage
demand fluctuations, since unnecessary IT resources are efficiently
reclaimed without requiring manual interaction.
• The automated scaling listener is configured with workload
thresholds that dictate when new IT resources need to be added to the
workload processing.

06/11/ 11
2023
Dynamic Scaling Architecture
• This mechanism can be provided with logic that determines how many
additional IT resources can be dynamically provided, based on the
terms of a given cloud consumer’s provisioning contract.
• Dynamic Horizontal Scaling – IT resource instances are scaled out and
in to handle fluctuating workloads.
• The automatic scaling listener monitors requests and signals resource
replication to initiate IT resource duplication, as per requirements and
permissions.

06/11/ 12
2023
Dynamic Scaling Architecture
• Dynamic Vertical Scaling – IT resource instances are scaled up and
down when there is a need to adjust the processing capacity of a single
IT resource.
• For example, a virtual server that is being overloaded can have its
memory dynamically increased or it may have a processing core
added.

06/11/ 13
2023
Dynamic Scaling Architecture
• Dynamic Relocation – The IT resource is relocated to a host with more
capacity.
• For example, a database may need to be moved from a tape-based
SAN storage device with 4 GB per second I/O capacity to another
disk-based SAN storage device with 8 GB per second I/O capacity.
• Cloud Usage Monitor
• Hypervisor
• Pay-Per-Use Monitor

06/11/ 14
2023
Dynamic Scaling Architecture

06/11/ 15
2023
Dynamic Scaling Architecture

06/11/ 16
2023
Dynamic Scaling Architecture

06/11/ 17
2023
Elastic Resource Capacity Architecture
• The elastic resource capacity architecture is primarily related to the
dynamic provisioning of virtual servers, using a system that allocates
and reclaims CPUs and RAM in immediate response to the fluctuating
processing requirements of hosted IT resources.

• Resource pools are used by scaling technology that interacts with the
hypervisor and/or VIM to retrieve and return CPU and RAM resources
at runtime.

06/11/ 18
2023
 Elastic Resource Capacity Architecture

• Cloud service consumers are

actively sending requests to a
cloud service (1), which are
monitored by an automated
scaling listener (2). An
intelligent automation engine
script is deployed with
workflow logic (3) that is
capable of notifying the
resource pool using allocation
requests (4).
06/11/ 19
2023
Elastic Resource Capacity Architecture

• Cloud service consumer requests increase

(5), causing the automated scaling listener
to signal the intelligent automation engine
to execute the script (6). The script runs
the workflow logic that signals the
hypervisor to allocate more IT resources
from the resource pools (7). The
hypervisor allocates additional CPU and
RAM to the virtual server, enabling the
increased workload to be handled (8).

06/11/ 20
2023
Elastic Resource Capacity Architecture
• The runtime processing of the virtual server is monitored so that
additional processing power can be leveraged from the resource pool
via dynamic allocation, before capacity thresholds are met.
• The virtual server and its hosted applications and IT resources are
vertically scaled in response.
• This type of cloud architecture can be designed so that the intelligent
automation engine script sends its scaling request via the VIM instead
of to the hypervisor directly.

06/11/ 21
2023
Elastic Resource Capacity Architecture
• Virtual servers that participate in elastic resource allocation systems
may require rebooting for the dynamic resource allocation to take
effect.
• The intelligent automation engine automates administration tasks by
executing scripts that contain workflow logic.

06/11/ 22
2023
Service Load Balancing Architecture
• The service load balancing architecture can be considered a
specialized variation of the workload distribution architecture that is
geared specifically for scaling cloud service implementations.
• Redundant deployments of cloud services are created, with a load
balancing system added to dynamically distribute workloads.
• The duplicate cloud service implementations are organized into a
resource pool, while the load balancer is positioned as either an
external or built-in component to allow the host servers to balance the
workloads themselves.
06/11/ 23
2023
Service Load Balancing Architecture
• Depending on the anticipated workload and processing capacity of host server
environments, multiple instances of each cloud service implementation can be
generated as part of a resource pool that responds to fluctuating request volumes
more efficiently.
• The service load balancing architecture can involve the following mechanisms in
addition to the load balancer:
1. Cloud Usage Monitor – Cloud usage monitors may be involved with monitoring
cloud service instances and their respective IT resource consumption levels, as well
as various runtime monitoring and usage data collection tasks.
2. Resource Cluster – Active cluster groups are incorporated into this architecture to
help balance workloads across different members of the cluster.
06/11/ 24
2023
 Service Load Balancing Architecture

3. Resource Replication - The

resource replication mechanism is
utilized to generate cloud service
implementations in support of
load balancing requirements.

06/11/ 25
2023
 Service Load Balancing Architecture

Cloud service consumer requests are sent to Cloud

Service A on Virtual Server A (1). The cloud
service implementation includes built-in load-balancing
logic that is capable of distributing requests to the
neighboring Cloud Service A implementations on Virtual
Servers B and C (2).

06/11/ 26
2023
Cloud Bursting Architecture
• Cloud Bursting is an application deployment technique in which an
application runs in a private cloud or data center and bursts into a
public cloud when the demand for computing capacity spikes.
• The cloud bursting architecture establishes a form of dynamic scaling
that scales or “bursts out” on-premise IT resources into a cloud
whenever predefined capacity thresholds have been reached.
• The corresponding cloud- based IT resources are redundantly pre-
deployed but remain inactive until cloud bursting occurs.
• After they are no longer required, the cloud-based IT resources are
released and the architecture “bursts in” back to the on-premise
environment.
06/11/ 27
2023
Cloud Bursting Architecture
• Cloud bursting is a flexible scaling architecture that provides cloud
consumers with the option of using cloud- based IT resources only to
meet higher usage demands.
• The foundation of this architectural model is based on the automated
scaling listener and resource replication mechanisms.
• The automated scaling listener determines when to redirect requests to
cloud-based IT resources, and resource replication is used to maintain
synchronicity between on-premise and cloud-based IT resources in
relation to state information.

06/11/ 28
2023
 Cloud Bursting Architecture

An automated scaling listener

monitors the usage of on-premise
Service A, and redirects Service
Consumer C’s request to Service A’s
redundant implementation in the
cloud (Cloud Service A) once
Service A’s usage threshold has been
exceeded (1). A resource replication
system is used to keep state
management databases synchronized
(2).

06/11/ 29
2023
Elastic Disk Provisioning Architecture
• Cloud consumers are commonly charged for cloud-based storage space
based on fixed-disk storage allocation, meaning the charges are
predetermined by disk capacity and not aligned with actual data storage
consumption.
• The elastic disk provisioning architecture establishes a dynamic storage
provisioning system that ensures that the cloud consumer is consisting of
billed for the exact amount of storage that it uses.
• This system uses Thin-Provisioning technology for the dynamic
allocation of storage space, and is further supported by runtime usage
monitoring to collect accurate usage data for billing purposes.
06/11/ 30
2023
 Elastic Disk Provisioning Architecture
The cloud consumer requests a virtual server
with three hard disks, each with a capacity of
150 GB (1). The virtual server is provisioned
according to the elastic disk provisioning
architecture, with a total of 450 GB of disk
space (2). The 450 GB is allocated to the virtual
server by the cloud provider (3). The cloud
consumer has not installed any software yet,
meaning the actual used space is currently 0 GB
(4). Because the 450 GB are already allocated
and reserved for the cloud consumer, it will be
charged for 450 GB of disk usage as of the point
of allocation (5).

06/11/ 31
2023
 Elastic Disk Provisioning Architecture
A request is received from a cloud consumer,
and the provisioning of a new virtual server
instance begins (1). As part of the provisioning
process, the hard disks are chosen as dynamic
or thin provisioned disks (2). The hypervisor
calls a dynamic disk allocation component to
create thin disks for the virtual server (3).
Virtual server disks are created via the thin-
provisioning program and saved in a folder of
near-zero size. The size of this folder and its
files grow as operating applications are
installed and additional files are copied onto
the virtual server (4). The pay-per-use monitor
tracks the actual dynamically allocated storage
for billing purposes (5).
06/11/ 32
2023
Elastic Disk Provisioning Architecture
• The following mechanisms can be included in this architecture in
addition to the
• Cloud storage device.
• Virtual server.
• Hypervisor.
• Pay-per-use monitor.
• Cloud Usage Monitor.
• Resource Replication.
06/11/ 33
2023
Redundant Storage Architecture
• Cloud storage devices are occasionally subject to failure and
disruptions that are caused by network connectivity issues, controller
or general hardware failure, or security breaches.
• A compromised cloud storage device’s reliability can have a ripple
effect and cause impact failure across services and availability is
compromised.
The storage service gateway is a
component that acts as the external
interface to cloud storage services and is
capable of automatically redirecting cloud
consumer requests whenever the location
A logical unit number (LUN) is a of the requested data has changed.
logical drive that represents a
06/11/ 34
2023 partition of a physical drive.
Redundant Storage Architecture
• The redundant storage architecture introduces a secondary duplicate
cloud storage device as part of a failover system that synchronizes its
data with the data in the primary cloud storage device.
• A storage service gateway diverts cloud consumer requests to the
secondary device whenever the primary device fails.
• This cloud architecture primarily relies on a storage replication system
that keeps the primary cloud storage device synchronized with its
duplicate secondary cloud storage devices.

06/11/ 35
2023
Redundant Storage Architecture

The primary cloud storage device is routinely replicated to the secondary cloud storage device
06/11/ 36
2023
 Redundant Storage Architecture

The primary storage becomes unavailable and the storage service gateway forwards the cloud consumer
requests to the secondary storage device (2). The secondary storage device forwards the requests to the
LUNs, allowing cloud consumers to continue to access their data (3).

06/11/ 37
2023
Redundant Storage Architecture
• Storage Replication
• Storage replication is a variation of the resource replication mechanisms used to
synchronously or asynchronously replicate data from a primary storage device to a
secondary storage device.
• It can be used to replicate partial and entire LUNs.
• Cloud providers may locate secondary cloud storage devices in a different
geographical region than the primary cloud storage device, usually for economic
reasons.
• Legal issues need to be addressed. (Data Privacy and Protection, Data Ownership
and Control, Data Retention and Deletion, Security and Compliance Audits, Disaster
Recovery and Business Continuity, etc..,
06/11/ 38
2023
 Redundant Storage Architecture

Storage replication is used to keep the redundant storage device synchronized with the primary storage device.

06/11/ 39
2023
End of Module 4

06/11/ 40
2023