oVirt and OpenStack


Published on

oVirt and OpenStack look kind of similar from a distance. But they cater to different use-cases. That said, they do have some common needs. How can they work together? And when is it better to use one over the other?

Published in: Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • A subset of the OpenStack Basic Tenants Scalability and elasticity are the ma in goals Any feature that limits our main goals must be optional All required components must be horizontally scalable Always use shared nothing architecture
  • He answers to “Ellison”. ;) One of the problems with scale up is that you inadvertently increase the size of your failure domain.
  • oVirt and OpenStack

    1. 1. 1 oVirt and RDO: Mixing the “old” and the “new” Dave Neary Open Source and Standards, Red Hat
    2. 2. 2 Agenda 1. Comparing oVirt and OpenStack 2. Overlap and potential for interoperability
    3. 3. 3 Infrastructure as a Service STORAGE (GlusterFS) HARDWARE (x86) VIRTUALIZATION (KVM) OPERATING SYSTEM (RHEL) APPLICATION PLATFORM (JBOSS, PHP, RUBY, ETC) APPLICATION Automated and Managed by the Public or Private Cloud Offering Managed and Controlled by Customer (IT, Dev, or User) IaaS PaaS SaaS Increased Control Increased Automation
    4. 4. 4 Overview of OpenStack Software and Community
    5. 5. OpenStack Design and Architecture DASHBOARD (Horizon) COMPUTE (Nova) IDENTITY SERVICE (Keystone) Modular architecture Based on a (growing) set of core services Designed for Scalability and Elasticity BLOCK STORAGE (Cinder) OBJECT STORE (Swift) NETWORKING (Quantum) IMAGE SERVICE (Glance)
    6. 6. 6 What is RDO? RDO is a freely-available, community supported distribution of OpenStack, packaged and integrated for Red Hat Enterprise Linux and its clones, and for Fedora http://openstack.redhat.com
    7. 7. 7 PackStack ● PackStack is a tool to enable fast and simple deployment of OpenStack ● Makes complex installation and configuration as simple as possible ● Built on Puppet
    8. 8. 8 Overview of oVirt
    9. 9. 9 Overview of oVirt Storage Compute Dashboard Reporting Identity
    10. 10. “Pets vs Cattle” (Yes, again) The above adapted from Tim Bell, CERN http://www.slideshare.net/noggin143/20121017-openstack-cern-accelerating-cience “Future application architectures should use Cattle but Pets with strong configuration management are viable and still needed” - Tim Bell, CERN “ Scale Up - Servers are like pets. Pets are given names, are unique, lovingly hand raised and cared for. When they get ill, you nurse them back to health Scale Out - Servers are like cattle. Cattle are given numbers and are almost identical to each other. When they get ill, you get another one.
    11. 11. oVirt vs OpenStack oVirt OpenStack Scale up Scale out HA VMs – expect to stay up Stateless VMs – expect to be redundant Resiliency in platform Resiliency in application VMs need shared storage VMs need shared storage Need to define VLANs Need to define VLANs Needs dashboard Needs dashboard
    12. 12. 12 Overview of oVirt Glance, Cinder Neutrron for SDN FreeIPA for Identity – shared with Keystone Nova driver for oVirt
    13. 13. 13 One Ring to Rule them All ● Cloud management software ● “Single pane of glass” to allow management of traditional Virt and private and public IaaS ● Enables policy enforcement ● Facilitates service migration ● Frees you from vendor lock-in ● CloudForms Management Engine – Open Sourcing soon, at a theatre near you!
    14. 14. 14 Scenario for today ● Install oVirt and OpenStack side by side ● Shared image storage with Glance ● Shared block storage (Gluster, NFS, iSCSI, FCoE for oVirt, Cinder for OpenStack, consuming same storage) ● Shared SDN framework (define oVirt VLANS with Neutron) ● Ability to monitor and control oVirt VMs in Horizon ● Freedom to gradually migrate “old” to “new”
    15. 15. REDHAT OPENSTACK |2013DOC144908-20130513r1 QUESTIONS?