Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Attendees: Ghada Khalil, Joseph Richard, Steve Webster, Sabeel Ansari, Chris Winnicki, Yi Wang, Nicolae Jascanu stx.4.0 Features - TSN support in Container - Prime: Shuicheng / Yi C - Story: https://storyboard.openstack.org/#!/story/2006746 - Status: Starting - setting up environment, but not much progress on feature yet - The hard dependency on the host kernel being 4.19 is required for regular containers, but not kata containers. Can proceed with work for kata containers. - From Yi C: - NIC driver should be okay given IGB (Intel I210) is already there. To support TSN, we still need some kernel features, for example, - Qdisc TAPRIO: implemented TSN protocol 802.1Qbv and was introduced in Linux 4.20 - Qdisc CBS: implemented 802.1Qav and was introduced in Linux 4.15 - probably other features like AF_XDP socket family which was introduced in Linux 4.18. - For the feature of " TSN support in Kata", since Kata container has its own kernel, there is not hard dependency with CentOS 8 upgrade task - Is there any code for this? or just a procedure? - IPv6 PXE boot network support - Prime: Kunpeng Zhang - 99cloud - Story: https://storyboard.openstack.org/#!/story/2006442 - Status: Not Started - Received email from Kunpeng on March 5 indicating that he will provide the plan for this feature shortly. - OVS-DPDK Containerization in StarlingX - Story: https://storyboard.openstack.org/#!/story/2005496 - Status: Out of stx.4.0 - As per Huifeng Le, the detailed status when the feature was put on hold is as follows: - Openstack-helm: - Wait for merge： - Override configurations more than conf section.( https://review.opendev.org/#/c/701676/) - Ongoing： - 1. Make more sections in daemonset overridable.( https://review.opendev.org/#/c/707788/) ? code ready, work on CI - 2. Modify files related to overrides.( https://review.opendev.org/#/c/707775/) ? code ready, work on CI - 3. Ovs per-host overrides support. (https://review.opendev.org/#/c/703639/) ? 50% done - Starlingx: - Ongoing： - Add dpdk parameters for openvswitch.(https://review.opendev.org/#/c/694188/) - This patch depends on the openstack-helm patch. - Todo: - Add dpdk parameters for NEUTRON. stx.4.0 Bugs - Total: 4 - https://bugs.launchpad.net/starlingx/+bug/1862651 -- IPv6 DC: 100.113 alarm "'DATA-NETWORK0' interface failed" raised at both system controller and subclouds after installation - New. Issue appears to be related to having multiple data ports. Not assigned yet. - https://bugs.launchpad.net/starlingx/+bug/1833463 -- armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - Needs to be re-assigned. Action with Yong. Work is related to openstack-helm - https://bugs.launchpad.net/starlingx/+bug/1850438 -- The sriov device plugin pod may start before it's config manifest is written - Steve. On hold. As per Steve, he hasn't been seeing this issue in recent testing. The race condition still exists, but is happening at a much lower frequency. - Agreed to keep as gating for stx.4.0 for now, but as a lower priority item. - https://bugs.launchpad.net/starlingx/+bug/1859641 - IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" - This is related to IPv6. Review in progress, but it only addresses a mariadb issue. As per Zhipeng, another issue related to rabbitmq is hit after that. stx.3.0 Bugs - Total: 1 - https://bugs.launchpad.net/starlingx/+bug/1821026 -- Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - Confirmed to be an issue in stx master (stx.4.0) as well. One code review is posted, but Marvin had issues w/ testing (and is transitioning out of StarlingX) - https://review.opendev.org/#/c/700100/ - Bug transferred to Joseph Richard; not started yet. stx.2.0 Bugs - Total: 0 Low Priority Bugs - Total: 9 - 3 bugs are in progress with reviews posted Test Team Update - Still ramping up the team on the StarlingX project in general. - Nobody has been specifically assigned to the networking domain yet. Expect this to happen in the future after ramp.