openstack/devstack
Code Issues Proposed changes

docs: Add placement-client to compute's ENABLED_SERVICES

Browse Source 
In a multinode setup, the compute node needs to report to the
placement service. If it does not do so, it effectively does not exist
from the scheduler's point of view. This patch adds placement-client
to the compute node's ENABLED_SERVICES so that this can happen.

Change-Id: Ibfcd84e4626301bcdea70f719ade7f8365d03497
This commit is contained in:
Artom Lifshitz 2018-05-02 10:38:57 -04:00 committed by Artom Lifshitz
parent 200f8dd0fe
commit 7e36ded0cf
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/guides/neutron.rst
View File

@ -244,7 +244,7 @@ The host `devstack-2` has a very minimal `local.conf`.
## Neutron options
PUBLIC_INTERFACE=eth0
ENABLED_SERVICES=n-cpu,rabbit,q-agt
ENABLED_SERVICES=n-cpu,rabbit,q-agt,placement-client
Network traffic from `eth0` on the compute nodes is then NAT'd by the
controller node that runs Neutron's `neutron-l3-agent` and provides L3