enabling uplink_status_propagation ML2 extension is not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Guide |
Fix Released
|
Undecided
|
Diko Parvanov | ||
OpenStack Neutron API Charm |
Fix Released
|
Undecided
|
Diko Parvanov | ||
Train |
In Progress
|
Undecided
|
Danny Cocks | ||
Ussuri |
In Progress
|
Undecided
|
Danny Cocks | ||
Victoria |
In Progress
|
Undecided
|
Danny Cocks | ||
Wallaby |
In Progress
|
Undecided
|
Danny Cocks | ||
Xena |
In Progress
|
Undecided
|
Danny Cocks |
Bug Description
The ML2 extension "uplink_
Currently, this config option isn't exposed in any way in OVN or neutron charms.
Feature that we'd like to see configurable through charm config was developed as part of [0].
Example use case: bonding of VF interfaces inside a VM. When both VFs have a "link-state: enable" (the only possible configuration with current limitations), one will not get the benefit of bonding when the PF link's state goes down (e.g. network switch failure). The instance won't be aware of that fact as both VFs will be reported as UP, and will send 50% of network traffic into a black hole.
Changed in charm-neutron-api: | |
status: | In Progress → Fix Committed |
milestone: | none → 22.04 |
Changed in charm-guide: | |
status: | New → In Progress |
assignee: | nobody → Diko Parvanov (dparv) |
Changed in charm-guide: | |
status: | In Progress → Fix Committed |
Changed in charm-neutron-api: | |
assignee: | nobody → Diko Parvanov (dparv) |
Changed in charm-neutron-api: | |
status: | Fix Committed → Fix Released |
Changed in charm-guide: | |
status: | Fix Committed → Fix Released |
Tests confirmed that neutron-api config change is enough to make this work cluster-wide.