CC-Module 3 (2)
CC-Module 3 (2)
ARCHITECTURE OVER
VIRTUALIZED DATA CENTERS
CLOUD COMPUTING AND SERVICE MODELS:
• Over the past two decades, the world economy has rapidly moved from manufacturing to
more service-oriented.
• Cloud computing benefits the service industry most and advances business computing
with a new paradigm.
• Developers of innovative cloud applications no longer acquire large capital equipment in
advance. They just rent the resources from some large datacenters that have been
automated for this purpose.
Cloud computing can be classified
1. By deployment models
• Public
• Private
• Hybrid
2. Types of services offered
• IaaS
• PaaS
• SaaS
PUBLIC CLOUD:
• A public cloud is built over the Internet and can be accessed by any user who has paid for the service.
• Public clouds are owned by service providers and are accessible through a subscription.
• The providers of the clouds are commercial providers that offer a publicly accessible remote interface for
creating and managing VM instances within their proprietary infrastructure.
• A public cloud delivers a selected set of business processes.
• The application and infrastructure services are offered on a flexible price-per-use basis.
Examples:
• Google App Engine (GAE)
• Amazon Web Services (AWS)
• Microsoft Azure
• IBM Blue Cloud
• Salesforce.com’s Force.com.
Advantages:
• Standardization
• Preserves Capital Investment
• Offers Application Flexibility
PRIVATE CLOUD:
• A private cloud is built within the domain of an intranet owned by a single organization.
• It is client owned and managed, and its access is limited to the owning clients and their partners.
• Its deployment was not meant to sell capacity over the Internet through publicly accessible interfaces.
• Private clouds give local users a flexible and agile private infrastructure to run service workloads within
their administrative domains.
• A private cloud is supposed to deliver more efficient and convenient cloud services.
• It may impact the cloud standardization, while retaining greater customization and organizational control.
Examples:
• IBM RC2
• Amazon Virtual Private Cloud
• VMware Private Cloud
• Rackspace Private Cloud (Powered by OpenStack)
• CloudBees
Advantage:
• Customization & offers higher efficiency
• Resiliency
• Security
• Privacy
HYBRID CLOUDS:
• A hybrid cloud is built with both public and private clouds as in fg4.1
• Private clouds can also support a hybrid cloud model by supplementing local
infrastructure with computing capacity from an external public cloud.
• A hybrid cloud provides access to clients, the partner network, and third parties.
• Hybrid clouds operate in the middle, with many compromises in terms of resource
sharing.
Example:
• Research Compute Cloud (RC2) is a private cloud, built by IBM, that interconnects the
computing and IT resources at eight IBM Research Centers scattered throughout the
United States, Europe, and Asia.
Data-Center Networking Structure:
CLOUD SERVICES:
The services provided over the cloud can be generally categorized into three different service models: namely
1. Infrastructure as a Service(IaaS),
2. Platform as a Service (PaaS),
3. Software as a Service (SaaS).
1. Infrastructure as a Service(IaaS):
• This model allows users to use virtualized IT resources for computing, storage, and networking.
• The service is performed by rented cloud infrastructure.
• The user can deploy and run his applications over his chosen OS environment.
• The user does not manage or control the underlying cloud infrastructure, but has control over the OS,
storage, deployed applications, and possibly select networking components.
• This IaaS model encompasses storage as a service, compute instances as a service, and communication as a
service.
• Many startup cloud providers have appeared in recent years. GoGrid, FlexiScale, and Aneka are good
examples.
Platform as a Service (PaaS):
• To be able to develop, deploy, and manage the execution of applications using
provisioned resources demands a cloud platform with the proper software environment.
• Such a platform includes operating system and runtime library support. This has triggered
the creation of the PaaS model to enable users to develop and deploy their user
applications.
• The platform cloud is an integrated computer system consisting of both hardware and
software infrastructure.
• The user application can be developed on this virtualized cloud platform using some
programming languages and software tools supported by the provider (e.g., Java, Python,
.NET).
• The user does not manage the underlying cloud infrastructure. The cloud provider
supports user application
Software as a Service (SaaS):
• This refers to browser-initiated application software over thousands of cloud customers. Services and tools
offered by PaaS are utilized in construction of applications and management of their deployment on
resources offered by IaaS providers.
• The SaaS model provides software applications as a service. As a result, on the customer side, there is no
upfront investment in servers or software licensing.
• On the provider side, costs are kept rather low, compared with conventional hosting of user applications.
Customer data is stored in the cloud that is either vendor proprietary or publicly hosted to support PaaS and
IaaS.
Examples of SaaS:
• Google Gmail and docs
• Microsoft SharePointa
• CRM software from Salesforce.com.
Case Studies of Service Models
Case Study 1: Netflix (IaaS)
• Netflix runs its streaming service on Amazon Web Services (AWS) using EC2 for compute and S3 for storage.
• This allows Netflix to handle high traffic and scale dynamically.
Case Study 2: Heroku (PaaS)
• Heroku, a cloud platform for developers, provides a fully managed runtime environment that simplifies application
deployment, allowing startups and enterprises to quickly build and scale applications.
Case Study 3: Google Workspace (SaaS)
• Google Workspace (formerly G Suite) offers cloud-based email, document editing, and collaboration tools, reducing IT
overhead and improving productivity.
Benefits and Challenges of Each Service Model
Service Model Benefits Challenges
PaaS Faster development, automated management Limited customization and vendor lock-in
SaaS Easy to use, minimal maintenance Data security concerns, limited control
over infrastructure
CLOUD ECOSYSTEM AND ENABLING TECHNOLOGIES:
CLOUD DESIGN OBJECTIVES:
The following list highlights six design objectives for cloud computing:
• Shifting computing from desktops to data centers Computer processing, storage, and software delivery is
shifted away from desktops, local servers and towards data centers over the Internet.
• Service provisioning and cloud economics Providers supply cloud services by signing SLA(service level
agreement) with consumers and end users. The services must be efficient in terms of computing, storage
and power consumption. Pricing is based on a pay-as-you-go policy.
• Scalability in performance The cloud platforms and software and infrastructure services must be able to
scale in performance as the number of users increases.
• Data privacy protection Can you trust data centers to handle your private data and records? This concern
must be addressed to make clouds successful as trusted services.
• High quality of cloud services The QoS of cloud computing must be standardized to make clouds
interoperable among multiple providers.
• New standards and interfaces This refers to solving the data lock-in problem associated with data centers
or cloud providers. Universally accepted APIs and access protocols are needed to provide high portability
and flexibility of virtualized applications
Cloud Ecosystems:
DATA-CENTER DESIGN AND INTERCONNECTION NETWORKS
• Data-Center Construction Requirements
Cooling System of a Data-Center Room
Data-Center Interconnection Networks
A Fat-Tree Interconnection Network for Data Centers
Data-Center Management Issues
The basic requirements for managing the resources of a data center are as follows:.
• Making common users happy: The data center should be designed to provide quality service to
the majority of users for at least 30 years.
• Controlled information flow: Information flow should be streamlined. Sustained services and
high availability (HA) are the primary goals.
• Multiuser manageability: The system must be managed to support all functions of a data center,
including traffic flow, database updating, and server maintenance.
• Scalability: to prepare for database growth. The system should allow growth as workload
increases. The storage, processing, I/O, power, and cooling subsystems should be scalable.
• Reliability: in virtualized infrastructure Failover, fault tolerance, and VM live migration should be
integrated to enable recovery of critical applications from failures or disasters.
• Low cost: to both users and providers The cost to users and providers of the cloud system built
over the data centers should be reduced, including all operational costs.
• Security enforcement and data protection: Data privacy and security defense mechanisms must
be deployed to protect the data center against network attacks and system interrupts and to
maintain data integrity from user abuses or network attacks.
• Green information technology Saving power consumption and upgrading energy efficiency are in
high demand when designing and operating current and future data centers.
ARCHITECTURAL DESIGN OF COMPUTE AND STORAGE CLOUDS
LAYERED CLOUD ARCHITECTURAL DEVELOPMENT:
A Generic Cloud Architecture
Market-Oriented Cloud Architecture
• The SLA resource allocator acts as the interface
between the data center/cloud service provider and
external users/brokers. It requires the interaction of
the following mechanisms to support SLA-oriented
resource management.
• When a service request is first submitted the service
request examiner interprets the submitted request
for QoS requirements before determining whether
to accept or reject the request.
• The request examiner ensures that there is no
overloading of resources whereby many service
requests cannot be fulfilled successfully due to
limited resources.
• It also needs the latest status information regarding
resource availability (from the VM Monitor
mechanism) and workload processing (from the
Service Request Monitor mechanism) in order to
make resource allocation decisions effectively.
• Then it assigns requests to VMs and determines
resource entitlements for allocated VMs.
• 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).
• 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.
• 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.
• 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 requests.
• In addition, multiple VMs can concurrently
run applications based on different
operating system environments on a single
physical machine since the VMs are isolated
from one another on the same physical
machine
VIRTUALIZATION SUPPORT AND DISASTER RECOVERY
• One very distinguishing feature of cloud computing infrastructure is the use of system virtualization and
the modification to provisioning tools. Virtualization of servers on a shared cluster can consolidate web
services.
• As the VMs are the containers of cloud services, the provisioning tools will first find the corresponding
physical machines and deploy the VMs to those nodes before scheduling the service to run on the
virtual nodes.
• In addition, in cloud computing, virtualization also means the resources and fundamental infrastructure
are virtualized. The user will not care about the computing resources that are used for providing the
services. Cloud users do not need to know and have no way to discover physical resources that are
involved while processing a service request.
VM CLONING FOR DISASTER RECOVERY
• VM technology requires an advanced disaster recovery scheme. One scheme is to recover one physical
machine by another physical machine. The second scheme is to recover one VM by another VM.
• Traditional disaster recovery from one physical machine to another is rather slow, complex, and
expensive. Total recovery time is attributed to the hardware configuration, installing and configuring the
OS, installing the backup agents, and the long time to restart the physical machine.
PUBLIC CLOUD PLATFORMS: GAE, AWS, AND AZURE
AMAZON WEB SERVICES (AWS)
WHAT IS AZURE?
Microsoft Windows Azure platform for cloud computing
• Cloud- level services provided by the Azure platform are
• Live service: Users can visit Microsoft Live applications and apply the data
involved across multiple machines concurrently.
• .NET service: This package supports application development on local
hosts and execution on cloud machines.
• SQL Azure : This function makes it easier for users to visit and use the
relational database associated with the SQL server in the cloud.
• SharePoint service: This provides a scalable and manageable platform for
users to develop their special business applications in upgraded web
services.
• Dynamic CRM service: This provides software developers a business
platform in managing CRM applications in financing, marketing, and sales
and promotions.
Azure services
4.5 INTER-CLOUD RESOURCE MANAGEMENT