Armando, yes I will be using the latest version for heading up the work. From: Armando M. [mailto:[email protected]] Sent: 05 June 2015 08:57 To: OpenStack Development Mailing List (not for usage questions) Cc: Kalyankumar Asangi; Ramanjaneya palleti Subject: Re: [openstack-dev] [neutron] Service Chain project IRC meeting minutes - 06/04/2015
On 4 June 2015 at 19:32, Vikram Choudhary <[email protected]<mailto:[email protected]>> wrote: Hi Cathy, Thanks for heading up this meeting. No worries about the timing, time zones are really difficult to handle ;) I do agree with Armando that finalization of the API is important and must be done at the earliest. As discussed over the last meeting I will start working on this and hope by the next meeting we have something in the kitty. Are you going to use a polished up version of spec [1] (which needs a rebase and a transition to the networking-sfc repo when that's ready)? [1] https://review.openstack.org/#/c/177946/ Thanks Vikram On Fri, Jun 5, 2015 at 6:36 AM, Armando M. <[email protected]<mailto:[email protected]>> wrote: On 4 June 2015 at 14:17, Cathy Zhang <[email protected]<mailto:[email protected]>> 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. 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. 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. Cheers, Armando [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). Thanks, Cathy __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
