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
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?
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 RDO: Mixing the “old” and
Open Source and Standards, Red Hat
1. Comparing oVirt and OpenStack
2. Overlap and potential for interoperability
Infrastructure as a Service
(JBOSS, PHP, RUBY, ETC)
Automated and Managed
by the Public or Private
Managed and Controlled
by Customer (IT, Dev, or
IaaS PaaS SaaS
OpenStack Design and Architecture
Based on a (growing) set of core services
Designed for Scalability and Elasticity
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
● PackStack is a tool to enable fast and simple
deployment of OpenStack
● Makes complex installation and configuration as simple
● Built on Puppet
Overview of oVirt
“Pets vs Cattle” (Yes, again)
The above adapted from Tim Bell, CERN
“Future application architectures should use Cattle but Pets with strong
configuration management are viable and still needed”
- Tim Bell, CERN
- Servers are like pets.
Pets are given names, are unique,
lovingly hand raised and cared for.
When they get ill, you nurse them back
- Servers are like cattle.
Cattle are given numbers and are
almost identical to each other. When
they get ill, you get another one.
oVirt vs 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
Overview of oVirt
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!
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
● Ability to monitor and control oVirt VMs in Horizon
● Freedom to gradually migrate “old” to “new”