Cloud Computing

(DS3104)
Part - 1

Presented By:
Dr. Sukhwinder Sharma
Associate Professor
Department of Data Science and Engineering
Manipal University Jaipur, Jaipur
Syllabus
 Introduction to Cloud Computing
Virtualization and Infrastructure as a service
Hyper Converged Infrastructure
Introduction to Cloud Computing
Edge vs Fog vs Cloud
What is Cloud
Computing?
It is a techno-business
disruptive model of using
distributed large-scale data
centers either private or public
or hybrid offering customers a
scalable virtualized
infrastructure or an abstracted
set of services qualified by
service-level agreements
(SLAs) and charged only by the
abstracted IT resources
consumed.
What comprises
Cloud Computing?
• NIST Visual Model of
Cloud Computing
Essential
Characteristics
What comprises
Cloud Computing?
• NIST Visual Model of
Cloud Computing
 • Service Models are the
Service Reference Models on which
the Cloud Computing is Based.
Models
Products at
each
Service
Level
Cloud
Infrastructure
• Infrastructure
• Platform
• Application
Infrastructure as
a Service (IaaS)
 On premise
Data Centers
• Key Challenges
• Capital expenditure to purchase physical
and digital assets
• Building
• People
• Expansion
Given the current state of extreme weather events
impacting all areas of the globe – a single on-premise
data center can appear quite vulnerable; something may
occur nearby that server’s power, floods the grounds, or
limits access to the facility.
 • With Infrastructure as a
Service – Data Center
manages the physical
IaaS infrastructure required to
run a proper data
center.
IaaS
• With Data Center owning responsibility for the physical infrastructure – in an
infrastructure as a service model – the business manages everything else.
• A good conceptual model of this would be using Azure to spin up virtual machines
upon which the business installs and maintains all of the necessary software and tools
(i.e. SQL Server, Windows, etc)
• Here the business still retains responsibility for upgrading software, installing patches,
etc. They are essentially renting space from which to do this.
• What you gain: Computer/Server
• Consumer: SysAdmins
• Examples: Rackspace.com, Go Grid, Amazon Web Services (AWS)
• The advantages of IaaS versus On-premise
•Pay for what you use •Better ability to scale and grow IT workloads
•Improved stability and reliability •Reduction of capital expenditures
•Better disaster recovery •Future proof
•Better security •Free up IT staff
 PaaS
• Platform as a Service is the next natural iteration of cloud
computing.
• In this model, Data Centre manages all the physical
infrastructure, as well the software tools to connect to that
infrastructure. The business manages tools they wish to use
within that framework, but is not responsible for software
upgrades to the tool.
• So in the chart above – the business brings the data and pays
to provision the desired data application, but is not responsible
for patching the SQL Server running the database or upgrading
it when a new version is released. This is all handled by Data
Centre.
• What you gain: Application/Framework
• Consumer: App Developers
• Examples: force.com, Google App Engine, Microsoft Azure
Advantages of PaaS
• Affordable access to sophisticated tools
• Faster development
• Easy management of application lifecycle
Software as a Service
(SaaS)
• Software as a Service is Data Centre providing a complete
software package end to end.
• They manage everything.
• Some great examples here would be Teams, OneDrive,
Outlook, and Skype.
• We just interact with these tools, and have little control in
how they are designed, deployed, or managed.
• What you gain: Business Functionality
• Consumer: End Users
• Examples: Google Docs/Gmail, FreshBooks, Salesforce, BaseCamp
Anything as a
Service (XaaS)
• This only makes sense as the idea is to
leverage nearly any technology
product – as a service.
• This section could be extensive – but
let’s try to lay a foundation for what
the future will bring as the movement
of physical hardware to the cloud
continues.
• Desktop as a Service
• IoT as a Service
What comprises
Cloud Computing?
• NIST Visual Model of
Cloud Computing
Cloud Deployment
Models

• Public: Infrastructure made available to general public or large industry

