yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #84486
[Bug 1905276] [NEW] Overriding hypervisor name for resource provider always requires a complete list of interfaces/bridges
Public bug reported:
In some deployments, hostnames can be different between hosts and resource provider records. For example in deployment managed by TripleO we use short host name (without domain name) in host, while we use FQDN for resource provider records (this comes from the FQDN set to the host
option in nova.conf).
This causes an issue with the way how currently neutron looks up the
root resource provider because placment API requires the exact hostname
and doesn't automatically translate short name and FQDN.
To fix the issue we need to set the resource_provider_hypervisors
option[1] now but it is very redundant to list up all devices or bridges
in this option to override hostnames for the devices/bridges by the same
value.
[1] https://review.opendev.org/#/c/696600/
** Affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- Overriding defualt hypervisor name always requires a complete list of interfaces/bridges
+ Overriding hypervisor name for resource provider management always requires a complete list of interfaces/bridges
** Summary changed:
- Overriding hypervisor name for resource provider management always requires a complete list of interfaces/bridges
+ Overriding hypervisor name for resource provider always requires a complete list of interfaces/bridges
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1905276
Title:
Overriding hypervisor name for resource provider always requires a
complete list of interfaces/bridges
Status in neutron:
New
Bug description:
In some deployments, hostnames can be different between hosts and resource provider records. For example in deployment managed by TripleO we use short host name (without domain name) in host, while we use FQDN for resource provider records (this comes from the FQDN set to the host
option in nova.conf).
This causes an issue with the way how currently neutron looks up the
root resource provider because placment API requires the exact
hostname and doesn't automatically translate short name and FQDN.
To fix the issue we need to set the resource_provider_hypervisors
option[1] now but it is very redundant to list up all devices or
bridges in this option to override hostnames for the devices/bridges
by the same value.
[1] https://review.opendev.org/#/c/696600/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1905276/+subscriptions
Follow ups