[Starlingx-discuss] Minutes: StarlingX Networking Meeting - 01/24
Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Jan 24/2019 * Forrest's team off for Chinese New Year -- Feb 4 - 15 * Patch upstreaming: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1... * Summary: ? Network Segment Range: * Issue with zuul CI for neutron submission https://review.openstack.org/#/c/625544/ o works locally, but fails in the openstack CI env / focusing on debugging this issue * This feature is required for containers cut-over in mid-Feb o If not merged by Feb 1, we will build an updated neutron image with the gerrit reviews. ? Other * 2 patches merged in the last two weeks. * 6-7 patches still on-going. * 0 patches not started * Containerized OVS Integration * Design/Coding pointers provided by WR (Joseph/Matt/Brent). WR will also look to provide a design document describing sysinv to help with ramp up * Huifeng & Cheng to start prototyping code changes tomorrow -- there is one week before the Chinese holidays * The goal is to be able to set the vswitch type during run-time. StarlingX is supported by one base ISO. Two deployment scenarios: ? 1: ovs-dpdk on the host ? 2: the vswitch set to none on the host and the customer able to deploy ovs in a container. In the future, this would be extended to cover other vswitch types. ? The plan is to set the default VSWITCH_TYPE to none ...i.e. containerized ovs is the default starlingx config (deployment scenario #2) * This aligns better with our target configuration and also handles the case of containerized non-openstack deployments where there is no vswitch on the worker nodes. * OVS process monitoring and alarming * Coding pointers provided by Matt. * Chenjie will start coding. * OVS-DPDK firewall: Kailun * Started performance testing and collecting data results Regards, Ghada
participants (1)
-
Khalil, Ghada