
This change fixes a few things with the recently added "os_interface" option in the [placement] config group. 1. It adds tests for the scheduler report client that were missing in the original change that added the config option. 2. It uses the option in the "nova-status upgrade check" command so it is consistent with how the scheduler report client uses it. 3. It removes the restrictive choices list from the config option definition. keystoneauth1 allows an "auth" value for the endpoint interface which means don't use the service catalog to find the endpoint but instead just read it from the "auth_url" config option. Also, the Keystone v3 API performs strict validation of the endpoint interface when creating an endpoint record. The list of supported interfaces may change over time, so we shouldn't encode that list within Nova. 4. As part of removing the choices, the release note associated with the new option is updated and changed from a 'feature' release note to simply 'other' since it's not really a feature as much as it is a bug fix. Change-Id: Ia5af05cc4d8155349bab942280c83e7318749959 Closes-Bug: #1664334
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at: