Comment 0 for bug 1805645

We are facing an issue to configure metadata service correctly. Neutron API charm's dns-domain was configured for an specific value but nova metadata service continues to return original "NAME_OF_SERVER.novalocal." as hostname.

dns-domain seems to correctly configure DHCP domain name.

However, not all types of Guest OS follow DHCP's definition of domain. RHEL-based guest OS, for example, set their hostnames to the value present on metadata service despite DHCP's original configuration. Although one can work-around this by using user_data flag on "openstack server create" and setting "preserve_hostname: true", there are situations where this is not feasible (e.g. when OpenStack is under management of an orchestrator).

We have a request to setup Designate to register all machines that are connected to a self-service network. That deployment is using BGP to advertise that SSN.

On a particular customer, we have the following configuration set:
Neutron-api: https://pastebin.canonical.com/p/vPhfkCbdw6/
Please, check that vni_ranges jump on one value, that was necessary to make the SSN available to Designate, as described on: https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html

Nova-cloud-controller: https://pastebin.canonical.com/p/yThtgY95BT/
Neutron-Gateway: https://pastebin.canonical.com/p/q97hqfgMCP/
Neutron-Openvswitch: https://pastebin.canonical.com/p/MPJ3zKSYxK/