group; owned by the organization selling the service
• Private: Infrastructure operated solely for a single organization; may be
managed by the organization or a third party; may be located on-
premise or off-premise
• Community Cloud: Infrastructure is shared by several organizations and
supports a specific community that has shared concerns (e.g. mission,
security requirements, policy, compliance etc.); may be managed by the
organization or a third party; may be located on-premise or off-premise
• Hybrid/ Multi-Cloud: Infrastructure is a composition of two or more
clouds; remain unique entities but bound together by standardized or
proprietary technology that enable data and application portability
Cloud Deployment Models
Why adopt Cloud Computing?
• Scalability
• Organizations have access to many resources that scale based on user demand.
• Elasticity
• Organizations can request, use, and release as many resources as needed based on
changing needs
• Virtualization
• Each user has a single view of the available resources, independently of how they are
arranged in terms of physical devices
• Lower Infrastructure Cost
• The pay-per-use model allows an organization to only pay for the resources they
need with basically no investment in the physical resources available in the cloud.
There are no infrastructure maintenance or upgrade costs
Why adopt Cloud Computing?
• Availability
• Organizations have the ability for the user to access data and applications from
around the globe
• Collaboration
• Organizations are starting to see the cloud as a way to work simultaneously on
common data and information
• Risk Reduction
• Organizations can use the cloud to test ideas and concepts before making major
investments in technology
• Reliability
• In order to support SLAs, cloud providers have reliability mechanisms that are much
more robust than those that could be cost-effectively provided by a single
organization
Barriers to Cloud Adoption
• Security – organizations do not have control of or know where their data is
being stored
• Interoperability – universal set of standards and/or interfaces has not yet
been defined, resulting in a significant risk of vendor lock-in
• Resource Control – amount of control that the organization has over the
cloud environment varies greatly
• Latency - all access done via internet, latency into every communication
between the user and the environment
• Platform or Language Constraints – support for specific platforms and
languages only
• Legal Issues – concerns over jurisdiction, data protection, fair information
practices, and international data transfer
Virtualization
• Separation of OS from Hardware
• Ability to easily move OS (including Applications & Settings) to new
physical hardware
• Accomplished with Virtualization Software
• Client Installed Virtualization
• Hypervisors
Client Installed
Virtualization
• A piece of software that's
installed on physical
endpoints or clients such
as laptops, desktops,
tablets, phones, thin
clients, and more.
• It enables these endpoints
to run virtual applications.
Hypervisor
• More powerful than
Client Installed
Virtualization Software
• Provides high reliability
for critical services (e.g.
MS Exchange Server)
 Hypervisor Two-part
Solution
(Hypervisor and
Management Software)

• Hypervisor is installed on the physical server

hardware • Management Software is installed on an Admin Computer
• It’s like a thin OS
• Purpose: Configure each virtual machine, or instance and
• Only provides rudimentary connection info (IP provide fault tolerance
Address, Computer Name, etc) for the
management software • Connects to the hypervisor installed on server(s)
• Supports installation of OS’s when installing • Allows creation of the virtual computer instances on the
computer instances server
Software(s): • Create virtual disk partitions, allocate memory, install OS
Hypervisor – VMWare, Citrix (Free/Open Source) • Instances can be copy/paste to any other server on
Management – Lite Version (free), Fault Tolerance and network running compatible hypervisors
other features (Paid)
• On-the-fly reconfiguration when hardware fails
What is Hyper Converged Infrastructure?
• Hyper Converged Infrastructure (Also called HCI in short)
combines storage, computing and networking into a single
system to reduce complexity and increase scalability.
• Hyper Converged platforms use a hypervisor for virtualized
computing, software-defined storage and network virtualization.
• Multiple nodes are combined to form a pool of shared compute
and storage resources designed for convenient consumption.

“Hyper Converged infrastructure is a software-defined, unified

