a1673d3118
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
14 lines
645 B
YAML
14 lines
645 B
YAML
---
|
|
features:
|
|
- |
|
|
The scheduler can now verify if the requested networks or the port are
|
|
related to Neutron `routed networks`_ with some specific segments to use.
|
|
In this case, the routed networks prefilter will require the related
|
|
aggregates to be reported in Placement, so only hosts within the asked
|
|
aggregates would be accepted.
|
|
In order to support this behaviour, operators need to set the
|
|
``[scheduler]/query_placement_for_routed_network_aggregates`` configuration
|
|
option which defaults to ``False``.
|
|
|
|
.. _`routed networks`: https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html
|