In short words
• Cloud computing is a phrase used to describe a
variety of computing concepts that involve a large
number of computers connected through a real-
time communication network such as the Internet.
• In science, cloud computing is a synonym for
distributed computing over a network, and
means the ability to run a program or application
on many connected computers at the same time.
• The phrase is often used in reference to network-
based services, which appear to be provided by
real server hardware, and are in fact served up
by virtual hardware, simulated by software
running on one or more real machines.
• In common usage, the term "the cloud" is
essentially a metaphor for the Internet. Marketers
have further popularized the phrase "in the cloud"
to refer to software, platforms and infrastructure
that are sold "as a service", i.e. remotely through
• …from Wikipedia
• A lot of servers
• Distributed computing
• … as a remote service
History of Computing
1960 1970 1980 1990 2000
• Service models are NOT to classify software,
platforms or products, but are to help us to
understand customers whom our customers
• There are no dependencies between each models.
All the solutions are bounded together when it is
• Private Cloud
• Public Cloud
• Community Cloud
• Hybrid Cloud
Public Cloud Services
Data source: TechRepulic
Why Cloud Computing
• Reduced time to beneﬁt
• Lower costs
• Scalability and integration
• New releases
• Easy to use and perform proof of concepts
… from IBM Thoughts on Cloud
• PaaS and IaaS
• Easy to use
• Scalable and high-performance
… from AWS
• OpenStack is a cloud operating system that
controls large pools of compute, storage, and
networking resources throughout a datacenter, all
managed through a dashboard that gives
administrators control while empowering their users
to provision resources through a web interface.
• Open source software for building private and
A Brief History
• Jointly founded in July 2010
by Rackspace and NASA
with merger of two projects:
• Swift object storage based on
Rackspace’s Cloud Files
• Nova based on Nebula compute
• Six month cycle
• The OpenStack cloud operating system enables enterprises and service providers to offer on-demand
computing resources, by provisioning and managing large networks of virtual machines.
• The compute architecture is designed to scale horizontally on standard hardware, enabling the cloud
economics companies have come to expect.
• It’s similar to Amazon EC2.
• OpenStack Compute does not include any visualization software; rather it deﬁnes drivers that interact
with underlying visualization mechanisms, as well as bare meal and high-performance conﬁgurations.
• Use Cases
• Service providers offering an IaaS compute platform or services higher up the stack
• IT departments acting as cloud service providers for business units and project teams
• Processing big data with tools like Hadoop
• Scaling compute up and down to meet demand for web resources and applications
• High-performance computing (HPC) environments processing diverse and intensive workloads
• Group A
• KVM on x86
• Qumu on x86
• Group B
• Group C
• Xen via libvirt
• LXC via libvirt
• XenAPI on x86
• See Hypervisor Support Matrix
Nova and VMware
ESXi Integration with Nova !
ESXi Integration with Nova !
• Object Storage
• Storing petabytes of data.
• A distributed storage system for static data
such as VM images, photo storage, email
storage, backups and archives.
• Storage clusters scale horizontally simply
by adding new servers.
• Block Storage
• Block level storage devices.
• Block storage is appropriate for
performance sensitive scenarios such as
database storage, expandable ﬁle
• OpenStack provides ﬂexible networking models to suit the needs of different applications or
user groups. Standard models include ﬂat networks or VLANs for separation of servers and
• OpenStack Networking manages IP addresses, allowing for dedicated static IPs or DHCP.
Floating IPs allow trafﬁc to be dynamically rerouted to any of your compute resources, which
allows you to redirect trafﬁc during maintenance or in the case of failure.
• Users can create their own networks, control trafﬁc and connect servers and devices to one or
• The pluggable backend architecture lets users take advantage of commodity gear or advanced
networking services from supported vendors.
• Administrators can take advantage of software-deﬁned networking (SDN) technology like
OpenFlow to allow for high levels of multi-tenancy and massive scale.
• OpenStack Networking has an extension framework allowing additional network services, such
as intrusion detection systems (IDS), load balancing, ﬁrewalls and virtual private networks
(VPN) to be deployed and managed.
Service Project name Description
Provides a web-based self-service portal to interact with underlying OpenStack services, such as
launching an instance, assigning IP addresses and conﬁguring access controls.
Manages the lifecycle of compute instances in an OpenStack environment. Responsibilities include
spawning, scheduling and decomissioning of machines on demand.
Enables network connectivity as a service for other OpenStack services, such as OpenStack Compute.
Provides an API for users to deﬁne networks and the attachments into them. Has a pluggable
architecture that supports many popular networking vendors and technologies.
Object Storage Swift
Stores and retrieves arbitrary unstructured data objects via a RESTful, HTTP based API. It is highly fault
tolerant with its data replication and scale out architecture. Its implementation is not like a ﬁle server
with mountable directories.
Block Storage Cinder
Provides persistent block storage to running instances. Its pluggable driver architecture facilitates the
creation and management of block storage devices.
Identity Service Keystone
Provides an authentication and authorization service for other OpenStack services. Provides a catalog of
endpoints for all OpenStack services.
Image Service Glance
Stores and retrieves virtual machine disk images. OpenStack Compute makes use of this during instance
Telemetry Ceilometer Monitors and meters the OpenStack cloud for billing, benchmarking, scalability, and statistical purposes.
Orchestrates multiple composite cloud applications by using either the native HOT template format or
the AWS CloudFormation template format, through both an OpenStack-native REST API and a
CloudFormation-compatible Query API.
• April 17, 2014: Icehouse Software Release
• May 13-16, 2014: Juno Release Design Summit
• October 2014: Juno Software Release
• November 5-8, 2014: "K" Release Design Summit
• New Capabilities
• Database Service (Trove) - Scalable and reliable cloud database as a service provisioning
functionality for both relational and non-relational database.
• Bare Metal (Ironic) - Provides an API for management and provisioning of physical machines.
• Queue Service (Marconi)
• Data Processing (Savannah) - Hadoop on OpenStack
Hadoop vs OpenStack
• Each of them presents total different philosophy.
• Hadoop is designed to scalable and distributed computing.
• OpenStack is designed to manage and control a large pool
of compute, storage and networking resources throughout
HDFS vs Swift
• HDFS uses a central system to maintain ﬁle metadata (Namenode), where as in
Swift the metadata is distributed and replicated across the cluster. Having a
central meta-data system is a single point of failure for HDFS, and makes it
more difﬁcult to scale to very large sizes.
• Swift is designed with multi-tenancy in mind, where HDFS has no notion of
• HDFS is optimized for larger ﬁles (as is typical for processing data), where
Swift is designed to store any sized ﬁles.
• Files in HDFS are write once, and can only have one writer at a time, in Swift
ﬁles can be written many times, and under concurrency, the last write wins.
• HDFS is designed to store a medium number of larges ﬁles to support data
processing, where Swift is designed as a more generic storage solution to
reliably store very large numbers of varying sized ﬁles.
vSphere vs OpenStack
• vSphere originated
as a way to provide
originated as a way
vSphere vs OpenStack
• Virtual machines and
• Custom VMs and ﬂavors
• Templates and images
• Virtual disks and volumes
• vMotion and instance
• Monolithic architecture
• Ugly community support
• The true state of cloud adoption.
• See downloaded slide.
• Internal project name: Laika
• Focus on Object Storage at ﬁrst
• Easily and quickly deployment and conﬁguration
• Integrated with existing software like VMware in enterprise
• OpenStack for SynDriver
• OpenStack for VDI