Comment 17 for bug 1926693

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/796230
Committed: https://opendev.org/openstack/neutron/commit/5f57525c9d7bed778fc481019008b312a58e17c4
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 5f57525c9d7bed778fc481019008b312a58e17c4
Author: Takashi Kajinami <email address hidden>
Date: Fri Nov 20 22:29:19 2020 +0900

    Add a single option to override the default hypervisor name

    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
    (cherry picked from commit ddf0fef28b7095724c8ba27f3275d0dad2252251)