Cloud Architecture and

Management

1
Prepared by: Assistant Prof. Aslamzai
 Contents
• Cloud architecture
• Workload Distribution Architecture
• Resource Pooling Architecture
• Dynamic Scalability Architecture
• Elastic Resource Capacity Architecture
• Service Load Balancing Architecture
• Redundant Storage Architecture
• Anatomy of the cloud
• Applications in the cloud
• Managing the cloud
• Application migration to the cloud 2
• The cloud migration process
Cloud Architecture
• The architecture is mainly divides the cloud architecture into two parts:

1) Front End
2) Back End

Each end is connected to others through a network, generally to the Internet.

3
View of cloud computing architecture

4
Front End
• The front end is the side of computer user or client.
• It involves the interfaces and the applications that are necessary to access the Cloud
Computing system.

5
Back End
• The back end is the cloud section of the system.
• It involves all the resources which are necessary to give Cloud computing services.
• It includes huge data storage, virtual machines, security mechanism, services,
deployment models, servers etc.
• To give built-in security mechanism, traffic control and protocols is the responsibility
of the back end.

6
Workload Distribution Architecture

• IT resources can be horizontally scaled via the addition of one or more identical
IT resources, and a load balancer that provides runtime logic capable of equally
distributing the workload among the available IT resources.

7
Workload Distribution Architecture

• A redundant copy of
Cloud Service A is
implemented on
Virtual Server B.
• The load balancer
intercepts cloud
service consumer
requests and directs
them to both Virtual
Servers A and B to
ensure even workload
distribution.
8
Resource Pooling Architecture
• A resource pooling architecture is based on the use of one or more resource
pools, in which identical IT resources are grouped and maintained by a system
that automatically ensures that they remain synchronized.

9
Resource Pooling Architecture
• 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.

10
Dynamic Scalability Architecture

• The dynamic scalability architecture is an architectural model based on a system

of predefined scaling conditions that activate the dynamic allocation of IT
resources from resource pools.

11
Cont.
• Dynamic Horizontal Scaling – IT resource instances are scaled out and in
to handle changing workloads. The automatic scaling listener monitors
requests and signals resource replication to initiate IT resource duplication,
as per requirements and permissions.

• 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.

12
Cont.
• 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.

13
Cont.

Cloud service consumers are

sending requests to a cloud
service
(1). The automated scaling listener
monitors the cloud service to
determine if
predefined capacity thresholds are
being exceeded

14
Cont.

15
Cont.

16
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 changing processing requirements of
hosted IT resources

17
Elastic Resource Capacity Architecture

18
Elastic Resource Capacity Architecture

19
Service Load Balancing Architecture
• The service load balancing architecture can be considered a specialized
variation of the workload distribution architecture that is used specifically for
scaling cloud service implementations. Redundant deployments of cloud
services are created, with a load balancing system added to dynamically
distribute workloads.

20
Service Load Balancing Architecture
• The load balancer
intercepts messages
sent by cloud service
consumers (1) and
forwards them to the
virtual servers so that
the workload
processing is
horizontally scaled (2)

21
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 22
(2)
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 all of the services, applications, and
infrastructure components in the cloud that are reliant on its availability.

23
Cont.
• Storage Service Gateway
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 of the
requested data has changed

24
Cont.
• 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

25
Cont.

• The primary cloud

storage device is
routinely replicated to
the
secondary cloud storage
device (1)

26
Cont.
• 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).

27
Anatomy of the Cloud

cloud anatomy can be simply defined as the structure of the cloud. cloud anatomy
cannot be considered the same as cloud architecture. it may not include any
dependency on which or over which the technology works, whereas architecture
wholly defines and describes the technology over which it is working, thus, anatomy
can be considered as a part of architecture

28
Broker Example

29
Cont..
1. application: the upper layer is the application layer. in this layer, any applications
are executed.
2. platform: this component consists of platforms that are responsible for the
execution of the application. this platform is between the infrastructure and the
application.
3. infrastructure: the infrastructure consists of resources over which the other
components work. this provides computational capability to the user.
4. virtualization: virtualization is the process of making logical components of
resources over the existing physical resources. the logical components are isolated
and independent, which form the infrastructure.
30
5. physical hardware: the physical hardware is provided by server and storage units.
Applications on the Cloud

The power of a computer is realized through the applications. there are several
types of applications. the first type of applications that was developed and used
was a stand-alone application. a stand-alone application is developed to be run
on a single system that does not use network for its functioning. these stand-
alone systems use only the machine in which they are installed. the functioning of
these kinds of systems is totally dependent on the resources or features available
within the system. these systems do not need the data or processing power of
other systems; they are self-sustaining

31
Cont..

32
Cont..

• The web application is not elastic and cannot handle very heavy loads, that is, it
cannot serve highly varying loads.
• The web application does not provide a quantitative measurement of the
services that are given to the users, though they can monitor the user.
• The web applications are usually in one particular platform.
• The web applications are not provided on a pay-as-you-go basis; thus, a
particular service is given to the user for permanent or trial use and usually the
timings of user access cannot be monitored.
• Due to its nonelastic nature, peak load transactions cannot be handled.
33
Cont..
A cloud application is different from other applications; they have unique
features. a cloud application usually can be accessed as a web application but its
properties differ. according to nist [3], the features that make cloud applications
unique are described in the following (figure 3.4 depicts the features of a cloud
application):
1. multitenancy: multitenancy is one of the important properties of cloud that
make it different from other types of application in which the software can be
shared by different users with full independence. here, independence refers to
logical independence.

