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

2017-09-22 Thread Volodymyr Litovka
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 deprecate

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

2017-09-22 Thread Matt Riedemann
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

[Openstack-operators] Contributor Portal PTG Recap

2017-09-22 Thread Mike Perez
# Contributor Portal Next Steps ## Landing Page Mock ups * Current mock up: https://drive.google.com/file/d/0BxMh9oiou2xMLVRvRWRFVklHa2c/view * Limited click through mock up: https://invis.io/CSDEZTBDJ#/252645774_Landing ## Todo - [ ] thingee: A proposal for the *second level* of what the landing

[Openstack-operators] OpenStack Developer Mailing List Digest September 16-22

2017-09-22 Thread Mike Perez
PDF: http://www.openstack.org/blog/wp-content/uploads/2017/09/devdigest-20170922.pdf HTML: https://www.openstack.org/blog/2017/09/openstack-developer-mailing-list-digest-20170922/ # OpenStack Developer Mailing List Digest September 16-22 ## Summaries * [Technical Committee Status update](http