[Starlingx-discuss] Minutes: StarlingX Networking meeting - 9/20

Khalil, Ghada Ghada.Khalil at windriver.com
Thu Sep 20 21:05:16 UTC 2018


The StarlingX networking team had their first meeting on 8/30. Weekly meetings are scheduled for Thursday at 9am Eastern.
Meeting Details are available on the wiki: https://wiki.openstack.org/wiki/StarlingX/Networking

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

Team Meeting Agenda/Notes - Sept 20/2018
*        Neutron Blueprint Status / Next Steps

  *   Provider Network Management -- Highest priority
?  Merge the Segment Range Management in this spec: https://review.openstack.org/579411
?  Also include the current API (w/o the Host Management piece)
?  Rename to Provider Segment Range Configuration
?  Action: Ruijing<?> to add a note to the current spec review saying we will re-work the spec based on the feedback from PTG and re-publish it. Fcst: Sept 21
?  Next Step: Ruijing<?> to re-work the spec. Time-Line: 1-2wks to have the updated spec. Fcst: Sept 28-Oct5
*        Action: Forrest to confirm the resourcing for this work

  *   System Host Management
?  neutron community did not agree to move forward with this spec. The neutron spec will not be pursued any further.
?  Action: Ruijing<?> to add a note to the gerrit review and mark the review as Abandoned. Fcst: Sept 21
?  Plan is to move this functionality to the stx-nfv project
*        Use the neutron APIs from stx-nfv. Need to prototype the use of admin_state_up / admin_state_down
o   This may drive an Enhancement Request into neutron. Neutron team was open to this.
?  Next Step: Matt to write story in SB describing the requirements.
*        After consultation with the Technical Lead for stx-nfv, he advised us to defer this work for a while as the code is undergoing churn due to containerization support.
*        We will revisit this again in a few weeks  - October 18

  *   Rescheduling of DHCP Servers and Routers
?  neutron community did not agree to move forward with this spec. The neutron spec will not be pursued any further.
?  Action: Ruijing<?> to add a note to the gerrit review and mark the review as Abandoned. Fcst: Sept 21
?  Plan is to move this functionality to the stx-nfv project
*        Implement a plugin in the stx-nfv vim to do the re-scheduling
?  Next Step: Matt to capture requirements in SB. Note: This will be included in the same story as the "System Host Management" since they are closely related

  *   Fault Management
?  Plan is to not pursue this spec with neutron. The corresponding gerrit review will be abandoned.
?  Action: Ruijing<?> to add a note to the review and mark the review as Abandoned. Fcst: Sept 21
?  For now, leave the patch in stx-neutron as is. This is broader than just neutron, same hooks exist in glance/cinder/etc. Need a larger discussion/decision.
?  Put on hold for now.

  *   ML2 Connection Auditing and Monitoring
?  Plan is to review the current neutron logging capabilities to see if it is sufficient to diagnose issues
*        Neutron team is open to receiving Enhancement Requests if needed.
?  Action: Forrest to confirm the resourcing for this work
*        Other Neutron Upstreaming Patches - Bugs

  *   Not reviewed in the meeting
*        stx.2018.10 Status

  *   2 features planned and on track

  *   6 bugs: 2 well understood, 2 need more info, 2 need further investigation
?  Kailun to follow up on https://bugs.launchpad.net/starlingx/+bug/1790252
*        ovs-dpdk Enhancements - stx.2019.03

  *   Kailun working on OVS-DPDK Firewall Driver Enhancements.
?  Facing some issues <Kailun to update with details>. Steve to send output from his system.

Regards,
Ghada

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180920/26b8437d/attachment-0001.html>


More information about the Starlingx-discuss mailing list