[Starlingx-discuss] Minutes: StarlingX Networking Meeting - 04/18

[Khalil, Ghada]

Meeting minutes/agenda are captured at:
https://etherpad.openstack.org/p/stx-networking

Networking Test Status
- TC Definition for Regression (update by Elio, Matt and Chris)
        - Still working on this. 
        - Elio is working on comments provided by Matt by email.
        - Lots of changes are required. Elio coordinating with the rest of the test team.
        - Expect to have a new version for review in the next two weeks - 1st wk of May
        - Link to work in progress documents:
        - https://drive.google.com/drive/folders/1LS-gSj0Obfa9Qle2Ver2j5dZjmQJ9etB 

- Regression Execution (update by Elio)
        - Agreed to include some networking TCs in the automated sanity
        - Still not able to ping testing between 2 VMs on virtual env -- this was a limitation with ovs-dpdk. With the use of ovs in virtual env, this should no longer be an issue.
        - For automated sanity in virtual env, test with OVS. For automated sanity on baremetal, use OVS-DPDK
        - Action: Elio to share the TCs planned for sanity with the team. Send to starlingx-discuss mailing list.
        - Elio to provide time-line for adding TCs to sanity by next week.

- Feature Testing for ovs-dpdk upversion (update by Ricardo and Elio)
        Testing on two systems:
        - Duplex (config 4)
           - No issues found with testing. Trunk re-test successful. Still need to re-test dns.
        - 2+2 (config 4)
           - Facing issues potentially with connectivity - https://bugs.launchpad.net/starlingx/+bug/1824923
           - Given testing is successful on Duplex & 2+2 with another set of NICs, this points more to a networking configuration issue.
           - Christopher will look into the switch configuration to see if there is an issue there

- Feature Testing for ovs-dpdk firewall (update by Elio)
        - TC creation is about 50%. Will work to incorporate Matt and Kailun's feedback
        - Expect to start execution next week

- OVS process monitoring and alarming (update by Chenjie)
        - Code has been merged:
           - https://review.openstack.org/#/c/648330/
           - https://review.openstack.org/#/c/648367/
        - Ready for test verification

- Containerized OVS Integration
        - Remaining item: Follow-up on version of ovs used in the container image. 
        - Right now, the default docker image (with ovs 2.8.0)  is used. 
        - Agreed to align with the openvswitch version of the host. Target is 2.11.0 once the ovs-dpdk upversion feature is merged.
        - This means that we need to build/update the ovs docker image in starlingx
        - Need to get more information from Don on how to do this -- is a build required? or can we specify the ovs version via manifest?
        - Agreed to wait until the openvswitch 2.11 is merged in stx master and gets some soak first before proceeding with changing the version in the container

- Bugs
        - All bugs are now assigned and being worked by Forrest's team
        - Expect to be able to address the current backlog in 2-3wks