Add support back for VPNaaS

Bug #1742510 reported by Jaime Guzman on 2018-01-10
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack neutron-gateway charm
Wishlist
Unassigned

Bug Description

Hi,

When I try to do any operation with neutron vpn-* not work.

Enviroment:
 - neutron-gateway charm-244
 - neutron-api charm-255

For example:

telmex@srvmaas01:~$ neutron vpn-service-list
The resource could not be found.
Neutron server returns request_ids: ['req-65d1a373-9de5-4d62-b1ad-a96dda52f9d8']

neutron ext-list not show the vpnaas. I tried to install the vpn-agent at network node:
 apt-get install neutron-vpn-agent

But the result is the same.

The neutron-api unit the neutron-server.log:
2c8faf64d99b73f34559d5736d5 - default default] No controller found for: vpn - returning response code 404: PecanNotFound
2018-01-10 18:07:51.063 42385 INFO neutron.wsgi [req-65d1a373-9de5-4d62-b1ad-a96dda52f9d8 15b14836d789423b90e3019a3fb96031 13a432c8faf64d99b73f34559d5736d5 - default default] 10.1.3.95 "GET /v2.0/vpn/vpnservices.json HTTP/1.1" status: 404 len: 309 time: 0.0918939

Regards,

Jaime Guzman

Corey Bryant (corey.bryant) wrote :

Development seems to be picking back up: https://github.com/openstack/neutron-vpnaas/commits/master

summary: - VPNaaS not works
+ Add support back for VPNaaS
Corey Bryant (corey.bryant) wrote :

I'm going to add this as a wishlist item which we typically do for feature requests, as adding this back would technically be a new feature.

Changed in charm-neutron-gateway:
status: New → Triaged
importance: Undecided → Wishlist
Trent Lloyd (lathiat) on 2018-05-09
Changed in charm-neutron-gateway:
assignee: nobody → Trent Lloyd (lathiat)
Changed in charm-neutron-gateway:
status: Triaged → In Progress
tags: added: canonical-bootstack

Change abandoned by Trent Lloyd (<email address hidden>) on branch: master
Review: https://review.openstack.org/551168
Reason: VPNaaS support will note be re-integrated at this time

Dmitrii Shcherbakov (dmitriis) wrote :

vpnaas is back under the OpenStack governance from what I can see:

https://github.com/openstack/governance/blame/master/reference/projects.yaml#L2012-L2017
    neutron-vpnaas:
      repos:
        - openstack/neutron-vpnaas
      tags:
        - stable:follows-policy
        - assert:follows-standard-deprecation

https://github.com/openstack/governance/commit/feb90ea14b0ceacf670bf8fce9a1ea6fdb69ab8d
https://review.openstack.org/#/c/506012

But the package is still getting removed for pike+.
https://github.com/openstack/charm-neutron-api/commit/b9115f6c

Trent Lloyd (lathiat) wrote :

This was rejected by the OpenStack team until VPNaaS had good upstream support for 3 releases. Will look at resubmitting then. Given that it was re-added to "Stadium" in Queens, I will aim for resubmitting this in the T release timeframe.

However before that both neutron-vpnaas (separate package) as well as the openstack-dashboard-vpnaas packages needed to be created. We can probably look at fixing the dashboard packaging in the meantime.

Changed in charm-neutron-gateway:
status: In Progress → Confirmed
assignee: Trent Lloyd (lathiat) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers