The StrongSwan driver has been proposed as the new 'reference'
implementation for VPNaaS, eventually replacing the current OpenSwan
driver.
The StrongSwan driver requires that StrongSwan is installed, and that
AppArmor is disabled for the charon and stroke processes. To do this,
a separate DevStack based functional job will be created.
To support both jobs, and to allow sharing of test cases that may
apply to both driver implementations, the plan is to create the
following directory structure (and corresponding test filtering):
tests/functional/ - Shared test cases/modules
tests/functional/strongswan/ - StrongSwan specific tests
tests/functional/openswan/ - OpenSwan specific tests
Note: As StrongSwan test modules are developed, they will need to
be located in tests/functional/strongswan/. Likewise, the existing
placeholder module for the OpenSwan driver (test cases are empty
currently) will be moved into the tests/functional/openswan area.
As a result, this change will not affect any existing functional
tests.
For this functional job, a different argument will be passed into
the hook scripts to indicate the tests will use StrongSwan. The
gate hook will set the environment variable IPSEC_PACKAGE=strongswan
and DevStack (modified under review 158741) will install StrongSwan
and disable AppArmor for charon/stroke.
Depends-On: fbde695ac2bef255703dc131beeede769d9e005a
Change-Id: Ie0a45fe450ccded61b66a96cd95fac3878d00cfb
Partial-Bug: 1424757
Generally this area of the repo is organized by project, so rename
the *-functional.yaml files to avoid the suggestion that each job
needs its own file. Instead, name them for their projects to suggest
that you can look in each project file to see the jobs that apply
specifically to that project.
Change-Id: I31e95a405c03c207e26f9a63403e1b7205595b7f