RHEV-M/oVirt Clusters as compute resources
© Copyright 2013 Hewlett-Packard Development Company, L.P.
This blueprint proposes customers who have RHEV-M/oVirt Management solutions in their data centers to make use of Cluster as an elastic compute pool in OpenStack.
The proposal is to have a nova compute proxy connects to a RHEV-M/oVirt through oVirt Rest APIs and expose configured clusters as a compute hosts.
• To allow a single RHEV-M/oVirt driver to model multiple Clusters in RHEV-M/oVirt as multiple nova-compute nodes.
• To allow the RHEV-M/oVirt driver to be configured to represent a set of clusters as compute nodes.
• To dynamically create / update / delete nova-compute nodes based on changes in RHEV-M/oVirt Clusters.
With this driver, there is no change expected in the scheduler. The RHEV-M templates which are available as glance images can be used to create instances.
Blueprint information
- Status:
- Started
- Approver:
- Russell Bryant
- Priority:
- Undefined
- Drafter:
- Srinivasa Acharya
- Direction:
- Needs approval
- Assignee:
- Romil Gupta
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Srinivasa Acharya
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Design Summit Slides: http://
Do you mean use openstack Dashboard to manage ovirt ? of course include host/cluster/vm and network(Quantum Integration) etc. block storage is hard problem.
Is someone signing up to do this work in Havana? I wasn't able to attend the design summit session, but my impression was that it was not clear if anyone was willing to do the work to get this upstream. If there is someone wanting to do this work, please start a thread on the openstack-dev mailing list so that we can discuss it. --russellb
Is there any specific reason to map oVirt cluster (which itself is a set of multiple hosts) to nova-compute node ? I was wondering why not map nova-compute to one host inside oVirt Cluster... so as many hosts , as many nova compute nodes... curious to know the reason behind mapping Cluster <-> nova-compute ? thanks - deepakcs
--> oVirt clusters should probably be treated like a single nova-compute unit, as Virtual Machines may live-migrate automatically between cluster nodes when resource usage and node availability changes. --maccam94
Design Summit Slides: http://
Do you mean use openstack Dashboard to manage ovirt ? of course include host/cluster/vm and network(Quantum Integration) etc. block storage is hard problem.
Is someone signing up to do this work in Havana? I wasn't able to attend the design summit session, but my impression was that it was not clear if anyone was willing to do the work to get this upstream. If there is someone wanting to do this work, please start a thread on the openstack-dev mailing list so that we can discuss it. --russellb
Is there any specific reason to map oVirt cluster (which itself is a set of multiple hosts) to nova-compute node ? I was wondering why not map nova-compute to one host inside oVirt Cluster... so as many hosts , as many nova compute nodes... curious to know the reason behind mapping Cluster <-> nova-compute ? thanks - deepakcs
--> oVirt clusters should probably be treated like a single nova-compute unit, as Virtual Machines may live-migrate automatically between cluster nodes when resource usage and node availability changes. --maccam94
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
