Let me rephrase that to be more explicit. Certain organizations, for various reasons, require people in the process chain to actually make dns changes... No amount of automation can easily address that issue. Hopefully that can change in time. But stuff as simple as letting users launch vm's can be a hard enough enough sell, without requiring automated access to change dns.
That being said, thats a cool patch. I wish I could use it. :) Hopefully some day. Thanks, Kevin ________________________________________ From: Carl Baldwin [c...@ecbaldwin.net] Sent: Tuesday, September 15, 2015 3:52 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model On Tue, Sep 15, 2015 at 3:09 PM, Fox, Kevin M <kevin....@pnnl.gov> wrote: > DNS is preferable, since humans don't remember ip's very well. IPv6 is much > harder to remember then v4 too. > > DNS has its own issues, mostly, its usually not very quick to get a DNS entry > updated. At our site (and I'm sure, others), I'm afraid to say in some cases > it takes as long as 24 hours to get updates to happen. Even if that was > fixed, caching can bite you too. We also have work going on now to automate the addition and update of DNS entries as VMs come and go [1]. Please have a look and provide feedback. [1] https://review.openstack.org/#/q/topic:bp/external-dns-resolution,n,z Carl __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
