c5c8612375
The automatic scheduling that was introduced in [0] is having some issues. Add a StaticScheduler that can be used as an alternative for deployments that want explicit control over where their BGP speakers are getting scheduled. Add a job that runs with the new scheduler. [0] https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/478455 Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/815294 Closes-Bug: 1920065 Signed-off-by: Dr. Jens Harbott <harbott@osism.tech> Change-Id: Ib7fcd0c7371bc75089b10024ee1b6e75c98f0188 (cherry picked from commit |
||
---|---|---|
.. | ||
.placeholder | ||
add-static-scheduler-a3b0f54b964ae306.yaml | ||
drop-py27-support-795303ca12cccd34.yaml | ||
dvr-aware-announcements-24bfcb8fee87161d.yaml | ||
mp-bgp-support-d408e8569e94d07f.yaml | ||
support-4byte-asn-d89d7100c0890ebf.yaml |