keep dns nameserver order consistency

Registered by changzhi on 2015-07-20

Currently, there is no dns servers prioritization for subnets
for Neutron.

Fox example:
command1: neutron subnet-update [subnet_id] --dns_nameservers list=true 1.1.1.1 2.2.2.2 3.3.3.3
command2: neutron subnet-update [subnet_id] --dns_nameservers list=true 3.3.3.3 2.2.2.2 1.1.1.1

Generally speaking, in Neutron, command1 is same as command2. These commands are update dns_nameservers of subnet. There is no priority about dns nameservers. But in many situations, there are many differences between every dns nameserver. So we want Neutron to keep dns nameserver order consistency.

Blueprint information

Status:
Complete
Approver:
Kyle Mestery
Priority:
Low
Drafter:
changzhi
Direction:
Approved
Assignee:
changzhi
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 7.0.0
Started by
Kyle Mestery on 2015-07-20
Completed by
Thierry Carrez on 2015-09-03

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bug/1218629,n,z

Addressed by: https://review.openstack.org/203542
    Keep dns nameserver order consistency

Addressed by: https://review.openstack.org/199588
    Keep dns nameserver order consistency

Gerrit topic: https://review.openstack.org/#q,topic:bug/1478512,n,z

Addressed by: https://review.openstack.org/207903
    Merge remote-tracking branch 'origin/master' into merge-branch

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.