Hi Matt,
On 9/22/17 7:10 PM, Matt Riedemann wrote:
while this approach is ok in general, some comments from my side -
1. For a new instance, if the neutron network has a dns_domain set,
use it. I'm not totally sure how we tell from the metadata API if it's
a new instance or not, except when
On 9/22/2017 10:02 AM, Volodymyr Litovka wrote:
And another topic, in Neutron, regarding domainname. Any DHCP-server,
created by Neutron, will return "domain" derived from system-wide
"dns_name" parameter (defined in neutron.conf and explicitly used in
argument "--domain" of dnsmasq). There is
Hi Stephen,
I think, it's useful to have hostname in Nova's metadata - this provides
some initial information for cloud-init to configure newly created VM,
so I would not refuse this method. A bit confusing is domain part of the
hostname (novalocal), which derived from Openstack-wide
I rely on cloud-init to set my hostnames.
I have a number of internal systems which rely on a machine knowing its own
hostname. In particular, at least one of my configuration management
systems requires that a host pass its fqdn to an API to fetch its CM data,
so grabbing hostnames and
[Re-posting (in edited from) from openstack-dev]
Nova has a feature whereby it will provide instance host names that cloud-init
can extract and use inside the guest, i.e. this won't happen without cloud-
init. These host names are fully qualified domain names (FQDNs) based upon the
instance name
