neutron vpn run as l3 extenstions now

Bug #1753617 reported by Jeffrey Zhang on 2018-03-06
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla
Critical
Unassigned
Queens
Critical
Unassigned
kolla-ansible
Critical
Unassigned
Queens
Critical
Unassigned

Bug Description

neutron vpn run as l3 extensions now, no need built and run vpn image.

Changed in kolla:
importance: Undecided → Critical
Changed in kolla-ansible:
importance: Undecided → Critical
no longer affects: kolla/pike

Reviewed: https://review.openstack.org/551729
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=c62c8da375e9267b2da4a1e14f4bdb47b5866f99
Submitter: Zuul
Branch: stable/queens

commit c62c8da375e9267b2da4a1e14f4bdb47b5866f99
Author: chenxing <email address hidden>
Date: Mon Mar 5 14:07:32 2018 +0800

    Migrate neutron-vpnaas-agent to neutron-l3-agent

    Closes-Bug: #1753617
    Change-Id: I47cd8ba5a14da3c76d5b1eb0b4c0cf0c729eb2ff
    Partially-Implements: blueprint restructure-neutron-vpnaas
    (cherry picked from commit 1ca33914f8c154ed1b4263cec5ac35bf1aebecc7)

This issue was fixed in the openstack/kolla 6.0.0.0rc2 release candidate.

Derek Yang (hswayne77) wrote :

Will kolla-ansible support vpnaas horizon dashboard in the future?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers