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

[Khalil, Ghada]

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


Team Meeting Agenda/Notes - Apr 11/2019
- Networking Documentation  
        - https://wiki.openstack.org/wiki/StarlingX/Networking#Useful_Networking_Commands 
        - Add a note regarding VMs w/ huge pages when using ovs-dpdk
        - Add a reference to the packaged helm chart for neutron (as it can be used as a guide
        - Add an example for updating a single value with helm override
        - Continue to update as needed

- Networking Test Status
        - 3 activities currently in progress: Regression TC definition, Feature testing for ovs-dpdk upversion, Feature testing for ovs-dpdk firewall
        - Testing time-lines are captured in the Test Release Plan
        - https://docs.google.com/spreadsheets/d/1Fyg-z4MirgE7CP-H8EXSeZ5CoN5t62hKk6lmX83rmQk/edit#gid=0 

- TC Definition for Regression
        - Elio working to include feedback from Matt & Chris
        - Elio to update the networking domain sub-analysis and re-organize based on feedback
        - Matt plans to provide feedback on the neutron test-cases included in "StarlingX Tests" by end of week
        - Ghada also requested that Chris provided feedback

- Regression Execution
        - Networking regression is currently planned to start in mid-June.
        - Need to have a mini-regression suite run as part of sanity/automation to ensure the load is sane in terms of networking.
                 - Action: Elio to follow up with Ada
        - General: Are the automated test-cases implemented so far run on a regular basis already (weekly or bi-weekly)?
                - Action: Elio to follow up with Ada

- Feature Testing for ovs-dpdk upversion
        - No need to run the TCs on config 2 and config 3. Config 4 covers data interfaces on all the required NIC families: Niantic, Mellanox, Fortville.
        - From Matt: When testing, ensure that VM traffic is traversing the different data networks configured on each of the NICs. TCs need to be adjusted accordingly.
        - No need to run TCs on virtual env as StarlingX only supports ovs-dpdk on baremetal. 
        - No need to run all TCs on baremetal duplex; only a small subset is enough. Focus on running all TCs on multi-node with config 4; exercising the different NICs
        - TC steps included in https://drive.google.com/file/d/1JAJ_cGTRkFCePIX8UCtV9TLydBiidUsF/view  are outdated. They need to be updated.
        - Failures
        - NET_PT_VLAN_01 - This is likely due to not having port trunking enabled in the neutron agents. helm-override is required. Action: Chenjie to investigate and provide steps. Add steps to the networking wiki above.
        - NET_BASIC_NT_06 - Needs to be retested with VM flavor ("hw:mem_page_size=large"). Action: Elio to arrange re-test
        - NET_DPDK_OVS_05 - Steps need to use helm-override (not service parameters). Needs to be retested with correct VM flavor. Action: Elio to arrange re-test

- Feature Testing for ovs-dpdk firewall
        - Testplan sent; looking for feedback
        - Testing not started yet