Jump to: navigation, search


< Meetings
Revision as of 15:49, 24 February 2015 by Mathieu-rohon (talk | contribs) (Announcements)


  • Weekly on Tuesdays at 1500 UTC
  • IRC channel: #openstack-meeting-4
  • Chair: Paul Michali (pc_m)

Logs and Minutes

Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/vpnaas/


Updated February 23rd, 2015


Functional Testing

All commits will need to pass dsvm-neutron-vpnaas-dsvm-functional test results. Working on a non-voting (initially)StrongSwan functional test.

Will likely need to split functional tests out of StrongSwan commit, so it can move forward in a timely manner.

Scenario Testing

After talking to QA team, we need to modify the scenario tests to run in the VPN repo, without relying on Tempest framework. There is a tempest-lib, but it is very minimal currently (and utis for Neutron resources won't be for a while). Nikolay is proceeding with modifications to his scenario test (https://review.openstack.org/#/c/140072/8). Plan is to use DHCP namespace to test connectivity of IPSec connection.


Current bugs: VPNaaS bugs

We need to get StrongSwan commit tested out and reviewed, so please help out (https://review.openstack.org/144391)

Bring up any other bugs of interest.

Bucket List

Here are some ideas for tasks that need to be done (feel free to work on them - put your name by any you choose)...

  • The 'docs' target needs to be implemented for our repo (doc file was removed from Neutron).
  • Coverage, especially in database modules, is lacking.
  • Need functional tests for OpenSwan device driver
  • Refactor duplication out of device driver code (OpenSwan, StrongSwan, Cisco, Vyatta)
  • The OpenSwan class should be separated from the ABC definition, and placed into a new module.

Open Discussion


VPNaaS Team Charter

Meeting Commands

/join #openstack-meeting-4
#startmeeting vpnaas
#topic Announcements