CCS335- CLOUD COMPUTING NOTES

UNIT I CLOUD ARCHITECTURE MODELS AND INFRASTRUCTURE 6

Cloud Architecture: System Models for Distributed and Cloud Computing – NIST Cloud
Computing Reference Architecture – Cloud deployment models – Cloud service models;
Cloud Infrastructure: Architectural Design of Compute and Storage Clouds – Design
Challenges.

System Models for Distributed and Cloud Computing

 Distributed and cloud computing systems are built over a large number of
autonomous computer nodes.

 These node machines are interconnected by SANs, LANs, or WANs in a

hierarchical manner.
 With today’s networking technology, a few LAN switches can easily connect
hundreds of machines as a working cluster.
 A WAN can connect many local clusters to form a very large cluster of
clusters.
 Massive systems are considered highly scalable, and can reach web-scale
connectivity, either physically or logically.
Massive systems are classified into four groups:

1. Clusters of Cooperative Computers

 A computing cluster consists of interconnected stand-alone computers
which work cooperatively as a single integrated computing resource.

 In the past, clustered computer systems have demonstrated impressive

results in handling heavy workloads with large data sets.
1.1 Cluster Architecture
 In Figure 1.15 shows the architecture of a typical server cluster built around a
low- latency, high-bandwidth interconnection network.

 This network can be as simple as a SAN (e.g., Myrinet) or a LAN (e.g.,

Ethernet).

 To build a larger cluster with more nodes, the interconnection network can
be built with multiple levels of Gigabit Ethernet, Myrinet, or InfiniBand
switches.

 Through hierarchical construction using a SAN, LAN, or WAN, one can build
scalable clusters with an increasing number of nodes.
  The cluster is connected to the Internet via a virtual private network
(VPN) gateway.
 All resources of a server node are managed by their own OS.
 Thus, most clusters have multiple system images as a result of having many
autonomous nodes under different OS control.

1.2 Single System Image

 A cluster operating system or some middle-ware to support SSI at various levels,

including the sharing of CPUs, memory, and I/O across all cluster nodes.

 An SSI is an illusion created by software or hardware that presents a collection of

resources as one integrated, powerful resource.

 SSI makes the cluster appear like a single machine to the user.

 A cluster with multiple system images is nothing but a collection of

independent computers.

1.3 Hardware, Software, and Middleware Support

 Most clusters run under the Linux OS.

 The computer nodes are interconnected by a high-bandwidth network

