Open Stack

Hi Paul,

There is an old bug on this issue:  
https://bugs.launchpad.net/neutron/+bug/1218629

If I remember correctly, the root of the problem was the database
definition for the DNS values.

On 06/23/2015 01:48 PM, Paul Ward wrote:
> I haven't dug into the code yet, but from testing via CLI and REST
> API, it appears neutron does not honor the order in which users
> specify their dns-nameservers.  For example, no matter what order I
> specify 10.0.0.1 and 10.0.0.2 for dns-nameservers, they are always
> ordered with the numerically lowest IP first when doing a subnet-show
> (ie, 10.0.0.1 will be first, even if I specified 10.0.0.2 first).  As
> stated above, CLI and REST API behave the same.
>
> I believe this is a problem because these are passed to activation on
> a deployed VM in the order neutron lists them in the subnet.  A user
> may have a reason they want the numerically higher DNS IP listed
> first, say if they are trying to load balance their DNS servers.  By
> always ordering them numerically, we give them no way to do this.
>
> So my question is... is this by design or an oversight?  If it's an
> oversight, I'll dig into the code and propose a patch.
>
>
> __________________________________________________________________________
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
John Kasperski