nova/releasenotes/notes/placement-config-section-59891ba38e0749e7.yaml

12 lines
667 B
YAML
Raw Normal View History

rt: ensure resource provider records exist from RT This patch adds functionality to the scheduler "report client" to ensure that the client calls the placement API to create a resource provider record for the local compute host managed by the Nova resource tracker. The report client keeps a cache of resource provider objects, keyed by resource provider UUID and constructed from the results of placement REST API calls to get information about a resource provider. If a resource provider matching a UUID was not found in the placement REST API, the report client automatically creates the resource provider record via the placement REST API. These resource provider objects will be used in followup patches that add creation of inventory and allocation records to the scheduler report client. Included in this patch is a new [placement] nova.conf configuration section with a single os_region_name configuration option that allows Nova to grab the placement API endpoint URL for the particular OpenStack region that it is in. We do not support endpoint URL overrides for the placement API service. We only use the Keystone service catalog for finding the endpoint for the placement service. We intentionally modeled the determination of the placement endpoint URL after similar code that determines the volume endpoint URL in /nova/volume/cinder.py. This redoes the placement API using keystone session, and stubs out where we can do more reasonable handling of errors. This works if we fill out the right credentials in the placement section of the config file. Co-Authored-By: Sean Dague <sean@dague.net> Change-Id: I9d28b51da25c523d22c373039e6d8b36fd96eba6 blueprint: generic-resource-pools
2016-08-22 13:52:44 -04:00
---
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.
rt: ensure resource provider records exist from RT This patch adds functionality to the scheduler "report client" to ensure that the client calls the placement API to create a resource provider record for the local compute host managed by the Nova resource tracker. The report client keeps a cache of resource provider objects, keyed by resource provider UUID and constructed from the results of placement REST API calls to get information about a resource provider. If a resource provider matching a UUID was not found in the placement REST API, the report client automatically creates the resource provider record via the placement REST API. These resource provider objects will be used in followup patches that add creation of inventory and allocation records to the scheduler report client. Included in this patch is a new [placement] nova.conf configuration section with a single os_region_name configuration option that allows Nova to grab the placement API endpoint URL for the particular OpenStack region that it is in. We do not support endpoint URL overrides for the placement API service. We only use the Keystone service catalog for finding the endpoint for the placement service. We intentionally modeled the determination of the placement endpoint URL after similar code that determines the volume endpoint URL in /nova/volume/cinder.py. This redoes the placement API using keystone session, and stubs out where we can do more reasonable handling of errors. This works if we fill out the right credentials in the placement section of the config file. Co-Authored-By: Sean Dague <sean@dague.net> Change-Id: I9d28b51da25c523d22c373039e6d8b36fd96eba6 blueprint: generic-resource-pools
2016-08-22 13:52:44 -04:00
- 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.