[Starlingx-discuss] MoM: Bi-Weekly StarlingX networking meeting, 5/28/2020
MoM for 5/28 meeting: * TSN * https://storyboard.openstack.org/#!/story/2006746 * Testing w/ Kata is set to start soon, with TSN to follow * IPv6 PXE boot network support * https://storyboard.openstack.org/#!/story/2006442 * Moved out of stx-4.0 * Bug updates: * New: * https://bugs.launchpad.net/starlingx/+bug/1880777 - Periodic message loss between VIM and Openstack pods * Similar to fixed bug https://bugs.launchpad.net/starlingx/+bug/1817936, but the problem seems to have returned * https://bugs.launchpad.net/starlingx/+bug/1879243 - Vxlan MTU size not respected * Steve to request more info * https://bugs.launchpad.net/starlingx/+bug/1876754 - Host unlock fails while changing interface from data network (OVS-system) to pci-sriov network * Assigned * Updated: * https://bugs.launchpad.net/starlingx/+bug/1821026 - Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures * Partial fix proposed: https://review.opendev.org/729758 * stx-puppet fix will be required as well * https://bugs.launchpad.net/starlingx/+bug/1862651 - IPv6 DC: 100.113 alarm "DATA-NETWORK0" inteface failed raised at both system controller and subclouds after installation * invalid: lab configuration issue * https://bugs.launchpad.net/starlingx/+bug/1875963 - Enhance StarlingX network documentation * assigned (mcamp859) * https://bugs.launchpad.net/starlingx/+bug/1850438 - The sriov device plugin pod may start before it's config manifest is written * lowered priority. Intermittent and happening at much lower frequency * https://bugs.launchpad.net/starlingx/+bug/1833463 - armada-manifest upload failed when configuring bond with OVS container (vswitch-type = none) * lowered priority. Not much activity on upstream helm-openstack fix. Thanks, Steve
participants (1)
-
Webster, Steven