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
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: