Changes in [1] could potentially break a mixed-compute-version
environment as we don't have grenade coverage for cold migrate and
resize. This adds that coverage to the nova-grenade-multinode
job.
[1]https://review.opendev.org/#/c/655721/10
Change-Id: I81372d610ddf8abb473621deb6e7cb68eb000fee
We are planning to add non-live-migration multinode tests to this job
so first we rename it to be more generic.
Change-Id: I7571ff508fcccba40cf2307a8788c1850d2d9fd8
This patch resolves a TODO in the .zuul.yaml about using common
irrelevant files in our dsvm jobs. To be able to do that we need to move
the test hooks from nova/tests/live_migraton under gate/.
Change-Id: I4e5352fd1a99ff2b4134a734eac6626be772caf1
Due to bug 1802143, devstack was ignoring variables set in the
$NOVA_CPU_CONF section of local_conf. Now that that bug has been fixed
(see the Depends-On) we can put those back in their rightful place.
This patch moves the [compute]resource_provider_association_refresh
setting, introduced via [1], accordingly.
[1] https://review.opendev.org/616033
Depends-On: https://review.opendev.org/672805
Change-Id: Ifa50748b6d6e91ac954d0a7a6060505fd45716d4
Related-Bug: #1802143
Compared to tempest-full-py3 and tempest-slow-py3
the nova-multi-cell job has been relatively stable
for the past couple of months so let's make it voting
so we don't regress multi-cell functionality.
Change-Id: I11081177abfe2fb69fbd8fc17464c9f08962ab4c
This adds a nova-specific variant of the
tempest-smoke-py3-osprofiler-redis job to nova's
experimental queue. This could be useful in comparing
before and after results on nova changes that are
related to performance, although that's admittedly
hard in a CI environment where we could be running on
different node providers (we could pin that though?)
and differing levels of noisy neighbors during each
job run.
Change-Id: I2dcb5c1e8289eaf7977b38a3d26e74183823c42b
We don't run any tests that require the cinder backup
service in the nova-next job nor do we care to so save
some time in stacking and space on the node by not
installing that service.
Change-Id: I6991a231366908920847fa1b8375ece8d8b35268
For the most part this should be a pretty straight-forward
port of the run.yaml. The most complicated thing is executing
the post_test_hook.sh script. For that, a new post-run playbook
and role are added.
The relative path to devstack scripts in post_test_hook.sh itself
had to drop the 'new' directory since we are no longer executing
the script through devstack-gate anymore the 'new' path does not
exist.
Change-Id: Ie3dc90862c895a8bd9bff4511a16254945f45478
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
Tempest has defined the new job 'tempest-ipv6-only'(adding
in Depends-On patch) which will deploy services on IPv6 and run smoke
tests and IPv6 related tests present in Tempest.
This job will be part of Nova, Neutron, Cinder, Keystone, Glance, Swift
gate.
Verification structure will be:
- 'devstack-IPv6' deploy the service on IPv6
- 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address
- 'tempest-ipv6-only' will run the smoke + IPv6 related test case.
This commit adds the new job 'tempest-ipv6-only' run on gate.
Story: #2005477
Task: #35909
Depends-On: https://review.opendev.org/#/c/671231/
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: I21cba258e4ad55681468c66060f4e0c1f4becbd4
tempest-full-py3 job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate-py3 gate template which run on
multiple services (nova, neutron, cinder, glance, placement, swift, keystone)
check and gate pipeline.
Due to all services tests run in single tempest-full-py3 job, it has
been not so stable. Many times unrelated service test break other
project gate.
But not all those services are dependent of Nova. Dependent in term of
both way, not all services used by Nova or use Nova. Nova gate
does not need to run all those independent services tests. It can run only
Nova, Neutron, Cinder and Glance related tests.
Idea here is to make integrated-gate testing more stable without losing
the test coverage.
Tempest has new "integrated-gate-compute" template which will run only
Nova, Neutron, Cinder and Glance related tests[1].
This commit replaces the "integrated-gate-py3" template with new
"integrated-gate-compute".
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
[1] https://opendev.org/openstack/tempest/src/branch/master/.zuul.yaml#L594
Change-Id: I11dd1a94054ed29f70330906c1d95967b3de718c
Due to regression bug 1833902 we should have the option to
run the neutron job that tests the OVS hybrid plug configuration
on specific patches.
We could eventually consider running this in the check queue
like neutron-tempest-linuxbridge with a strict set of irrelevant
files but that would require some thought, i.e. we'd want to run
the job on changes to nova/compute/manager.py since the network
vif model bind events code is used in the ComputeManager and is
specific to OVS hybrid plug ports. Rather than get bogged down in
thinking up what that set is, this change takes the easy path and
just throws the job into the on-demand experimental queue.
Change-Id: Id5172d97b349abe59b47d1284e97943091652419
Related-Bug: #1833902
This reverts commit 47b73030cba7d67fe308c5b89c2a64e93d74bcd6.
The dependent devstack change fixes the issue so we can enable
vnc console tempest testing in the nova-multi-cell job.
Depends-On: https://review.opendev.org/661391/
Change-Id: Iad71b6e15bb91e51080cd9f940410dc9af791963
Related-Bug: #1830417
This addresses comments from the series:
* Remove usage-specific info from docstring
* Add note to nova-next job description "changelog"
* Add info about data migration to config option help
* Consolidate code under count_usage_from_placement conditional
* Consolidate variables for checking data migration doneness
* Remove hard-coded user_id and project_id from func test
* Re-word code comment about checking data migration doneness
Related to blueprint count-quota-usage-from-placement
Change-Id: Ida2de9256fcc9e092fb9977b8ac067fc1472c316
In I73f9dacd912331d209a6fa04eaf5591d94d720f2 the functional-py36
was made reusable by other projects by adding explicitly adding
nova to projects and explicitly stating the zuul work dir.
This change adds the other functional jobs.
Change-Id: Iaf2c1f87ae4a4ec2ecf6cc19220c6d15f8580321
Story: 2005562
NoVNCConsoleTestJSON.test_novnc is intermittently failing
in the multi-cell job when trying to get a vnc console for
an instance in cell2. It looks like requests aren't getting
routed to the novnc-cell2 service properly, so let's skip
novnc tests until the bug is fixed since we want to stabilize
this job to make it voting.
Change-Id: I74a4b392ccec66a7a80a117d1cdf83a418c7dcdc
Related-Bug: #1830417
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: I095770fabafda1a7735c2711d4df061a6dc2bb78
Depends-On: https://review.opendev.org/#/c/641878/
We'd like placement to be able to run this job itself. Instead of
duplicating it, we can simply use it directly. However, according
to discussions with the infra gang, to ensure that works properly
we need to make openstack/nova a required project and explicitly
set zuul_work_dir. These are the default values already when
used from nova itself.
Change-Id: I73f9dacd912331d209a6fa04eaf5591d94d720f2
Story: 2005562
With the dependent devstack fix we should be able to run
the n-novnc service in a multi-cell setup.
Depends-On: https://review.opendev.org/649473/
Change-Id: I6d2a564840a5ac4f4f7e803619d9962653bb5d6c
Related-Bug: #1822873
This adds a non-voting nova-multi-cell job which
is a 2-node job with 2 non-cell0 cells (cell1 and cell2).
The compute on the controller will be in cell1 and the
subnode compute will be in cell2.
Until cross-cell resize is supported, cold migration
has to be disabled since we can't cold migrate to
the same host (and there is only one compute host per
cell). As a result, resize to the same host is enabled
(it is normally disabled in the tempest multinode job).
The parent job enables live migration testing but since
we only have one host per cell and don't support live
migration across cells, the live migration tests are
also disabled.
The job is also setup to run with python3 since that
is the way of the future.
Non-essential services, like cinder-backup, are disabled
since we (1) won't need it for the tests we run and
(2) would like to save as much room on the hosts as possible
since we're running multiple cell conductors on the
controller host.
Since this is new and its already uncovered at least one
bug (bug 1826472), the job is non-voting in the check queue
for now until we're happy with its stability.
Related to blueprint cross-cell-resize
Change-Id: I8ad3f8bcbecf0f6b1d0f57e9f61ff21bd7fbe365
We already skip running the devstack/tempest integration jobs
for changes which only touch nova/tests/* but not the nova/test.py
module itself, so this adds that filter.
Change-Id: I8984e5b68ccb7d327b7ce16c50f19e46e769699a
We're going to start ripping out cells v1. First step is removing the
tests for this soon-to-be-removed feature.
Part of blueprint remove-cells-v1
Change-Id: I2031bf2cc914d134e5ed61156d2cfc621f006e0b
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
The functional tests are configured to install placement from git
so that they test with placement-from-master. In the py27 and py35
functional tests, placement is a part of required-projects, which
means that depends-on to a particular patch of placement can work
via tox-siblings[1].
This patch adds the same functionality for py36 and py37 functional
tests, which currently run only in the experimental queue.
[1] https://docs.openstack.org/infra/manual/zuulv3.html#installation-of-sibling-requirements
Change-Id: Ia40aba6d3036fea2bc62fdf76e8e221b552f1cdc
The job was added to nova with change:
05ab017907376cc262887104556b01fee18db0c2
As I explained in the mailing list [1], we should
have sufficient test coverage in other voting jobs
that run against nova changes with the use of the
tempest-full-py3, tempest-slow-py3, nova-next, and
nova-(grenade)live-migration jobs. The tempest-full
and nova-next jobs are single-node jobs which run
compute API tests and some scenario tests but no
slow tests and no live migration. The tempest-slow
job is multinode and only runs slow tests. The
live migration jobs run live migration tests over
two nodes (and nova-live-migration also runs
evacuate tests). So tempest-multinode-full is
probably mostly redundant, a waste of time and
resources, especially since it's non-voting.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004139.html
Change-Id: Id2f748d4b119002292bda45689472a68254079ee
I noticed change Iea6288fe6d341ee92f87a35e0b0a59fe564ab96c
was not running the nova-live-migration job even though
it was making changes to nova/tests/live_migration/hooks/run_tests.sh.
The reason is the nova-live-migration job irrelevant-files were
excluding changes to nova/tests/*.
This copies the nova-grenade-live-migration irrelevant-files list
to the nova-live-migration job and defines it as a variable so it
can be re-used in the nova-grenade-live-migration job definition.
Change-Id: I753fda1a83b340f4699c049158e6744b099f55d8
While moving the legacy job nova-next on bionic, tls-proxy
did not work and leads to nova-next job fail.
To proceed further on Bionic migration which is blocked by nova-next failure,
this commit temporary disable the tls-proxy service until bug#1819794 is fixed.
Also this updates the parent of nova-tox-functional-py35 from openstack-tox
to openstack-tox-functional-py35 in order to handle the upcoming change
of the infra CI default node type from ubuntu-xenial to ubuntu-bionic.
The python3.5 binary is not provided on ubuntu-bionic and the shared
"py35" job definitions in the openstack-zuul-jobs repository have been
patched to force them to run on ubuntu-xenial [1]. We should inherit
from one of these jobs for jobs that rely on python3.5.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003746.html
Related-Bug: #1819794
Change-Id: Ie46311fa9195b8f359bfc3f61514fc7f70d78084
The test_network* scenario tests in tempest take a really long
time. For example, the tempest.scenario.test_network_v6.TestGettingAddress
tests in one job (that timed out) took ~35 minutes.
We already run test network scenario tests in the tempest-slow job
so let's just let that job handle these and exclude them from
nova-next.
Change-Id: I9c7fc0f0b0937f04c5b3ab9c5e8fff21c4232b86
This moves the legacy-grenade-dsvm-neutron-multinode-live-migration
job from openstack-zuul-jobs in-tree. Nova is the only project
that runs this job and this allows nova to directly manage it.
The job will still use the same irrelevant-files list and is still
non-voting for the time being and only runs in the check queue.
It has been renamed to "nova-grenade-live-migration".
This change is meant to be backported to rocky, queens and pike
to allow us to drop legacy-grenade-dsvm-neutron-multinode-live-migration
from openstack-zuul-jobs where the job is branchless but restricted
to pike+ branches.
A follow up master-only (stein) change will make the job voting
and gate per the plan in the mailing list [1].
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003341.html
Change-Id: Ie9b61775dbb92b10237688eaddaca606c1c73a23
Tempest live migration tests do not create the server
with config drive so we do not, by default, have test
coverage of live migrating an instance with a config
drive. This change forces nova to create a config
drive for all instances in the nova-live-migration
job which will also run evacuate tests with a config
drive attached.
Change-Id: I8157b9e6e9da492a225cbb50a20f434f83a5fecb
Related-Bug: #1770640
The change to irrelevant-files in I902e459093af9b82f9033d58cffcb2a628f5ec39
made it such that the job will *only* run on changes to the
nova/tests/live_migration/ path which was not the intent. This fixes
the regex to not run the job on changes to nova/tests/ unless those
changes are in the nova/tests/live_migration/ directory.
This would probably be easier to reason about long-term if the
nova/tests/live_migration/ directory was moved under nova/gate/
and then we could just use the standard irrelevant-files list. That
refactoring is left for another day though.
Change-Id: Iff2fca18a779e70deecf8e57279e2daf9bc5529a
Closes-Bug: #1816152