system that combines all the elements of a traditional data
center: storage, compute, networking, and management.”
Traditional vs Converged vs Hyper Converged
• A traditional multi-tiered datacenter (legacy or non converged
infrastructure) requires by design that server (compute), storage and
networking components be individually configured and linked together.
Usually a dedicated IT team would be responsible for managing a single
component which can become costly and complex.
• In contrast a converged infrastructure (CI) will deliver all of these separate
components build and unified into one physical appliance out of the box.
Therefore enterprises will reduce costs associated with cabling, cooling,
power and hiring dedicated teams of IT professionals.
• On the other hand, hyperconverged infrastructure (HCI) uses intelligent
software to combine x86-based server and storage resources into a 100%
software-defined solution.
Background
• Modern businesses rely on the data center to provide the computing,
storage, networking and management resources that are necessary to host
vital enterprise workloads and data.
• But data centers can be notoriously complex places where a multitude of
vendors compete to deliver myriad different devices, systems and
software.
• This heterogeneous mix often struggles to interoperate -- and rarely
delivers peak performance for the business without careful, time-
consuming optimizations.
• Today, IT teams simply don't have the time to wrestle with the deployment,
integration and data center management challenges posed by traditional
heterogeneous environments.
Background
• The notion of convergence originally arose as a means of addressing
the challenges of heterogeneity.
• Early on, a single vendor would gather the systems and software of
different vendors into a single pre-configured and optimized set of
equipment and tools that was sold as a package. This was known as
converged infrastructure, or CI.
• Later, convergence vendors took the next step to design and produce
their own line of prepackaged and highly integrated compute, storage
and network gear for the data center. It was an evolutionary step now
called hyper-converged infrastructure, or HCI.
Benefits of HCI
• HCI delivers simplicity and flexibility, scalability, data security as compared
with legacy infrastructure.
• Integrated storage, servers and networking devices are designed to be
managed as a single entity across all instances of a hyper converged
infrastructure.
• Hyper Converged environment is cost savings in areas including data center
power and space.
• Key benefits are
• Management Efficiency
• Data Efficiency
• High Availability
• Scalability
• Data Protection
Comparing Traditional Storage and Hyper
Convergence
• In comparison with the traditional storage infrastructure, Hyper
Convergence offers the following 5 benefits over traditional infrastructure:
• Hyper Convergence provides single point of administration, monitoring and control
on storage, servers and virtual infrastructure.
• Hyper Convergence provides lower cost of infrastructure due to both the elimination
of dedicated SAN/NAS and the greater efficiencies of management.
• Hyper Convergence provides highly available storage and compute that built-in and
available should a node fail.
• Hyper Convergence provides included data protection in the form of wide-striping
and replication.
• Hyper Convergence provides reduced cost (through eliminating dedicated storage
maintenance and support contracts), greater utilization of servers and storage,
increased uptime, and inclusion of advanced features.
Advantages of Hyper Convergence vs.
Traditional Three-Tier Architecture
• Lower costs: Reduces storage footprint, power use and maintenance costs.
• Simplicity and agility: Hyper Converged systems can be deployed in a fraction of the time
as compare to traditional infrastructure. And there’s no need for specialists for
implementation.
• Performance: Hyper Convergence renders high levels of performance. Many
organizations use hyper converged apps and SQL Server for their best performance.
• Flexible scaling: Hyper Converged infrastructure scales easily. New resources are
identified and integrated into the cluster quickly.
• MultiCloud support: Hyper Convergence reduces the time and cost of transitioning to a
hybrid cloud. Easy to move data and applications between on-premises servers and the
public cloud.
• Security and data protection: On-premises IT infrastructure is more secure than other
options. Security features including self-encrypting drives and tools that provide high
levels of visibility. Backup and DR are also built in feature.
Disadvantages of Hyper Convergence
• Cost to add compute in hyper converged infrastructure is high.
• Adding Hyper Convergence is more expensive than adding
incremental compute/storage to traditional system.
• Vendor Lock-in for all the Infrastructure types i.e. Network, Compute
and Storage.
What challenges will Hyper Convergence
resolve?
• By centralizing resources and management, Hyper Convergence
resolves the Lowers cost, Reduces Complexity, less staff burdens and
high performance.
 Hyper
converged
Infrastructure
Hyper-converged
infrastructure is a
software-centric
architecture that tightly
integrates compute,
storage and
virtualization resources
in a single system that
usually consists of x86
hardware.
Final Thoughts
• Cloud Computing is in essence an economical model
• It is a different way to acquire and manage IT resources
• There are multiple cloud providers – the cloud is real
• Currently most cloud consumers are small enterprises
• Large enterprises are exploring private clouds
• The number of providers will most probably grow as people start seeing greater
savings and improvements to reduce adoption barriers
• Cloud computing adoption requires cost/benefit/risk analysis to determine
• What resources to move to the cloud (if any)
• What situations warrant use of cloud resources, even for one-time situations
• Implementation of private clouds vs usage of public clouds
• What risks are associated with using resources on the cloud
• What risks are associated to providing resources in the cloud
Final Thoughts
• Decisions from a cloud consumer perspective depend on
• Required control level
• Required Security level
• Compatibility with local infrastructure
• Decisions from a cloud provided perspective depend on
• Market/user characteristics
• Established SLAs
• Available Technology