[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 6/2/2016

Carl Baldwin carl at ecbaldwin.net
Thu Jun 9 00:45:25 UTC 2016

On Thu, Jun 2, 2016 at 2:29 PM, Korzeniewski, Artur
<artur.korzeniewski at intel.com> wrote:
> I would like to remind that agreed approach at Design Summit in Austin was,
> that every new resource added to neutron should have OVO implemented. Please
> comply, and core reviewers please take care of this requirements in patches
> you review.

How about the networksegments table?  It was already a part of the ML2
model but was moved out of ML2 to make it available for the OVN
plugin.  Just days after the summit, it was made in to a first class
resource [2] with its own CRUD operations.  Is this part of the model
on your radar?  What needs to be done?

Since then, a relationship has been added between segment and subnet
[3].  Also, a mapping to hosts has been added [4].  What needs to be
done for OVO for these?  I'm sorry if these are slipping through the
cracks but we're still learning.  There are a couple of other model
tweaks in play on this topic too [5][6].  I'd like to begin doing
these the correct way.


[1] https://review.openstack.org/#/c/242393/
[2] https://review.openstack.org/#/c/296603/
[3] https://review.openstack.org/#/c/288774/
[4] https://review.openstack.org/#/c/285548/
[5] https://review.openstack.org/#/c/326261/
[6] https://review.openstack.org/#/c/293305/

More information about the OpenStack-dev mailing list