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

[Khalil, Ghada]

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

Next Meeting: 04/11 << agreed to add another meeting next week to work thru the actions related to test strategy/definition/planning.

Team Meeting Agenda/Notes - Apr 4/2019
- Networking Testing Status
        - Welcome!
                - Elio is the networking test prime for stx - with help from Juan Pablo / Richo for execution
                - Chris Winnicki is the networking test prime in WR
        - Test Environment / Strategy
                - OVS testing will be done predominantly in virtual env. However, still need a subset of TCs run on baremetal for NIC coverage
                          - Regression must accommodate this, identifying a subset of test-cases to be run on h/w with OVS
                - OVS-DPDK testing will be done on baremetal; not supported in virtual env.
                - NIC Types: 520, CX4 (10G?), CX5 (40G?), X710 (10G), 10G baseboard NICs
                          - Due to lack of hardware, the team is re-configuring the switches to enable different configurations >> may be susceptible to config issues
                - Servers: wolfpass (?)
                - Need to add cluster networks to the lab configurations -- Action: Elio & team
                        - Recommended Configurations:
                                 - No explicit cluster network << already covered in current config shared by Elio
                                 - Separate interface from mgmt network
                                 - A VLAN on the mgmt network
                                 - Shared on the mgmt network (multi-netting)
                        - Recommend this is done on a number of systems so that you can get implicit coverage just by using the system.
                - Traffic Generation Capability
                        - No current current traffic generation; just using ping 
                        - Good tools to use are netperf, pktgen (for DPDK-supported guests)
                        - Action: Elio & team to investigate and propose traffic capability
                - Reporting Issues
                        - There are a set of data that should be collected for connectivity issues
                        - Action: Numan to share with the Intel team
                - No changes to neturon conf files directly, use helm overrides

        - Networking coverage during sanity
                - Basic networking test-cases will be added to sanity  -- Time-Frame: 2-3wks (end of April)
                - Action: Elio to add list of proposed sanity TCs here for team to review
        - Networking Regression Testing
                - Test-case definition is still in progress. 
                - The initial set chosen is around 150 test-cases. Action: Elio to make the test-cases visible to the team
                - Areas of Focus for Regression
                        - Action:  Matt & team to add areas of focus priority here
                        - Add short justification for chosen priority
        - Networking Feature Testing
                - Currently testing OVS-DPDK Upversion (subset of regression TCs?)
                - Test-cases were sent by email.
                - Test-cases were not run on the standard load, so we don't have baseline results. 
                - Given the time crunch, agreed for Elio to continue with testing with the new ovs-dpdk version. When needed, he can do specific checks against the standard load.

        - Test-case References
                - https://git.openstack.org/cgit/openstack/stx-test/tree/doc/source/manual_tests/networking
                - Structure and organization in the repo is hard to follow; suggest to re-organize this based on input from the team of the regression focus areas


- General Action: Networking team will start a wiki to capture common commands / useful info 
<add-link-here-when-created>

- Containerized OVS Integration
        - Code merged as of March 23
        - 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. 

- openvswitch package Upversion
        - Code Merge Plan: Apr 19  (pending test progress)
        - Issue with vhostuser is now understood: https://bugs.launchpad.net/starlingx/+bug/1820378 
                - waiting for Chenjie to re-test and confirm

- OVS-DPDK Firewall
        - Code Merge Plan: Apr 5
        - https://review.openstack.org/#/c/645054/ 

- OVS process monitoring and alarming
        - Code Merge Plan: Apr 12
        - https://review.openstack.org/#/c/648330/ 
        - https://review.openstack.org/#/c/648367/