Revision as of 17:39, 23 February 2015

Meetings

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/

Agenda

Updated February 23rd, 2015

Announcements

Starting on modifications for StrongSwan functional job.
Functional gate is voting.
Kilo-3 is coming up quickly (3/19?). Please update any open reviews targeted for the release!
Functional and unit test coverage targets working.
Please review open bugs and blueprints.

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.

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.

Open Discussion

Charter

VPNaaS Team Charter

Meeting Commands

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

...

#endmeeting

@@ Line 10: / Line 10: @@
 = Agenda =
-Updated February 17th, 2015
+Updated February 23rd, 2015
 == Announcements ==
-* Will need new functional job for StrongSwan. Plan to use separate root areas.
+* Starting on modifications for StrongSwan functional job.
-* Deferring making functional gate voting, until restructure functional tests.
+* Functional gate is voting.
-* Please push up for review (or recheck existing reviews) code for functional tests.
+* Kilo-3 is coming up quickly (3/19?). Please update any open reviews targeted for the release!
-* Review out to enable functional test coverage for VPN.
+* Functional and unit test coverage targets working.
 * Please review open bugs and blueprints.
 == Functional Testing ==
-Be sure to check dsvm-neutron-vpnaas-dsvm-functional test results, when code pushed for review, as test is non-voting.
+All commits will need to pass dsvm-neutron-vpnaas-dsvm-functional test results. Working on a non-voting  (initially)StrongSwan functional test.
-Since StrongSwan has different requirements for operation (IPSEC_PACKAGE set to strongswan, and AppArmor disabled), a separate job will be needed. WIll be posting a proposal to mailing list on how to organize test area, along with questions on handling scenario testing (see below)
+Will likely need to split functional tests out of StrongSwan commit, so it can move forward in a timely manner.
-Need functional tests for both OpenSwan and StrongSwan (have some under https://review.openstack.org/#/c/144391/).
 == Scenario Testing ==
-Several complications here. First, we'll need different jobs to handle the StrongSwan versus OpenSwan cases.
+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.
-Second, we have two implementations of functional tests out for review (https://review.openstack.org/#/c/140072/8, https://review.openstack.org/#/c/153292/5). Have discussed with both developers and neither had a preference on their particular proposal. Nikolay is able to proceed with his review (the first one), Zhang is on vacation for 10 days, and agreed that it would be fine to move forward with Nikolay's implementation. It's great that both are stepping up to help on this. We need everyone's help in making sure the solution that we end up with is the best, so please review Nikolay's code and provide feedback (also look at Zhang's and if there are elements there that should be in Nikolay's). If there are better approaches to testing this, please speak up in the review, so we avoid rework!
-Third, both commits are targeted to the Tempest repo, which is in the process of being migrated to Neutron, and a tempest library is being developed. Need to discuss with QA team (above email will start discussion), on whether the scenario test should be placed into the Tempest repo and then let it migrate along with other tests, or whether this can be placed in the VPNaaS repo and use the tempest library (and when will that be available).
 == Bugs ==
 Current bugs:  [https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas,n,z VPNaaS bugs]
-Bring up any bugs of interest.
+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.
 == Open Discussion ==

Difference between revisions of "Meetings/VPNaaS"