openstack/nova
Code Issues Proposed changes

Update placement config reno

Browse Source 
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
This commit is contained in:
Matt Riedemann 2016-08-31 11:57:17 -04:00
parent d805875fe8
commit a6ad102c9d
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
releasenotes/notes/placement-config-section-59891ba38e0749e7.yaml
View File

@ -3,9 +3,9 @@ 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'.
'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. The only configuration option currently available is
`os_region_name` which provides support for Nova to query the appropriate
OpenStack region's service catalog for the placement service.
API service. This contains the usual keystone auth and session options.