9 Commits

Author SHA1 Message Date
madhusudhan-kandadai
4805bb372b Add a new job to run neutron_vpnaas tempest tests
Set up a job for Tempest Integration of neutron-vpnaas API tests
This needs to be merged so [1] can be tested

[1]: https://review.openstack.org/#/c/279787/

Change-Id: Id8ef765e1cac1f48a5cb156cc81e5500cb9097fb
2016-02-24 23:47:54 +00:00
madhusudhan-kandadai
1413eeb857 Add rally gate job for neutron-vpnaas project
Setup rally gate job to run neutron-vpnaas tests

Change-Id: Id6240c0d239de9c580065c7a379e9193b7e79757
2016-02-12 18:24:14 +00:00
Andreas Jaeger
065a80d9c2 Remove DEVSTACK_GATE_TIMEOUT [part 4]
With change Iff5e96bd80b8f165ccc7d6be09b53208613571eb, we do not need
to pass DEVSTACK_GATE_TIMEOUT anymore to devstack-gate, instead the
value from the build-timeout wrapper is passed.

Remove DEVSTACK_GATE_TIMEOUT for jenkins/jobs/[n-z]*.yaml

Increase timeout for all non-grenade jobs by 5 mins since
Iea866e4cc40e149e598f35e010ec855937bdf9ae will use a 10 minute buffer
and the internal timeout should stay the same. The grenade jobs already
have 10 mins of buffer, so no need adjust the timeout.

Adjust timeout for gate-rally-dsvm-cue-{broker},
the removed variable in builder devstack-cue-rally-gate was 100,
so set timeout to 110.

Change-Id: I623fff029fb2e0acdbe2bf93a13af02547062a71
2016-02-07 10:45:25 +01:00
Andreas Jaeger
4331f670b4 Print the JJB template name in some more jobs
Print JJB template name in more job templates so that it's easy to
identify them.

Change-Id: Ia92e39d0ac8c7655577e8fa4accde5748f30d5f1
2015-11-26 20:09:53 +01:00
Paul Michali
22cb0da79a Refactor VPN functional tests to use common template
This will change the existing functional test jobs to use a common job
template. To do this the following steps were taken:

- Make the jobs non-voting, so they don't break the gate. This means
  that reviewers need to check the non-voting results, prior to +A.

- Removed experimental functional jobs that were previously created,
  in neutron-vpnaas repos. These jobs were going to replace the existing
  ones (but do the same thing). Aborting that approach.

- Remove the experimental API job. A separate commit will add it back
  in, and use the new common template, as part of work to getting the
  API job working.

Partial-Bug: #1495584

Change-Id: I015bb7727676a68b1dfc3f04d10a80a308b00435
2015-11-09 16:33:25 -05:00
Andreas Jaeger
bd882cdd7a s/branch-designator/job-suffix/g
As clarkb suggested on #openstack-infra at 17:46 2015-10-22:
"maybe we should s/branch-designator/job-suffix/g in all those files
 as job-suffix makes more sense considering how branch-designator has been
 used".

The rename should make it easier for newcomers to understand
these jobs.

This renames branch-designator everywhere in jenkins/jobs/*.

Change-Id: Icb11271b958d92957fb9907ff03c0b898d7b76fc
2015-10-28 07:50:13 +01:00
madhusudhan-kandadai
100e232ca6 Create experimental job for all neutron-vpnaas tests
1. Add new experimental jobs to run neutron-vpnaas functional
(openswan/strongswan) and api tests with one job template
2. once this new job template verified and tested, remove old functional
jobs and templates

Note: This idea is chosen based on the community reviews so it should not
affect vpn jobs in vpnaas repo and leaving them untouched

Change-Id: Id4614ea1103a9ecc9b069f0b9cd47c0e385f9eba
2015-09-15 11:17:43 -06:00
Paul Michali
d6ce863b1a Setup non-voting VPNaaS func test for StrongSwan
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
2015-03-01 13:54:25 -05:00
James E. Blair
52051c9d67 Rename functional files to projects.
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
2015-02-24 10:17:03 -08:00