The PLACEMENT_DB_ENABLED variable in devstack was removed
in Stein: I0b217e7a8c68a637b7a3445f6c44b7574117e320
Change-Id: Ic0a3551cdfa45adc23506143c0fbef6a3ab140dc
The way of the future is python 3 so it makes sense
that our nova-next job, which is meant to test future
things and advanced configuration, would run under python3.
Change-Id: Ie33efb41de19837b488d175900d9a4666f073bce
Set [compute]resource_provider_association_refresh=0 to turn off all
periodic refreshing of the provider cache in the report client.
Note that this probably will have zero effect in the nova-next job
other than making sure that that setting doesn't blow up the world.
Because the job is always doing something, there's never a lull long
enough for the refresh timers to expire anyway, so no periodic
refreshing was happening even before this change.
Change-Id: I072b3fa4847db14e5a3f03c775a377e3514224f1
gate/post_test_perf_check.sh did some simplistic performance testing of
placement. With the extraction of placement we want it to happen during
openstack/placement CI changes so we remove it here.
The depends-on is to the placement change that turns it on there, using
an independent (and very small) job.
Depends-On: I93875e3ce1f77fdb237e339b7b3e38abe3dad8f7
Change-Id: I30a7bc9a0148fd3ed15ddd997d8dab11e4fb1fe1
This adds a post-test bash script to test evacuate
in a multinode job.
This performs two tests:
1. A negative test where we inject a fault by stopping
libvirt prior to the evacuation and wait for the
server to go to ERROR status.
2. A positive where we restart libvirt, wait for the
compute service to be enabled and then evacuate
the server and wait for it to be ACTIVE.
For now we hack this into the nova-live-migration
job, but it should probably live in a different job
long-term.
Change-Id: I9b7c9ad6b0ab167ba4583681efbbce4b18941178
The CachingScheduler has been deprecated since Pike [1].
It does not use the placement service and as more of nova
relies on placement for managing resource allocations,
maintaining compabitility for the CachingScheduler is
exorbitant.
The release note in this change goes into much more detail
about why the FilterScheduler + Placement should be a
sufficient replacement for the original justification
for the CachingScheduler along with details on how to migrate
from the CachingScheduler to the FilterScheduler.
Since the [scheduler]/driver configuration option does allow
loading out-of-tree drivers and the scheduler driver interface
does have the USES_ALLOCATION_CANDIDATES variable, it is
possible that there are drivers being used which are also not
using the placement service. The release note also explains this
but warns against it. However, as a result some existing
functional tests, which were using the CachingScheduler, are
updated to still test scheduling without allocations being
created in the placement service.
Over time we will likely remove the USES_ALLOCATION_CANDIDATES
variable in the scheduler driver interface along with the
compatibility code associated with it, but that is left for
a later change.
[1] Ia7ff98ff28b7265058845e46b277317a2bfc96d2
Change-Id: I1832da2190be5ef2b04953938860a56a43e8cddf
This change adds a post test hook to the nova-next job to report
timing of a query to GET /allocation_candidates when there are 1000
resource providers with the same inventory.
A summary of the work ends up in logs/placement-perf.txt
Change-Id: Idc446347cd8773f579b23c96235348d8e10ea3f6
This will configure [placement_database]/connection to its
own database.
The depends on is to a devstack fix which changes the ordering of
database creation in devstack to ensure the placement database exists
before something tries to sync it.
Depends-On: https://review.openstack.org/564180
Change-Id: I896cd77d1ce793dddbd68a8dd8dcf04c1ab38f2d
This defines the nova-live-migration job, based on the
tempest-dsvm-multinode-live-migration job from openstack-zuul-jobs.
The branch override parts of the job definition are removed since
the job will be defined per-branch now.
Change-Id: Idea86d6bb648b1e6fef8813dbe569724ce81a750
The dependent change to devstack makes devstack use the
Queens Ubuntu Cloud Archive which has libvirt 4.0.0 so we
can remove the flag from the job which disabled the UCA
in devstack since the versions of qemu and libvirt in the
Pike UCA wouldn't work for multiattach.
This also allows us to make the job voting and gating again.
Closes-Bug: #1763382
Depends-On: https://review.openstack.org/554314
Depends-On: https://review.openstack.org/560931
Change-Id: I0962474ff6dfc5fa97670c09a1af97a0f34cd54f
This changes the nova-cells-v1 job to run with neutron instead
of nova-network.
SSH validation is already disabled in Tempest for this job.
Since the os-server-external-events API is not plumbed in for
cells v1, we have to disable vif plugging settings in
nova-cells.conf. This means servers will be ACTIVE before
networking is sure to be ready so we can't rely on ssh validation.
We also configure Tempest to say floating IPs aren't available
which skips several scenario tests that wouldn't work with cells v1
anyway due to them trying to ssh into the guest.
Part of blueprint remove-nova-network
Change-Id: I9de6b710baffdffcd1d7ab19897d5776ef27ae7e
This defines the nova-cells-v1 job, based the tempest-dsvm-cells
job from openstack-zuul-jobs.
The branch override parts of the job definition are removed since
the job will be defined per-branch now (we'll also have to backport
this to stable/queens).
There will be related changes to project-config, devstack, tempest
and openstack-zuul-jobs on this topic branch to use the new job name.
Part of blueprint remove-nova-network
Change-Id: I25c87f27c69e0cdb74e8553305a09cb85f43d87e
This adds an experimental queue job to run non-slow tempest
API and scenario tests using the CachingScheduler as the
scheduler driver.
A blacklist is added since there are a few tests that rely on
filters which don't work well with the CachingScheduler.
The CachingScheduler is deprecated, but this is useful to have
when we're making changes to the scheduler or flows within the
code that involve the scheduler, such as the alternate hosts
work.
Change-Id: I8630ea11c3067ed934de2ef27a63432418e98c33
This moves the legacy-tempest-dsvm-neutron-nova-next-full
job from openstack-zuul-jobs in-tree and updates a
few things since it's now branch specific:
- The cells v2 and placement stuff can be removed since those
are required now (they were optional when this job would run
against newton changes).
- Use nova/gate/post_test_hook.sh rather than the symlink under
nova/tools/hooks/.
The job is currently non-voting and needs to remain that way
until bug 1747511 is fixed.
According to the branch restrictions in project-config, apparently
this job is only running against stable/newton (which no longer
exists) and master, presumably when master was pike. We should also
run this job against stable/pike for the service user test coverage
and post_test_hook.sh run, so we'll likely backport this change
to stable/pike as well.
The related project-config change is:
I36d96f89b3e5323746fcbcef5cc7e4d0384a184d
Change-Id: I24a5f73c29094a23e2fdef8ee8b43601300af593
- renames the base job that is for dsvm jobs
- removes the unused legacy branch override stuff
- moves the comment about keeping the jobs sorted
Change-Id: Idf20864fe3371e4bbafb8c18bcf979a8f3c3eb62
This change adds a new voting check/gate queue job for running
volume multiattach compute API tests.
This configures devstack to enable tempest for volume multiattach
support and disables the Pike UCA since we need qemu<2.10 for
libvirt to work with multiattach volumes.
Depends on the following devstack patch to add the
ENABLE_VOLUME_MULTIATTACH variable. The devstack patch
depends on the tempest patch that adds the volume multiattach
tests and the tempest patch depends on the series of nova
changes that add volume multiattach support.
Depends-On: I46b7eabf6a28f230666f6933a087f73cb4408348
Depends on the following nova patch to fix a bug when
creating a server snapshot of a paused instance when not
using the Pike UCA:
Depends-On: If6c4dd6890ad6e2d00b186c6a9aa85f507b354e0
Depends on the tip of the series of Tempest tests which include
additional tests for resize with a multiattach volume and swap
volume with a multiattach volume.
Depends-On: I751e9e4237e2997e102dd13c4f060deaea73d543
Part of blueprint multi-attach-volume
Change-Id: I51adbbdf13711e463b4d25c2ffd4a3123cd65675
Implement part of step one of the zuulv3 migration guide: move the
purely nova projects to the nova repo [1]. This does not migrate any
jobs used in other projects nor does it convert what is migrated to use
the new 'devstack' or 'devstack-tempest' base jobs. Both of these steps
should be done separately.
What's migrated:
- experimental:
- legacy-tempest-dsvm-nova-lvm (renamed to nova-lvm)
What's dropped:
- experimental:
- legacy-tempest-dsvm-nova-lxc (no one's using this)
- legacy-tempest-dsvm-nova-wsgi-full (WSGI is the default since Pike)
What's still to be migrated, here or to other projects:
- check:
- legacy-grenade-dsvm-neutron-multinode
- legacy-grenade-dsvm-neutron-multinode-live-migration
- legacy-tempest-dsvm-cells
- legacy-tempest-dsvm-full-devstack-plugin-ceph
- legacy-tempest-dsvm-neutron-linuxbridge
- legacy-tempest-dsvm-neutron-multinode-full
- legacy-tempest-dsvm-neutron-nova-next-full
- legacy-tempest-dsvm-multinode-live-migration
- ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa
- legacy-tempest-dsvm-neutron-full
- legacy-grenade-dsvm-neutron
- gate:
- legacy-tempest-dsvm-cells
- legacy-tempest-dsvm-multinode-live-migration
- legacy-tempest-dsvm-neutron-full
- legacy-grenade-dsvm-neutron
- experimental:
- legacy-tempest-dsvm-nova-v20-api
- legacy-grenade-dsvm-neutron-nova-next
- legacy-tempest-dsvm-multinode-full
- legacy-tempest-dsvm-neutron-dvr-multinode-full
- legacy-tempest-dsvm-neutron-dvr-ha-multinode-full
- legacy-tempest-dsvm-neutron-scenario-multinode-lvm-multibackend
- ironic-tempest-dsvm-pxe_ipa-full
- legacy-tempest-dsvm-nova-os-vif
- legacy-tempest-dsvm-nova-libvirt-kvm-apr
- legacy-grenade-dsvm-neutron-multinode-zero-downtime
- ironic-tempest-dsvm-multitenant-network
- ironic-tempest-dsvm-ipa-resourceclasses-partition-pxe_ipmitool-tinyipa
- legacy-tempest-dsvm-full-devstack-plugin-nfs
- legacy-tripleo-ci-centos-7-nonha-multinode-oooq
- legacy-barbican-simple-crypto-dsvm-tempest-nova
- legacy-tempest-dsvm-py35-full-devstack-plugin-ceph
- legacy-tempest-dsvm-neutron-pg-full
- legacy-tempest-dsvm-neutron-full-opensuse-423
- legacy-tempest-dsvm-neutron-src-oslo.versionedobjects
[1] https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details
Change-Id: I41b03a34795efe139d5911c605cdbd3c47a2f059
Matt Riedemann