Difference between revisions of "Meetings/VPNaaS"
Paul Michali (talk | contribs) (→Bucket List) |
Paul Michali (talk | contribs) (→Agenda) |
||
Line 15: | Line 15: | ||
= Agenda = | = Agenda = | ||
− | Updated | + | Updated April 6th, 2015 |
== Announcements == | == Announcements == | ||
− | * | + | * VPNaaS API documentation upstreamed and marked as non-experimental. |
− | * Need StrongSwan | + | * Refactoring complete for L3 callbacks and *aaS |
− | * | + | * StrongSwan upstreamed (Ubuntu only). Need adaptation for Fedora. |
− | * Need | + | * Testing needed (IPv6, StrongSwan/OpenSwan interop, Strongswan). |
+ | * In process of revising Functional jobs to setup environment using DevStack, w/o stacking. | ||
+ | * Need scenario tests implemented (using updated functional jobs). | ||
== Functional Testing == | == Functional Testing == | ||
− | + | StrongSwan and OpenSwan jobs voting. In process of revising tests to operate similar to Neutron, where only the environment is set up for DevStack. | |
− | == | + | == Bugs under Review == |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Current bugs: [https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas,n,z VPNaaS bugs] | Current bugs: [https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas,n,z VPNaaS bugs] | ||
Line 40: | Line 36: | ||
* StrongSwan supported on Fedora. | * StrongSwan supported on Fedora. | ||
* The 'docs' target needs to be implemented for our repo (doc file was removed from Neutron). | * The 'docs' target needs to be implemented for our repo (doc file was removed from Neutron). | ||
− | |||
* Coverage, especially in database and device driver modules, is lacking. | * Coverage, especially in database and device driver modules, is lacking. | ||
* Need functional tests for OpenSwan device driver (and StrongSwan driver) | * Need functional tests for OpenSwan device driver (and StrongSwan driver) |
Revision as of 11:33, 6 April 2015
Contents
Meetings
- Weekly on-demand on Tuesdays at 1600 UTC
- IRC channel: #openstack-meeting-3
- Chair: pc_m (Paul Michali)
If you want to hold a meeting. Update this wiki page with agenda modifications, date of meeting desired, date of update, and then post a notice on the openstack-dev mailing list, at least 24 hours prior to the meeting start time. We have reserved this (new) channel on the IRC for the time/day of week.
Next meeting: TBD
Logs and Minutes
Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/vpnaas/
Agenda
Updated April 6th, 2015
Announcements
- VPNaaS API documentation upstreamed and marked as non-experimental.
- Refactoring complete for L3 callbacks and *aaS
- StrongSwan upstreamed (Ubuntu only). Need adaptation for Fedora.
- Testing needed (IPv6, StrongSwan/OpenSwan interop, Strongswan).
- In process of revising Functional jobs to setup environment using DevStack, w/o stacking.
- Need scenario tests implemented (using updated functional jobs).
Functional Testing
StrongSwan and OpenSwan jobs voting. In process of revising tests to operate similar to Neutron, where only the environment is set up for DevStack.
Bugs under Review
Current bugs: VPNaaS bugs
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)...
- StrongSwan supported on Fedora.
- The 'docs' target needs to be implemented for our repo (doc file was removed from Neutron).
- Coverage, especially in database and device driver modules, is lacking.
- Need functional tests for OpenSwan device driver (and StrongSwan driver)
- Refactor duplication out of device driver code (OpenSwan, StrongSwan, Cisco, Vyatta) (Sridar R working on?)
- The OpenSwan class should be separated from the ABC definition, and placed into a new module. (Brian Bowen working on)
- Remove /n from execute method in utils.py so that duplicate code can be removed in VPN drivers.
- Documentation on how to use StrongSwan
- Documentation on the differences between StrongSwan and OpenSwan
- Should enhance/add unit test cases for:
- Checking various sync() cases: router w/o VPN running on it any more; router with VPN running, but no longer a service configured; process running VPN, but no longer VPN configured.
- Verification of contents of configuration files created for StrongSwan and OpenSwan.
- Verification of reported status for various cases: connections (active, down, pending create), service (created, deleted, admin down).
Open Discussion
Charter
Meeting Commands
/join #openstack-meeting-4
#startmeeting vpnaas
#topic Announcements
#undo
...
#endmeeting