Change I95b5390ef24a754f66ccdb9ccde34cd0820b02fd moved the python-
barbicanclient gate to use the new local_conf setting, but this
wasn't compatible with the way the stable python-barbicanclient branches
enabled the barbican plugin. Adds back the old version of the gate
and enables it for only the stable branches.
Change-Id: Ib266438ae46145cdaf757b0a25128a30f5967d17
Unbreak python-barbicanclient gate ("enable_plugin barbican" in
DEVSTACK_LOCAL_CONFIG was removed here:
Idd94b900b238c865a4074ec7d1f9c1c16ef8d434)
Also enables only tempest, rabbit, mysql, and key services, which should
make stacking faster anyway.
Change-Id: I95b5390ef24a754f66ccdb9ccde34cd0820b02fd
For the barbcan functional tests, most of the core
services such as Cinder and Nova are not needed.
Hopefully we can remove them and speed up the gates.
This change adds them as experimental checks. If they succeed, we can
promote these to be the main gates and remove the existing ones.
Change-Id: I68810330dbee4033f8198f39aba5b75cd3357399
Use devstack-gate variable DEVSTACK_PROJECT_FROM_GIT instead of devstack
variable LIBS_FROM_GIT. In this case, we do not need to set PROJECTS
variable and can thus avoid some duplication.
In barbican.yaml: Rework several if conditions into elifs since only one
of these can be true - this makes it easy to see that we do not override
DEVSTACK_PROJECT_FROM_GIT wrongly.
Change-Id: Ib7b187ab9d44d76a007abc23a0feafaab1855030
The grenade gate attempts to run the barbican-tempest-plugin
tests, but the proper configuration of security features needs
to happen before the tests will pass. The configuration
happens in barbican-tempest-plugin's pre_test_hook.sh.
Change-Id: Id8c5fa6c59e1036958a8954305747c60292462dc
This patch will add some configuations to fix
a bug during running gate_grenade for Barbican.
Closes-Bug: #1680713
Change-Id: I9d8c64217d622fd36bf8a8e5cd2f89aecc358fb9
The barbican-tempest-plugin project contains
scenario tests for security features which use
the cursive library. Adding this job to cursive's
jobs will help ensure that changes to cursive
will not break these features.
Change-Id: Id1f3802d4ed10edf355bfe366c192ec5e4fedad1
disable_python3_package did not work. This patch
changes to the more popular disable_service call
to disable Swift when running devstack with Python 3.5.
Change-Id: Iab58f4b79a9120ec325f6b41376cc141a637fd02
Adding a non-voting job that runs Barbican's functional test
suite using Python 3.
Partially-Implements: blueprint goal-py3
Change-Id: Ifd89039513dd27807a6866ef56d41cbb0d521afe
With the recent modifications to merge local.conf and localrc,
setting local.conf values in the pre_test_hook.sh get overwritten
unless KEEP_LOCALRC is set to 1.
It is understood that setting configuration options via
DEVSTACK_LOCAL_CONFIG is preferable, but it is beneficial to
be able to test configuration options alongside the change
being proposed.
Change-Id: Ib06ae8aa890d09ac2cd9e3bf4bfd45440618dcc2
Castellan is used by various projects (nova, glance, cinder, etc.)
for different security features (including image signing, cinder
volume encryption, and ephemeral storage encryption). As scenario
tests are being added to the barbican-tempest-plugin for these
features, it would be valuable to confirm that changes to castellan
to not break these features.
This change adds an experimental gate check to castellan for
the barbican-tempest-plugin, including setting the variable
LIBS_FROM_GIT=castellan to cause the current patchset of castellan
to be used instead of the latest version from pypi.
Change-Id: Ic5b3e86e8f58916bd645a8a7f0d701e8757830ed
Allows the post_test_hook to know which plugin was configured,
so tests specific to the plugin can be executed.
Change-Id: I9fe7b156c4a825c8bfe94a3c48ce686ce0dee01e
Previously, barbican-tempest-plugin was installed every time the
barbican devstack plugin was enabled, which was breaking things for
other projects that were trying to use barbican in their tests, but
not run the barbican tempest tests themselves (see
Iabbdc5177f62514bf5fc4dff5b79ba3c11083506). This is the first step
to explicitly install the barbican-tempest-plugin where the tests
are wanted.
Change-Id: Ibef3f9a135f14727bf57c29e766f838d7da56c68
Co-Authored-By: Brianna Poulos <Brianna.Poulos@jhuapl.edu>
Adds the image signature verification option set to True to local.conf,
which is done in the pre_test_hook.sh in the repository.
Change-Id: I3d96ba5797b0010054137629e484fed0fdecb600
Depends-On: I9b1b412d59bd99c551af6b4d10d2e47c6eebda76
Adds a job for barbican-tempest-plugin that will run DevStack,
enable the Barbican Tempest plugin, and run just the Barbican
tempest plugin tests
Change-Id: I87b5f45b9658df5eb7578a64d5ac360e404859f8
No need for an extra file per repo, we normally have one per project.
In this case each file has exactly one job, so let's clean up.
Change-Id: Ia56096bf5aa3ce66956e7246890b9cbb6f8479e5
Shift barbican plugin testing ahead to run on Xenial for changes against
branches >= newton. Older branches continue to run on Trusty. Note for
the one experimental job it is only set to run on Xenial because it was
already restricted to >= newton.
Change-Id: If8ff8a9efcb12ca8756c058b797ff1fa7f2d897b
Holding off on openstack-dev/devstack, openstack-dev/grenade,
openstack-dev/pbr and openstack/requirements as their branches aren't
gone quite yet.
Change-Id: I12adc42629da0089b8520a6f06d3f59d9522fc02
Barbican currently supports a plugin architecture for secret stores.
One such secret store implementation is the KMIP secret store. There
are no checks in place at the moment to test the functionality of
Barbican with this plugin.
This patch creates a new Jenkins job to test Barbican with the KMIP
secret store plugin. The end effect will be running all of Barbican's
functional tests using a KMIP secret store plugin. This change enables
the PyKMIP server to run as part of the devstack setup.
The tests can only be run on the latest code. The older stable
branches for kilo, liberty, and mitaka are not supported because the
necessary devstack plugin code is not backported to those branches.
The KMIP secret store job is experimental for now until tests verify
the correct operation.
Change-Id: I3fc6abe6f34bcb31c9ea01bfd7c7ccfd22b28bcc
Depends-On: Ib804fa97545f14ed866bfd73bb251e85923a2e4e
Increase devstack wrapper timeout by 5 mins since devstack-gate will use
10 mins - instead of the previous 5 mins - as buffer.
This is needed in this form only for those jobs changed by
21837612a5.
Change-Id: Ida6e84f6c9458d46b7c3792bf57eff27dd72b258
Needed-By: Iea866e4cc40e149e598f35e010ec855937bdf9ae
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/[a-c]*.yaml
Correct timeout value in congress, the variable had 60 minutes, the
wrapper 125 - use 65 now since that's what would have been used.
Change-Id: I8a737755608f7a085424d3010c3da8b81a457ebf
Between the Icehouse and Juno releases, OpenStack changed its
supported Ubuntu LTS platform from Precise to Trusty. In support of
continuing testing stable/icehouse and prior branches on Precise
while starting to test newer branches on Trusty, a branch-based
decision tree was introduced into our Zuul configuration by way of
complex parameter functions with an ever growing list of regular
expression matches on job names.
Now that Icehouse is EOL (in fact, Juno is too) this simply adds
unnecessary complexity and an attractive nuisance for cargo-cult
copying into new job and job-template definitions which don't even
need it. In preparation to remove the associated parameter
functions, get rid of multiple labels in all jobs and set them to
whatever label Zuul would ultimately select.
This change touches a vast number, possibly a majority, of our jobs
and so manual jenkins-jobs updates on all Jenkins masters will be
needed after this merges, before it's safe to approve the
corresponding Zuul configuration cleanup.
Change-Id: Ic952ee02da2c77fe2ace81c4e2fa87531be6119c
The setup in Fedora 21 is broken due to some package issues. On the
other hand, Fedora 21 will be EOL soon. So upgrading to Fedora 23 is the
best step in the long run.
Change-Id: I77fa548e4bc96682808d3721bc5528e091871b6a
This moves the new jobs into place, replacing the old jobs and becoming
the voting jobs for Barbican moving forward. The old jobs become
"-oldstable" and are used only for the juno/kilo branches.
Change-Id: Ib9612a5ac77b8e3d2e4b8fa82b4a462661d4d148
Depends-On: I95219c75b59fc4d49874fb228bba1ae131495159
This will merge the experimental new-plugin job into the existing gate
job, removing the experimental job in the process as it was only for
testing these changes.
Change-Id: I39c9877a2e6dcb8b08c92f9ac51294ffb0d2f1db
Depends-On: I0ec63819b3aae21a6ffaed5cf8285e26dce6ae94
We're working on updating the Barbican devstack plugin, and some changes
would be breaking for the existing gate. This experimental job is to
allow us to test the new job definition without risking temporary
breakage to the gate. This is the change on the Barbican side:
https://review.openstack.org/#/c/167885/
This experimental job is a very minor tweak of the existing gate job, so
hopefully merging this is trivial. It will be removed as soon as it is
shown to work and the primary gate job is updated to match.
Change-Id: I3ceea997a391c8c3fc8b416f6c2d3bb876315cf3
Rename the experimental dogtag devstack-gate job in barbican's tests to
add the '-f21' suffix so it can be run in Fedora 21.
Change-Id: I883e255ac526f3a04c010e0e78572a62a6692760
Add a new devstack-gate job to Barbican to enable functional testing
using RedHat's DogTag as a backend for Barbican.
Change-Id: If5ee9930bfd89459a2f4d7c8f6b5c1ae8bfd0806
Depends-on: I40dfdbc414dbc4fa07b5a5cbed074e6d340c7778
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3
Monty Taylor