ddf0fef28b
Currently neutron uses socket.gethostname() to determine hypervisor names, but this implementation is not fully compatible with libvirt driver which uses canonical name for hypervisor name. This incompatibility causes an issue with root resource provider detection if a deployment uses FQDNs as canonicanl names. This change introduces the resource_provider_default_hypervisor option, so that users can override the hypervisor name by the single option(*1) instead of setting two list options(*2). This is especially useful if the deployment has multiple bridges or interfaces. (*1) [OVS] resource_provider_bandwidths=br-data1:1024:1024,br-data2:1024:1024,\ br-data3:1024,1024,br-data4,1024:1024 resource_provider_default_hypervisor=compute0.mydomain (*2) [OVS] resource_provider_bandwidths=br-data1:1024:1024,br-data2:1024:1024,\ br-data3:1024,1024,br-data4,1024:1024 resource_provider_hypervisors=br-data1:compute0.mydomain,br-data2:\ compute0.mydomain,br-data3:compute0.mydomain,br-data4:compute0.mydomain Related-Bug: #1926693 Change-Id: I692219200535df3af1265248e88c96947e4d8f9d
OpenStack Neutron
Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).
To learn more about neutron:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/neutron
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute, please read the CONTRIBUTING.rst file.