Description of problem:

The following cell testing scenarios should be covered:
1) deploy additional cell
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deploy_cellv2.html#deploy-an-additional-nova-cell-v2

Also using 3 stacks for central controller + regional cell controllers + multiple stacks for edge computes connected to regional cell.

2) scale cell up
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deploy_cellv2.html#add-a-compute-to-a-cell

3) scale cell down
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deploy_cellv2.html#delete-a-compute-from-a-cell

4) replace controller in cell

5) delete cell
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deploy_cellv2.html#deleting-a-cell

6) cell minor update

7) cell major upgrade
The procedure would be upgrade all controller (also cell controllers) and in second step the computes.


Administrative tasks which are not directly deployment related:

a) disable/enable cell
From https://docs.openstack.org/nova/rocky/user/cells.html

~~~
- Can I create a cell but have it disabled from scheduling?

Yes. It is possible to create a pre-disabled cell such that it does not become a candidate for scheduling new VMs. This can be done by running the nova-manage cell_v2 create_cell command with the --disabled option.

- How can I disable a cell so that the new server create requests do not go to it while I perform maintenance?

Existing cells can be disabled by running nova-manage cell_v2 update_cell --cell_uuid <cell_uuid> --disable and can be re-enabled once the maintenance period is over by running nova-manage cell_v2 update_cell --cell_uuid <cell_uuid> --enable
~~~


b) reinstate/recreate a formerly deleted cell record
recreate the cell record with same cell uuid and perform host discovery



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: