[Starlingx-discuss] Minutes: StarlingX Networking Meeting - 03/07
Khalil, Ghada
Ghada.Khalil at windriver.com
Fri Mar 8 15:32:38 UTC 2019
Meeting minutes/agenda are captured at:
https://etherpad.openstack.org/p/stx-networking
Team Meeting Agenda/Notes - Mar 7/2019
- Network Patch Upstreaming -- Network Segment Range
- Expect neutron patches to merge for Stein ms-3. Remaining neutron-lib patches will not make Stein. Analysis confirms that they are not must-have for StarlingX, so should be ok for them to merge for Train
- problems with Neutron gates which may block stein-3 release, Neutron team is working on it
- Network Patch Upstreaming -- Neutron uwsgi switch: No plan for Stein, may make apache wsgi solution as default web server in Train cycle
- Agreed to live with this in StarlingX until the apache solution is available in Train. This is an issue for large scale deployments
- Containerized OVS Integration
- Code Merge Plan: Mar 15 >> Mar 22
- openstack-helm changes merged; will need to port as a patch until the next StarlingX rebase to the latest openstack-helm code.
- https://review.openstack.org/#/c/641542/
- Ghada to ask Bob to review and allow the merge
- stx-config code is ready for review. https://review.openstack.org/#/c/633924/
- Ghada asked Chenjie to add a W-1 to avoid merging before all the testing is complete
- Next step is to test -- For now, I have tested several cases on VM. I will go ahead with baremetal soon. But before that, I would like the code be reviewed, to make sure no big problem.
- Will test multi-node as well as Simplex & Duplex
- OVS process monitoring and alarming
- Code Merge Plan: Mar 22
- Still on hold. Expect to get back to this after OVS-DPDK Upverison testing on ~Mar 18
- OVS-DPDK Firewall
- Code Merge Plan: Mar 22
- Given the move to containers, the code has to be moved from the puppet manifest to the Armada manifest (minor change). Then need a re-test in the container env.
- openvswitch package Upversion
- Code Merge Plan: Mar 22 >> Apr 5
- Basic functional testing on 3/1 OVS-DPDK Upgrade ISO image and will test again on new image.
- TC Feedback
- Provider Network Connectivity TCs are no longer valid and should be removed
- SDN: SDN does not work with the current version of ovs-dpdk, so this is out of scope of the upversion test-plan.
- Need a story to enable SDN
- QoS: TCs need to be updated to test enabling rate-limiting thru user helm chart overrides
- OpenStack Docs: https://docs.openstack.org/neutron/rocky/admin/config-qos.html
- Example StarlingX Command:
- system helm-override-update neutron openstack --set conf.plugins.ml2_conf.ml2.extension_drivers=port_security,qos
- system application-apply stx-openstack
Regards,
Ghada
More information about the Starlingx-discuss
mailing list