Re: [openstack-dev] [Neutron] Dublin PTG Summary
Miguel Lavalle, 2018-03-12 13:45: > * Ruijing Guo proposed to support VLAN transparency in Neutron OVS > agent. > > [...] - While on this topic, the conversation temporarily forked to > the use of registers instead of ovsdb port tags in L2 agent br-int > and possibly remove br-tun. Thomas Morin committed to draft a RFE for > this. Here is the RFE: https://bugs.launchpad.net/neutron/+bug/1756296 It does not yet cover a possible following step where br-tun would be removed. Cheers, -Thomas > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Dublin PTG Summary
Very good summary, thanks for leading the PTG and neutron so well. :) On Mon, Mar 12, 2018 at 11:25 PM fumihiko kakuma wrote: > Hi Miguel, > > > * As part of the neutron-lib effort, we have found networking projects > that > > are very inactive. Examples are networking-brocade (no updates since May > of > > 2016) and networking-ofagent (no updates since March of 2017). Miguel > > Lavalle will contact these projects leads to ascertain their situation. > If > > they are indeed inactive, we will not support them as part of neutron-lib > > updates and will also try to remove them from code search > > networking-ofagent has been removed in the Newton release. > So it will not be necessary to support it as part of neutron-lib updates. > > Thanks > kakuma. > > > On Mon, 12 Mar 2018 13:45:27 -0500 > Miguel Lavalle wrote: > > > Hi All! > > > > First of all, I want to thank you the team for the productive week we had > > in Dublin. Following below is a high level summary of the discussions we > > had. If there is something I left out, please reply to this email thread > to > > add it. However, if you want to continue the discussion on any of the > > individual points summarized below, please start a new thread, so we > don't > > have a lot of conversations going on attached to this update. > > > > You can find the etherpad we used during the PTG meetings here: > > https://etherpad.openstack.org/p/neutron-ptg-rocky > > > > > > Retrospective > > == > > > > * The team missed one community goal in the Pike cycle ( > > https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html) > and > > one in the Queens cycle (https://governance.openstack. > > org/tc/goals/queens/policy-in-code.html) > > > >- Akihiro Motoki will work on https://governance.openstack.o > > rg/tc/goals/queens/policy-in-code.html during Rocky > > > > - We need volunteers to complete https://governance.op > > enstack.org/tc/goals/pike/deploy-api-in-wsgi.html) and the two new goals > > for the Rocky cycle: https://governance.openstack.o > > rg/tc/goals/rocky/enable-mutable-configuration.html and > > https://governance.openstack.org/tc/goals/rocky/mox_removal.html. > Akihiro > > Motoki will lead the effort for mox removal > > > > - We decided to add a section to our weekly meeting agenda where we are > > going to track the progress towards catching up with the community goals > > during the Rocky cycle > > > > * As part of the neutron-lib effort, we have found networking projects > that > > are very inactive. Examples are networking-brocade (no updates since May > of > > 2016) and networking-ofagent (no updates since March of 2017). Miguel > > Lavalle will contact these projects leads to ascertain their situation. > If > > they are indeed inactive, we will not support them as part of neutron-lib > > updates and will also try to remove them from code search > > > > * We will continue our efforts to recruit new contributors and develop > core > > reviewers. During the conversation on this topic, Nikolai de Figueiredo > and > > Pawel Suder announced that they will become active in Neutron. Both of > > them, along with Hongbin Lu, indicated that are interested in working > > towards becoming core reviewers. > > > > * The team went through the blueprints in the backlog. Here is the status > > for those blueprints that are not discussed in other sections of this > > summary: > > > >- Adopt oslo.versionedobjects for database interactions. This is a > > continuing effort. The contact is Ihar Hrachyshka (ihrachys). > Contributors > > are wanted. There is a weekly meeting led by Ihar where this topic is > > covered: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting > > > >- Enable adoption of an existing subnet into a subnetpool. The final > > patch in the series to implement this feature is: > > https://review.openstack.org/#/c/348080. Pawel Suder will drive this > patch > > to completion > > > >- Neutron in-tree API reference (https://blueprints.launchpad. > > net/neutron/+spec/neutron-in-tree-api-ref). There are two remaining TODOs > > to complete this blueprint: > https://bugs.launchpad.net/neutron/+bug/1752274 > > and https://bugs.launchpad.net/neutron/+bug/1752275. We need volunteers > for > > these two work items > > > >- Add TCP/UDP port forwarding extension to L3. The spec was merged > > recently: https://specs.openstack.org/openstack/neutron-specs/specs/qu > > eens/port-forwarding.html. Implementation effort is in progress: > > https://review.openstack.org/#/c/533850/ and > https://review.openstack.org/# > > /c/535647/ > > > >- Pure Python driven Linux network configuration ( > > https://bugs.launchpad.net/neutron/+bug/1492714). This effort has been > > going on for several cycles gradually adopting pyroute2. Slawek Kaplonski > > is continuing it with https://review.openstack.org/#/c/545355 and > > https://review.openstack.org/#/c/548267 > > > > > > Port behind port API proposal > >
Re: [openstack-dev] [Neutron] Dublin PTG Summary
Hi Miguel, > * As part of the neutron-lib effort, we have found networking projects that > are very inactive. Examples are networking-brocade (no updates since May of > 2016) and networking-ofagent (no updates since March of 2017). Miguel > Lavalle will contact these projects leads to ascertain their situation. If > they are indeed inactive, we will not support them as part of neutron-lib > updates and will also try to remove them from code search networking-ofagent has been removed in the Newton release. So it will not be necessary to support it as part of neutron-lib updates. Thanks kakuma. On Mon, 12 Mar 2018 13:45:27 -0500 Miguel Lavalle wrote: > Hi All! > > First of all, I want to thank you the team for the productive week we had > in Dublin. Following below is a high level summary of the discussions we > had. If there is something I left out, please reply to this email thread to > add it. However, if you want to continue the discussion on any of the > individual points summarized below, please start a new thread, so we don't > have a lot of conversations going on attached to this update. > > You can find the etherpad we used during the PTG meetings here: > https://etherpad.openstack.org/p/neutron-ptg-rocky > > > Retrospective > == > > * The team missed one community goal in the Pike cycle ( > https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html) and > one in the Queens cycle (https://governance.openstack. > org/tc/goals/queens/policy-in-code.html) > >- Akihiro Motoki will work on https://governance.openstack.o > rg/tc/goals/queens/policy-in-code.html during Rocky > > - We need volunteers to complete https://governance.op > enstack.org/tc/goals/pike/deploy-api-in-wsgi.html) and the two new goals > for the Rocky cycle: https://governance.openstack.o > rg/tc/goals/rocky/enable-mutable-configuration.html and > https://governance.openstack.org/tc/goals/rocky/mox_removal.html. Akihiro > Motoki will lead the effort for mox removal > > - We decided to add a section to our weekly meeting agenda where we are > going to track the progress towards catching up with the community goals > during the Rocky cycle > > * As part of the neutron-lib effort, we have found networking projects that > are very inactive. Examples are networking-brocade (no updates since May of > 2016) and networking-ofagent (no updates since March of 2017). Miguel > Lavalle will contact these projects leads to ascertain their situation. If > they are indeed inactive, we will not support them as part of neutron-lib > updates and will also try to remove them from code search > > * We will continue our efforts to recruit new contributors and develop core > reviewers. During the conversation on this topic, Nikolai de Figueiredo and > Pawel Suder announced that they will become active in Neutron. Both of > them, along with Hongbin Lu, indicated that are interested in working > towards becoming core reviewers. > > * The team went through the blueprints in the backlog. Here is the status > for those blueprints that are not discussed in other sections of this > summary: > >- Adopt oslo.versionedobjects for database interactions. This is a > continuing effort. The contact is Ihar Hrachyshka (ihrachys). Contributors > are wanted. There is a weekly meeting led by Ihar where this topic is > covered: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting > >- Enable adoption of an existing subnet into a subnetpool. The final > patch in the series to implement this feature is: > https://review.openstack.org/#/c/348080. Pawel Suder will drive this patch > to completion > >- Neutron in-tree API reference (https://blueprints.launchpad. > net/neutron/+spec/neutron-in-tree-api-ref). There are two remaining TODOs > to complete this blueprint: https://bugs.launchpad.net/neutron/+bug/1752274 > and https://bugs.launchpad.net/neutron/+bug/1752275. We need volunteers for > these two work items > >- Add TCP/UDP port forwarding extension to L3. The spec was merged > recently: https://specs.openstack.org/openstack/neutron-specs/specs/qu > eens/port-forwarding.html. Implementation effort is in progress: > https://review.openstack.org/#/c/533850/ and https://review.openstack.org/# > /c/535647/ > >- Pure Python driven Linux network configuration ( > https://bugs.launchpad.net/neutron/+bug/1492714). This effort has been > going on for several cycles gradually adopting pyroute2. Slawek Kaplonski > is continuing it with https://review.openstack.org/#/c/545355 and > https://review.openstack.org/#/c/548267 > > > Port behind port API proposal > == > > * Omer Anson proposed to extend the Trunk Port API to generalize the > support for port behind port use cases such as containers nested as > MACVLANs within a VM or HA proxy port behind amphora VM port: > https://bugs.launchpad.net/bugs/1730845 > >- After discussing the proposed use cases, the agreement was to develop > a sp