17:15:35 #startmeeting service_chaining 17:15:36 Meeting started Thu Nov 30 17:15:35 2017 UTC and is due to finish in 60 minutes. The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:15:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:15:40 The meeting name has been set to 'service_chaining' 17:15:45 hi all 17:16:07 #topic agenda 17:16:13 https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting 17:16:53 hey LouisF 17:16:59 bcafarel: hi 17:17:40 I put a "date: next one" meeting entry in the page, hope it did not collide with your changes 17:17:52 vks1: o/ 17:18:00 bcafarel: thanks 17:18:12 hi all 17:18:18 vks1: hi 17:19:00 #topic meeting time change 17:19:36 how about 1 or 2 hours earlier? 17:19:48 +1 17:19:52 what is your preference? 17:20:23 earlier times are fine for me (both 1 or 2) 17:20:32 ditto 17:20:34 vks1: how about you? 17:20:36 LouisF: did tmorin have a preference? 17:20:57 igordc: ? 17:21:01 bcafarel: i think 2 hours may be better 17:21:28 i propose 2 hours earlier 17:21:39 need to check if slot is available 17:22:11 sounds good 17:22:26 worst case, we can host meetings in project IRC channels now (octavia does theirs in #openstack-lbaas now) 17:22:49 so if no #-meeting chan slot is available we can do it in #networking-scf 17:22:51 *sfc 17:22:58 bcafarel: ok 17:23:23 that is best 17:23:56 lets do 2 hours earlier on #networking-sfc next week 17:24:48 #topic tempest slit 17:25:03 ^split 17:25:08 :) 17:25:22 I brought the subject to recent Neutron meetings, no feedback yet 17:25:22 bcafarel: what is status 17:25:29 bcafarel: ok 17:25:44 though the general opinion seems to be a common repo for all stadium projects (less paperwork per project) 17:25:47 #topic non-transparent sf 17:25:56 work to resume 17:26:20 #topic python-neutronclient updates 17:26:28 bcafarel: what is status? 17:26:51 I have to ping a few other Neutron cores here, to get that second +2 17:27:08 bcafarel: ok thanks 17:27:23 #topic api reference 17:27:47 i hope that Thomas Morin can start this work 17:29:11 indeed 17:29:42 i will tell him about the meeting time change 17:29:52 #topic vm failure detection 17:30:47 btw LouisF http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings/neutron-service-chaining-meeting.yaml will need an update too 17:31:18 bcafarel: yes will do 17:32:22 we can put ideas into an etherpad 17:32:59 before meeting me and bcafarel were discussing same 17:33:06 we have discussed in this week 17:33:17 I was looking to the way tacker is doing 17:34:12 bcafarel: ? 17:34:47 vks1: can you elaborate 17:36:02 LouisF: https://github.com/openstack/tacker/tree/master/tacker/vnfm/monitor_drivers 17:36:28 https://blueprints.launchpad.net/tacker/+spec/health-monitor 17:38:13 vks1: what work would be required from networking-sfc to support that? 17:40:10 #topic other items 17:40:22 LouisF: We need to add monitoring code (tacker first started thru ping test) and later added ceilometer , then there are API addition in plugin side and openvswitch driver changes 17:41:44 vks1: ok we can add create a bp for that work 17:42:21 LouisF: ok 17:43:49 ok another possible work item is adding a neutron network as a source network to the classifier 17:44:02 thomas morin has suggested this 17:44:07 thoughts? 17:46:19 alternative to source-ip-prefix? I recognize the idea :) 17:46:43 bcafarel: yes 17:46:44 (sorry another meeting is stealing my attention) 17:47:15 ok thats all i have 17:47:28 the idea is nice, not sure about what it implies in the code 17:47:42 (like what happens if the network is modified etc) 17:48:20 bcafarel: needs some thought 17:48:36 ok thanks all 17:48:40 bye 17:48:54 #endmeeting