34
Cont..

35
Cont..

2. elasticity: elasticity is also a unique property that enables the cloud to serve better.
according to herbst et al. [4], elasticity can be defined as the degree to which a system
is able to adapt to workload changes by provisioning and de provisioning resources in
an autonomic manner such that at each point in time, the available resources match
the current demand as closely as possible. elasticity allows the cloud providers to
efficiently handle the number of users, from one to

36
Cont..

3. heterogeneous cloud platform: the cloud platform supports heterogeneity,

wherein any type of application can be deployed in the cloud. because of this
property, the cloud is flexible for the developers, which facilitates deployment.
4. quantitative measurement: the services provided can be quantitatively
measured. the user is usually offered services based on certain charges. here, the
application or resources are given as a utility on a pay-per-use basis. thus, the use
can be monitored and measured.
5. on-demand service: the cloud applications offer service to the user, on
demand, that is, whenever the user requires it.
37
Managing the Cloud
Cloud so as to maintain the qos. it is one of the prime jobs to be considered. the
whole cloud is dependent on the way it is managed. cloud management can be
divided into two parts:
1. managing the infrastructure of the cloud
2. managing the cloud application

38
Managing the Cloud Infrastructure

The infrastructure of the cloud is considered to be the backbone of the cloud. this
component is mainly responsible for the QOS factor.
if the infrastructure is not properly managed, then the whole cloud can fail and
QOS would be adversely affected. the core of cloud management is resource
management.
Resource management involves several internal tasks such as resource scheduling,
provisioning, and load balancing.

39
Managing the Cloud Application

Business companies are increasingly looking to move or build their corporate

applications on cloud platforms to improve agility or to meet dynamic
requirements that exist in the globalization of businesses and responsiveness to
market demands. so, understanding the availability of an application requires
inspecting the infrastructure, the services it consumes, and the upkeep of the
application. the composite nature of cloud applications requires visibility into all
the services to determine the overall availability and uptime.

40
Migrating Application to Cloud
Cloud migration encompasses moving one or more enterprise applications and
their it environments from the traditional hosting type to the cloud
environment, either public, private, or hybrid. cloud migration presents an
opportunity to significantly reduce costs incurred on applications. this activity
comprises, of different phases like evaluation, migration strategy, prototyping,
provisioning, and testing

41
Phases of Cloud Migration

1. evaluation: evaluation is carried out for all the components like current
infrastructure and application architecture, environment in terms of compute,
storage, monitoring, and management, slas, operational processes, financial
considerations, risk, security, compliance, and licensing needs are identified to build
a business case for moving to the cloud.
.

42
Cont..

2. migration strategy: based on the evaluation, a migration strategy is drawn a

hotplug strategy is used where the applications and their data and interface
dependencies are isolated and these applications can be operationalized all at
once. a fusion strategy is used where the applications can be partially migrated;
but for a portion of it, there are dependencies based on existing licenses,
specialized server requirements like mainframes, or extensive interconnections
with other applications

43
Cont..

3. prototyping: migration activity is preceded by a prototyping activity to validate

and ensure that a small portion of the applications are tested on the cloud
environment with test data setup.
4. provisioning: premigration optimizations identified are implemented. cloud
servers are provisioned for all the identified environments, necessary platform
softwares and applications are deployed, configurations are tuned to match the
new environment sizing, and databases and files are replicated. all internal and
external integration points are properly configured. web services, batch jobs, and
operation and management software are set up in the new environments.
44
Cont..
5. testing: postmigration tests are conducted to ensure that migration has been
successful. performance and load testing, failure and recovery testing, and scale-
out testing are conducted against the expected traffic load and resource
utilization levels.

45
The cloud migration process

• Planning your migration: Before getting started, you should be clear on your reasons
for the move and which strategy can best support them.
• Start by assessing your current environment. It is important to calculate your cloud server
requirements based on current application resource requirements to avoid buying more
than you need. At this critical stage, you will need the resources and expertise of a
specialist.

46
Cont.

• Choosing your cloud environment: Now that you have the visibility you need to
achieve success, you are ready to decide what kind of cloud model you want to
adopt.
• Whether you choose public cloud, hybrid cloud, private cloud, or multicloud (or services
like Google, Azure, or AWS) depends on which best serves your current and future needs.

47
Cont.

• Migrating your apps and data: Planned accurately, your actual migration should be
plain sailing. Still, keep in mind cloud security concerns, such as complying with
security policies and planning for data backup and recovery.

48
Cont.

• Validating post-move success: You cannot declare a cloud migration successful

without evidence that it works as expected. you can prove the benefits of cloud
migration by comparing pre- and post-move application performance, from both a
technical and business perspective, in a low-risk test environment.

49
Summary
• cloud computing has several concepts that must be understood before starting off
with the details about the cloud, which include one of the important concepts of
cloud architecture. it consists of a basic hierarchical structure with dependencies of
components specified. similarly, anatomy is also important as it describes the basic
structure about the cloud, though it does not consider any dependency as in
architecture. further, the cloud network connectivity that forms the core of the cloud
model is important. the network is the base using which the cloud works. similarly,
cloud management is one of the important concepts that describe the way in which
the cloud is managed, and it has two components: infrastructure management and
application management. both are important as both affect the qos. finally, an
application should be successfully migrated to a cloud. an application will radiate its
complete properties as a cloud only when it has perfectly migrated.
50