nic ordering is inconsistent in backend and ui

[Vish Ishaya]

The order of nics in both the UI and the backend should be consistent since it has a strong impact in the guest. The first network shown should be the first network that the guest is connected to. Unfortunately we store this info in a dict which has inconsistent ordering. This should be an ordered dict.

[Vish Ishaya (vishvananda)]

https://review.openstack.org/#/c/143730/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/143730
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2ec71f6d04862fe909ef03fa881ff7e915766def
Submitter: Jenkins
Branch: master

commit 2ec71f6d04862fe909ef03fa881ff7e915766def
Author: Vishvananda Ishaya <email address hidden>
Date: Tue Dec 23 11:40:26 2014 -0800

    Maintain the creation order for vifs

    Ensure that the backend and the front end keep the vifs in the
    same order that they were specified in when they were created.

    Closes-Bug: 1405271
    Change-Id: If6e1dc51609c764de8352b933b7a847952d08931

[Alexander Bozhenko (alexbozhenko)]

With this issue order of interfaces that you specified on instance creation is ignored, and alphabetical order used instead. Is it correct?

[Alexander Bozhenko (alexbozhenko)]

*With this patch

[Alexander Bozhenko (alexbozhenko)]

@Vish does this fixes nova network only? Or neutron too?