The v3 migration script can handle these just fine - but if we go ahead
and remove them the output can be predominantely shell rather than
script.
Change-Id: I440851a0149e1cc7f8c5c6e8a4e3e0b94088ee82
Extension is required for Neutron ML2 plugin if QoS service plugin
is enabled.
Commit Ic716cf4e5ae94766751d6a391e426946c8b4f8ba enabled QoS
service plugin in Devstack used for Shade functional tests so this
extension driver should also be added.
Change-Id: I48727649f53171055b1949d8a003a3af58404fd3
This patch enables Neutron QoS service plugin in Devstack
used for Shade functional tests.
QoS service plugin is necessary to run QoS related functional
tests added to shade in commit:
Iebff3309423bea1fa871612c5e824940c13926c1
Change-Id: Ic716cf4e5ae94766751d6a391e426946c8b4f8ba
In the -legacy functional tests, besides enabling keystone v2.0, shade
needs to be told to use v2.0
Change-Id: I3aee7a396199532c7e43da057cf8ea5e1e82ced1
We want to be able to test pagination, but the current limit before
pagination starts is 1000. We don't want to try to make 1001 volumes in
devstack. Set it to 6.
Change-Id: Iaeeae708a02fd630f6ad1a5f1cff3cc1045347ec
Similar to the last collapse, the differences in these sets of jobs is
small, and this gives us a very nice pile of combinations of things
available.
Also, remove "dsvm" from the name. These titles are getting a bit log.
There is a tiny hack, which is sed-ing /tmp/dg-local.conf after the
local_conf macro has written it - but that's just because there is one
local.conf setting we want different between legacy and non.
BTW - If you're wondering why I'm doing so much refactoring of shade's
jobs - it's because I'm starting to think about what they need to look
like in a zuul v3 world, so consolidating is the first step for my
brain.
Change-Id: Ie430cbb948de2ae9b5ee75d006d250588a44abbd
legacy and legacy-libs are only different in the git repo checkout.
neutron and neutron-libs are only different in the git repo checkout.
Collapse them from 4 definitions to 2, with parameters.
Also, collapse the template expansion into single calls. This will
expand a few combos we don't use, but that's not actually important
since we're not creating jobs in jenkins.
Finally, remove "neutron" from the normal job names. Neutron is the
default, there is no need to name it.
Change-Id: Ia1c5a25c8b3d1205e34456a46b862e3ea55cda43
The two defintions are the same except for a flag. Collapse them into a
single template with a new parameter.
Change-Id: Ib238597d0b23b93842f1d2c7134e3701c1af1f7f
We're using the old syntax. Use the new syntax. It's the same for most
of the jobs, so define a builder.
While we're at it, sort some of the lists of things and switch from
cloning over git:// to https://
Change-Id: Id91e308514154e4a6f00b9d6fe50cab60dffa0e7
We should make sure that running shade's functional tests under python3
works.
Start off non-voting, but if it passes, we'll flip the switch quickly.
Change-Id: Iffb9f6767c30d171a12481ccd1df502b7aabc4f4
The purpose of this job is to test that latest libs work with
newton devstack. We don't want to install devstack from branch
tips. Rather, we want to install branch tips (of master) into our
functional venv. This means we need zuul to prepare the repo states
for the libraries based on master, even though devstack is set with
a branch-override of stable/newton. It should be ok though, since
we did not set DEVSTACK_PROJECT_FROM_GIT for the projects as well.
Change-Id: I7de309504b5f52c1f7da64d3924efbb6db9a02e7
The magnum plugin seems to want to install magnumclient from source, so
not having it here seems to be making this job very unhappy.
Change-Id: If3441ff22ed352da8c761578b0e1f041da0f56b4
The designate devstack jobs are broken in multiple ways. I have a patch
that fixes two of them, but there is also something about eventlet
versions. So for now, just turn it off - we still have the unit tests.
Once designate's devstack jobs are green again, we can re-enable.
Change-Id: I4eec135f59b30287bb0acb8ad27b1862b3f99a58
Also, fix the job that tests with latest libs on current openstack by
having it actually install into the functional-tips virtualenv.
Finally, add both of these jobs to os-client-config.
Change-Id: Ic841070d572d6363e960b9fef092e1a7ee30f752
Both are there so that we can test old deprecated but still existing
things. There's no need to test those configs separately.
Change-Id: I675809b8a1f51eb74bc3749d94691b1d5da71ba3
The missing-services test works! Except we told it that the keystone job
has designate and it doesn't. Also, remove the plugin references since
they don't work with this config.
Change-Id: I53da84b3cf548f2a3b551f4ea8b52081f7febae7
Shade has traps in its tests to only run tests on services that exist.
However, that can allow skipping of tests that _should_ run in a given
config. Add explicit variables for the things we expect to exist in the
gate so that if they're missing all of a sudden we'll see test jobs
fail.
Change-Id: I2433c7bced6c8ca785634056de45ddf624031509
The magnum team reports problems with having magnum and all the other
services enabled at the same time due to memory pressure. We see a
flakier gate when we have magnum enabled than when we don't. So - split
out magnum support into its own job that does not include swift, heat or
designate, then include swift, heat and designate in the other jobs.
Finally, turn off horizon and ceilometer from the gate since we do not
test either of them.
Change-Id: I7e7ede279be2acabd469fbe997ae54743768dfd8
Add the magnum config back to shade's gate jobs once the offending swift
disablement is done in magnum's gate hook.
This reverts commit 0e098421e2.
Change-Id: I6b9af586f57c3865809ab1867dde8e5c99847adf
Depends-On: Icd82a4ab68533f39f967575c2125b0f61c70e0a6
The magnum devstack plugin landed a change to disable swift. That
breaks shade's swift tests which tests functionality essential for Infra
production.
Turn off magnum support for now. We can revert this when the magnum
devstack plugin works again.
Change-Id: Iee92cb3e386651fb5a9669c3cf0bdedf1326d8b1
We have now some rather long job-template names, shorten them with
replacing job-suffix with suffix.
Before this change we had 1500 usages of job-suffix and 700 of just
suffix. This change therefore unifies to one setting.
Note that this does not change any job names at all, they are unchanged,
it changes and shortens only the names of job-templates.
Change-Id: I514df039a848d9f6619bca3adc05dfb84a761fc9
heat is not in normal devstack anymore, it's in the heat repo. That's
awesome- but our jobs didn't know that. How about let's re-enable it.
Change-Id: I6e8944a18a0d0c80cadc0bd62bb6cdb04c03aee6
Neither library have the ability to be put into LIBS_FROM_GIT, so
putting them into the project or libs list just results in errors.
Change-Id: Ieecf91bfafc35624f7e172bed46a6df02174fcb8
It's good to know about things that client libs do to break us before
they release and break us. Add a devstack job config that installs all
of the client libs from source rather than from pip. This should usually
work, but if it breaks, it means there is something coming that we need
to be prepared for.
Change-Id: Ie387ab3f47d9f79f5d344bcd330784d49198e095
The non-voting job for neutron has been passing consistently.
Integrate with the shade neutron magnum job.
Change-Id: I16b68a8240a9b304f823f487bdc0e4082b544932
This is running on liberty, and magnum liberty version
won't be supported in shade, because is giving compatibility
problems and failures with images.
Change-Id: Ief7f08634c66a6451ff1e73bb62a70eff41b54b1
This job was set to experimental and non-voting, and has
been passing successfully. Integrate magnum in real
keystone2 tests on shade.
Change-Id: Ic1fc9d26fc9cfe4d94f444399dff581b8cf6e2fe
Magnum always need to have neutron enabled to work,
so the test with neutron disabled will always fail.
Change-Id: I9d37a052d0beef3b837385324d9f9fa2f1ec9617
In order to validate the magnum plugin integration,
add more experimental jobs to ensure we have proper coverage
of all tests before moving to check.
Change-Id: Ic3ffc4996eac2d3a7e817ef732f75d0204bd3a80
This patch had been proposed before:
https://review.openstack.org/#/c/295969
But had to be reverted because we were consuming external images
from fedorapeople, that caused our tests to timeout. We are now on
the situation where we have our own custom atomic images, to start
adding that on shade as a previous step for adding magnum integration
to shade.
Change-Id: Ifae8e54e78f6f36cf025ac92ba704391b2052769
When enabling magnum plugin, python-magnumclient is
required, and the job is failing when cloning. Add that project
to the specified list of projects in the job.
Change-Id: I38d65e91750454e958669f44619bbaba05928e52
Start with an experimental job to add magnum plugin
to shade, consuming the atomic images that have been
published in our mirrors.
Change-Id: I1684ee47f1b3afe9a3c365a8a77d25e7bfc38b85
This change needs to land prior to adding Designate support
on shade, as the functional tests will require DevStack
with Designate enabled
Change-Id: Ieaddeb4a0b317f85a2161e67bc5c202cc1b01464
Shade does heat things. Would be nice if we could test that
functionality beyond unit tests. So let's turn on the heat.
Change-Id: I45b58942c54f23b71c45f9118e3c68304afd32b0
Adds a non-voting job that will allow shade to test against
development versions of Ansible.
Change-Id: Ic286193e7ca87d82345f3bf74f29f3f785685715
Depends-On: I7ac84487dd323ef95191fab966244da586b37cd3
Monty Taylor