[openstack-dev] [neutron] Service Chain project IRC meeting minutes - 06/04/2015

Cathy Zhang Cathy.H.Zhang at huawei.com
Wed Jun 10 21:58:05 UTC 2015

Hi Armando,

Sorry to reply late since I just saw these emails due to improper filter setup in my mailbox. Please see inline.


From: Armando M. [mailto:armamig at gmail.com]
Sent: Thursday, June 04, 2015 6:06 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Service Chain project IRC meeting minutes - 06/04/2015

On 4 June 2015 at 14:17, Cathy Zhang <Cathy.H.Zhang at huawei.com<mailto:Cathy.H.Zhang at huawei.com>> wrote:
Thanks for joining the service chaining meeting today! Sorry for the time confusion. We will correct the weekly meeting time to 1700UTC (10am pacific time) Thursday #openstack-meeting-4 on the OpenStack meeting page.

Cathy, thanks for driving this. I took the liberty to carry out one of the actions identified in the meeting: the creation of repo to help folks collaborate over code/documentation/testing etc [1]. As for the core team definition, we'll start with a single member who can add new folks as more docs/code gets poured in.

Cathy> Thanks for helping with this. I have asked the infra team to add me to the core team. I will add more folks based on their commitment to this project contribution.

One question I had when looking at the minutes, was regarding slides [2]. Not sure if discussing deployment architectures when the API is still baking is premature, but I wonder if you had given some thoughts into having a pure agentless architecture even for the OVS path.

Cathy> Slide 2 shows the component architecture involved in supporting the port-chain API since many people request more info on what component work are needed  for supporting SFC functionality than just an API proposal in https://review.openstack.org/#/c/177946/. As to agentless architecture for OVS path, could you clarify what you mean?

Having said that, as soon as the repo is up and running, I'd suggest to move any relevant document (e.g. API proposal, use cases, etc) over to the repo and reboot the review process so that everyone can be on the same page.

Cathy> Sure, I will do that.



[1] https://review.openstack.org/#/c/188637/
[2] https://docs.google.com/presentation/d/1SpVyLBCMRFBpMh7BsHmpENbSY6qh1s5NRsAS68ykd_0/edit#slide=id.p

Meeting Minutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-04-16.59.html
Meeting Minutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-04-16.59.txt
Meeting Log:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-04-16.59.log.html

The next meeting is scheduled for June 11 (same place and time).


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150610/8c889ecc/attachment-0001.html>

More information about the OpenStack-dev mailing list