yahoo-eng-team team mailing list archive

[Paul Michali <1464387@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

To support the case where the VPN service is provided outside of the
Neutron router (appliance, VM, separate S/W, H/W, etc), the following
changes should be made:

- Add a field to VPN service table for the local tunnel IP
- When the VPN service GET REST API is called, return the IP address
- When creating a VPN service, populate the database field with the GW IP of the Neutron router (for current implementations).
- Update UTs for this functionality.

This IP information could be used by orchestration tools when setting up
two ends of a VPN IPSec connection.

** Affects: neutron
     Importance: Undecided
     Assignee: Paul Michali (pcm)
         Status: New


** Tags: vpnaas

** Changed in: neutron
     Assignee: (unassigned) => Paul Michali (pcm)

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

Title:
  VPNaaS: Provide local tunnel IP for service

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  To support the case where the VPN service is provided outside of the
  Neutron router (appliance, VM, separate S/W, H/W, etc), the following
  changes should be made:

  - Add a field to VPN service table for the local tunnel IP
  - When the VPN service GET REST API is called, return the IP address
  - When creating a VPN service, populate the database field with the GW IP of the Neutron router (for current implementations).
  - Update UTs for this functionality.

  This IP information could be used by orchestration tools when setting
  up two ends of a VPN IPSec connection.

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