Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-07 Thread Ben Nemec
On 09/06/2017 04:40 AM, Stephen Finucane wrote: On Tue, 2017-09-05 at 12:30 -0500, Ben Nemec wrote: On 09/04/2017 07:48 AM, Stephen Finucane wrote: On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: Nova has a feature

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-07 Thread Stephen Finucane
On Wed, 2017-09-06 at 15:06 +, Jeremy Stanley wrote: > On 2017-09-06 10:40:14 +0100 (+0100), Stephen Finucane wrote: > [...] > > OK, and we do want to use a FQDN as the hostnames inside the > > guest? That's my key question. Random ServerFault questions seems > > to suggest no clear answer to

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-06 Thread Jeremy Stanley
On 2017-09-06 10:40:14 +0100 (+0100), Stephen Finucane wrote: [...] > OK, and we do want to use a FQDN as the hostnames inside the > guest? That's my key question. Random ServerFault questions seems > to suggest no clear answer to this [1]. [...] As a data point, the servers maintained by the

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-06 Thread Stephen Finucane
On Tue, 2017-09-05 at 12:30 -0500, Ben Nemec wrote: > On 09/04/2017 07:48 AM, Stephen Finucane wrote: > > On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: > > > On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: > > > > Nova has a feature whereby it will provide instance

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-05 Thread Ben Nemec
On 09/04/2017 07:48 AM, Stephen Finucane wrote: On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: Nova has a feature whereby it will provide instance host names that cloud- init can extract and use inside the guest,

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-05 Thread Michael Johnson
FYI, code in Octavia that checks for the extensions you could borrow: https://github.com/openstack/octavia/blob/master/octavia/network/drivers/neutron/base.py#L49 On Mon, Sep 4, 2017 at 11:18 PM, Gary Kotton wrote: > > > On 9/4/17, 3:47 PM, "Stephen Finucane"

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-05 Thread Gary Kotton
On 9/4/17, 3:47 PM, "Stephen Finucane" wrote: On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: > On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: > > Nova has a feature whereby it will provide instance host names that cloud- > > init

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-04 Thread Stephen Finucane
On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: > On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: > > 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.

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-04 Thread Gary Kotton
Hi, Your patch https://review.openstack.org/#/c/480616/ requires that neutron expose the ‘DNS Integration’ extension be support by neutron and the relevant networking plugin. If it does not then will be a gression and things will not work. In addition to this that is per network and not global

[openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

2017-09-04 Thread Stephen Finucane
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 and local domain name. However, as noted in bug