[Starlingx-discuss] Networking Team -- Call for members

[Zhao, Forrest]

Hi Ghada,

Good to see this mail that networking team is created :) My team will join in the networking team together with your team.

We're working on up-streaming the patches in stx-neutron to Openstack Neutron. So far we analyzed 140+ patches in stx-neutron and categorized them into 20+ sub-functions. We've finished analyzing the patches for VLAN trunk/SRIOV/QoS/security group/firewall/custom settings/bindings and sent out the analysis report to starlingx-discuss mailing list. Also one analysis report for L2POP was sent out last week; the others are on the way.

There're 3 major features to be up-streamed to Neutron in stx-neutron. We finished the initial version of BP/spec for these features proposal. They're attached. We hope WR can co-own them with us. We plan to upload their BP/spec before Neutron PTG in Denver this September. Then we can review them with PTL and core developers at PTG.

-        Provider network management

-        System host management

-        Fault management

We also extracted 2 standalone sub-features after analyzing the above 3 major features; their BP/specs were uploaded to Neutron upstream for review.

-        Segment Range Management of Self-service Networks: https://review.openstack.org/579411

-        Rescheduling of DHCP Servers and Routers: https://review.openstack.org/595978

As a joint effort, I recommend myself to be co-lead of the networking team with focus on upstreaming effort; recommend Ruijing, Guo to be tech lead together with Matt.

Thanks,
Forrest


From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com]
Sent: Tuesday, August 28, 2018 2:26 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Networking Team -- Call for members

Hello all,
I am volunteering to be the Project Lead for the starlingx networking team. There are a few members identified from Wind River already. Any others wish to join? I will be looking for a timeslot for a regular meeting once I gather the list of participants.

Sub-team wiki:
https://wiki.openstack.org/wiki/StarlingX/Networking

Work Backlog:
https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.networking&project_group_id=86

I'm particularly interested in having someone work on the following for the stx.2018.10 release:
https://storyboard.openstack.org/#!/story/2002946 - OVS LLDP inventory
https://storyboard.openstack.org/#!/story/2002944 - OVS-DPDK firewall driver

Thanks,
Ghada

Ghada Khalil, Manager, Titanium Cloud, Wind River
direct 613.270.2273  skype ghada.khalil.ottawa
350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180828/ff78ab81/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Provider Network Management.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 9548 bytes
Desc: Provider Network Management.docx
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180828/ff78ab81/attachment-0003.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: System Host Management.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 8669 bytes
Desc: System Host Management.docx
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180828/ff78ab81/attachment-0004.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fault Management.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 7130 bytes
Desc: Fault Management.docx
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180828/ff78ab81/attachment-0005.docx>