[Openstack-operators] (dis)Continuation of Neutron VPNaaS
armamig at gmail.com
Thu Jan 19 23:17:17 UTC 2017
On 19 January 2017 at 13:41, Bruno L <teolupus.ext at gmail.com> wrote:
> November last year the Neutron team has announced that VPN as a Service
> will be no longer part of Neutron.
> We run a public cloud based in New Zealand called Catalyst Cloud. Our
> customers find the VPN service extremely useful to integrate their cloud
> tenant's with on-premise infrastructure or even other clouds. We have
> almost one hundred VPNs that were established by customers using it.
> While customers could run a compute instance with something like VyOS,
> they are used to the convenience of having a service managed by us that is
> easy to consume via the APIs or dashboard. It would be a step back for us
> to discontinue VPNaaS.
> As a result, we are interested in picking up the development of VPNaaS and
> keeping it alive. If like us, you are an organisation that sees value in
> VPNaaS, please get in touch with me to discuss how we can collaborate on it.
> As a first step, we would like to ensure that it continue to pass CI and
> it is free of major bugs. Then, we would like to address some of the points
> raised in the VPNaaS scorecard to bring it up to standard with other
> Neutron services. We don't envisage introducing new features during this
> period, but rather focus on stability and maturity.
> Could someone from the Neutron team please help us with the questions
> 1) What would be the process to transfer ownership of the project?
That's great to hear. If you have dev resources who are ready to jump in
Gerrit, please point me to their IRCs and Gerrit accounts and I am happy to
engage with them directly. Yamamoto and I have still core rights on the
repo and work on pushing fixes on an occasional basis. Once your devs feel
more confident, we can definitely talk about adding them to the
neutron-vpnaas core team.
> 2) Until we bring it up to standard, would we need to maintain it as a
> separate project, or as part of Neutron?
My suggestion is to focus on the technical aspect of things before worrying
about the governance change. Those typically can happen only in certain
time windows of the release and with the Ocata release approaching feature
freeze, we definitely need to postpone the governance discussion until Pike
>  http://lists.openstack.org/pipermail/openstack-dev/2016-
>  http://catalyst.net.nz/catalyst-cloud
>  http://specs.openstack.org/openstack/neutron-specs/specs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators