[Starlingx-discuss] Minutes: StarlingX Networking Meeting - 03/19
Khalil, Ghada
Ghada.Khalil at windriver.com
Thu Mar 19 22:29:39 UTC 2020
Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking
- Attendees: Ghada Khalil, Joseph Richard, Steve Webster, Chris Winnicki, Yi Wang, Alexandru Dimofte, Cosmin Albescu, Mihal-Laurentiu Trica, Nicolae Jascanu
- Steve Webster has taken on the role of networking PL. He will chair the meetings moving forward.
stx.4.0 Features
- TSN support in kata container
- Question: Is there any code for this? or just a procedure?
- As per Yi, the kernel will need be upgraded in the kata container. At a minimum, the 4.20 kernel is needed. Currently, the kata runtime in stx uses a 4.18 or 4.19 kernel.
- kata upstream (currently alpha release) is now using a 5.x kernel
- Not sure when this release of kata will be officially available
- Ghada will check w/ Yong if we can get schedule information
- As per Steve, he expects stx will need to build a custom kata runtime to pick up additional drivers
- Reference: https://bugs.launchpad.net/starlingx/+bug/1867927
- Yi is currently setting up a TSN network
- First step is to setup a generic Ubunutu node w/ a TSN switch
- Once that is working, will proceed to setup a StarlingX node.
- Yi will be working closely with Shuicheng to coordinate efforts on kata upgrade.
- Will target code merge (feature ready for test) by milestone-3 (May 15)
- Test Status
- The plan is to test Kata containers first, then test TSN after.
- The test team in Romainia is ordering Extreme Network switches. Nick will verify if they have TSN capabilities.
- IPv6 PXE boot network support
- Kunpeng is investigating. He's sent some questions to the stx mailing list. Joseph is helping with responses.
- Feature plan / timing: TBD
- Test Update
- Received some servers in Galati and will start setup.
- Right now, test activities rely on the infrastructure in Mexico
stx.4.0 Bugs
- Total: 5
- https://bugs.launchpad.net/starlingx/+bug/1867927 - Kata container runtime does not include support for SR-IOV devices
- New. Assigned to Shuicheng as he is the prime for the kata container feature
- https://bugs.launchpad.net/starlingx/+bug/1866230 - Tracebacks related to LLPD neighbor (INSERT INTO lldp_tlvs) filling sysinv.log
- New, Assigned to Thomas. This is a simple fix to avoid a sysinv exception in the lldp tlv is too long.
- 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
- No update. Still not assigned. Issue appears to be related to having multiple data ports.
- https://bugs.launchpad.net/starlingx/+bug/1850438 -- The sriov device plugin pod may start before it's config manifest is written
- No update: Still on hold. Intermittent 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/1833463 -- armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none)
- No update. Action with Yong to re-assign. Work is related to openstack-helm
- https://bugs.launchpad.net/starlingx/+bug/1859641 - IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status"
- One fix merged. Zhipeng is making progress on the next issue related to rabbitmq
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
- No Update. Work has not resumed
Low Priority Bugs
- Total: 6
- 2 bugs merged. 1 in progress (code review posted)
More information about the Starlingx-discuss
mailing list