[Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/20
Wang, Yi C
yi.c.wang at intel.com
Mon Feb 24 08:06:02 UTC 2020
Hi Ghada/Matt,
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.
Thanks.
Yi
-----Original Message-----
From: Khalil, Ghada <Ghada.Khalil at windriver.com>
Sent: Friday, February 21, 2020 9:15 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/20
Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking
Team Introductions (for Romania team)
- Nikoli Jascanu: Leader of StarlingX Intel validation team in Europe
- Team size is 10 people - 7 in Romania + 3 in Germany
- Mihail-Laurentiu Trica: Ramping up in general on StarlingX; not particularly focused on networking at this time
- Chris Winnicki: WR StarlingX Test team
- Matt Peters: StarlingX Networking Technical Lead
- Steve Webster: StarlingX WR Networking team
- Joseph Richard: StarlingX WR Networking team
- Sabeel Ansari: StarlingX WR Networking team - new to the team
- Yi Wang: StarlingX Intel team
stx.4.0 Features
- TSN support in Kata
- Prime: Shuicheng
- Status: Not Started
- Question from Matt: Is there a hard dependency on the 4.19 / CentOS 8 kernel? Is there a possibility to break this dependency?
- Are there specific features of the newer kernel that is required?
- Ghada to follow up with Shuicheng & Yong
- IPv6 PXE boot network support
- Prime: Kunpeng Zhang - 99cloud
- Status: Not Started
- Ghada to reach out to him
- OVS-DPDK Containerization
- Question from Matt: Was there any StarlingX work done on this feature before it was put on hold?
- What are the plans for the current reviews posted in other projects? Are they being abandoned or transitioned to a new owner?
- Current reviews:
- starlingx/openstack-armada-app: https://review.opendev.org/#/c/696437/
- starlingx/config: https://review.opendev.org/#/c/694188
- openstack/openstack-armada-app: https://review.opendev.org/#/c/701676/
- Ghada to follow up with Huifeng
stx.4.0 Bugs
- Total: 4
- 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. This is a larger scope item. Should re-gate?
- https://bugs.launchpad.net/starlingx/+bug/1855191 - Unable to modify interface to use static IP
- Thomas. Review in progress
- https://bugs.launchpad.net/starlingx/+bug/1856587 - Traceback in unlock host when configuring pci-passthrough interfaces and sriovdp label enabled
- Thomas. Review in progress
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
- This is a valid issue and we want to continue working on it. There is a review in progress, but there are issues with testing.
- Is Zhipeng taking this over? Recent emails sent from Weifei
stx.2.0 Bugs
- Total: 2
- https://bugs.launchpad.net/starlingx/+bug/1849655 -- StarlingX R2 duplex: VM not getting IP assigned to the vlan network when re-spawned on controller-0 after shutting down controller-1
- Lowering the priority as this appears to be a setup issue, not a software issue
- https://bugs.launchpad.net/starlingx/+bug/1839181 -- Platform CPU threshold exceeded in compute after lock/unlock a different compute host (Storage System)
- Recently re-opened. Not enough data (reference to duplicate LP which also has no data). Following up with the reporter.
Low Priority Bugs
- Total: 8
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
More information about the Starlingx-discuss
mailing list