DPDK enabled nodes can't serve External ports

Bug #1934678 reported by Giuseppe Petralia
10
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
Revision history for this message
Frode Nordahl (fnordahl) wrote :

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.

Frode Nordahl (fnordahl)
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)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-ovn-chassis (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/x/charm-ovn-chassis/+/799674

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)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-ovn-dedicated-chassis (master)
Changed in charm-ovn-dedicated-chassis:
status: Triaged → In Progress
Changed in charm-deployment-guide:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-deployment-guide (master)

Reviewed: https://review.opendev.org/c/openstack/charm-deployment-guide/+/799836
Committed: https://opendev.org/openstack/charm-deployment-guide/commit/12a02a451379a3c847a5f7b7d407b8a8194eb8d2
Submitter: "Zuul (22348)"
Branch: master

commit 12a02a451379a3c847a5f7b7d407b8a8194eb8d2
Author: Frode Nordahl <email address hidden>
Date: Wed Jul 7 15:55:10 2021 +0200

    ovn: Document use of prefer-chassis-as-gw option

    Related-Bug: #1908377
    Closes-Bug: #1934678
    Change-Id: I4d2d79d4b542ad8acfae53352d764c54be429216

Changed in charm-deployment-guide:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-ovn-chassis (master)

Reviewed: https://review.opendev.org/c/x/charm-ovn-chassis/+/799674
Committed: https://opendev.org/x/charm-ovn-chassis/commit/857fa870246165ce93088688bb8a8f877ccfaaf5
Submitter: "Zuul (22348)"
Branch: master

commit 857fa870246165ce93088688bb8a8f877ccfaaf5
Author: Frode Nordahl <email address hidden>
Date: Tue Jul 6 15:43:22 2021 +0200

    Add prefer-chassis-as-gw configuration option

    By default the CMS will schedule HA chassis groups across all
    chassis with bridge- and bridge interface mappings configured.

    This configuration option would allow you to influence where
    gateways are scheduled when all units have equal bridge- and
    bridge interface mapping configuration.

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/599
    Closes-Bug: #1908377
    Closes-Bug: #1934678
    Related-Bug: #1848757
    Change-Id: I52f37a512fccbb3a025ffef81fcecb69fa169792

Changed in charm-ovn-chassis:
status: In Progress → Fix Committed
Changed in charm-ovn-dedicated-chassis:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-ovn-dedicated-chassis (master)

Reviewed: https://review.opendev.org/c/x/charm-ovn-dedicated-chassis/+/799819
Committed: https://opendev.org/x/charm-ovn-dedicated-chassis/commit/257bb43029699ea820cac036f2558245b3ff62d2
Submitter: "Zuul (22348)"
Branch: master

commit 257bb43029699ea820cac036f2558245b3ff62d2
Author: Frode Nordahl <email address hidden>
Date: Wed Jul 7 15:10:18 2021 +0200

    Add prefer-chassis-as-gw configuration option

    By default the CMS will schedule HA chassis groups across all
    chassis with bridge- and bridge interface mappings configured.

    This configuration option would allow you to influence where
    gateways are scheduled when all units have equal bridge- and
    bridge interface mapping configuration.

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/599
    Closes-Bug: #1908377
    Closes-Bug: #1934678
    Related-Bug: #1848757
    Change-Id: Ifd8f6b29c4f117850b243e2fdb79067659242a0e

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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.