cloud vision & openstack - dcc.fc.up.ptfds/aulas/cp/1415/slides/cloud-openstack.pdf · cloud...
TRANSCRIPT
Porto Linux June 20141/35
Cloud Vision
& OpenStack
Rui GouveiaEMEA Cloud Inside Solution [email protected]
Porto Linux June 20142/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.
OPENSHIFT ENTERPRISE RELEASED
FUSESOURCE & POLYMITA ACQUIRED
PLATINUM MEMBER OPENSTACK FOUNDATION
RED HAT STORAGE RELEASED
CLOUDFORMS & OPENSHIFT RELEASED
RED HAT ENTERPRISE VIRTUALIZATION
RELEASED
JOINS S&P 500
OPENSOURCELEADER
#1
199319992002 2007 2010 2011
FOUNDED
IPO FIRST RELEASE OF ENTERPRISE
LINUXJBOSS EAP 4.2 RELEASED
MAKARA ACQUIRED
2012
CEO JIM WHITEHURST
2009
$1 BILLION IN REVENUE
OFFICES WORLDWIDE
90%MORE THAN
FORTUNE500COMPANIES
of
use
PRODUCTS & SOLUTIONS. *
RED HAT
2013
MANAGEIQ ACQUIRED
* Red Hat client data, 2013
RHEL OPENSTACK PLATFORM &
OPENSTACK PARTNER
PROGRAM
2014
CENTOS JOINS RED HAT
0
50
100
150
200
250
300
350
400
RED HAT
FY '04 FY '06 FY '08 FY '10 FY '12 FY '14
90%MORE THAN
FORTUNE500COMPANIES
of
use
PRODUCTS & SOLUTIONS.
RED HAT
OPENSHIFT ENTERPRISE RELEASED
FUSESOURCE & POLYMITA ACQUIRED
RED HAT ENTERPRISE VIRTUALIZATION
RELEASED
JOINS S&P 500
199319992002 2007 2010 2011
FOUNDEDFIRST RELEASE OF ENTERPRISE
LINUX
20122009 2013
MANAGEIQ ACQUIRED
RHEL OPENSTACK PLATFORM &
OPENSTACK PARTNER
PROGRAM
RED HAT SUBSCRIPTION MODEL
AWARD-WINNING SUPPORT
MULTI-LINGUAL
24x7
UNLIMITEDINCIDENTS
MISSION-CRITICAL
MULTI-VENDORCASE OWNERSHIP
GLOBAL SUPPORTSERVICES
CUSTOMER PORTAL & FORUMS
KNOWLEDGEBASE
HARDWARE CERTIFICATION
SOFTWARECERTIFICATION
OPTIONAL TRAINING
CURRICULA AVAILABLE
STABILITY WITH A PRODUCT LIFE CYCLEOF UP TO 10 YEARS
SOFTWAREASSURANCE
SECURITYRESPONSE
TEAMSOFTWARE
ASSURANCE
UPDATES
PATCHES UPGRADES
YEARS AWARDED:
201120122013
Porto Linux June 20149/35
Cloud Computing by Stephen Fry
Youtube Video:
https://www.youtube.com/watch?v=J9LK6EtxzgM
Porto Linux June 201410/35
Summary of Cloud features
● Utility.
● On demand.
● The amount I need.
● When I need it.
● Pay only for resources used.
● Scale up and down according to demand.
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.”
- National Institute of Standards & Technology (NIST)
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
DevelopersDevOps
IT Admins
Amazon AWS RackSpace OpenStack vCloud Director
OpenShift Force.com Heroku
Google Apps Salesforce Many moreIaaS
PaaS
SaaS
Porto Linux June 201419/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
Which workload type suits the customers requirements?
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 another one
21
Manufacturing as a Model for ITConsolidated 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.
THIS IS OUR CHALLENGE TODAY.
Porto Linux June 201424/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● Completely written in Python (yay!)
Porto Linux June 201427/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 201429/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
● OpenStack enables organisations to achieve this, today... and without lock-in.
Porto Linux June 201430/35
OpenStack distributions
● RackSpace
● Debian, Ubuntu
● OpenSUSE, SUSE
● Mirantis
● DevStack
● RHEL, Fedora, RDO
Ref: http://en.wikipedia.org/wiki/OpenStack
Porto Linux June 201431/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
● No certifications, no support
Porto Linux June 201434/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
● Bug fixes, security errata, selected backports, etc.
● Full support for RHEL and Windows workloads.