The I303a28afe69d5d17261a07fd45c4fa92bbad5598 added tempest test coverage
for the new unshelve-to-host nova feature. However the test fails in the
multi cell job as it tries to unshelve the instance to another cell
which is clearly not supported.

So this patch skips the unshelve to host test cases to unblock the gate.

Related-Bug: #1988316
Change-Id: I50c08a5dcffbf7c31bf02bdfb8615966f9271791

Tempest replaced the below rolevar for run-tempest role
- tempest_test_blacklist is replaced by tempest_test_exclude_list
- tempest_black_regex is replaced by tempest_exclude_regex

old name are still supported for compatiblity but we recommend
to switch to new one.

Change-Id: I4f2d01a4cf443f9c539158e77032cd3d8ce24ad7

This reverts commit c11f4e533676abc676884053544607d263b3ffca.

Test should work since change:
    I0b81282eba8238d8b64a67e38cf9d6392de1f85c

Conflicts:
        devstack/nova-multi-cell-blacklist.txt

NOTE(aarents): the confict is due to change
I95bc22f7d65454cd9e7b54a0e6d9516f2f204978
Disable qos resize tempest test for nova-multi-cell job

Change-Id: Ib953470cf0ccddfec5f253097ddd7f7f0eaf4883

It turned out that during the qos resize work we did not implemented
support of cross cell resize with qos ports. Tempest test coverage for
the resize and migrate is landed recently that made the nova-multi-cell
job to fail.

So this patch disables the qos resize and migrate tempest tests for the
nova-multi-cell job to unblock the gate.

Related-Bug: #1907522

[1] I8c573c4a11a76932057d8415d76114a03269b9f3

Change-Id: I95bc22f7d65454cd9e7b54a0e6d9516f2f204978

Change-Id: I494bf6b10ffb2f54ac4d6079760b44178d82b3fd
Related-Bug: #1906428

When associating a floating IP to instance A but it was already
associated with instance B, we try to refresh the info cache on
instance B. The problem is the context is targeted to the cell
for instance A and instance B might be in another cell, so we'll
get an InstanceNotFound error trying to lookup instance B.

This change tries to find the instance in another cell using its
instance mapping, and makes the code a bit more graceful if
instance B is deleted.

Change-Id: I71790afd0784d98050ccd7cc0e046321da249cbe
Closes-Bug: #1826472

Converts the job to zuul v3 native format so the legacy
playbook is deleted.

Drops the blacklist regex file in favor of simply configuring
tempest to not run resize or cold migration tests.

Change-Id: I4630066731f12c42091ddf9dd3159e0494df88b1

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