a6ad102c9d
This addresses some review comments from when this reno was added, namely (1) that you have to restart nova-compute to try and get a connection to the placement API if the initial connection fails due to the service catalog not having a placement entry, and (2) that the [placement] section in nova.conf has the usual keystone auth options for connecting to the placement API. Part of blueprint generic-resource-pools Change-Id: I27c63df6753bcc89ce6866cd4d20952b664fced9
12 lines
667 B
YAML
12 lines
667 B
YAML
---
|
|
features:
|
|
- The nova-compute worker now communicates with the new placement API
|
|
service. Nova determines the placement API service by querying the
|
|
OpenStack service catalog for the service with a service type of
|
|
'placement'. If there is no placement entry in the service catalog,
|
|
nova-compute will log a warning and no longer try to reconnect to the
|
|
placement API until the nova-worker process is restarted.
|
|
- A new [placement] section is added to the nova.conf configuration file for
|
|
configuration options affecting how Nova interacts with the new placement
|
|
API service. This contains the usual keystone auth and session options.
|