17:02:22 #startmeeting service_chaining 17:02:24 Meeting started Thu Jul 6 17:02:22 2017 UTC and is due to finish in 60 minutes. The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:27 The meeting name has been set to 'service_chaining' 17:02:38 hi 17:02:43 hi all 17:02:53 pcarver: hi 17:02:57 vks1: hi 17:03:06 hi all 17:03:07 agenda https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting 17:03:14 #topic agenda 17:04:48 #topic CLI in python-neutronclient 17:05:12 https://review.openstack.org/#/c/409759/ 17:05:22 i see still more comments 17:06:17 i will contact Mohan 17:06:37 #topic API reference 17:06:57 pcarver: what is status? 17:07:33 The API reference is fine, but I'm really not getting much of anywhere with the API definition. I don't have a lot of time to concentrate on it an every time I start I end up digging into dependencies on things I can't import. 17:08:46 were you able to contact the neutron-lib folks to resolve this? 17:09:57 no, I'm working on it in short periods between meetings. Hardly have any block of time to dedicate to discussing it. 17:10:46 pcarver: ok i will look at getting help for you 17:10:58 My last attempt is to roll back everything and try to do it a little bit at a time 17:11:40 pcarver: ok 17:11:51 #topic Pike work 17:12:05 I'm thinking I could upload a partial patch set and get feedback on a little piece at a time and try to keep it passing tox tests all the time even though incomplete 17:12:37 pcarver: ok thanks sounds like a good approach 17:12:51 #topic API and CLI changes for Passive TAP SF 17:13:39 looks like Vikash dropped 17:14:36 anyway there was discussion on port-pair-group-parameters 17:14:56 to split it up into separate parameters 17:15:49 pcarver: i think you suggested that 17:16:14 LouisF: yes, it looks like that one parameter is getting too overloaded 17:16:35 pcarver: i think it would be best to do that 17:17:00 I don't know exactly where the line is, but passing complicated data structures as a single parameter isn't very user friendly 17:17:07 i will suggest to Vikash to do that 17:18:22 #topic SFC graph 17:18:32 igordcard: what is status? 17:19:58 ok moving on 17:20:23 #topic OVN driver work 17:20:39 doonhammer: how is the OVN work going? 17:21:32 not much - been swamped by my day job :-( 17:21:41 doonhammer: ok thanks 17:21:54 #topic other topics 17:22:09 sorry i logged in as guest_145 - vks1 17:22:12 anythng else to discuss? 17:22:24 look like issue in my irc client 17:22:59 hi Louis regarding your comment on ppg parameter 17:23:14 guest_145: yes? 17:24:02 https://review.openstack.org/#/c/449954/ 17:24:12 ur last comment 17:25:12 guest_145: go ahead 17:25:46 so i was thinking to put a separate patch to have ppg-parameters as separate API 17:26:16 as pcarver also have given comment to rellok on the parameters 17:27:12 LouisF: or you are suggesting we should add 'tap_enabled' attribute to ppg directly instead of ppg-parmeters 17:27:17 LouisF: ? 17:27:24 guest_145: yes, correct 17:28:05 LouisF: so move 'tap_enabled' attribute will suffice ? 17:28:14 *moving 17:28:32 guest_145: add a 'tap-enabled' option to PPG 17:29:14 and remove from ppg-parameters 17:29:17 OK but it will take some time 17:29:29 LouisF: will it be fine ? 17:29:35 guest_145: that's fine 17:29:51 LouisF: OK thankyou, will do that 17:30:04 guest_145: great, thanks 17:30:30 any other topics? 17:31:32 ok thats all I have, thanks all 17:31:42 bye all 17:31:46 bye 17:31:51 #endmeeting