GR20A3118 -

CLOUD COMPUTING
UNIT - 3
Cloud Infrastructure: Architectural Design of Compute and Storage
Clouds, Layered Cloud Architecture Development, Design
Challenges, Inter Cloud Resource Management, Resource
Provisioning and Platform Deployment, Global Exchange of Cloud
Resources
Course Objectives:

1. Understand the current trend and basics of cloud computing.

2. Learn cloud services from different providers.
3. Understand the architecture and concept of different cloud models: IaaS, PaaS, SaaS.
4. Understand the underlying principle of cloud virtualization, cloud storage, data management
and data visualization.
5. Learn basic concepts of Map Reduce programming models for big data analysis on cloud.

Course Outcomes:

1. Understand the features, advantages and challenges of cloud computing, compare their
operation ,implementation and performance.
2. Understand, Analyze and compare different types of clouds and cloud services.
3. Understanding and validating the financial and technological implications in selecting cloud
computing paradigm for an organization.
4. Understand and Analyze the security challenges and risks involved in the cloud.
5. Create/Deploying of an application in cloud.

UNIT-III CLOUD INFRASTRUCTURE 2

 Architectural Design Challenges
Cloud computing is powerful network architecture intended to
perform large-scale, complex operations.
There are many challenges which need to be addressed during its architectural design.
I. Service Availability and Data Lock-in Problem
II. Data Privacy and Security Concerns
III. Unpredictable Performance and Bottlenecks
IV. Distributed Storage and Widespread Software Bugs

UNIT-III CLOUD INFRASTRUCTURE 3

 I. Service Availability and Data Lock-in Problem
 Cloud is not managed by a single company which would be source of single points
of failure. Multiple cloud providers are work together to achieve high availability
(HA).
 Even if a company has multiple data centre's located in different geographic
regions, it may have common software infrastructure and accounting systems.
 Therefore, using multiple cloud providers may provide more protection from
failures.
 Another availability obstacle is distributed denial of service (DDoS) attacks which
make services unavailable to intended users.
 Some utility computing services offer SaaS providers the opportunity to defend
against DDoS attacks by using quick scale-ups.

UNIT-III CLOUD INFRASTRUCTURE 4

I. Service Availability and Data Lock-in Problem….
 Software stacks have improved interoperability among different cloud platforms, but
the APIs itself are still proprietary.
 The solution is to standardize the APIs, so that a SaaS developer can deploy services and
data across multiple cloud providers. This will rescue the loss of all data due to the failure
of a single company.
 In addition to mitigating data lock-in concerns, standardization of APIs enables a new
usage model in which the same software infrastructure can be used in both public and
private clouds.
 Such an option could enable “surge computing,” in which the public cloud is used to
capture the extra tasks that cannot be easily run in the data centre of a private cloud.

UNIT-III CLOUD INFRASTRUCTURE 5

 II Data Privacy and Security Concerns
 Current cloud offerings are essentially public (rather than private) networks, exposing the
system to more attacks.
 Many obstacles can be overcome immediately with well understood technologies such as
encrypted storage, virtual LANs, and network middleboxes (e.g., firewalls, packet filters).
 Many nations have laws requiring SaaS providers to keep customer data and copyrighted
material within national boundaries.
 Traditional network attacks include buffer overflows, DoS attacks, spyware, malware, rootkits,
Trojan horses, and worms.
 In a cloud environment, newer attacks may result from hypervisor malware, guest hopping and
hijacking, or VM rootkits. Another type of attack is the man-in-the-middle attack for VM
migrations.
 Passive attacks steal sensitive data or passwords.
 Active attacks may manipulate kernel data structures which will cause major damage to cloud
servers.
UNIT-III CLOUD INFRASTRUCTURE 6
 III Unpredictable Performance and Bottlenecks
 Multiple VMs can share CPUs and main memory in cloud computing, but I/O
sharing is problematic.
 It is required to improve I/O architectures and operating systems to efficiently
virtualize interrupts and I/O channels.
 Internet applications continue to become more data-intensive. If we assume
applications to be “pulled apart” across the boundaries of clouds, this may
complicate data placement and transport.
 Data transfer bottlenecks must be removed, to resolve bottleneck links must be
widened, and weak servers should be removed for minimizing the cost.

UNIT-III CLOUD INFRASTRUCTURE 7

 IV Distributed Storage and Widespread Software Bugs
 The database is always growing in cloud applications.
 The opportunity is to create a storage system that will not only meet this growth,
but also combine it with the cloud advantage of scaling arbitrarily up and down on
demand.
 This demands the design of efficient distributed Storage Area Network (SANs).
 Data centre's must meet programmers’ expectations in terms of scalability, data
durability, and high availability (HA).
 Data consistence checking in SAN-connected data centre's is a major challenge in
cloud computing.

UNIT-III CLOUD INFRASTRUCTURE 8

 IV Distributed Storage and Widespread Software Bugs

 Large-scale distributed bugs cannot be reproduced, so the debugging must occur

