Browse code
docs: Add placement-client to compute's ENABLED_SERVICES
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
Artom Lifshitz authored on 2018/05/02 23:38:57Showing 1 changed files
| ... | ... |
@@ -244,7 +244,7 @@ The host `devstack-2` has a very minimal `local.conf`. |
| 244 | 244 |
|
| 245 | 245 |
## Neutron options |
| 246 | 246 |
PUBLIC_INTERFACE=eth0 |
| 247 |
- ENABLED_SERVICES=n-cpu,rabbit,q-agt |
|
| 247 |
+ ENABLED_SERVICES=n-cpu,rabbit,q-agt,placement-client |
|
| 248 | 248 |
|
| 249 | 249 |
Network traffic from `eth0` on the compute nodes is then NAT'd by the |
| 250 | 250 |
controller node that runs Neutron's `neutron-l3-agent` and provides L3 |