yahoo-eng-team team mailing list archive

[Akihiro Motoki <1751069@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In Queens release, neutron-vpnaas-agent has gone and the vpnaas feature
is now implemented as l3-agent extension.

Looking at the VPNaaS release notes, there is no information in Queens [1].
vpnaas-agent change is an important topic and it should be documented in the release notes at least.

In addition, more important thing is that there is no documentation on
how to upgrade Pike neutron-vpn-agent to Queens vpnaas L3 agent
extension (with L3-agent). We must document what operators need to do
during upgrade. Perhaps the release note is the right place to document
it (as the first target).

[1] https://docs.openstack.org/releasenotes/neutron-vpnaas/queens.html

** Affects: neutron
     Importance: High
     Assignee: Akihiro Motoki (amotoki)
         Status: New


** Tags: vpnaas

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1751069

Title:
  missing release note (or doc) on vpn-agent change in queens

Status in neutron:
  New

Bug description:
  In Queens release, neutron-vpnaas-agent has gone and the vpnaas
  feature is now implemented as l3-agent extension.

  Looking at the VPNaaS release notes, there is no information in Queens [1].
  vpnaas-agent change is an important topic and it should be documented in the release notes at least.

  In addition, more important thing is that there is no documentation on
  how to upgrade Pike neutron-vpn-agent to Queens vpnaas L3 agent
  extension (with L3-agent). We must document what operators need to do
  during upgrade. Perhaps the release note is the right place to
  document it (as the first target).

  [1] https://docs.openstack.org/releasenotes/neutron-vpnaas/queens.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1751069/+subscriptions