at a scale in the production data centers.
 No data center will provide such a convenience. One solution may be a reliance on
using VMs in cloud computing.
 The level of virtualization may make it possible to capture valuable information in
ways that are impossible without using VMs.
 Debugging over simulators is another approach to attacking the problem, if the
simulator is well designed.

UNIT-III CLOUD INFRASTRUCTURE 9

 Layered Cloud Architectural Development

The architecture
of a cloud is
developed at
three layers:

I. Infrastructure
II. Platform
III. Application

UNIT-III CLOUD INFRASTRUCTURE 10

Layered Cloud Architectural Development…
 These three development layers are implemented with virtualization and
standardization of hardware and software resources provisioned in the cloud.
 The services to public, private, and hybrid clouds are conveyed to users through
networking support over the Internet and intranets involved.
 Infrastructure layer is deployed first to support IaaS services. This layer serves as the
foundation for building the platform layer of the cloud for supporting PaaS services.
 In turn, the platform layer is a foundation for implementing the application layer for
SaaS applications. Different types of cloud services demand application of these
resources separately.
 The infrastructure layer is built with virtualized compute, storage, and network
resources.

UNIT-III CLOUD INFRASTRUCTURE 11

Layered Cloud Architectural Development…
 The platform layer(PAAS) is for general-purpose and repeated usage of the collection of
software resources. This layer provides users with an environment to develop their
applications, to test operation flows, and to monitor execution results and performance.
 Virtualized cloud platform serves as a “system middleware” between the infrastructure and
application layers of the cloud.
 The application layer(SAAS) is formed with a collection of all needed software modules for
SaaS applications. Service applications in this layer include daily office management work,
such as information retrieval, document processing, and calendar and authentication
services.
 The application layer is also heavily used by enterprises in business marketing and sales,
consumer relationship management (CRM), financial transactions, and supply chain
management.
 In general, SaaS demands the most work from the provider, PaaS is in the middle, and IaaS
demands the least.

UNIT-III CLOUD INFRASTRUCTURE 12

 Market-Oriented Cloud Architecture
 Cloud providers consider and meet the different QoS parameters of each
individual consumer as negotiated in specific SLAs.
 Market-oriented resource management is necessary to regulate the supply
and demand of cloud resources.
 The designer needs to provide feedback on economic incentives for both
consumers and providers.
 The purpose of market oriented architecture is to promote QoS-based
resource allocation mechanisms.
 Figure shows the high level architecture for supporting market-oriented
resource allocation in a cloud computing environment.

UNIT-III CLOUD INFRASTRUCTURE 13

Market-Oriented
Cloud Architecture

UNIT-III CLOUD INFRASTRUCTURE 14

Market-Oriented Cloud Architecture….
 Users or brokers submit service requests to the data centre and cloud to be processed.
 The service level agreement (SLA) resource allocator acts as the interface between the
data centre/cloud service provider and external users/brokers.
 When a service request is first submitted the service request examiner interprets the
request for QoS requirements before determining whether to accept or reject the
request.
 The request examiner ensures that there is no overloading of resources, after that it
assigns requests to VMs and determines resource entitlements for allocated VMs.
 The Pricing mechanism decides how service requests are charged. Pricing serves as a
basis for managing the supply and demand of computing resources within the data center
and facilitates in prioritizing resource allocations effectively.

UNIT-III CLOUD INFRASTRUCTURE 15

Market-Oriented Cloud Architecture….
 The Accounting mechanism maintains the actual usage of resources by requests so that the
final cost can be computed and charged to users.
 In addition, the maintained historical usage information can be utilized by the Service
Request Examiner and Admission Control mechanism to improve resource allocation
decisions.
 The VM Monitor mechanism keeps track of the availability of VMs and their resource
entitlements.
 The Dispatcher mechanism starts the execution of accepted service requests on allocated
VMs.
 The Service Request Monitor mechanism keeps track of the execution progress of service
requests.

UNIT-III CLOUD INFRASTRUCTURE 16

Market-Oriented Cloud Architecture….

 Multiple VMs can be started and stopped on demand on a single physical machine to
meet accepted service requests, hence providing maximum flexibility to configure
various partitions of resources on the same physical machine to different specific
requirements of service request.

UNIT-III CLOUD INFRASTRUCTURE 17

 Quality of Service Factors
 There are critical QoS parameters to consider in a service request, such as time, cost, reliability,
and trust/security.
 QoS requirements cannot be static and may change over time due to continuing changes in
business operations.
 Negotiation mechanisms are needed to respond to alternate offers protocol for establishing SLAs.
 Commercial cloud offerings must be able to support customer-driven service management based
on customer profiles and requested service requirements.
 Commercial clouds define computational risk management tactics to identify, assess, and
manage risks involved in the execution of applications with regard to service requirements and
customer needs.
 The system incorporates autonomic resource management models that effectively self-manage
changes in service requirements to satisfy both new service demands and existing service
obligations, and leverage VM technology to dynamically assign resource shares according to
service requirements.

UNIT-III CLOUD INFRASTRUCTURE 18