Difference between revisions of "Meetings/VPNaaS"
Paul Michali (talk | contribs) (→Announcements) |
Paul Michali (talk | contribs) (→Functional Testing) |
||
Line 18: | Line 18: | ||
== Functional Testing == | == Functional Testing == | ||
− | + | Plan is to have tests/functional/ hold shared functional test modules, tests/functional/openswan/ to hold OpenSwan specific tests, and tests/functional/strongswan/ to hold StrongSwan specific tests. | |
− | + | A new check-neutron-vpnaas-dsvm-functional-sswan is being created, to set up DevStack for StrongSwan operation. | |
+ | |||
+ | The post-test-gate.sh script needs to be modified for support of scenario testing (159746). | ||
== Scenario Testing == | == Scenario Testing == |
Revision as of 17:44, 2 March 2015
Contents
Meetings
Since there has been very limited participation over the past several weeks, a questionnaire was sent to the mailing list last Tuesday (2/24) to see if the format (periodic/on-demand) and/or date/time should be changed for these meetings. No one replied, so the default action will apply, which is to have VPNaaS discussions as an on-demand topic during Neutron meetings.
Logs and Minutes
Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/vpnaas/
Agenda
Updated February 23rd, 2015
Announcements
- DevStack support for StrongSwan is now upstreamed.
- VPN agent refactoring has started to eliminate dependency on L3 agent.
- New functional job being created for StrongSwan (out for review) - will run in experimental mode.
- Directory structure change for functional test area (out for review).
Functional Testing
Plan is to have tests/functional/ hold shared functional test modules, tests/functional/openswan/ to hold OpenSwan specific tests, and tests/functional/strongswan/ to hold StrongSwan specific tests.
A new check-neutron-vpnaas-dsvm-functional-sswan is being created, to set up DevStack for StrongSwan operation.
The post-test-gate.sh script needs to be modified for support of scenario testing (159746).
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.
Bugs
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
Charter
Meeting Commands
/join #openstack-meeting-4
#startmeeting vpnaas
#topic Announcements
#undo
...
#endmeeting