Bug 1272231 - [RFE][nova]: multiple back-ends for nova-compute
[RFE][nova]: multiple back-ends for nova-compute
Status: CLOSED DUPLICATE of bug 1272228
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 8.0 (Liberty)
Assigned To: Eoghan Glynn
nlevinki
https://blueprints.launchpad.net/nova...
upstream_milestone_none upstream_defi...
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-15 15:52 EDT by Stephen Gordon
Modified: 2015-11-11 14:09 EST (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-15 15:53:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Gordon 2015-10-15 15:52:16 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/multi-back-ends-for-nova-compute.

Description:

#1. Efficient node usage: Nova-compute is designed to configure with only one type of nova compute driver like kvm, vmware, citrix,etc. Here Hypervisors like kvm, the nova-compute is installed on the hypervisor itself.
So the CPU, memory load will be high as hypervisor is running on the nova-compute. But for the vmware hypervisors, nova-compute is installed on the separate node and its called proxy nova-compute. So the load on the proxy-compute node will be comparatively lesser and it will be more efficient if nova-compute node is allowed to configure multiple compute proxy driver similar to the cinder-volume multi-backend architecture. https://wiki.openstack.org/wiki/Cinder-multi-backend

#2. scalability: By enabling the multiple back-ends, it also helps to improve the scale-ability of the given compute proxy driver such as vmware vc driver.

Implementation Note
===============
It can be implemented by leveraging  the cinder implementation where only one instance of cinder-volume is installed, but when the cinder-volume service is started, it spawns one cinder-volume process for every back-end configured in the cinder.conf. In the same approach,
nova.conf will be as follows:

[DEAFULT]
....

#back_ends will have comma separated set of compute drivers section
#Each compute driver could be same or different
back_ends = vcdriver1, vcdriver2, xen1

[vcdriver1]
...

[vcdriver2]
...

[xen1]
...

With these configuration in place, when nova-compute starts, it will spawn 3 nova-compute one for each of the configured driver.

Specification URL (additional information):

None
Comment 2 Stephen Gordon 2015-10-15 15:53:49 EDT

*** This bug has been marked as a duplicate of bug 1272228 ***

Note You need to log in before you can comment on or make changes to this bug.