(such as Gigabit Ethernet, Myrinet, InfiniBand, etc.

 Special cluster middleware supports are needed to create SSI or high

availability (HA).

 Both sequential and parallel applications can run on the cluster.

 distributed memory to be shared by all servers by forming distributed

shared memory (DSM).
  Many SSI features are expensive or difficult to achieve at various cluster
operational levels.
 Using virtualization, one can build many virtual clusters dynamically, upon
user demand.
1.4 Major cluster design issues
 Middleware or OS extensions were developed at the user space to achieve
SSI at selected functional levels.
 Without this middleware, cluster nodes cannot work together effectively
to achieve cooperative computing.

 The software environments and applications must rely on the middleware

to achieve high performance.

 The cluster benefits come from scalable performance, efficient message

passing, high system availability, seamless fault tolerance, and cluster-wide job
management, as summarized in Table 1.3.

2. Grid Computing Infrastructures

 users have experienced a natural growth path from Internet to web and grid
computing services.
 Internet services such as the Telnet command enables a local computer to
connect to a remote computer.
 A web service such as HTTP enables remote access of remote
 web pages.
 Grid computing is envisioned to allow close interaction among applications
running
on distant computers simultaneously.
 The evolution from Internet to web and grid services is certainly playing a
major role in this growth.

2.1 computational grids

 computing grid offers an infrastructure that couples computers,
software/middleware, special instruments, and people and sensors together.

 The grid is often con-structed across LAN, WAN, or Internet backbone

networks at a regional, national, or global scale.

 Enterprises or organizations present grids as integrated computing resources.

 They can also be viewed as virtual platforms to support virtual organizations.

 Figure 1.16 shows an example computational grid built over multiple resource
sites owned by different organizations.

 The resource sites offer complementary computing resources, including

workstations, large servers, a mesh of processors, and Linux clusters to
satisfy a chain of computational needs.

 The grid is built across various IP broadband networks including LANs

and WANs already used by enterprises or organizations over the Internet.

 The grid is presented to users as an integrated resource pool as shown in the

upper half of the figure.

At server end: grid is a network.

At client end : Wired or Wireless terminals.

2.2 Grid Families

 Grid technology demands new distributed computing models,

software/middleware support,network protocols, and hardware infrastructures.
 National grid projects are followed by industrialgrid plat-form development.
 New grid service providers (GSPs) and new grid applications have
emerged rapidly similar to internet and web services.
 Table 1.4, grid systems are classified in essentially two categories:

1. computational or data grids

2. P2P grids.

3. Peer-to-Peer Network Families

An example of a well-established distributed system is the client-server architecture.

In this scenario, client machines (PCs and workstations) are connected to a central
server for compute, e-mail, file access, and database applications.

The P2P architecture offers a distributed model of networked systems.

First, a P2P network is client-oriented instead of server-oriented.

In this section, P2P systems are introduced at the physical level and overlay
networks at the logical level.

3.1 P2P Systems

 In a P2P system, every node acts as both a client and a server, providing
part of the system resources.
 Peer machines are simply client computers connected to the Internet.
 All client machines act autonomously to join or leave the system freely.
 This implies that no master-slave relationship exists among the peers.
 No central coordination or central database is needed.
  In other words, no peer machine has a global view of the entire P2P
system.
 The system is self-organizing with distributed control.
 Figure 1.17 shows the architecture of a P2P network at two abstraction
levels.
 Initially, the peers are totally unrelated.
 Each peer machine joins or leaves the P2P network voluntarily.
 Only the participating peers form the physical network at any time.
 Unlike the cluster or grid, a P2P network does not use a dedicated
interconnection network.
 The physical network is simply an adhoc network formed at various Internet
domains randomly using the TCP/IP and NAI protocols.
 Thus, the physical network varies in size and topology dynamically due to the
free membership.

3.2 Overlay Networks

 Data items or files are distributed in the participating peers.

 Based on communication or file-sharing needs, the peer IDs form an
overlay network at the logical level.
 This overlay is a virtual network formed by mapping each physical
machine with its ID, logically.
 new peer joins the system, its peer ID is added.
 peer ID is removed from the overlay network automatically.
 There are two types of overlay networks: unstructured and structured.

1.unstructured

 An unstructured overlay network is characterized by a random graph.

 There is no fixed route to send messages or files among the nodes.

2.structured
  overlay net-works follow certain connectivity topology and rules for inserting
and removing nodes (peer IDs) from the overlay graph.
 Routing mechanism are developed by structured overlays.

3.3 P2P Application Families

Based on application, P2P networks are classified into four groups, as shown in
Table 1.5.

1.Distributed sharing

2.collaborative platform

3.Distributed P2P computing

4.P2P platform

3.4 P2P Computing Challenges

 P2P computing faces three types of heterogeneity problems in hardware,

software, and network requirements.
 Data locality, network proximity, and interoperability are three design
objectives in distributed P2P applications.
 Issues in using P2P network are

1.fault tolerance

2.failure management

3.load balancing

4. cloud computing over the Internet

4.1 internet cloud

 cloud computing applies a virtualized platform with elastic resources on

demand by provisioning hardware, software, and data sets dynamically (see
Figure 1.18).
 The idea is to move desktop computing to a service-oriented platform using
server clusters and huge databases at data centers.
 The cloud ecosystem must be designed to be secure, trustworthy,and
dependable.

4.2 cloud landscape

 To resolve the traditional problems. Cloud provides three service models are
Iaas,Paas,Saas.
 Internet cloud offers five deployment models are

1.private

2.public

3. community

4.hybrid

5.Multi cloud

Cloud services offerings eight resources to adapt cloud

1.higher energy efficiency

2.improving overall utilization

3.reduction in cost

4.cloud computing program and application development.

5.privacy, security, copyright

 6.service agreements, business models.

7.service and data discovery.

8.infrastructure maintenance.

NIST Cloud Computing Reference Architecture

 The reference architecture model given by the National Institute of Standards

andTechnology (NIST).
 The model offers approaches for secure cloud adoption.
 The NIST team works closely with leading IT vendors, developers of
standards, industries and other governmental agencies and industries at a
global level to support effective cloud computing security standards and their
further development.

Fig. 1.2 : Conceptual cloud reference model showing different actors and entities

the cloud reference architecture includes five major actors :

1.Cloud Consumer :A person or organization that maintains a business relationship

with, and uses service from, Cloud Providers.

2.Cloud Provider :A person, organization, or entity responsible for making a service

available to interested parties.

3.Cloud Carrier :An intermediary that provides connectivity and transport of cloud

services from Cloud Providers to Cloud Consumers.

4.Cloud Auditor :A party that can conduct independent assessment of cloud

services, information system operations, performance and security of the cloud
implementation.
5.Cloud Broker :An entity that manages the use, performance and delivery of cloud
services, and negotiates relationships between Cloud providers and cloud consumer.

Each actor is an organization or entity plays an important role in a transaction or a

process, or performs some important task in cloud computing. The interactions
between these actors are illustrated in Fig. 1.3

1.Cloud consumer

 A cloud consumer is the most important stakeholder. The cloud service is built
to support a cloud consumer.
 The consumer then verifies the service catalogue from the cloud provider and
requests an appropriate service or sets up service contracts for using the
service.
 The cloud consumer is billed for the service used.
Some typical usage scenarios include :

Example 1 : Cloud consumer requests the service from the broker instead of
directly contacting the CSP. The cloud broker can then create a new service by
combining multiple services or by enhancing an existing service. Here, the actual
cloud provider is not visible to the cloud consumer. The consumer only interacts
with the broker. This is illustrated in Fig. 1.4.

Fig. 1.4 : Cloud broker interacting with cloud consumer

2.Cloud Provider

 Cloud provider is an entity that offers cloud services to interested parties.

  A cloud provider manages the infrastructure needed for providing cloud
services.
 The CSP also runs the software to provide services and organizes the service
delivery to cloud consumers.

Fig. 1.8 : Major activities of a cloud provider

The major activities of a cloud provider include :

• Service deployment: Service deployment refers to provisioning private, public,

hybrid and community cloud models.

• Service orchestration: Service orchestration implies the coordination,

management of cloud infrastructure and arrangement to offer optimized capabilities
of cloud services.The capabilities must be cost-effective in managing IT resources
and must be determined by strategic business needs.

• Cloud services management: This activity involves all service-related functions

needed to manage and operate the services requested or proposed by cloud
consumers.

• Security: Security, which is a critical function in cloud computing, spans all layers
in the reference architecture. Security must be enforced end-to-end. It has a wide
range from physical to application security. CSPs must take care of security.

• Privacy: Privacy in cloud must be ensured at different levels, such as user privacy,
data privacy, authorization and authentication and it must also have adequate
assurance levels. Since clouds allow resources to be shared, privacy challenges are
a big concern for consumers using clouds.

3. Cloud Auditor
  The cloud auditor performs the task of independently evaluating cloud service
controls to provide an honest opinion when requested.
 Cloud audits are done to validate standards conformance by reviewing the
objective evidence.
 The auditor will examine services provided by the cloud provider for its
security controls, privacy, performance, and so on.

4.Cloud Broker

 The cloud broker collects service requests from cloud consumers and
manages the use, performance, and delivery of cloud services.
 The cloud broker will also negotiate and manage the relationship between
cloud providers and consumers.
 A cloud broker may provide services that fall into one of the following
categories :

• Service intermediation : Here the cloud broker will improve some specific

capabilities, and provide value added services to cloud consumers.

• Service aggregation : The cloud broker links and integrates different services into

one or more new services.

• Service Arbitrage : This is similar to aggregation, except for the fact that services

that are aggregated are not fixed. In service arbitrage, the broker has the liberty to

choose services from different agencies.

5. Cloud Carrier

 The cloud carrier tries to establish connectivity and transports cloud services
between a cloud consumer and a cloud provider.
 Cloud carriers offer network access for consumers, by providing
telecommunication links for accessing resources using other devices (laptops,
computers, tablets, smartphones, etc.)
 Cloud carriers provide secure and dedicated high – speed links with cloud
providers and between different cloud entities.

Cloud Deployment Model

Cloud Deployment Model functions as a virtual computing environment with a

deployment architecture that varies depending on the amount of data you want to
store and who has access to the infrastructure.

Types of Cloud Computing Deployment Models

  The cloud deployment model identifies the specific type of cloud environment
based on ownership, scale, and access, as well as the cloud’s nature and
purpose.
 Relationships between the infrastructure and your users are also defined by
cloud deployment types.
 Different types of cloud computing deployment models are

1. Public Cloud

2. Private Cloud

3. Hybrid Cloud

4. Community Cloud

5. Multi-Cloud

1.Public Cloud:

 The public cloud makes it possible for anybody to access systems and
services.
 The public cloud may be less secure as it is open to everyone.
 The public cloud is one in which cloud infrastructure services are provided
over the internet to the general people or major industry groups.
 . For example, Google App Engine etc.

Public cloud

Advantages of the Public Cloud Model

 Minimal Investment: Because it is a pay-per-use service, there is no

substantial upfront fee, making it excellent for enterprises that require
immediate access to resources.
 No setup cost: The entire infrastructure is fully subsidized by the cloud
service providers, thus there is no need to set up any hardware.

 Infrastructure Management is not required: Using the public cloud does not
necessitate infrastructure management.
  No maintenance: The maintenance work is done by the service provider (not
users).
 Dynamic Scalability: To fulfill your company’s needs, on-demand resources
are accessible.

Disadvantages of the Public Cloud Model

 Less secure: Public cloud is less secure as resources are public so there is
no guarantee of high-level security.
 Low customization: It is accessed by many public so it can’t be customized
according to personal requirements.

2.Private Cloud

 The private cloud deployment model is the exact opposite of the public
cloud deployment model.
 It’s a one-on-one environment for a single user(customer).
 It is also called “ Internal cloud”.

Private cloud

Advantages of the Private Cloud Model

 Better Control: You are the sole owner of the property. You gain complete
command over service integration, IT operations, policies, and user behavior.
 Data Security and Privacy: It’s suitable for storing corporate informatioon to
which only authorized staff have access. By segmenting resources within the
same infrastructure, improved access and security can be achieved.
 Supports Legacy Systems: This approach is designed to work with legacy
systems that are unable to access the public cloud.
  Customization: Unlike a public cloud deployment, a private cloud allows a
company to tailor its solution to meet its specific needs.

Disadvantages of the Private Cloud Model

 Less scalable: Private clouds are scaled within a certain range as there is

less number of clients.

 Costly: Private clouds are more costly as they provide personalized.

4.Hybrid Cloud

 By bridging the public and private worlds with a layer of proprietary

software, hybrid cloud computing gives the best of both worlds.
 With a hybrid solution, you may host the app in a safe environment
while taking advantage of the public cloud’s cost savings.
 Organizations can move data and applications between different clouds using
a combination of two or more cloud deployment methods, depending on their
needs.

Advantages of the Hybrid Cloud Model

 Flexibility and control: Businesses with more flexibility can design

personalized solutions that meet their particular needs.

 Cost: Because public clouds provide scalability, you’ll only be responsible

for paying for the extra capacity if you require it.
 Security: Because data is properly separated, the chances of data theft
 by attackers are considerably reduced.

Disadvantages of the Hybrid Cloud Model

 Difficult to manage: Hybrid clouds are difficult to manage as it is a

combination of both public and private cloud. So, it is complex.
 Slow data transmission: Data transmission in the hybrid cloud takes
place through the public cloud so latency occurs.

Community Cloud

 It allows systems and services to be accessible by a group of

organizations.
 It isa distributed system that is created by integrating the services of
different clouds to address the specific needs of a community, industry,
or business.
 The infrastructure of the community could be shared between the organization
which has shared concerns or tasks.
 It is generally managed by a third party or by the combination of one or more
organizations in the community.

Advantages of the Community Cloud Model

 Cost Effective: It is cost-effectiveve because the cloud is shared by multiple
organizations or communities.
 Security: Community cloud provides better security.
 Shared resources: It allows you to share resources, infrastructure, etc.
with multiple organizations.
Collaboration and data sharing: It is suitable for both collaboration and
data sharing.
Disadvantages of the Community Cloud Model
  Rigid in customization: As the data and resources are shared among
different organizations according to their mutual interests if an
organization wants some changes according to their needs they cannot
do so because it will have an impact on other organizations.
 Limited Scalability: Community cloud is relatively less scalable as many
organizations share the same resources according to their collaborative
interests.

5.Multi-Cloud

 We’re talking about employing multiple cloud providers at the same time
under this paradigm, as the name implies.
 It’s similar to the hybrid cloud deployment approach, which combines public
and private cloud resources.
 Instead of merging private and public clouds, multi-cloud uses many public
clouds.
 As a result, multi-cloud deployment improves the high availability of your
services even more.

Advantages of the Multi-Cloud Model

 Reduced Latency: To reduce latency and improve user experience, you

can choose cloud regions and zones that are close to your clients.

 High availability of service: It’s quite rare that two distinct clouds would

have an incident at the same moment. So, the multi-cloud deployment

improves the high availability of your services.

Disadvantages of the Multi-Cloud Model

 Complex: The combination of many clouds makes the system complex

and bottlenecks may occur.

 Security issue: Due to the complex structure, there may be loopholes to

which a hacker can take advantage hence, makes the data insecure.

Cloud Service Models

 A Cloud computing is meant to provide variety of services and applications for

users over the internet or intranet.
  The most widespread services of cloud computing are categorised into three
service classes which are called cloud service models or cloud reference
models or working models of cloud computing.
 They are based on the abstraction level of the offered capabilities and the
service model of the CSPs. The various service models are :

• Infrastructure as a Service (IaaS)

• Platform as a Service (PaaS)

• Software as a Service (SaaS)

The three service models of cloud computing and their functions are shown in
Fig.1.10

1. Infrastructure as a service (IaaS)

 Infrastructure as a Service (IaaS) helps in delivering computer infrastructure

on an external basis for supporting operations.
 Generally, IaaS provides services to networking equipment,
devices,databases, and web servers.
 Infrastructure as a Service (IaaS) helps large organizations, and large
enterprises in managing and building their IT platforms.
 This infrastructure is flexible according to the needs of the client.

Advantages of IaaS

 IaaS is cost-effective as it eliminates capital expenses.

 IaaS cloud provider provides better security than any other software.
 IaaS provides remote access.

Disadvantages of IaaS

 In IaaS, users have to secure their own data and applications.

 Cloud computing is not accessible in some regions of the World.
2.Platform as a service (PaaS)

 Platform as a Service (PaaS) is a type of cloud computing that helps

developers to build applications and services over the Internet by providing
them with a platform.
 PaaS helps in maintaining control over their business applications.

Advantages of PaaS

 PaaS is simple and very much convenient for the user as it can be accessed
via a web browser.
 PaaS has the capabilities to efficiently manage the lifecycle.

Disadvantages of PaaS

 PaaS has limited control over infrastructure as they have less control over the
environment and are not able to make some customizations.
 PaaS has a high dependence on the provider.

3. Software as a service (SaaS)

 Software as a Service (SaaS) is a type of cloud computing model that is the

work of delivering services and applications over the Internet.
 The SaaS applications are called Web-Based Software or Hosted Software.
 SaaS has around 60 percent of cloud solutions and due to this, it is mostly
preferred by companies.

Advantages of SaaS

 SaaS can access app data from anywhere on the Internet.

 SaaS provides easy access to features and services.

Disadvantages of SaaS

 SaaS solutions have limited customization, which means they have some
restrictions within the platform.
 SaaS has little control over the data of the user.
 SaaS are generally cloud-based, they require a stable internet connection for
proper working.

Cloud infrastructure

Generic Cloud Architecture Design:

An Internet cloud is envisioned as a public cluster of servers provisioned on demand
to perform collective web services or distributed applications using data-center
resources.

 Cloud Platform Design Goals

 Enabling Technologies for Clouds
 A Generic Cloud Architecture

Cloud Platform Design Goals

 Scalability
 Virtualization
 Efficiency
 Reliability
 Security

Cloud management receives the user request and finds the correct resources. Cloud
calls the provisioning services which invoke the resources in the cloud. Cloud
management software needs to support both physical and virtual machines.

Enabling Technologies for Clouds

🞂 Cloud users are able to demand more capacity at peak demand, reduce costs,

experiment with new services, and remove unneeded capacity.

🞂 Service providers can increase system utilization via multiplexing, virtualization

and dynamic resource provisioning.

🞂 Clouds are enabled by the progress in hardware, software and networking

technologies

🞂 Cloud users are able to demand more capacity at peak demand, reduce costs,

experiment with new services, and remove unneeded capacity.

🞂 Service providers can increase system utilization via multiplexing, virtualization

and dynamic resource provisioning.
A Generic Cloud Architecture

🞂 The Internet cloud is envisioned as a massive cluster of servers.

🞂 Servers are provisioned on demand to perform collective web services using data-

center resources.

🞂 The cloud platform is formed dynamically by provisioning or deprovisioning

servers,software, and database resources.

🞂 Servers in the cloud can be physical machines or VMs.

🞂 User interfaces are applied to request services.

The cloud computing resources are built into the data centers.

🞂 Data centers are typically owned and operated by a third-party provider.

Consumers do not need to know the underlying technologies

🞂 In a cloud, software becomes a service.

🞂 Cloud demands a high degree of trust of massive amounts of data retrieved from
large data centers.

🞂 The software infrastructure of a cloud platform must handle all resource

management and maintenance automatically.

🞂 Software must detect the status of each node server joining and leaving.

🞂 Cloud computing providers such as Google and Microsoft, have built a large
number of data centers.

🞂 Each data center may have thousands of servers.

🞂 The location of the data center is chosen to reduce power and cooling costs.

Layered cloud architecture design:

The architecture of a cloud is developed at three layers: infrastructure, platform and

application as demonstrated in Figure 3.1.

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

● It is clear that the infrastructure layer is deployed first to support IaaS services.

● This infrastructure 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.

● The abstraction of these hardware resources is meant to provide the flexibility

demanded by users.

● Internally, virtualization realizes automated provisioning of resources and optimizes

the infrastructure management process.

● The platform layer 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.

● The platform should be able to assure users that they have scalability,
dependability, and security protection.

● In a way, the virtualized cloud platform serves as a “system middleware” between

the infrastructure and application layers of the cloud.

● The application layer 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.

● From the provider’s perspective, the services at various layers demand different

amounts of functionality support and resource management by providers.

● In general, SaaS demands the most work from the provider, PaaS is in the middle,
and IaaS demands the least.

● For example, Amazon EC2 provides not only virtualized CPU resources to users
but also management of these provisioned resources.

● Services at the application layer demand more work from providers.

● The best example of this is the Salesforce.com CRM service in which the provider
supplies not only the hardware at the bottom layer and the software at the top layer
but also the platform and software tools for user application development and
monitoring.

1.Market Oriented Cloud Architecture

● In Market Oriented Cloud Architecture, as consumers rely on cloud providers to

meet more of their computing needs, they will require a specific level of QoS to be
maintained by their providers, in order to meet their objectives and sustain their
operations.

● Market-oriented resource management is necessary to regulate the supply and

demand of cloud resources to achieve market equilibrium between supply and
demand.
● This cloud is basically built with the following entities:

○ Users or brokers acting on user’s behalf submit service requests from anywhere

in the world to the data center and cloud to be processed.

○ The request examiner ensures that there is no overloading of resources whereby

many service requests cannot be fulfilled successfully due to limited resources.

○ The Pricing mechanism decides how service requests are charged. For instance,

requests can be charged based on submission time (peak/off-peak), pricing rates

(fixed/changing), or availability of resources (supply/demand).

○ The VM Monitor mechanism keeps track of the availability of VMs and their

resource entitlements.

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

2.Quality of Service Factors

• The data center comprises multiple computing servers that provide

resources to meet service demands. In the case of a cloud as a commercial

offering to enable crucial business operations of companies, there are

critical QoS parameters to consider in a service request, such as time, cost,

reliability, and trust/security.

• In short, there should be greater importance on customers since they pay

to access services in clouds. In addition, the state of the art in cloud

computing has no or limited support for dynamic negotiation of SLAs

between participants and mechanisms for automatic allocation of resources

to multiple competing requests. 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 cloud also derives appropriate market-based resource management

strategies that encompass both customer-driven service management and

computational risk management to sustain SLA-oriented resource

allocation.

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

Architectural Design Challenges

Challenge 1: Service Availability and Data Lock-in Problem

● The management of a cloud service by a single company is often the source of

single points of failure.

● To achieve HA, one can consider using multiple cloud providers.

● Even if a company has multiple data centers 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.

● Criminals threaten to cut off the incomes of SaaS providers.

 The obvious 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.

Challenge 2: 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 middle boxes (e.g., firewalls,
packet filters).

● For example, the end user could encrypt data before placing it in a cloud. Many
nations have laws requiring SaaS providers to keep customer data and copyrighted
material within national boundaries.

● Another type of attack is the man-in-the-middle attack for VM migrations.

● In general, passive attacks steal sensitive data or passwords.

● On the other hand, Active attacks may manipulate kernel data structures which will

cause major damage to cloud servers.

Challenge 3: Unpredictable Performance and Bottlenecks

● Multiple VMs can share CPUs and main memory in cloud computing, but I/O
sharing is problematic.

● This demonstrates the problem of I/O interference between VMs.

● One solution is 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.

● Cloud users and providers have to think about the implications of placement and
traffic at every level of the system, if they want to minimize costs.

● This kind of reasoning can be seen in Amazon’s development of its new

CloudFront service.
● Therefore, data transfer bottlenecks must be removed, bottleneck links must
be widened and weak servers should be removed.

Challenge 4: 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 SANs.

● Data centers must meet programmer’s expectations in terms of scalability, data

durability and HA.

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

Challenge 5: Cloud Scalability, Interoperability, and Standardization

● The pay as you go model applies to storage and network bandwidth; both are
counted in terms of the number of bytes used.

● Computation is different depending on virtualization level.

● GAE automatically scales in response to load increases or decreases and the

users are charged by the cycles used.

● AWS charges by the hour for the number of VM instances used, even if the
machine is idle.

● The opportunity here is to scale quickly up and down in response to load variation,
in order to save money, but without violating SLAs.

 The user need to realize cross platform live migration between x86 Intel and

AMD technologies and support legacy hardware for load balancing.

● All these issues are wide open for further research.

Challenge 6: Software Licensing and Reputation Sharing

● Many cloud computing providers originally relied on open source software because
the licensing model for commercial software is not ideal for utility computing.

● The primary opportunity is either for open source to remain popular or simply for

commercial software companies to change their licensing structure to better fit cloud

computing.

● One can consider using both pay for use and bulk use licensing schemes to widen
the business coverage.