No meeting in Dec 26, Happy New Year! Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Dec 12/2019 * stx.3.0 Bugs: All open issues should try with latest daily build with train patch (ISO 20191115: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006973.h...) * stx.3.0 final compile candidate build: Dec.11 * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.3.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * High: ? https://bugs.launchpad.net/starlingx/+bug/1841189 ping to vm fails in live migration test - Gongjun * As per Matt, the NAT-Box is directly connected to the neutron router via an L2 switch. The rest of the topology diagram is pretty accurate. * Next steps: o Review the logs from Wendy to see if there are any ovs or neutron issues o Review the system data (which is also included in the collect data (./var/extra) ) to help replicate the setup to reproduce more closely o Huifeng will also ask Wendy to try some additional tests when the system is in the failure condition ? https://bugs.launchpad.net/bugs/1854875 neutron router external gateways unreachable on Train - Yao, Le * Close as Invalid * Medium: ? https://bugs.launchpad.net/starlingx/+bug/1821026 Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - fupingxie * Change to high and target to fix in 3.0 * stx 3.0 features * Openstack Rebase to Train ? on track from the release meeting update * stx.4.0 Feature Proposals: https://etherpad.openstack.org/p/stx.4.0-feature-candidates * Milestones: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbr... ? Milestone-1 1/24/2020 ? Milestone-2 3/27/2020 ? Milestone-3 5/15/2020 ? Feature Test 5/29/2020 ? Regression Test TBD ? RC1 6/12/2020 ? Final Regression TBD ? Release 7/3/2020 * Unit Test Initiative: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006710.ht... (To be discussed) ? Interface/Networking configuration is part of the config repo * Follow the same unit test framework already in place * Action: Review the test cases (related to networking) to understand if we can increase the coverage o One gap is related to validating the puppet configuration output is valid for the various configs ? As per Matt, the main gap here is the functional/intergration testing with OVS and OVS-DPDK * No need to re-run ovs or neutron tests as these are covered by these projects * Need to focus on unique setup for starlingx * TSN support in Kata: ? Depend on Kata container support * Containerize OVS-DPDK (cheng): propose for 4.0 ? https://review.opendev.org/#/c/694188 , ovs chart patch, this patch is in progress ? https://review.opendev.org/#/c/696437/ , import OVS-DPDK patches, cherry-pick latest ovs-dpdk feature patch from openstack-helm-infra into STX, Can we consider to upgrade the openstack-helm version in 4.0? - Check with Frank on the 4.0 plan ? Will need one more patch in openstack-helm-infra project to support ovs chart per-host overrides. As discussed in irc meeting, the community is happy to see this feature implemented * https://storyboard.openstack.org/#!/story/2006965 * IPv6 PXE boot network support: https://storyboard.openstack.org/#!/story/2006442 - Huang, XiangDong - Plan to start from Feb. * OVS collectd resource monitoring: Chenjie ? https://storyboard.openstack.org/#!/story/2002948 - Monitor other features besides interface/port * Monitor datanetwork for non openstack worker node by link monitor Marvin o Patch submitted: https://review.opendev.org/#/c/695390/, https://review.opendev.org/#/c/695391/,https://review.opendev.org/#/c/694940..., https://review.opendev.org/#/c/694927/ ? WIP to add test cases and fix puppet issues * Support SR-IOV NIC with VFIO and Netdevice VF's: Steve ? https://storyboard.openstack.org/#!/story/2006842 ? Small enhancement related to configuration -- code merged in master a couple of days * Backlog Stories * A number of networking stories exist, but have no target release. Any actions we want to take on those? * Use openstack-helm-infra calico to manipulate network settings: https://storyboard.openstack.org/#!/story/2005848 * Userspace CNI plugin backed by OVS-DPDK: https://storyboard.openstack.org/#!/story/2005207 * OVS rx multi-queue affinity: https://storyboard.openstack.org/#!/story/2002960 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss