VPNaaS: Help reduce cross project breakage

[Paul Michali]

One issue that has been occurring is that a neutron project commit may change a method/attribute that the neutron-vpnaas project uses, resulting in breakage in the neutron-vpnaas project (which may not be detected for days).

To help reduce this probability, there is a desire to have neutron commits run VPN unit and functional tests. This bug is to document the need for running VPN functional tests on neutron commits.

Code review 203201 upstreamed (before this bug was created) a pair of neutron jobs that will run VPN functional tests in the experimental queue. These jobs need to move to check, and eventually gate queues.

[Paul Michali (pcm)]

Changing the approach a bit here. Plan currently is to do the following:

- Refactor functional jobs to use a common job template
- Test the jobs (non-voting)
- Make the jobs voting
- Add the gate-neutron-vpnaas-dsvm-functional-sswan job to neutron experimental queue
- Test the job for Neutron commits
- Move the job to check and gate queue

On a related bug (#1483417), which is moving API tests for VPN to neutron-vpnaas repo, that bug can leverage off of the same job template to create an API job.

[Paul Michali (pcm)]

Additional changes to approach. Currently, will refactor jobs to use a common template. Community may decide to (later) use one of the jobs (SSwan) for Neutron commits.

[Paul Michali (pcm)]

Not sure why review 240990 is not showing up here.

[Armando Migliaccio (armando-migliaccio)]

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]