DPDK enabled nodes can't serve External ports
Bug #1934678 reported by
Giuseppe Petralia
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charms Deployment Guide |
Fix Released
|
High
|
Frode Nordahl | ||
charm-ovn-central |
Invalid
|
Undecided
|
Unassigned | ||
charm-ovn-chassis |
Fix Released
|
High
|
Frode Nordahl | ||
charm-ovn-dedicated-chassis |
Fix Released
|
High
|
Frode Nordahl |
Bug Description
SRIOV dhcp is served by External ports in OVN. Those ports are scheduled on the Chassis with highest priority in the HA Chassis Group.
If this host has dpdk enabled, overlay networks are not working on it and SRIOV VMs can't reach the external ports scheduled on it.
Who is responsible for adding the Hosts to HA Chassis Group? Is charm-ovn-central with the relation to charm-ovn-chassis?
If so, should charm-ovn-central avoid adding nodes with dpdk enabled to this group?
description: | updated |
Changed in charm-ovn-central: | |
status: | New → Invalid |
Changed in charm-ovn-chassis: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-deployment-guide: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-ovn-dedicated-chassis: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-deployment-guide: | |
status: | Triaged → In Progress |
Changed in charm-ovn-chassis: | |
milestone: | none → 21.10 |
Changed in charm-ovn-dedicated-chassis: | |
milestone: | none → 21.10 |
Changed in charm-ovn-chassis: | |
status: | Fix Committed → Fix Released |
Changed in charm-ovn-dedicated-chassis: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
At present the DPDK-enabled nodes do not really participate in the overlay network, and they should not really be considered for use as part of HA Chassis groups. The chassis charms currently always set the `external_ ids:ovn- cms-options= enable- chassis- as-gw` flag for units with valid bridge mapping and external networking configuration.
As noted in bug 1908377 there should be a way to influence this further and this is a good example of a use case where it is required.