Schema enhancement to support MultiSegment Network
Description:
Currently, there is nothing in the schema that ensures segments
for a network are returned in the same order they were specified
when the network was created, or even in a deterministic order.
Solution:
We need to add another field named 'segment_index' in
'ml2_network_segment' table containing a numeric position index.
With segment_index field we can retrieve the segments in the
order in which user created.
This patch set also fixes ML2 invalid unit test case in
test_create_network_multiprovider().
Reviewed: https:/ /review. openstack. org/103546 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=db5e370b0d6 8c3e71626c99941 fe487059b3cf88
Committed: https:/
Submitter: Jenkins
Branch: master
commit db5e370b0d68c3e 71626c99941fe48 7059b3cf88
Author: Romil Gupta <email address hidden>
Date: Mon Jun 30 05:35:08 2014 -0700
Schema enhancement to support MultiSegment Network
Description:
Currently, there is nothing in the schema that ensures segments
for a network are returned in the same order they were specified
when the network was created, or even in a deterministic order.
Solution: network_ segment' table containing a numeric position index.
We need to add another field named 'segment_index' in
'ml2_
With segment_index field we can retrieve the segments in the
order in which user created.
This patch set also fixes ML2 invalid unit test case in create_ network_ multiprovider( ).
test_
Closes-Bug: #1224978
Closes-Bug: #1377346
Change-Id: I560c34c6fe1c54 25469ccdf9b8b49 05c123d496d