d2e58cb490
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
10 lines
483 B
Plaintext
10 lines
483 B
Plaintext
# --blacklist-file contents for the nova-multi-cell job defined in .zuul.yaml
|
|
# See: https://stestr.readthedocs.io/en/latest/MANUAL.html#test-selection
|
|
|
|
# Exclude tempest.scenario.test_network tests since they are slow and
|
|
# only test advanced neutron features, unrelated to multi-cell testing.
|
|
^tempest.scenario.test_network
|
|
|
|
# Disable associate floating IP tests until bug 1826472 is fixed.
|
|
tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsAssociationTestJSON
|