
As explained in the spec, in order to support routed networks, we need to add a new scheduler pre-filter with a specific conf option so we can then look at the nova aggregates related to the segments. Since this pre-filter is called every time we verify the scheduler, that means that when we move instances, we should be also be able to only support hosts that are in the same related aggregate. NOTE(sbauza) : We're just setting admin_api variable in the integrated helpers as it's used by _get_provider_uuid_by_host() Implements: blueprint routed-networks-scheduling Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Co-Authored-By: Balazs Gibizer <balazs.gibizer@est.tech> Change-Id: I667f56612d7f63834863476694cb1f4c71a58302
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, 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: