Limitation to schedule guest for a given segment
Bug #1979959 reported by
Sahid Orentino
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
There is a limitation today in Nova when using routed provider network. Even if the scheduler is able to select the right host. It will not be able to select the right segment for a given fixed IP.
The current algorithm sticks on selecting the first segment that it discovers.
Changed in nova: | |
status: | Incomplete → New |
To post a comment you must log in.
Which release are you talking ? I guess you're using Wallaby or later, as we added scheduling capabilities for routed networks in there : /specs. openstack. org/openstack/ nova-specs/ specs/wallaby/ implemented/ routed- networks- scheduling. html
https:/
IIUC, you're refering to a limitation we have in the current prefilter, which takes the first subnet of a list based on the fixed IP that was passed. /github. com/openstack/ nova/blob/ c53ec4e48884235 566962bc934cbf2 92ad5b67b8/ nova/scheduler/ request_ filter. py#L327- L330
https:/
Putting this bug report as Incomplete until we figure out the exact need.