| 2017-02-23 06:14:10 |
Prashant Shetty |
description |
Our requirement is as below,
- Single controller which runs service,
enable_service q-svc
enable_service placement-api
enable_service h-eng h-api h-api-cfn h-api-cw
- Remaining services like dhcp,meta,routing etc we will make use of platform native solution
- Have different types of computes(KVM and ESXi) with service,
i. ENABLED_SERVICES=n-cpu,neutron,placement-api & VIRT_DRIVER=vsphere for ESXi
ii. ENABLED_SERVICES=n-cpu,neutron,placement-api for KVM node
As below code suggests current devstack code configures [placement] section on nova.conf of controller only if n-cpu is running along with placement service, which seems to be wrong.
https://github.com/openstack-dev/devstack/blob/7a30c7fcabac1cf28fd9baa39d05436680616aef/stack.sh#L875
In multi node setup we don't want to run n-api,q-svc and n-cpu together. |
Our requirement is as below,
- Single controller which runs service,
enable_service q-svc
enable_service placement-api
enable_service h-eng h-api h-api-cfn h-api-cw
- Remaining services like dhcp,meta,routing etc we will make use of platform native solution
- Have different types of computes(KVM and ESXi) with service,
i. ENABLED_SERVICES=n-cpu,neutron,placement-api & VIRT_DRIVER=vsphere for ESXi
ii. ENABLED_SERVICES=n-cpu,neutron,placement-api for KVM node
As below code suggests current devstack code configures [placement] section on nova.conf of controller only if n-cpu is running along with placement service, which seems to be wrong.
https://github.com/openstack-dev/devstack/blob/7a30c7fcabac1cf28fd9baa39d05436680616aef/stack.sh#L875
In multi node setup we don't want to run n-api,q-svc and n-cpu together on controller. |
|
