[openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
anlin.kong at gmail.com
Sat Dec 3 07:07:36 UTC 2016
Thanks for working on this project, we (Catalyst Cloud) also provide VPNaaS
in our OpenStack based public cloud, so maybe we can also provide help from
Lingxian Kong (Larry)
On Mon, Nov 28, 2016 at 5:50 PM, Takashi Yamamoto <yamamoto at midokura.com>
> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <armamig at gmail.com> wrote:
> > Hi
> > As of today, the project neutron-vpnaas is no longer part of the neutron
> > governance. This was a decision reached after the project saw a dramatic
> > drop in active development over a prolonged period of time.
> > What does this mean in practice?
> > From a visibility point of view, release notes and documentation will no
> > longer appear on openstack.org as of Ocata going forward.
> > No more releases will be published by the neutron release team.
> > The neutron team will stop proposing fixes for the upstream CI, if not
> > solely on a voluntary basis (e.g. I still felt like proposing ).
> > How does it affect you, the user or the deployer?
> > You can continue to use vpnaas and its CLI via the python-neutronclient
> > expect it to work with neutron up until the newton
> > release/python-neutronclient 6.0.0. After this point, if you want a
> > that works for Ocata or newer, you need to proactively request a release
> > , and reach out to a member of the neutron release team  for
> > Assuming that the vpnaas CI is green, you can expect to have a working
> > vpnaas system upon release of its package in the foreseeable future.
> > Outstanding bugs and new bug reports will be rejected on the basis of
> > of engineering resources interested in helping out in the typical
> > review workflow.
> > Since we are freezing the development of the neutron CLI in favor of the
> > openstack unified client (OSC), the lack of a plan to make the VPN
> > available in the OSC CLI means that at some point in the future the
> > client CLI support for vpnaas may be dropped (though I don't expect this
> > happen any time soon).
> > Can this be reversed?
> > If you are interested in reversing this decision, now it is time to step
> > That said, we won't be reversing the decision for Ocata. There is quite a
> > curve to ramp up to make neutron-vpnaas worthy of being classified as a
> > neutron stadium project, and that means addressing all the gaps
> > in . If you are interested, please reach out, and I will work with
> you to
> > add your account to , so that you can drive the neutron-vpnaas agenda
> > going forward.
> > Please do not hesitate to reach out to ask questions and/or
> i'm interested in working on the project.
> well, at least on the parts which is used by networking-midonet.
> > Cheers,
> > Armando
> >  https://review.openstack.org/#/c/392010/
> >  https://review.openstack.org/#/c/397924/
> >  https://review.openstack.org/#/admin/groups/150,members
> >  https://review.openstack.org/#/admin/groups/502,members
> >  https://github.com/openstack/releases
> > 
> > http://specs.openstack.org/openstack/neutron-specs/specs/
> > ____________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev