[neutron][fwaas] Removal of neutron-fwaas projects from the neutron stadium
Hi, In Shanghai PTG we agreed that due to lack of maintainers of neutron-fwaas project we are going to deprecate it in neutron stadium in Ussuri cycle. Since then we asked couple of times about volunteers who would like to maintain this project but unfortunatelly there is still lack of such maintainers. So now, as we are already in Victoria cycle, I just proposed serie of patches [1] to remove master branch of neutron-fwaas and neutron-fwaas-dashboard from the neutron stadium. Stable branches will be still there and can be maintained but there will be no any code in master branch and there will be no new releases of those 2 projects in Victoria. If You are using this project and wants to maintain it, You can respin it in x/ namespace if needed. Feel free to ping me on IRC (slaweq) or by email if You would have any questions about that. [1] https://review.opendev.org/#/q/topic:retire-neutron-fwaas+(status:open+OR+st...) -- Slawek Kaplonski Senior software engineer Red Hat
On 6/16/20 12:46 PM, Slawek Kaplonski wrote:
Hi,
In Shanghai PTG we agreed that due to lack of maintainers of neutron-fwaas project we are going to deprecate it in neutron stadium in Ussuri cycle. Since then we asked couple of times about volunteers who would like to maintain this project but unfortunatelly there is still lack of such maintainers. So now, as we are already in Victoria cycle, I just proposed serie of patches [1] to remove master branch of neutron-fwaas and neutron-fwaas-dashboard from the neutron stadium. Stable branches will be still there and can be maintained but there will be no any code in master branch and there will be no new releases of those 2 projects in Victoria.
If You are using this project and wants to maintain it, You can respin it in x/ namespace if needed.
Feel free to ping me on IRC (slaweq) or by email if You would have any questions about that.
[1] https://review.opendev.org/#/q/topic:retire-neutron-fwaas+(status:open+OR+st...)
Hi, with neutron-fwaas gone, what will happen to the APIs for fwaas? Will they get deprecated, too, at some point in time? We have a plan to use those APIs in our custom ml2/l3 drivers. Would that still make sense with neutron-fwaas out of the picture? Have a nice day, Johannes -- Johannes Kulik IT Architecture Senior Specialist *SAP SE *| Rosenthaler Str. 30 | 10178 Berlin | Germany
On Thu, Jun 18, 2020 at 5:19 PM Johannes Kulik <johannes.kulik@sap.com> wrote:
On 6/16/20 12:46 PM, Slawek Kaplonski wrote:
Hi,
In Shanghai PTG we agreed that due to lack of maintainers of neutron-fwaas project we are going to deprecate it in neutron stadium in Ussuri cycle. Since then we asked couple of times about volunteers who would like to maintain this project but unfortunatelly there is still lack of such maintainers. So now, as we are already in Victoria cycle, I just proposed serie of patches [1] to remove master branch of neutron-fwaas and neutron-fwaas-dashboard from the neutron stadium. Stable branches will be still there and can be maintained but there will be no any code in master branch and there will be no new releases of those 2 projects in Victoria.
If You are using this project and wants to maintain it, You can respin it in x/ namespace if needed.
Feel free to ping me on IRC (slaweq) or by email if You would have any questions about that.
[1] https://review.opendev.org/#/q/topic:retire-neutron-fwaas+(status:open+OR+st...)
Hi,
with neutron-fwaas gone, what will happen to the APIs for fwaas? Will they get deprecated, too, at some point in time?
We have a plan to use those APIs in our custom ml2/l3 drivers. Would that still make sense with neutron-fwaas out of the picture?
neutron-fwaas removal (and deprecation in Ussuri release) applies all stuffs related to neutron-fwaas including the API and the database plugin layer which provides driver interface. It is not specific to neutron-fwaas reference implementation. Even for API and DB layer, we cannot guarantee that the API and DB layer work well without a working implementation. We the neutron team called for the maintainer for neutron-fwaas several times during Ussuri cycle but nobody volunteered for it, and we believe we had enough time to communicate with the community. Thanks, Akihiro Motoki (irc: amotoki)
Have a nice day, Johannes
-- Johannes Kulik IT Architecture Senior Specialist *SAP SE *| Rosenthaler Str. 30 | 10178 Berlin | Germany
Hi, Thx for this question Johannes and this Akihiro for Your feedback. We were discussion this during our last drivers meeting [1]. We agreed there to keep neutron-fwaas api definition in neutron-lib as an official API. But we will highlight in api-ref that Neutron don't provides any official implementation of this API. That way we can keep support for it e.g. OSC or SDK. [1] http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers... On Thu, Jun 18, 2020 at 11:55:39PM +0900, Akihiro Motoki wrote:
On Thu, Jun 18, 2020 at 5:19 PM Johannes Kulik <johannes.kulik@sap.com> wrote:
On 6/16/20 12:46 PM, Slawek Kaplonski wrote:
Hi,
In Shanghai PTG we agreed that due to lack of maintainers of neutron-fwaas project we are going to deprecate it in neutron stadium in Ussuri cycle. Since then we asked couple of times about volunteers who would like to maintain this project but unfortunatelly there is still lack of such maintainers. So now, as we are already in Victoria cycle, I just proposed serie of patches [1] to remove master branch of neutron-fwaas and neutron-fwaas-dashboard from the neutron stadium. Stable branches will be still there and can be maintained but there will be no any code in master branch and there will be no new releases of those 2 projects in Victoria.
If You are using this project and wants to maintain it, You can respin it in x/ namespace if needed.
Feel free to ping me on IRC (slaweq) or by email if You would have any questions about that.
[1] https://review.opendev.org/#/q/topic:retire-neutron-fwaas+(status:open+OR+st...)
Hi,
with neutron-fwaas gone, what will happen to the APIs for fwaas? Will they get deprecated, too, at some point in time?
We have a plan to use those APIs in our custom ml2/l3 drivers. Would that still make sense with neutron-fwaas out of the picture?
neutron-fwaas removal (and deprecation in Ussuri release) applies all stuffs related to neutron-fwaas including the API and the database plugin layer which provides driver interface. It is not specific to neutron-fwaas reference implementation. Even for API and DB layer, we cannot guarantee that the API and DB layer work well without a working implementation.
We the neutron team called for the maintainer for neutron-fwaas several times during Ussuri cycle but nobody volunteered for it, and we believe we had enough time to communicate with the community.
Thanks, Akihiro Motoki (irc: amotoki)
Have a nice day, Johannes
-- Johannes Kulik IT Architecture Senior Specialist *SAP SE *| Rosenthaler Str. 30 | 10178 Berlin | Germany
-- Slawek Kaplonski Senior software engineer Red Hat
participants (3)
-
Akihiro Motoki
-
Johannes Kulik
-
Slawek Kaplonski