Porto Linux June 2014
1/35
Cloud Vision
& OpenStack
Rui Gouveia
EMEA Cloud Inside Solution Architect
[email protected]
Porto Linux June 2014
2/35
About me
●
Linux Enthusiast since the 90's (~1992 – RH5).
●
Joined Red Hat GSS in May 2012 (RHCE,RHCVA).
●
Supported RHEL base and IdM services.
●
Before transfer started training in Cloud Products.
●
Transfer to Inside Solution Architect team in Jan 2014.
●
As “the cloud guy”.
●
Started with OpenShift, but helps with OpenStack,
CloudForms, and all other products when needed.
Porto Linux June 2014
3/35
OPEN SHIFT ENTER PRISE RELEA SED FUSES OURC E & PO LYMITA ACQU IRED PLATIN UM ME MBER OPEN STACK FOUN DATIO N RED H AT STO RAGE RELEA SED CLOU DFOR MS & O PENS HIFT R ELEAS ED RED H AT EN TERPR ISE VIR TUALI ZATION RE LEASE D JOINS S&P 5 00
OPEN
SOURCE
LEADER
#
1
199319992002 2007 2010 2011 FOUN DED IPO FIRST RELEA SE OF ENTER PRISE LINUXJBO SS EA P 4.2 R ELEAS ED MAKA RA AC QUIRE D 2012CEO JIM WHITEHURST
2009 $1 BIL LION IN REVE NUE OFFICES WORLDWIDE
90%
MORE THANFORTUNE
500
COMPANIES
of
use
PRODUCTS & SOLUTIONS. *RED HAT
2013 MANA GEIQ ACQU IRED* Red Hat client data, 2013
RHEL OPEN STACK PLATF ORM & OP ENSTA CK PA RTNE R PROG RAM 2014 CENTOS JOINS RED H AT
0 50 100 150 200 250 300 350 400
RED HAT
FY '04 FY '06 FY '08 FY '10 FY '12 FY '1490%
MORE THANFORTUNE
500
COMPANIES
of
use
PRODUCTS & SOLUTIONS.RED HAT
OPEN SHIFT ENTE RPRIS E REL EASE D FUSE SOUR CE & POLY MITA A CQUIR ED RED H AT EN TERP RISE V IRTUA LIZAT ION RE LEAS ED JOINS S&P 5 00 199319992002 2007 2010 2011 FOUN DED FIRST RELE ASE O F ENT ERPR ISE LIN UX 2012 2009 2013 MANA GEIQ ACQU IRED RHEL OPEN STAC K PLA TFOR M & OP ENST ACK P ARTN ER PROG RAMPorto Linux June 2014
RED HAT SUBSCRIPTION MODEL
AWARD-WINNING SUPPORT MULTI-LINGUAL 24x7 UNLIMITED INCIDENTS MISSION-CRITICAL MULTI-VENDOR CASE OWNERSHIP GLOBAL SUPPORT SERVICES CUSTOMER PORTAL & FORUMS KNOWLEDGEBASE HARDWARE CERTIFICATION SOFTWARE CERTIFICATION OPTIONAL TRAINING CURRICULA AVAILABLE STABILITY WITH A PRODUCT LIFE CYCLEOF UP TO 10 YEARS SOFTWARE ASSURANCE SECURITY RESPONSE TEAM SOFTWARE ASSURANCE UPDATES PATCHES UPGRADES YEARS AWARDED: 2011 2012 2013
Porto Linux June 2014
8/35
Porto Linux June 2014
9/35
Cloud Computing by Stephen Fry
Youtube Video:
Porto Linux June 2014
10/35
Summary of Cloud features
●
Utility.
●
On demand.
●
The amount I need.
●When I need it.
●
Pay only for resources used.
11
Electricity went from customized and
differentiated…
12
To standardized
and commoditized
with economies
14
“...a model for enabling convenient,
on-demand
network access to a
shared pool
of
configurable
computing resources
(e.g., networks, servers,
storage, applications, and services) that can be
rapidly provisioned
and released
with minimal
management effort or service provider interaction
.”
15
Cloud Service Models
STORAGE
(RHS)
HARDWARE
(x86)
VIRTUALIZATION
(RHEV)
OPERATING SYSTEM
(RHEL)
APPLICATION PLATFORM
(JBOSS, PHP, RUBY, ETC)
APPLICATION
Managed by the Public
or Private Cloud Ofering
Managed and
Controlled by Customer
(IT, Dev, or User)
IaaS
PaaS
SaaS
Increased Control
Reduced DIY
16
Cloud Service Models
Software-as-a-Service (SaaS)
(hosted apps)
Platform-as-a-Service (PaaS)
(dev platform, apps middleware)
Infrastructure-as-a-Service (IaaS)
(compute, storage, network)
End-users
Developers
DevOps
IT Admins
Amazon AWS
RackSpace
OpenStack
vCloud Director
OpenShift
Force.com
Heroku
Google Apps
Salesforce
Many more
IaaS
PaaS
SaaS
Porto Linux June 2014
17/35
Models
Porto Linux June 2014
18/35
Porto Linux June 2014
19/35
A different kind of architecture...
TRADITIONAL WORKLOADS
● Stateful virtual machines
● Big VMs: vCPU, vRAM, local storage
inside VM
● Application SLA aligned to VM itself
● Relies on underlying HA technology to
meet SLA goals
● VMs scale up: add vCPU, vRAM, etc.
● Applications not designed to tolerate
failure of VMs
CLOUD WORKLOADS
● Stateless VMs, application distributed
● Small VMs: vCPU, vRAM, storage
separate
● Application SLA not dependent on any
one VM
● Many instances can provide application
availability
● Applications scale out: add more VMs
● Applications designed to tolerate failure of VMs
20
Analogy: Pets vs. farm animals
PETS =
TRADITIONAL WORKLOADS
FARM ANIMALS =
CLOUD WORKLOADS
Credit : Tim Bell @ CERN Labs, Bill Baker @ Microsoft, and others
Pets are given names like
rover.internal.redhat.com
They are unique, lovingly
hand raised and cared for
When they get ill you nurse
them back to health
Farm animals have tag
numbers like
piggie242.redhat.com
They are almost identical
to each other
When they get ill you get
21
Manufacturing as a Model for IT
Consolidated Aircraft B-24
Liberator
Incredibly sophisticated. ~500k parts,
assembled by unskilled labor.
No Mfg process. Parts were cast in rubber
molds, so every part was slightly
diferent.
Assembled in the heat of San Diego,
which warped the metal and required
whole assemblies to be adjusted.
Ford Motor Co. brought a Manufacturing
process … went from 250 planes a year to
650 planes a month.
Porto Linux June 2014
22/35
Red Hat Enterprise Linux
OpenStack Platform
Porto Linux June 2014
23/35
Porto Linux June 2014
24/35
OpenStack Components
●
Needs to access x86 hardware resources
●
Runs on Linux and requires access to existing technologies
●
e.g. a hypervisor, some storage and networking
Porto Linux June 2014
25/35
Porto Linux June 2014
26/35
Porto Linux June 2014
27/35
Common OpenStack Architecture
●
All data is held in a SQL database
●
Can be made highly-available if replicated
●Default is MySQL, but others are supported
●Components have two sub-component types:
●
API
Endpoints
– The RESTful entry-point into the component
●One or more 'daemons' – The services that carry out instructions
●Vast majority of OpenStack is
shared-nothing
and very
fault-tolerant
●
Components scale out using shared message bus (qpid, RabbitMQ etc)
●API Endpoints can be load-balanced (virtual IP's) for resilience/throughput
Porto Linux June 2014
28/35
Porto Linux June 2014
29/35
Why does the world need OpenStack?
●
Cloud is widely seen as the next-generation IT delivery model
●
Agile & flexible
●
Utility-based on-demand consumption
●
Self-service drives down overhead and maintenance
●
Public clouds setting the benchmark, organisations want the same level of
functionality but behind the firewall
●
Not all organisations are ready for public cloud
●Applications are being built differently
today-●
More tolerant of failure
●
Make use of scale-out elastic architectures
Porto Linux June 2014
30/35OpenStack distributions
●RackSpace
●Debian, Ubuntu
●OpenSUSE, SUSE
●Mirantis
●DevStack
●
RHEL, Fedora, RDO
Porto Linux June 2014
31/35
OpenStack Progression
● Enterprise-hardened
OpenStack software
● Delivered with an enterprise life
cycle
● Six-month release cadence
offset from community releases to allow testing
● Aimed at long-term production
deployments
● Certified hardware and
software through the Red Hat OpenStack Cloud Infrastructure Partner Network
● Supported by Red Hat
● Installs on Red Hat Enterprise
Linux only
● Latest OpenStack software,
packaged in a managed open source community
● Facilitated by Red Hat
● Aimed at architects and
developers who want to create, test, collaborate
● Freely available, not for sale
● Six-month release cadence
mirroring community
● No certification, no support
● Installs on Red Hat and
derivatives
● Open source,
community-developed (upstream) software
● Founded by Rackspace Hosting
and NASA
● Managed by the OpenStack
Foundation
● Vibrant group of developers
collaborating on open source cloud infrastructure
● Software distributed under the
Apache 2.0 license
Porto Linux June 2014
Porto Linux June 2014
33/35
OpenStack Red Hat Contribution
Porto Linux June 2014
34/35
WHY RED HAT OPENSTACK ?
●
Experience in managing Open Source communities.
●
Being leader in the core development of OpenStack brings in-house
know-how second to none.
●
Open Standards makes Red Hat one of the few company's that offer
non lock-in solutions to customers.
●
Compatible API's allows Red Hat Customer to Scale-out their
environment even to third-party clouds (Hybrid Cloud).
●
Complete Cloud portfolio.
●
Enterprise-grade version of OpenStack with the ecosystem, life-cycle,
and support that customers expect from Red Hat!
●
Longer supported life-cycle
Starts with two years for Folsom, Grizzly, or Havana
●
