• Save
Red Hat Cloud Infrastructure Conference 2013 -  Presentation about OpenStack (by Rhys Oxenham)
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Red Hat Cloud Infrastructure Conference 2013 - Presentation about OpenStack (by Rhys Oxenham)

  • 2,630 views
Uploaded on

Konference Red Hat Cloud Infrastructure 2013 ze dne 20.9. 2013 a prezentace od product managera pro cloud ze společnosti Red Hat. Všechna práva vyhrazena.

Konference Red Hat Cloud Infrastructure 2013 ze dne 20.9. 2013 a prezentace od product managera pro cloud ze společnosti Red Hat. Všechna práva vyhrazena.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,630
On Slideshare
2,591
From Embeds
39
Number of Embeds
2

Actions

Shares
Downloads
0
Comments
0
Likes
9

Embeds 39

http://www.elostech.cz 34
http://storify.com 5

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. 1 OpenStack IaaS Rhys Oxenham September 2013
  • 2. What is OpenStack? ● Fully open source cloud “operating system” ● Provides all of the tools/building blocks required to build a cloud environment from scratch - mimics public clouds ● Started by NASA and Rackspace but now has an independent foundation in which key industry members are present, including Red Hat ● Enormous market hype with investment from all major players, e.g. HP, Dell, IBM... and with 1000's of developers worldwide
  • 3. 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.
  • 4. 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
  • 5. Or an easier analogy... 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
  • 6. OpenStack Release History ● July 2010 - Initial announcement ● October 2010 - Austin Release ● February 2011 - Bexar Release ● April 2011 - Cactus Release ● October 2011 - Diablo Release ● April 2012 - Essex Release ● October 2012 - Folsom Release ● April 2013 - Grizzly Release ● October 2013 - Havana Release
  • 7. What is Red Hat doing about OpenStack?
  • 8. 8 OpenStack Contribution
  • 9. 9 OpenStack Contribution http://bitergia.com/public/reports/openstack/2013_04_grizzly/ Leading Contributor to Grizzly Release ● Leading in commits and line counts across all projects ● Note: Not including OpenStack dependencies, Linux, KVM, libvirt, etc
  • 10. 10 OpenStack Contribution ● Why do these statistics matter? ● Proof that Red Hat has the skills and resources to... ● Support customers ● Drive new features ● Influence strategy and direction of project ● Not a monopoly! ● We're not in full-control of the project and we don't intend to be ● Our commitment continues to grow ● But, overall contribution percentage in comparison to all contributions is getting smaller
  • 11. 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
  • 12. Community → Enterprise
  • 13. 13 Red Hat OpenStack Offering Red Hat will include the following in its Red Hat OpenStack distribution ● All core OpenStack Grizzly packages including Quantum ● Support for Open vSwitch via userspace tools in Red Hat OpenStack + kernel support in RHEL 6.4 ● Puppet modules for installing all services for OpenStack ● A multi-node installer for small deployments (PackStack) ● Reference architectures for large scale deployments ● Bug-fixes and features selectively back-ported from Havana
  • 14. 14 Release Cadence ● Upstream OpenStack.org ● Source code only ● Releases every 6 months ● 2 to 3 'snapshots' including bug fixes ● No more fixes/snapshots after next release ● Upstream RDO ● Follows upstream cadence ● Delivers 'binaries' in yum/rpm format for RHEL, Fedora, etc.
  • 15. 15 Release Cadence ● Red Hat OpenStack ● 6 month release cycle ● Roughly 2 months AFTER upstream ● Time to stabilize, certify, back-port etc. ● Initially 1 year lifecycle ● Support for Folsom ends after Havana release ● Support for Grizzly ends after Icehouse release ● Will increase lifecycle over time ● Based on upstream stability and customer requirements
  • 16. 16 Why Red Hat OpenStack? ● Red Hat brings what OpenStack really needs... ● Supportability ● Stability & Code Maturity ● Certified Ecosystem ● Lifecycle ● Support for the entire stack from one vendor ● OpenStack Components ● Stable, mature and trusted Linux Operating System ● Secure, high performance virtualisation ● Storage ● Software Defined Networking
  • 17. 17 OpenStack moving forward... ● Continued focus on OpenStack core ● Working on core OpenStack components ● Integrating with proven technologies underneath ● Cloud Partnership Program announced to help 3rd parties certify ● Work with vendors providing layered products to build ecosystem ● Integrating with existing Enterprise architecture requirements ● Management tools for RHOS ● Deliver in stages ● Tooling for installation and configuration management (Based around Foreman) ● Centralised Management Platform ● Optional CloudForms Integration
  • 18. OpenStack Architecture
  • 19. OpenStack Components ● Modular architecture ● Vast scale-out design ● Based on a (growing) set of core-components
  • 20. OpenStack Keystone ● Keystone provides a common authentication and authorisation store for OpenStack ● Users, their roles and the tenant (project) they belong to ● Authentication is based on tokens ● 24-hour expiry by default ● Easily revoked if compromised ● Each OpenStack component uses Keystone to verify a users token ● It also provides a catalogue of all other OpenStack services
  • 21. OpenStack Nova ● Core responsibility is to schedule and manage instances (think Amazon EC2) ● Supports multiple hypervisors ● VMware ESX (either direct to ESX or via vCenter) ● Xen ● KVM ● Microsoft Hyper-V ● Exposes an OpenStack API but also an EC2 compatible API
  • 22. OpenStack Glance ● Mechanism for storing and retrieving disk images ● Supports many standard image types ● raw, qcow2, vmdk, vhd, iso, ami/aki, ovf ● With various storage options for the images ● Filesystem (Default) ● Swift (OpenStack Object Storage) ● S3 (Amazon's Simple Storage Service)
  • 23. OpenStack Swift ● Mechanism for storing and retrieving arbitrary unstructured data (as objects) ● Entirely REST-ful HTTP API based, similar to Amazon S3 ● Highly fault tolerant ● Data replication (including geographically) ● Self-healing architecture ● Load-balancing with built-in proxy servers ● No single point of failure ● Doesn't require any specific hardware, purely scale-out.
  • 24. OpenStack Quantum ● OpenStack's Networking-as-a-Service Component ● Implements Software Defined Networking (SDN) ● Rich plugin architecture which allows Quantum to abstract the underlying technology implementation away. ● Cisco UCS ● VMware Nicira ● Open vSwitch etc.
  • 25. OpenStack Cinder ● Provides block storage for runtime of instances ● Can be used for persistent or tiered storage ● Enables ability to do live migration of instances ● Similar to Amazon Elastic Block Storage (EBS) ● Support for many storage vendors platforms for offload ● Default implementation exposes LVM's over iSCSI
  • 26. OpenStack Horizon ● Self-service portal exposing end-user OpenStack functionality ● Web-based interface that utilises underlying API's ● Permits the creation and life-cycle management of ● Instances (including snapshots) ● Images ● Volumes ● Networks ● Has different views depending on whether the user is an administrator or not.
  • 27. OpenStack Horizon - Screenshot
  • 28. Demo