Thursday, 2016-12-08

*** donghao has quit IRC00:00
*** sdake has quit IRC00:03
*** sdake has joined #openstack-meeting-300:03
*** benj_ has joined #openstack-meeting-300:04
*** bpokorny has quit IRC00:04
*** bpokorny has joined #openstack-meeting-300:05
*** singleth_ has joined #openstack-meeting-300:06
*** bpokorny has quit IRC00:07
*** bpokorny has joined #openstack-meeting-300:07
*** singlethink has quit IRC00:07
*** bpokorny has quit IRC00:11
*** bpokorny has joined #openstack-meeting-300:11
*** spzala has joined #openstack-meeting-300:14
*** bpokorny has quit IRC00:16
*** sambetts|afk has quit IRC00:18
*** singleth_ has quit IRC00:20
*** sambetts_ has joined #openstack-meeting-300:21
*** Patifa has quit IRC00:29
*** shu-mutou-AWAY is now known as shu-mutou00:38
*** hoangcx has joined #openstack-meeting-300:54
*** haleyb_ has joined #openstack-meeting-301:07
*** tovin07 has quit IRC01:08
*** julim has joined #openstack-meeting-301:11
*** haleyb_ has quit IRC01:12
*** bpokorny has joined #openstack-meeting-301:12
*** tuanluong has joined #openstack-meeting-301:12
*** bpokorny has quit IRC01:16
*** spzala has quit IRC01:25
*** jschwarz has quit IRC01:25
*** jschwarz has joined #openstack-meeting-301:27
*** zhurong has joined #openstack-meeting-301:32
*** spzala has joined #openstack-meeting-301:34
*** huanxuan has joined #openstack-meeting-301:34
*** mtanino has quit IRC01:41
*** Sukhdev has quit IRC01:42
*** sdake has quit IRC02:03
*** sdake has joined #openstack-meeting-302:05
*** bpokorny has joined #openstack-meeting-302:06
*** sdague has quit IRC02:12
*** revon has quit IRC02:32
*** baoli has joined #openstack-meeting-302:36
*** s3wong has quit IRC02:37
*** mtanino has joined #openstack-meeting-302:37
*** julim has quit IRC02:39
*** bpokorny_ has joined #openstack-meeting-302:41
*** bpokorny has quit IRC02:44
*** bpokorny_ has quit IRC02:45
*** clu_ has quit IRC02:47
*** baoli has quit IRC02:50
*** spzala has quit IRC02:54
*** haleyb_ has joined #openstack-meeting-302:57
*** mtanino has quit IRC03:02
*** rbak has quit IRC03:03
*** sheeprine has quit IRC03:11
*** sheeprine has joined #openstack-meeting-303:15
*** Rockyg has quit IRC03:31
*** yamamoto_ has joined #openstack-meeting-303:39
*** absubram has joined #openstack-meeting-303:48
*** absubram_ has joined #openstack-meeting-303:50
*** sdake has quit IRC03:52
*** absubram has quit IRC03:52
*** absubram_ is now known as absubram03:52
*** psachin has joined #openstack-meeting-303:54
*** VW has joined #openstack-meeting-303:56
*** yamahata has quit IRC04:02
*** iyamahat has quit IRC04:02
*** krtaylor has quit IRC04:04
*** sdake has joined #openstack-meeting-304:10
*** alexpilo_ has quit IRC04:14
*** alexpilotti has joined #openstack-meeting-304:15
*** julim has joined #openstack-meeting-304:15
*** julim_ has joined #openstack-meeting-304:19
*** julim has quit IRC04:22
*** dimtruck is now known as zz_dimtruck04:23
*** tuanluong has quit IRC04:27
*** harlowja has joined #openstack-meeting-304:37
*** krtaylor has joined #openstack-meeting-304:38
*** iyamahat has joined #openstack-meeting-304:43
*** huanxuan_ has joined #openstack-meeting-304:53
*** spzala has joined #openstack-meeting-304:54
*** haleyb_ has quit IRC04:57
*** spzala has quit IRC04:59
*** prateek has joined #openstack-meeting-305:19
*** numans has quit IRC05:21
*** yamahata has joined #openstack-meeting-305:24
*** Sukhdev has joined #openstack-meeting-305:26
*** iyamahat has quit IRC05:38
*** hurgleburgler has quit IRC05:40
*** harlowja has quit IRC05:46
*** hurgleburgler has joined #openstack-meeting-305:48
*** iyamahat has joined #openstack-meeting-305:52
*** shu-mutou is now known as shu-mutou-AWAY05:59
*** tovin07 has joined #openstack-meeting-305:59
*** sdake has quit IRC06:10
*** sdake has joined #openstack-meeting-306:10
*** sdake has joined #openstack-meeting-306:10
*** irenab has joined #openstack-meeting-306:14
*** VW has quit IRC06:15
*** gouthamr has joined #openstack-meeting-306:16
*** irenab has quit IRC06:18
*** irenab has joined #openstack-meeting-306:19
*** hurgleburgler has quit IRC06:19
*** alex_xu has quit IRC06:20
*** alex_xu has joined #openstack-meeting-306:24
*** iyamahat has quit IRC06:27
*** tenobreg has joined #openstack-meeting-306:29
*** negronjl has quit IRC06:30
*** tellesnobrega has quit IRC06:31
*** lpetrut has joined #openstack-meeting-306:32
*** yamamoto_ has quit IRC06:33
*** galstrom is now known as galstrom_zzz06:37
*** anilvenkata has joined #openstack-meeting-306:42
*** julim_ has quit IRC06:43
*** julim has joined #openstack-meeting-306:44
*** paul-carlton2 has joined #openstack-meeting-306:45
*** negronjl has joined #openstack-meeting-306:50
*** irenab has quit IRC06:50
*** rajinir has quit IRC06:56
*** nkrinner_afk is now known as nkrinner07:00
*** irenab has joined #openstack-meeting-307:01
*** coolsvap has joined #openstack-meeting-307:10
*** irenab has quit IRC07:10
*** lpetrut has quit IRC07:13
*** yamamoto_ has joined #openstack-meeting-307:17
*** irenab has joined #openstack-meeting-307:18
*** sankarshan_away is now known as sankarshan07:20
*** Sukhdev has quit IRC07:24
*** stevejims has joined #openstack-meeting-307:26
*** singlethink has joined #openstack-meeting-307:26
*** gouthamr_ has joined #openstack-meeting-307:28
*** gouthamr has quit IRC07:29
*** iyamahat has joined #openstack-meeting-307:30
*** lpetrut has joined #openstack-meeting-307:30
*** irenab has quit IRC07:31
*** anilvenkata is now known as anilvenkata_afk07:31
*** singlethink has quit IRC07:32
*** andreas_s has joined #openstack-meeting-307:33
*** irenab has joined #openstack-meeting-307:33
*** iyamahat has quit IRC07:35
*** matjazp has joined #openstack-meeting-307:36
*** irenab has quit IRC07:48
*** sdake has quit IRC07:51
*** irenab has joined #openstack-meeting-307:53
*** spzala has joined #openstack-meeting-307:54
*** spzala has quit IRC07:59
*** lpetrut has quit IRC08:02
*** matrohon has joined #openstack-meeting-308:04
*** gouthamr_ has quit IRC08:08
*** stevejims has quit IRC08:09
*** andreas_s has quit IRC08:09
*** ccamacho has quit IRC08:10
*** rmart04 has joined #openstack-meeting-308:13
*** ccamacho has joined #openstack-meeting-308:14
*** ibmko has quit IRC08:15
*** pgadiya has joined #openstack-meeting-308:15
*** lpetrut has joined #openstack-meeting-308:17
*** ralonsoh has joined #openstack-meeting-308:18
*** nkrinner has quit IRC08:20
*** nkrinner has joined #openstack-meeting-308:22
*** andreas_s has joined #openstack-meeting-308:23
*** lpetrut has quit IRC08:28
*** singlethink has joined #openstack-meeting-308:28
*** nkrinner has quit IRC08:28
*** anilvenkata_afk is now known as anilvenkata08:31
*** lpetrut has joined #openstack-meeting-308:31
*** gouthamr has joined #openstack-meeting-308:33
*** singlethink has quit IRC08:33
*** lpetrut has quit IRC08:41
*** stevejims has joined #openstack-meeting-308:41
*** irenab has quit IRC08:41
*** lpetrut has joined #openstack-meeting-308:41
*** nkrinner has joined #openstack-meeting-308:42
*** lpetrut has quit IRC08:46
*** julim has quit IRC08:46
*** irenab has joined #openstack-meeting-308:49
*** ibmko has joined #openstack-meeting-308:50
*** pcaruana has joined #openstack-meeting-308:58
*** zhurong has quit IRC09:06
*** zhurong has joined #openstack-meeting-309:09
*** irenab has quit IRC09:11
*** gouthamr has quit IRC09:11
*** irenab has joined #openstack-meeting-309:13
*** mickeys has quit IRC09:13
*** absubram_ has joined #openstack-meeting-309:17
*** absubram has quit IRC09:19
*** absubram_ is now known as absubram09:19
*** irenab has quit IRC09:26
*** emagana has joined #openstack-meeting-309:26
*** irenab has joined #openstack-meeting-309:29
*** singlethink has joined #openstack-meeting-309:30
*** emagana has quit IRC09:31
*** zhurong has quit IRC09:33
*** singlethink has quit IRC09:35
*** zhurong has joined #openstack-meeting-309:35
*** hogepodge has quit IRC09:45
*** hogepodge has joined #openstack-meeting-309:46
*** irenab_ has joined #openstack-meeting-309:49
*** irenab has quit IRC09:49
*** irenab_ is now known as irenab09:49
*** zhurong has quit IRC09:50
*** irenab has quit IRC09:53
*** zhurong has joined #openstack-meeting-309:55
*** zhurong has quit IRC10:01
*** numans has joined #openstack-meeting-310:06
*** irenab has joined #openstack-meeting-310:07
*** jtomasek has joined #openstack-meeting-310:07
*** yamahata has quit IRC10:08
*** bogdando has quit IRC10:08
*** yamamoto has joined #openstack-meeting-310:09
*** bks has joined #openstack-meeting-310:10
*** kzaitsev_mb has joined #openstack-meeting-310:10
*** yamamoto_ has quit IRC10:11
*** irenab_ has joined #openstack-meeting-310:12
*** yamamoto_ has joined #openstack-meeting-310:13
*** gouthamr has joined #openstack-meeting-310:14
*** irenab has quit IRC10:14
*** irenab_ is now known as irenab10:14
*** mickeys has joined #openstack-meeting-310:14
*** sambetts_ is now known as sambetts10:17
*** mickeys has quit IRC10:20
*** gouthamr_ has joined #openstack-meeting-310:23
*** bogdando has joined #openstack-meeting-310:23
*** gouthamr has quit IRC10:25
*** mariannelm has joined #openstack-meeting-310:25
*** gouthamr has joined #openstack-meeting-310:27
*** gouthamr_ has quit IRC10:30
*** singlethink has joined #openstack-meeting-310:31
*** lpetrut has joined #openstack-meeting-310:33
*** julim has joined #openstack-meeting-310:35
*** hoangcx has quit IRC10:36
*** singlethink has quit IRC10:37
*** julim has quit IRC10:40
*** yamamoto has quit IRC10:51
*** julim has joined #openstack-meeting-310:52
*** yamamoto has joined #openstack-meeting-310:52
*** yamamoto has quit IRC10:56
*** kzaitsev_mb has quit IRC10:57
*** hogepodge has quit IRC11:01
*** kzaitsev_mb has joined #openstack-meeting-311:11
*** mickeys has joined #openstack-meeting-311:17
*** mickeys has quit IRC11:21
*** hogepodge has joined #openstack-meeting-311:21
*** hogepodge has quit IRC11:26
*** stevejims has quit IRC11:32
*** singlethink has joined #openstack-meeting-311:33
*** rtheis has joined #openstack-meeting-311:33
*** hogepodge has joined #openstack-meeting-311:38
*** singlethink has quit IRC11:38
*** prateek has quit IRC11:42
*** psachin has quit IRC11:42
*** hogepodge has quit IRC11:48
*** huanxuan has quit IRC11:50
*** emagana has joined #openstack-meeting-311:54
*** gouthamr has quit IRC11:55
*** spzala has joined #openstack-meeting-311:55
*** julim has quit IRC11:56
*** spzala has quit IRC11:59
*** hogepodge has joined #openstack-meeting-312:00
*** psachin has joined #openstack-meeting-312:01
*** yamamoto_ has quit IRC12:02
*** psachin has quit IRC12:08
*** psachin has joined #openstack-meeting-312:10
*** mickeys has joined #openstack-meeting-312:17
*** bks has quit IRC12:18
*** mickeys has quit IRC12:21
*** alexismonville has joined #openstack-meeting-312:26
*** sdague has joined #openstack-meeting-312:26
*** alexismonville has quit IRC12:30
*** singlethink has joined #openstack-meeting-312:35
*** singlethink has quit IRC12:40
*** yamamoto has joined #openstack-meeting-312:45
*** psachin has quit IRC12:50
*** psachin has joined #openstack-meeting-312:52
*** psachin has quit IRC12:59
*** ianychoi_phone has joined #openstack-meeting-313:01
*** psachin has joined #openstack-meeting-313:03
*** iyamahat has joined #openstack-meeting-313:07
*** sdake has joined #openstack-meeting-313:09
*** haleyb_ has joined #openstack-meeting-313:13
*** pgadiya has quit IRC13:14
*** psachin has quit IRC13:15
*** ianychoi_phone has quit IRC13:18
*** mickeys has joined #openstack-meeting-313:18
*** anilvenkata has quit IRC13:21
*** mickeys has quit IRC13:23
*** yamahata has joined #openstack-meeting-313:24
*** prateek has joined #openstack-meeting-313:31
*** singlethink has joined #openstack-meeting-313:36
*** singlethink has quit IRC13:42
*** baoli has joined #openstack-meeting-313:45
*** baoli has quit IRC13:48
*** baoli has joined #openstack-meeting-313:49
*** baoli has quit IRC13:50
*** baoli has joined #openstack-meeting-313:50
*** absubram has quit IRC13:51
*** alexismonville has joined #openstack-meeting-313:55
*** coolsvap has quit IRC13:57
ttxo/14:00
alexismonvillehello :)14:00
* fungi smells a meeting14:00
gothicmindfoodohhai14:01
gothicmindfoodsorry, I went to the wrong channel14:01
* persia watches14:01
EmilienMbonjour :-)14:01
gothicmindfood#startmeeting openstack-swg14:01
openstackMeeting started Thu Dec  8 14:01:59 2016 UTC and is due to finish in 60 minutes.  The chair is gothicmindfood. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: openstack-swg)"14:02
openstackThe meeting name has been set to 'openstack_swg'14:02
* gothicmindfood needs to get her irssi windows memorized better14:02
gothicmindfoodanyhoo14:02
gothicmindfood#agenda https://wiki.openstack.org/wiki/Meetings/SWGMeeting14:02
* jroll moves over here14:03
gothicmindfoodI'll do a reping14:03
gothicmindfoodamrith, dhellmann, gothicmindfood, ttx, jroll, johnthetubaguy, sdague, mordred, carolbarrett, nikhil, mugsie, thingee, alexismonville, edleafe, EmilienM, harlowja, devananda, bastafidli14:03
gothicmindfood#topic Review/recap action items14:04
*** openstack changes topic to "Review/recap action items (Meeting topic: openstack-swg)"14:04
ttxlivefixing startmeeting stanza: https://review.openstack.org/40863314:04
* EmilienM is dancing for his first swg meeting :-)14:04
alexismonville:)14:04
gothicmindfood#link http://eavesdrop.openstack.org/meetings/openstack_swg/2016/openstack_swg.2016-11-08-15.04.html14:04
gothicmindfoodttx: oh yeah, thanks!14:04
gothicmindfoodI was going to bring that up in open discussion14:05
gothicmindfoodthings are a bit disorganized in our logs because of inconsistency14:05
gothicmindfoodwelcome EmilienM :)14:05
gothicmindfoodso I had all sorts of fun action items14:05
gothicmindfoodgo me14:05
gothicmindfoodttx: had one14:06
gothicmindfoodand amrith had another, which was to change this meeting time and he already did that.14:06
* gothicmindfood high fives amrith14:06
fungii could probably stream-edit the old logs on disk and them move them to a consistent directory, but that breaks any logs/minutes anyone might have linked to elsewhere (e.g., mailing list posts, et cetera)14:06
ttxHaven't collected my thoughts on that one yet. I consider it non-urgent though, more of a long-term discussion14:06
gothicmindfoodttx: no worries! that looks like a long-term project14:06
*** psachin has joined #openstack-meeting-314:07
gothicmindfoodttx: does it help to keep it as an action for the next meeting? Or do we want to maybe track it somewhere else/the vision doc for the PTG/etc?14:07
ttxOne thing we should discuss however is how to retrofit johnthetubaguy's visioning into this group activity14:07
gothicmindfoodagreed - I was planning on that for open discussion14:07
ttxgothicmindfood: probably better to track it elswhere14:07
*** VW has joined #openstack-meeting-314:07
persiaFormal agendas are good :)14:07
gothicmindfoodI can move through my stuff pretty quickly, so I'll get going :)14:07
*** VW has quit IRC14:08
*** jed56 has joined #openstack-meeting-314:08
*** VW has joined #openstack-meeting-314:08
gothicmindfoodso - I'll do my "Send a note to the ML about the SWG"14:08
gothicmindfoodthat is here now:14:09
gothicmindfood#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107712.html14:09
gothicmindfoodthere were zero responses14:09
gothicmindfoodwhich was a little sad14:09
gothicmindfoodbut maybe that just means I'm really good at explaining things?14:09
gothicmindfoodI'd love it, though, if folks from the group can chime in with their thoughts on the ML14:09
gothicmindfoodany thoughts?14:10
gothicmindfoodit was also pretty close to Thanksgiving, so it might've been lost in vacation for US folks14:10
alexismonvilleok, we could define on what aspect we want to foster the conversation ?14:10
*** spzala has joined #openstack-meeting-314:10
gothicmindfoodalexismonville: one productive direction might be to latch onto what you think we should accomplish in the next 6 or so months?14:11
gothicmindfoodI'd love to start a ML discussion on what people perceive the needs to be in the community around these themes14:11
ttxI think we can't explain much more... we should focus on getting something visible done14:11
ttxso that we can point back to it to illustrate how useful the SWG is14:12
alexismonvillethe draft of the vision that is announce in the email?14:12
fungiwe've certainly got some hard conversations the tc is raising, so maybe those fit into the set of "sorts of things [we'd] like to see tackled"14:12
ttxyeah, that sounds like a good visible thing14:12
gothicmindfoodfungi: yeah, I mean, part of "getting things done" feels more like fostering conversations that wouldn't happen otherwise, and less "here is a document" sometimes14:12
gothicmindfood(not all the time, but sometimes)14:12
*** lblanchard has joined #openstack-meeting-314:12
ttxthe principles and goals initiatives were not really SWG byproducts, more of a consequence of the training discussion14:13
ttx(which is good, but doesn't help "selling" the SWG14:14
gothicmindfoodttx: do you want to bring up the vision in the ML thread?14:14
ttxI can reply to thread and tie the visioning to the group yes14:14
gothicmindfoodthat'd be great14:14
gothicmindfoodanyone else have ideas for where that thread might want to go to start a larger discussion?14:14
*** yamamoto has quit IRC14:14
ttxaction me on that. Happy to leave it to johnthetubaguy if he wants it, since he started it14:14
gothicmindfood#action ttx or johnthetubaguy to reply to [swg] thread on mailing list with conversation about TC vision14:15
gothicmindfoodcool14:15
*** haleyb_ has quit IRC14:15
ttxI'll do it tomorrow unless he beats me to it14:15
alexismonvilleI would like to hear what EmilienM has to say as a new TC member :)14:15
ttxyes, that would be nice. Like how it is compared to how he thought it would be14:16
*** srobert has joined #openstack-meeting-314:16
gothicmindfoodEmilienM: we'd love to hear from you on what you think the SWG can do!14:16
*** yamamoto has joined #openstack-meeting-314:16
ttx(Emilien volunteered to drive eth Pike goals initiative, which is good trial by fire too)14:17
gothicmindfoodoooh, fun14:17
ttxgothicmindfood: sshh. Don't discourage him yet14:17
EmilienMyes I'm on travel this week but back home next week, i'll continue the work14:17
gothicmindfoodthat actually dovetails nicely into my next item, which is TC members/more leadership training dates14:17
fungitc members already seem well-placed to initiate "difficult conversations" so perhaps the swg is in a better position to help those outside leadership positions to be able to do the same?14:17
*** lblanchard1 has joined #openstack-meeting-314:17
EmilienMttx: good luck to discourage me.14:17
gothicmindfoodfungi: they might be well placed, but they often don't manage to always do it14:18
gothicmindfoodfungi: and sometimes that's just because there's not a shared language around it14:18
gothicmindfoodfungi: and sometimes that's for other reasons14:18
fungiat least i'm certainly not one to shy away from raising difficult issues. the bigger problem there is that it can be hard to get anyone else to engage in other sides of the conversation14:18
ttxfungi: yeah, I don't see the SWG really help the TC having discussion. Once it is raised at TC level we usually do a good job at addressing it. It's before and below that I think the SWG is most useful14:18
ttxLike identifying stuff we should be discussing, helping others having discussions, and providing tools14:19
gothicmindfoodttx: ++14:19
*** mickeys has joined #openstack-meeting-314:19
gothicmindfoodokay - so I was able to contact folks new to the TC and folks in the TC who haven't attended leadership training yet14:19
ttxthe principles stuff for example is a good example of something we should have been discussing earlier14:19
persiaWould it also be useful to indicate that those not on the TC who may not think the issue is ready to raise to the TC are welcome to suggest the issue to the SWG?14:19
ttxthe longer we waited, the more difficult it was to write14:20
*** lblanchard has quit IRC14:20
ttx"Office hours for questions on leadership"14:20
fungipersia: maybe, though i also wouldn't want people to get the impression that the tc or its members are unapproachable14:20
gothicmindfoodpersia: I think anyone can bring anything to the TC they want, but the SWG might stand in as an interpreter of items getting raised to help identify the themes around some of the issues and maybe the broader conversation that needs to hapen?14:20
*** gouthamr has joined #openstack-meeting-314:21
alexismonvillettx +1 on office hours14:21
EmilienMalexismonville: you want my feedback about my first days as a TC member?14:21
persiaAbsolutely.  The narrative of unapproachability is already too string.14:21
gothicmindfoodpersia: I don't see us as being some kind of intermediary for TC agenda items :)14:21
persias/string/strong/14:21
alexismonvilleEmilienM: yes14:21
EmilienMhttp://my1.fr/files/emilien-right-now.jpg14:21
gothicmindfoodEmilienM: :)14:21
persiagothicmindfood: I was also thinking of expanding/exploring things for presentation, or facilitating raising the point.14:21
gothicmindfoodso - re: leadership training at ZingTrain - we're looking at the week of April 10th14:22
EmilienMalexismonville: I notice the TC meetings are quite difficult to follow and participate as a non-native english speaker14:22
gothicmindfooddhellmann: ttx - I know we three in particular discussed the idea of having at least one person who was present at the last training present at the new one14:22
alexismonvilleEmilienM: why are they difficult to follow specifically?14:22
EmilienMit has nothing to do with TC org itself, but the way we do meetings might be revisited sometimes14:22
alexismonvilleEmilienM: what could be the suggestions to make?14:23
*** flaper87 has joined #openstack-meeting-314:23
gothicmindfooddhellmann: ttx - how does the week of April 10 look for you?14:23
EmilienMalexismonville: the one from Tuesday was really hard, because of the high flow14:23
EmilienMalexismonville: a lot of thoughts in the same time, quite hard to comment / express / give feedback on IRC during one hour14:24
jrollgothicmindfood: I'm happy to do that if nobody else wants to, given it's easy travel for me - otherwise I'll come meet up for dinner :P14:24
*** mickeys has quit IRC14:24
gothicmindfoodjroll: ah cool, \o/ for not having to take a plane there :)14:24
jroll\o/ indeed!14:24
*** donghao has joined #openstack-meeting-314:25
EmilienMalexismonville: other than meetings, a lot of positive things, like being able to give +2 on governance decision after thinking about it (outside a meeting ;-))14:25
gothicmindfoodalexismonville: persia - are either of you interested in attending a leadership training the week of April 10?14:26
* gothicmindfood already checked with fungi and EmilienM 14:26
fungiEmilienM: yeah, i think an unanticipated downside to explicit voicing in the discussion is that everyone queued up their positions and blasted them into the channel when their turn came around. as a native english speaker even i have trouble reading that fast14:26
*** rmart04 has quit IRC14:26
persiagothicmindfood: I can let you know by end-of-day.  I don't have an answer now.14:26
EmilienMgothicmindfood: yes, I checked with management, and I'm 99% sure to come. I'll confirm with you asap next week14:26
gothicmindfood#action gothicmindfood to poll #openstack-swg channel on leadership training dates14:26
alexismonvilleI am interested14:26
gothicmindfoodEmilienM: sounds good!14:26
* EmilienM will bring canadian mapple sirup14:27
gothicmindfoodWhere the date stands, btw: I have two separate weeks held with ZingTrain and will be checking in with the foundation on funding and their attendance this week14:27
flaper87gothicmindfood: will it be the same training ?14:27
gothicmindfoodflaper87: it will!14:27
gothicmindfoodflaper87: except different people, so probably will feel a bit different, I'm sure14:27
alexismonvillegothicmindfood: please avoid the spring break week :)14:27
flaper87gothicmindfood: gotcha, will that target still be the entire TC team ?14:28
alexismonvilleApril 1714:28
gothicmindfoodalexismonville: yeah, everyone has different spring breaks across the country14:28
flaper87gothicmindfood: and across the world :P14:28
gothicmindfoodthe week of April 17 was most people's, which is why I'm pushing for April 10th14:28
jrollspring break is a great time to be in michigan, everybody vacates to florida14:28
* alexismonville was not aware that it was different dates in the US14:28
alexismonvillegothicmindfood: cool14:29
fungischools and school systems all decide for themselves14:29
fungiit's pretty chaotic14:29
gothicmindfoodflaper87: right now the target is TC members who haven't gone, and others who are interested. And I'm very open to suggestions on targets for recruiting14:29
* gothicmindfood is thinking user committee and board members14:29
EmilienMgothicmindfood: do we have some documentation / website about that training? (like some sort of agenda, etc)14:29
fungias someone who lives in a spring break destination, we have a mini tourist season here that stretches for a month or so14:29
flaper87gothicmindfood: I was actually going to suggest that target so ++14:29
gothicmindfoodand one product working group member14:29
gothicmindfoodEmilienM: it's an amalgamation of a couple of the trainings that ZingTrain offers - I sort of worked with them for a few months to design it specifically for OpenStack14:30
gothicmindfoodEmilienM: https://www.zingtrain.com/our-seminars/leading-with-zing14:30
gothicmindfoodand https://www.zingtrain.com/our-seminars/managing-ourselves14:30
alexismonvillegothicmindfood: I don't remember the cost of the training14:30
EmilienMfungi: i'm not really concerned about "/me not being able yet to be productive during TC meetings" as I consider meetings a sync process. I personally consider more important async tasks, like Gerrit reviews and ML decisions.14:31
EmilienMgothicmindfood: thank you14:31
gothicmindfoodand cost will (hopefully, still confirming) be covered by the Foundation, so attendees only need to cover their travel costs14:31
fungiEmilienM: i completely agree with that viewpoint14:31
alexismonvillegothicmindfood: great :)14:31
ttxsorry got sidetracked, reading scrollback14:31
flaper87fwiw, the feedback after last year's training was that it was useful.  That was my feeling as well and I'd recommend it14:32
flaper87fungi: EmilienM ++14:32
* edleafe wanders in late14:32
jrollflaper87: +114:32
* ttx looks up APril calendar14:32
flaper87I'm not new in the TC already but I remember when I started as if it was yday14:32
flaper87so, I'm happy to talk about it and provide feedback14:32
fungii have an extreme distrust in "leadership seminars" on the whole, but i trust gothicmindfood so i'll be there ;)14:33
jrollfungi: I do too, and found this one super valuable14:33
gothicmindfoodfungi: hahah. So much pressure! but I think you might actually enjoy it14:33
gothicmindfoodI have more confidence in it now that I've taken a group through it14:33
ttxApril 10 week still open for me, but might close if I organize personal vacation. So no commitment yet14:33
fungii'm familiar with too many which are fronts for brainwashing ponzi schemes14:34
gothicmindfoodokay - my *last* action item for this meeting was "drive the creation of a list of deliverables for PTG"14:34
gothicmindfoodwhich i chose to do by starting the outline of a vision for the PTG for us14:34
gothicmindfoodit's... kind of short and sad right now, which has everything to do with my current performance schedule and nothing to do with how excited I am for the PTG :)14:35
gothicmindfood#link https://etherpad.openstack.org/p/AtlantaPTG-SWG14:35
gothicmindfoodI invite folks to take a look there14:35
gothicmindfoodI'll also post in the -swg channel so we can do edits between now and the next SWG meteing14:35
gothicmindfoodwe're entering holiday season, but do we think it's possible, given async contributions on that document, to get something we can feel excited about by our first meeting in January?14:36
gothicmindfoodI'd love to give ourselves two months of prep working around a vision to plan and make the sessions great (including recruiting and driving ML activity prior)14:37
*** singlethink has joined #openstack-meeting-314:37
ttxonly two months away ? Oh god14:37
EmilienMwhat is the intent behing mesure targets for diversity?14:37
*** mlavalle has joined #openstack-meeting-314:37
jrollttx++14:37
gothicmindfoodwell, post-December14:38
gothicmindfoodEmilienM: I mean diverse project representation14:38
EmilienMsome project are single vendor, we know that already.14:38
gothicmindfoodwhich is basically going for bringing in all sorts of different project perspectives14:38
EmilienMoh ok14:38
* alexismonville ttx realize... honey, I shrink the release cycle :p14:38
gothicmindfoodEmilienM: and I'm not even sure it matters, which is why I asked there14:38
gothicmindfoodI'm super open to input14:38
gothicmindfoodwe went with numbers for our Barcelona vision, so really I'm just wondering if we want to measure anything else based on types of attendee?14:39
alexismonvilleI think that representation from projects is something importnat to trakc14:39
alexismonvilleit will "force" us to encourage people from the different projects to joiun14:39
EmilienMgothicmindfood: indeed, we might be interested to know which projects in OpenStack have PTG sessions and collect some outputs (number of sessions, blueprints, topics, people, etc)14:39
gothicmindfoodI also think representation from projects could lead to the nice "vision" of the SWG that ttx outlayed above - having a place to help facilitate conversations with the TC that increases communication between the TC and the rest of OpenStack14:41
EmilienMit might help in understanding how OpenStack is progressing, etc, somehow14:41
fungiEmilienM: that may also depend on the level of formality each team decides to apply to their time during the ptg14:41
EmilienMfungi: that is true14:41
fungiit's still unclear to me the extent to which we should expect to adhere to any formal agenda14:41
fungi(in planning for the infra team specifically, i mean)14:42
gothicmindfoodfungi: given that level of formality-in-flux, do you think it's worthwhile for the SWG to plan on any informal reaching-out to teams there? and if so, what might that look like?14:42
fungimany teams may opt for unconference-style pitches the first morning, so be showing up with no pre-agreed-upon agenda at all14:42
* gothicmindfood is very keen on diversifying our vision from just "we did these sessions"14:42
fungimaybe it would help to get some community-wide discussions going about how different teams plan to organize )or not) their days14:43
ttxI'll admit I have limited time to dedicate to SWG activities with the PTG organization and all the things we usually do in 6 months to be done in 4.514:44
EmilienMfungi: as a PTL, I plan to prepare a rough agenda of our sessions.14:44
ttxshoudl be better in Pike !14:44
fungisharing ideas, for the benefit of teams who may not know what they want to do and are looking to others for suggestions14:44
jrollI plan to treat it like a midcycle, fwiw, a few set topics (priorites) and unconference for much of it14:44
gothicmindfoodfungi: yeah, probably. Hm. Should we do another ML thread devoted to that discussion? Or leave it to a [tc] led discussion, or ptl discussion, and just chime in there?14:44
EmilienMfungi: specially as we are creating TripleO squads, I might expect to have multiple TripleO tracks in same time, so agenda will be useful :-)14:44
fungifor infra, and i know we're a little different (isn't every team?), i expect there will be subgroups of us working on lots of different things in parallel and floating back and forth fluidly as required14:45
EmilienMjroll: yes, preparing topics before PTG sounds great14:45
ttxyeah, I think it's a safe bet to consider it a midcycle on steroids, with the ability to plug other people in and to attend extra things14:45
EmilienMfungi: yeah, I've noticed infra sessions work very well like that14:45
gothicmindfoodthe PTG sounds way more fun now :)14:46
gothicmindfoodI'd like to table this to move onto a quick discussion of johnthetubaguy 's vision, if y'all don't mind. We can continue this in the etherpad vision/ -swg channel and ML14:46
fungibut also we tend to send emissaries out to other teams' spaces to help them with infra-specific bits of their initiatives too14:46
gothicmindfood#topic Discuss TC vision document14:47
*** openstack changes topic to "Discuss TC vision document (Meeting topic: openstack-swg)"14:47
fungior at least that's how we structured our involvement during past summits so i expect things will sort of happen similarly in this context14:47
gothicmindfoodttx: dyou have a link on you?14:47
* gothicmindfood fishes in the -swg channel 14:47
ttxhmm14:47
ttxI have that14:48
gothicmindfood#link https://review.openstack.org/#/c/401225/14:48
ttx* Add a draft TC vision structure [https://review.openstack.org/401225]14:48
ttx* Add a draft OpenStack technical vision [https://review.openstack.org/401226]14:48
gothicmindfood#link https://review.openstack.org/#/c/401226/14:48
gothicmindfoodawesome14:48
gothicmindfoodjohnthetubaguy: you around?14:48
persiaI heard a rumour he was taking the week for personal activities.14:49
fungiyeah, he e-mailed the tc ml14:49
fungihe's otherwise occupied14:49
gothicmindfoodah, it is the vacation time of year :)14:50
gothicmindfoodwell, we can certainly have a quick cover of what's been going on with this and table further discussion til he's back14:50
gothicmindfoodone of the things that came up was that it's sort of a "motion to describe what a vision is" rather than a vision itself... he's basically laying the groundwork for the vision.14:51
gothicmindfoodttx: has there been discussion about this yet at TC meetings?14:51
* gothicmindfood has been stuck in rehearsals for the last few tuesdays so has had to miss them14:51
ttxyes there was14:51
gothicmindfoodttx: what's the movement there right now?14:51
ttxthe conclusion was that we should reboot the effort of building a vision, through the SWG group14:51
gothicmindfoodoh fun14:52
ttxrather than iterate on review14:52
gothicmindfood;)14:52
*** sankarshan is now known as sankarshan_away14:52
gothicmindfoodso it looks like we might have our first project, y'all14:52
ttxbecause it was unlikely to get anywhere fast. An etherpad was deemed a better solution to iterate fast on prose14:52
ttxlet me fetch meeting slogs for ya14:52
ttxhttp://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-11-29-20.01.log.html#l-23914:53
ttxwe also said we should work on TC vision before OpenStack vision, as it's simpler14:53
fungipresumably we'll just cram his draft change into an etherpad, hack it to bits, and then push the result up as a new patchset14:53
ttxand part of the TC vision can be to get an OpenStack vision developed14:53
*** johndperkins has joined #openstack-meeting-314:54
ttxfungi: ++14:54
jrollfungi: ++14:54
*** VW has quit IRC14:54
ttxI think we also need to bootstrap the "visioning" exercise by setting a target vision date etc14:54
*** matjazp has quit IRC14:55
ttxthings that were not really discussed on the review at all because it wasn't formulated as a vision but more as a set of topics to address through a vision14:55
jrollI quite like the march 2018 date john used here14:56
ttxI think 18 months / 2 years is a good timeframe for a TC vision14:56
*** galstrom_zzz is now known as galstrom14:56
ttxWe know there are a number of changes we need to navigate in that timeframe14:56
gothicmindfoodttx: do you see the OpenStack vision covering a longer timeframe than that?14:56
alexismonvilleI agree with the 18-24 month, with intermediate results14:56
*** galstrom is now known as galstrom_zzz14:56
ttxMarch 2018 is on the short end of it, but works14:56
ttxSept 2018 would work as well14:57
jrollagree14:57
gothicmindfoodI think I'd be more comfortable with September. I'm also curious how long it will take to work in user committee and board feedback to a document14:57
jrolland if the goal is to finish this by end of PTG, march 18 is actually a bit short14:58
ttxSept 2018 / by that time we would have had 3 PTGs and prepare for the 4th14:58
alexismonvilleso we could need to timebox the exercize?14:58
*** john-davidge has joined #openstack-meeting-314:58
ttxYeah, I think Sept 2018 is better because it will take us a few months to get there14:58
gothicmindfoodalexismonville: we absolutely should set a date for when we'll have a draft for community review, and then a final document14:58
gothicmindfoodokay14:58
flaper87ttx: ++14:59
gothicmindfoodthis is pretty cool, I'm really excited that the TC and johnthetubaguy have started all of this and that we get to participate14:59
ttxand then a one-year horizon between vision-defined and vision-complete is /very/ short:)14:59
EmilienMdoes a document like this can really be final?14:59
jrollgothicmindfood: ++14:59
gothicmindfoodwe have 60 seconds left, but I'd love to chat in #openstack-swg about this for a bit longer if you all have time14:59
alexismonvilleand we could encourage people to schedule 3 times 30 minutes in their calendar to work on that?14:59
persiaEmilienM: It can be posted as authoritative, subject to modification by empowered bodies.14:59
gothicmindfoodotherwise, there's our nice little PTG etherpad we can write in until our next meeting14:59
gothicmindfood:)14:59
ttxEmilienM: It's an exercise in describing a potential future, not an evolving roadmap14:59
EmilienMttx: fair enough15:00
ttx(it's new for me too)15:00
gothicmindfoodthanks so much for attending everyone!15:00
*** VW has joined #openstack-meeting-315:00
gothicmindfood#endmeeting15:00
jrollEmilienM: it's "this is where we want to get to", which helps define some of our actions on that path, even if we don't make it15:00
alexismonvillethanks :)15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Dec  8 15:00:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
jrollthanks gothicmindfood :)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_swg/2016/openstack_swg.2016-12-08-14.01.html15:00
*** janzian has joined #openstack-meeting-315:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_swg/2016/openstack_swg.2016-12-08-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_swg/2016/openstack_swg.2016-12-08-14.01.log.html15:00
ttxEmilienM: it's a thing you can use to weigh your decisions along the way15:00
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Dec  8 15:00:54 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
mlavalleHi, who is here for the L3 sub-team meeting?15:01
john-davidgeo/15:01
janziano/15:01
baoliHi15:01
* edleafe lurks in the shadows15:01
haleybhi15:01
mlavalleNice day to all of you!15:02
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
mlavalleBelieve it or not, Ocata-2 is almost here:15:02
mlavalle#link https://releases.openstack.org/ocata/schedule.html15:03
mlavalleAnd the Ocata-3 will be just 5 weeks afterwards. So, keep an eye on your commited deliverables15:04
*** psachin has quit IRC15:04
mlavalleA reminder also to the team regarding the upcoming PTG, February 20th - 24th:15:05
mlavalle#link https://www.openstack.org/ptg/15:05
mlavalleI checked half an hour ago, and there are 298 seats left15:05
mlavalleAnd finally, mlavalle completed his move to the Austin area yesterday.... :-)15:06
john-davidgemlavalle: Congrats!15:06
janzianWelcome to Austin!15:07
*** rbak has joined #openstack-meeting-315:07
mlavalleStill leaving surrounded by boxes, though ;-)15:07
mlavalleliving^^^^15:07
edleafesan antonio misses you already!15:07
mlavalleedleafe: LOL15:07
mlavalleAny other annoucements from the team?15:07
mlavalleOk, let's move on15:08
mlavalle#Topic Bugs15:08
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:08
mlavalleFirst one is https://bugs.launchpad.net/neutron/+bug/157012215:09
openstackLaunchpad bug 1570122 in neutron "ipv6 prefix delegated subnets are not accessable external of the router they are attached." [High,In progress] - Assigned to John Davidge (john-davidge)15:09
*** hurgleburgler has joined #openstack-meeting-315:10
mlavallejohn-davidge: you got a question from the reporter on how to deploy / test the fix. Did you see it?15:10
john-davidgemlavalle: There's a WIP patch here: https://review.openstack.org/#/c/407025 - which has already been tested by promethianfire. An issue with it using the wrong device-id has been uncovered, I'll have a fix up shortly15:10
mlavalleis promethianfire the reporter?15:11
john-davidgemlavalle: Yes, ended up responding to him privately, will post on LP as well15:11
mlavalleok, cool. THanks for the fix and the update15:11
john-davidgemlavalle: Yes he is15:11
mlavalle:-)15:11
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/162742415:12
openstackLaunchpad bug 1627424 in neutron "FlushError on IPAllocation" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:12
mlavalleI've been looking at this one since yesterday. I just assigned it to myself. Analyzed some of the tracebacks we are seeing in the Neutron server logs15:13
*** huanxuan_ has quit IRC15:13
mlavalleAnd found a reference in the SQLAlchemy docs to the specific exception. I posted a pointer to the relevant piece of doc in the bug15:14
mlavalleDoes anybody have any additional insight or comment?15:15
lcastellhey r1chardj0n3s forgot to ask yesterday about the  search-first stuff for user listings... is it the same as the "filter first" I did for other pages?15:15
mlavallelcastell: You might be in the wrong room. This is the Neutron l3 subteam meeting15:16
lcastellsorry yep15:16
lcastellI was reading the logs here :P... my bad15:16
mlavallelcastell: np15:17
mlavalleok, moving on to the next bug: https://bugs.launchpad.net/neutron/+bug/162748015:17
openstackLaunchpad bug 1627480 in neutron "create_port can succeed without returning fixed_ips on all requested subnets" [High,Confirmed]15:17
*** spotz_zzz is now known as spotz15:17
mlavalleThis one has not an owner. It is next in my list / backlog after the previous one. If someone wants to wrestle it out of my hands, please go ahead15:18
mlavalleOk, next one is https://bugs.launchpad.net/neutron/+bug/162790215:19
openstackLaunchpad bug 1627902 in neutron "DHCP agent conflicting with dynamic IPv6 addresses" [High,In progress] - Assigned to Brian Haley (brian-haley)15:19
mlavallehaleyb has a fix in progress for it, any comments?15:19
*** mickeys has joined #openstack-meeting-315:20
haleybre-fix is up for review, just had to add a release note to appease the review gods15:20
haleybhttps://review.openstack.org/#/c/406428/15:20
mlavalleyeah, I saw that. Actually it is the next patchset in my reviews backlog. I'll take a look later this morning15:20
haleybit had two +2's before i updated it, so it's ready to go15:21
mlavallecan I still take a look?15:21
mlavallehaleyb: ^^^^15:22
haleybof course :)15:22
mlavalle:-)15:22
*** prateek has quit IRC15:22
mlavalleNext one is https://review.openstack.org/#/c/392183/15:22
mlavalleOoops15:22
mlavallehttps://bugs.launchpad.net/neutron/+bug/163696315:22
openstackLaunchpad bug 1636963 in neutron "Service Subnets - DHCP port creation fails" [High,In progress] - Assigned to John Davidge (john-davidge)15:22
mlavalleThis one has a number of +1's in the proposed fix15:23
mlavallehaleyb: any chance you take a look?15:23
john-davidgehaleyb: commented to say he'd like to discuss it further here15:23
haleybi had looked and actually added this one to the agenda15:23
mlavallehaleyb: let's do it now15:24
*** mickeys has quit IRC15:24
haleybjohn-davidge: did you think that allowing network:dhcp when dhcp is enabled is a good change?  i haven't looked to see how difficult it would be15:25
haleybbut i would still do a fix that did not add network:dhcp to the types15:25
*** brianstajkowski has joined #openstack-meeting-315:25
john-davidgehaleyb: Yes, I think that's a reasonable ammendment. I haven't looked into the complexity either, but I don't anticipate it would add much15:25
john-davidgehaleyb: Yeah, your point about having to prevent users from removing it is valid, and would make for an ugly solution15:26
haleybjohn-davidge: right, plus we'd still have to treat it special since having just netowrk:dhcp there would cause other problems15:27
john-davidgeLet me look into what's necessary to restict it to dhcp_enabled subnets. If it's not too heavy I'll go ahead and do it15:27
haleybjohn-davidge: ok, let me know if you need help15:27
john-davidgeotherwise I'll comment with my findings15:27
john-davidgehaleyb: Thanks, will do15:27
baolihaleyb, hohn-davidge: I think my comments is more towards the semantics of service type. So the current fix should be good.15:27
haleybbaoli: you raised a good point though - that fix always allowed dhcp, but should probably only do it if it's enabled, so hopefully just a minor tweak15:28
john-davidgebaoli: I like your suggestion about only allowing it on dhcp_enabled subnets, narrows the use down some more15:29
baolihaleyb, john-davidge: cool, thanks15:29
mlavalleany other comments haleyb, john-davidge?15:30
haleybmlavalle: nope15:30
john-davidgemlavalle: no15:30
mlavallehaleyb, john-davidge: Thanks for working on this. Also thanks to baoli for his comments15:30
mlavalleLast one today is https://bugs.launchpad.net/neutron/+bug/161048315:31
openstackLaunchpad bug 1610483 in neutron "Pluggable IPAM rollback mechanism is not robust" [High,In progress] - Assigned to Aliaksandr Dziarkach (aliaksandr-dziarkach)15:31
mlavalleThere is a fix proposed for it:15:31
mlavalle#link https://review.openstack.org/#/c/390594/15:31
mlavalleI've been meaning to take a look at it. With the move to Austin, I couldn't find the time over the past few days15:32
mlavalleBut I'll get back to it. I encourage others to take a look15:32
mlavalleAny other bugs I might have missed?15:33
mlavalleOK, moving on15:34
mlavalle#topic Prefix delegation15:34
*** openstack changes topic to "Prefix delegation (Meeting topic: neutron_l3)"15:34
mlavallebaoli: you are up15:34
baolimlavalle: I have a couple of patches up for review15:34
baolimlavalle: kevinbenton -1'ed on one of them, I've been trying to reach out to him on IRC a couple of times15:35
baolimalavalle, I updated the etherpad15:35
mlavallebaoli: he's hard to reach. Works at very odd hours. I advise conduct the conversation in Gerrit15:36
baolimlavalle: I responded to his further comments. Let's what he has to say about it15:37
baolis/what/wait15:37
mlavallecool, any other updates?15:37
baoliI'd appreciate if folks in here would take a look at the patches15:38
mlavalleOk, thanks!15:38
baolimalvalle: one of the things I'm working on is to support PD on HA routers15:38
john-davidgebaoli: Cool!15:38
mlavalleyeah, that's great15:39
mlavalleThnaks15:39
baolijohn-davidge: sorry to take it over15:39
baolijohn-davidge: do we have a bug for it?15:39
john-davidgebaoli: You are very welcome to it :)15:39
john-davidgebaoli: For HA support? No I don't think so15:39
baoliif not, should I create a regular bug or a EFT?15:39
mlavallebaoli: I say it is a RFE15:40
john-davidgebaoli: I imagine that will need an RFE15:40
baolijohn-davidge, mlavalle: sure, I'll create a RFE bug.15:40
mlavallebaoli: Thank you15:40
mlavalleOk, moving on15:41
mlavalle#Topic Service Subnets15:41
*** openstack changes topic to "Service Subnets (Meeting topic: neutron_l3)"15:41
mlavalleWe already covered the dhcp stuff earlier15:42
mlavalleDo we want to say anything about the doc15:42
mlavalle?15:42
haleybi have not gotten to it yet, in my backlog15:42
mlavalleThat sounds good. Thanks!15:43
mlavalle#Topic Routed Networks15:43
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"15:43
haleybs/good/not good/ but...15:43
mlavalle:-)15:43
mlavalleI have continued working on the pathset to update Nova inventories with the routed neuworks ipv4 subnets topology15:44
mlavalle#link https://review.openstack.org/#/c/358658/15:44
mlavallekevinbenton asked me to do all the updates to Nova in batch15:45
mlavalleI finished that earlier this week15:45
mlavalleI've continued adding unit tests and I will be done with that soon15:45
kevinbenton\o/15:45
*** VW has quit IRC15:46
*** VW has joined #openstack-meeting-315:46
mlavalleAnd after that I just need to move my minimalist Nova placement client to a Neutron patchset15:46
mlavalleAnd will be done with this15:46
*** rmart04 has joined #openstack-meeting-315:47
mlavalleAny comments or questions?15:47
john-davidgeCarl and I got together to discuss the external networks enhancement on Monday. Currently working on a spec to cover that work. Will update the group when I have something for review.15:47
mlavallejohn-davidge: That's great. Thanks!15:48
*** robcresswell has left #openstack-meeting-315:48
mlavalleand thanks toi carl_baldwin to keep spending some time playing with us :-)15:48
*** mtanino has joined #openstack-meeting-315:49
mlavallejanzian: any comments as far as the Tempest test?15:49
janzianNope, just waiting for more reviews at the moment :)15:49
mlavallejanzian: Thanks!15:50
*** Marcellin__ has joined #openstack-meeting-315:50
mlavalleI don't see tidwellr on line. So we are going to skip BGP Dynamic Routing, unless someone wants to talk about it15:50
mlavalleOk....15:51
*** elmiko has joined #openstack-meeting-315:51
edleafemlavalle: let me know if I can help on the Nova side15:51
mlavalleedleafe: will do, thanks. And also thanks for lurking in the shadows :-)15:52
mlavalle#topic Open Agenda15:52
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_l3)"15:52
mlavalleAny other topics the team wants to bring up?15:52
mlavalleOk. Have a nice rest of your day15:53
mlavalleThanks for attending!15:53
mlavalle#endmeeting15:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:53
openstackMeeting ended Thu Dec  8 15:53:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-12-08-15.00.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-12-08-15.00.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-12-08-15.00.log.html15:53
*** janzian has left #openstack-meeting-315:54
*** cdent has joined #openstack-meeting-315:59
cdent#startmeeting api-wg16:00
openstackMeeting started Thu Dec  8 16:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api-wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
cdent#chairs elmiko etoews16:00
cdentwho's here, say hi.16:00
* cdent makes coffee16:00
elmikohi16:00
cdentoh noes, just the two of us?16:01
cdentedleafe?16:01
edleafe\o16:02
* edleafe was getting more coffee16:02
elmiko+116:02
cdentcoffee++16:02
*** rmart04 has quit IRC16:03
*** emagana has quit IRC16:04
cdentokay, lets get started16:04
*** nkrinner is now known as nkrinner_afk16:04
cdent#link agenda: https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:04
cdent#topic: old business16:05
*** openstack changes topic to ": old business (Meeting topic: api-wg)"16:05
cdent#link meeting notes: http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-12-01-16.00.html16:05
cdentthere was one action item on me to clean up references to api impact in the wiki, I did that16:05
scottdaHi16:05
cdentreplaced it with directions for other ways to get out attention for important reviews16:05
cdents/out/our/16:06
elmikonice16:06
cdent#topic open mic16:06
*** openstack changes topic to "open mic (Meeting topic: api-wg)"16:06
cdentnothing on the agenda16:06
cdentanyone have anything they'd like to talk about?16:06
* elmiko starts the beat-box16:06
cdentlooks like no16:08
cdent#topic guidelines16:08
*** openstack changes topic to "guidelines (Meeting topic: api-wg)"16:08
cdent#link under review: https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:08
cdentlooks like https://review.openstack.org/#/c/399131/ can be merged16:08
cdentand https://review.openstack.org/#/c/405515/ can be frozen16:09
cdentagree ?16:09
* elmiko looks16:09
edleafeyep16:09
elmiko+1 for merge16:09
elmikoand freeze16:10
cdentwith etoews not around, I'll violate protocol a bit and +1 his +216:11
cdentdone and done16:12
cdent#topic bug review16:12
*** openstack changes topic to "bug review (Meeting topic: api-wg)"16:12
cdentno new bugs16:12
cdentanybody have any bugs they think should exist?16:13
etoewsoops. i'm around but fighting a fire. sorry i missed the first notification.16:13
cdentetoews: no worries, fire trumps guideline16:13
*** haleyb_ has joined #openstack-meeting-316:13
*** galstrom_zzz is now known as galstrom16:13
cdent# topic newsletter16:14
cdent#link etherpad https://etherpad.openstack.org/p/api-wg-newsletter16:14
cdentanybody feeling saucy enough to write the gripping first paragraph? (I've done the rest)16:17
*** haleyb_ has quit IRC16:18
elmiko"it was a cold and dreary hour that day in freenode..."16:18
*** VW has quit IRC16:19
*** pcaruana has quit IRC16:19
elmiko"it was the best of guidelines, it was the worst of guidelines", better?16:19
*** mickeys has joined #openstack-meeting-316:20
cdentit is a far far better guideline16:21
elmikohahaha16:21
cdentokay, how's what we see there?16:22
elmikolooks good to me16:22
cdentmust be time to ship it then16:23
elmiko+116:23
cdentwill do that after the meeting ends16:23
cdent#topic end matter16:23
*** openstack changes topic to "end matter (Meeting topic: api-wg)"16:23
cdentanything else?16:23
elmikonothing from me16:23
edleafejust the feeling of powerlessness16:23
elmikoheh16:23
* edleafe thinks cdent knows what I'm talking about16:24
scottdaYeah, tough to sell smart API changes to Cinder team as well edleafe16:24
edleafescottda: these aren't even changes16:24
cdentshould we shut down for the 22nd? What about the 29th?16:24
edleafethey are brand spanking new greenfield APIs16:24
elmikocdent: that seems reasonable to me16:24
scottda:(16:24
elmikoedleafe: ouch...16:25
edleafeWell, cdent and I teamed up to fight back the forces of evil16:25
*** mickeys has quit IRC16:25
scottdaI've had to retreat and regroup myself.16:26
*** VW has joined #openstack-meeting-316:27
cdentIt's a common problem. It's hard to do good HTTP when habits have already been set.16:28
cdentEspecially when people aren't really wanting to do with HTTP what HTTP is for.16:28
*** baoli has quit IRC16:29
cdentbut anyway, that's a topic best saved for shady booths in smokey bars with beverages16:29
cdentShall we end the meeting?16:29
edleafe+116:29
scottdahttps://review.openstack.org/401941 is what I had issues with...thands edleafe for chiming in16:29
scottdas/thands/thanks16:29
cdent#endmeeting16:30
cdentthanks everyone for coming16:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:31
openstackMeeting ended Thu Dec  8 16:30:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-12-08-16.00.html16:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-12-08-16.00.txt16:31
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-12-08-16.00.log.html16:31
elmikothanks cdent16:31
*** VW has quit IRC16:31
*** elmiko has left #openstack-meeting-316:31
*** VW has joined #openstack-meeting-316:33
*** krtaylor has quit IRC16:34
*** cdent has left #openstack-meeting-316:38
*** mlavalle has left #openstack-meeting-316:43
*** numans has quit IRC16:44
*** jtomasek has quit IRC16:47
*** armax has joined #openstack-meeting-316:48
*** andreas_s has quit IRC16:54
*** alex_xu has quit IRC17:00
*** emagana has joined #openstack-meeting-317:01
*** bpokorny has joined #openstack-meeting-317:01
*** emagana has quit IRC17:01
*** emagana has joined #openstack-meeting-317:02
*** alex_xu has joined #openstack-meeting-317:02
*** yamamoto has quit IRC17:03
*** ralonsoh_ has joined #openstack-meeting-317:04
*** ralonsoh_ has quit IRC17:05
*** ralonsoh has quit IRC17:05
*** mickeys has joined #openstack-meeting-317:07
*** iyamahat has quit IRC17:08
*** matrohon has quit IRC17:09
*** krtaylor has joined #openstack-meeting-317:10
*** john-davidge has quit IRC17:11
*** lpetrut has quit IRC17:12
*** haleyb_ has joined #openstack-meeting-317:14
*** brianstajkowski has quit IRC17:17
*** donghao has quit IRC17:18
*** haleyb_ has quit IRC17:19
*** donghao has joined #openstack-meeting-317:21
*** piet has joined #openstack-meeting-317:21
*** s3wong has joined #openstack-meeting-317:22
*** johndperkins has left #openstack-meeting-317:22
*** yamamoto has joined #openstack-meeting-317:25
*** bpokorny has quit IRC17:27
*** bpokorny has joined #openstack-meeting-317:28
*** baoli has joined #openstack-meeting-317:30
*** singleth_ has joined #openstack-meeting-317:30
*** bpokorny has quit IRC17:32
*** singlethink has quit IRC17:34
*** yamamoto has quit IRC17:34
*** iyamahat has joined #openstack-meeting-317:36
*** bpokorny has joined #openstack-meeting-317:40
*** singleth_ is now known as singlethink17:47
*** s3wong has quit IRC17:50
*** tbachman has joined #openstack-meeting-317:50
*** Patifa has joined #openstack-meeting-317:52
*** Patifa has quit IRC17:54
*** SumitNaiksatam has joined #openstack-meeting-317:59
*** songole has joined #openstack-meeting-318:00
SumitNaiksatamtbachman: hi18:00
SumitNaiksatamsongole: hi18:00
tbachmanSumitNaiksatam: hi!18:00
songolehi18:00
SumitNaiksatam#startmeeting networking_policy18:00
openstackMeeting started Thu Dec  8 18:00:57 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
*** rkukura has joined #openstack-meeting-318:01
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Dec_8th_201618:01
rkukurahi18:01
SumitNaiksatam#topic Remove expunge_all calls18:01
*** openstack changes topic to "Remove expunge_all calls (Meeting topic: networking_policy)"18:01
SumitNaiksatam#link https://review.openstack.org/#/c/399772/18:01
tbachman:(18:01
SumitNaiksatami just rebased it18:01
SumitNaiksatamtbachman: :-)18:01
tbachmanSumitNaiksatam: I just got back to this mid-yesterday18:02
SumitNaiksatamsongole: any more data points at your end?18:02
SumitNaiksatamtbachman: np18:02
songoleRegarding sharing across threads..18:02
songolewe use getsession method provided by neutron18:03
songolewould that be an issue? we are talking about green threads here, right?18:03
tbachmansongole: in my mind, it *shouldn’t*, but I have yet to get through this code18:04
tbachmanI believe get_session is supposed to provide an interface that ensures each green thread gets its own session18:04
tbachmanbut I haven’t gotten thru this myself just yet18:04
* tbachman is doubting :)18:04
songoleok18:05
songoleregarding the specific patch, we ran tests locally with the patch18:05
SumitNaiksatami dont thinkg neutron does anything there, i think this has to have been implemented in oslo_db18:05
rkukurasongole: have you verified that each thread does its own getsession call, and that neither the session itself nor any of the DB objects associated with the sesssion are shared across threads?18:06
songoleand we hit the db exception which sumit and I debugged for lbaas v118:06
songolerkukura: yes. each thread does its own getsession18:06
*** ibmko has quit IRC18:06
rkukurasongole: thanks18:06
tbachmanokay, now I’m confused18:07
tbachmanyou’re hitting this w/o the expunge?18:07
tbachman(i.e. the DetachedInstanceError exception)18:07
*** jed56 has quit IRC18:07
SumitNaiksatamtbachman: i share your confusion ;-)18:08
SumitNaiksatamsongole: you hit the exception with or without the expunge_all ?18:09
SumitNaiksatamtbachman: thanks for referring to the exact exception, just so that we know we are all talking about the same thing :-)18:10
songoleI didn't see it myself. I just got an email from india team regarding this.18:10
songoleI will confirm18:10
SumitNaiksatamsongole: i hope its with the expunge_all call, otherwise it flies in the face of most of our analysis so far :-(18:10
songoleSumitNaiksatam: I understand.. I will confirm..18:11
tbachmanSumitNaiksatam: I’m hoping to have a better handle on this tomorrow18:12
SumitNaiksatamtbachman: on the side perhaps we can continue to rebase/recheck your patch to see if we see any consistent pattern of failures18:12
SumitNaiksatami will try to keep an eye as well18:13
tbachmanI realize that we’re short on time here, so unfortunately I’m not sure what to do here.18:13
SumitNaiksatami think there are several changes being made on the NFP side, and perhaps some of the exceptions we were seeing earlier on this patch were not related and might have gone away18:13
SumitNaiksatamtbachman: yeah same here, hence the offline email thread last week18:14
tbachmanSumitNaiksatam: maybe we can address this again offline tomorrow?18:14
tbachmanfor at least the core GBP stuff?18:14
SumitNaiksatamtbachman: sue18:14
SumitNaiksatam*sure18:14
tbachmanIf we’re lucky, any findings there might give us clues for NFP as well (if there are any)18:15
*** haleyb_ has joined #openstack-meeting-318:15
SumitNaiksatamsongole: so you are confirming that your usage of threads in NFP is session-safe i.e. sessions are not getting shared threads?18:16
songoleSumitNaiksatam: From our understanding, they are thread safe18:16
SumitNaiksatam*shared across18:16
*** harlowja has joined #openstack-meeting-318:17
songoleAnd, the lb db exception, i was seeing even without nfp18:17
SumitNaiksatamsongole: oh, but i thought you were earlier saying that was not the case with the lb exception18:18
SumitNaiksatamsongole: so the lb exception occured with or without GBP in the mix?18:19
songolewith GBP and with or without nfp18:19
SumitNaiksatamsongole: okay, so the expunge_all is still relevant18:19
SumitNaiksatambecause without GBP, it wont be18:20
*** haleyb_ has quit IRC18:20
*** harlowja_ has joined #openstack-meeting-318:20
* tbachman would like to expunge expunge_all18:20
SumitNaiksatamtbachman: yay to that18:21
SumitNaiksatamtbachman: songole: any other data point we need to discuss?18:21
tbachmanSumitNaiksatam: nothing from me (for now)18:21
SumitNaiksatamokay, so lets assume that NFP is indeed getting one session per thread18:22
*** harlowja has quit IRC18:22
SumitNaiksatamand sessions are not leaking across threads18:22
*** lpetrut has joined #openstack-meeting-318:22
*** songole has quit IRC18:22
SumitNaiksatamcan we analyze the exceptions we see henceforth on tbachman’s with that assumption?18:23
SumitNaiksatamtbachman’s patch i meant18:23
SumitNaiksatami think we got into the session leaking discussion because we were seeing some NFP exceptions which we could not explain18:24
tbachmanSumitNaiksatam: FWIW, in the original bug report from Ivar, the problem seemed to be state that wasn’t being created18:24
rkukuraDon’t forget that the DB objects stay associated with the session, so its important not to leak them across threads either.18:24
tbachmanthe UTs were failing b/c state wasn’t there18:24
SumitNaiksatamand attirbuted it to either the removal of the expunge_all call or the session leaking18:24
tbachman(e.g. assertEqual for a configuration that’s read back, but the configuration doesn’t exist)18:25
tbachmanwe should make sure that’s what the NFP failures were seeing (I believe they were, but don’t have the data in front of me atm)18:26
SumitNaiksatamtbachman: you are referring to this bug report, right: #link https://bugs.launchpad.net/group-based-policy/+bug/140441218:27
openstackLaunchpad bug 1404412 in Group Based Policy "Session's persistent objects across transactions create inconsistency" [High,Fix released] - Assigned to Ivar Lazzaro (mmaleckk)18:27
SumitNaiksatam?18:27
tbachmanSumitNaiksatam: ack18:27
SumitNaiksatamwhat i recall was that the problem was of stale state18:27
SumitNaiksatamand there are not threading issues with the UTs (at least not that i am aware off)18:28
SumitNaiksatamdoing the expunge_all was cleaning the in-session state and forcing reload from the db18:28
tbachmanSumitNaiksatam: one theory I had was that tox runs UTs in parallel, and somehow the two threads were affecting the same DB state18:29
tbachmanbut that’s a shaky theory at best18:29
*** songole has joined #openstack-meeting-318:29
tbachmanso, it wasn’t the sequential transactions per-se18:30
SumitNaiksatamtbachman: hmmm, i would be doubtful about that18:30
SumitNaiksatamtbachman: it might very well have been a bug at that time though18:30
songolesorry, networking issues. reconnected18:30
tbachmanSumitNaiksatam: ack18:30
tbachmanyeah18:30
SumitNaiksatamtbachman: and hence that problem does not manifest any more now18:30
tbachmanSumitNaiksatam: ack. But there are still a few things that don’t  make sense to me18:31
SumitNaiksatamtbachman: because you are not seeing any issues with the UTs after removing the call18:31
SumitNaiksatamsongole: np18:31
tbachmanfor example, changing it to expire should have had the same effect, were that the case18:31
tbachmanbut it didn't.18:31
SumitNaiksatamtbachman: hmmm, didnt think of that, but makes sense18:31
SumitNaiksatamrkukura: to your earlier point about sharing db objects across threads, if that is a culprit is some way with regards to the NFP errors, it would be difficult to track18:32
SumitNaiksatamrkukura: however, i don’t understand why it would manifest after removing the expunge_all call18:32
*** emagana has quit IRC18:33
SumitNaiksatam*is some way - in some way18:33
rkukuraSumitNaiksatam: Agreed it might be difficult to track, but the DB objects use the session when you try to follow associations, etc.18:33
tbachmanI think there are event logs we can turn on here, but I’m guessing it would be a complete overkill of info18:34
*** aweeks has joined #openstack-meeting-318:35
*** yamamoto has joined #openstack-meeting-318:35
SumitNaiksatamrkukura: answering my own question, if db objects were being used across threads, and removing the expunge_all call led to an exception, i think it means that it actually revealed an incorrect use of the db objects (across threads), no?18:35
tbachmanSumitNaiksatam: since the DB objects are tied to sessions, and sessions should only be used by a single thread, I’d say yes :)18:36
SumitNaiksatamtbachman: okay18:36
rkukuraSumitNaiksatam: Since expunge_all() dissaciates the DB objects from the session, it seems like it could be preventing the errors18:36
* tbachman believes that’s what rkukura was getting at18:36
rkukuradissassociates18:36
tbachmankeep in mind that the DB objects can only be used in this state if no backrefs are accessed18:37
tbachmanotherwise we get the exception18:37
*** emagana has joined #openstack-meeting-318:37
SumitNaiksatamtbachman: ah okay18:37
tbachmanSo, if the NFP code is doing this and not accessing backrefs, then we won’t see the exceptions in their code18:37
SumitNaiksatamtbachman: but that is regardless of the expunge_all, right?18:38
tbachmanSumitNaiksatam: actually, without the expunge_all, the object is still tied to the session18:38
tbachmanand the backref will work18:38
tbachmanand worse18:38
SumitNaiksatamtbachman: ah okay18:38
tbachmanIf two contexts are sharing the same DB object, and mutating it, then there are issues18:39
tbachmanSumitNaiksatam: I will also say that I’m still worried that my understanding of this is limited18:40
rkukuraI don’t think a DB object can be associated with two sessions at once18:40
SumitNaiksatamtbachman: by contexts you mean?18:40
*** bogdando has quit IRC18:40
rkukuraI read context as session, but maybe tbachman meant thread18:40
tbachmanyeah18:40
*** bpokorny has quit IRC18:40
* tbachman hates the terminology here18:40
tbachmancontext here meant thread18:41
tbachmansorry about that18:41
SumitNaiksatambut how can the db object with multiple sessions?18:41
SumitNaiksatam*be associated with18:41
*** bpokorny has joined #openstack-meeting-318:41
rkukuraSumitNaiksatam: I think “multiple sessions” was my mistaken interprettation of tbachman18:41
tbachmanrkukura: ack18:41
tbachmanI meant multiple threads sharing the same DB object18:41
SumitNaiksatamah sorry18:41
tbachmanSumitNaiksatam: my bad :)18:41
SumitNaiksatamtbachman: no my bad, didnt read your comment18:42
* tbachman is barely monolingual :)18:42
*** emagana has quit IRC18:42
SumitNaiksatamtbachman: lol18:42
SumitNaiksatamone more item on the agenda18:42
rkukuraMy point was that the DB objects (until expunged) stay associated with the session, so if they are shared across threads, they can cause the session to be shared across threads.18:42
SumitNaiksatamrkukura: but that is not a good usage pattern, right?18:43
rkukuraSumitNaiksatam: Correct18:43
rkukuraI’d also be somewhat concerned about continuing to use DB objects in the same thread after the transaction in which they were obtained is commited, and especially if a new transaction on the thread’s session gets started. Those old DB objects might become involved in the new transaction.18:44
SumitNaiksatamrkukura: agree, but i believe that pattern exists in several places in neutron code18:44
SumitNaiksatamso we cant change that18:45
tbachmanIt might be something we should emphasize for new code18:45
tbachman(in GBP of course)18:45
*** bpokorny has quit IRC18:45
SumitNaiksatamas for our NFP code, removing the expunge_all call somehow  is leading stale state being read within the threads, which was not earlier the case because (implicitly) the assumption for expunge was being made18:46
SumitNaiksatam*leading to18:46
rkukuraOr we just call expunge_all in the right places to dissassociate the DB objects from the sessions they came from ;)18:46
SumitNaiksatamrkukura: oh that can get really messy, i am sure you were indeed joking :-)18:47
SumitNaiksatamone more item on the agenda18:47
SumitNaiksatam#topic Configuring extension drivers from policy drivers18:47
*** openstack changes topic to "Configuring extension drivers from policy drivers (Meeting topic: networking_policy)"18:47
rkukuraSumitNaiksatam: Not really - I think it might explain why expunge_all seems to solve some problems, and maybe cause others18:47
SumitNaiksatamrkukura: yes, it might explain, but i dont think we want to solve that by calling expunge in a different place18:48
SumitNaiksatam#link https://review.openstack.org/#/c/407985/18:48
SumitNaiksatamin the above review you mentioned something to the effect of aggregating the driver extension i have proposed in the patch with another one18:49
SumitNaiksatamrkukura: this was ostensibly to avoid the need (and potential error) in specifying multiple driver extensions in the configraion18:50
rkukuraright18:50
rkukuraOr configuring extension meant for one driver with the other driver.18:51
SumitNaiksatami was thinking what if we allowed the policy driver to specify the driver extensions18:51
*** s3wong has joined #openstack-meeting-318:51
*** yamamoto has quit IRC18:52
SumitNaiksatamso if a particular policy driver always knows that it needs certaing driver extensions, it can internally specify that18:52
SumitNaiksatamthat would avoid the need for any additional extension driver configuration for that particular policy driver18:52
rkukuraSumitNaiksatam: That may be a reasonable idea, but I’m a bit worried about it not being consistent with the way EDs work in ML2.18:52
tbachmanFWIW, here’s the log of a failure in the NFP gatefor the last recheck on the expunge_all (search for “Traceback”): http://logs.openstack.org/72/399772/3/check/gate-group-based-policy-dsvm-nfp-ubuntu-xenial-nv/67fd5b7/logs/q-svc.txt.gz18:53
SumitNaiksatamtbachman: thanks18:53
SumitNaiksatamrkukura: but the GBP framework can diverge where relevant, right?18:54
rkukuraFirst question is whether we want users to be able to choose whether or not to enable these extensions. If so, we should make them individual EDs that are not automatically pulled in by the PD/MD.18:54
*** paul-carlton2 has quit IRC18:54
SumitNaiksatamrkukura: there are two aspects to this, one is how they are implemented, and second how they are configured18:54
SumitNaiksatamrkukura: if they are implemented as separate extensions/drivers, it leaves the possibility open for configuring them individually18:55
rkukuraI think it would be reasonable for a deployer to decide they want to use the aim_mapping PD, but only expose the standard GBP API. But I don’t know if the PD code will even work if the EDs are not enabled.18:55
SumitNaiksatamrkukura: specificall as for the AIM PD (and its reliance on the ml2+, etc) i think there is enough going on there that we should assume that it wont work without the EDs18:56
*** zz_dimtruck is now known as dimtruck18:57
SumitNaiksatamrkukura: so in such cases why not let the PD decide that it always needs certain EDs18:57
SumitNaiksatam* or at least certain EDs18:58
rkukuraBut then why package each (required) feature as a separate extension and ED? Wouldn’t it be a lot simpler to just have one extension and one ED for all of them?18:58
SumitNaiksatamrkukura:  so that some other PD could potentially consume them in a different combination18:58
rkukuraSumitNaiksatam: maybe that makes sense18:59
SumitNaiksatamokay we reached the hour18:59
SumitNaiksatamthanks all for your time18:59
SumitNaiksatambye!18:59
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Dec  8 19:00:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-12-08-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-12-08-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-12-08-18.00.log.html19:00
rkukurabye19:00
*** bpokorny has joined #openstack-meeting-319:00
tbachmanSumitNaiksatam: thanks!19:01
*** tbachman has left #openstack-meeting-319:01
*** huanxuan has joined #openstack-meeting-319:02
*** baoli has quit IRC19:05
*** baoli has joined #openstack-meeting-319:05
*** VW has quit IRC19:08
*** VW has joined #openstack-meeting-319:08
*** Sukhdev has joined #openstack-meeting-319:09
*** matjazp has joined #openstack-meeting-319:11
*** VW has quit IRC19:13
*** songole has quit IRC19:15
*** iyamahat has quit IRC19:15
*** yamahata has quit IRC19:16
*** huanxuan has quit IRC19:22
*** huanxuan has joined #openstack-meeting-319:24
*** bpokorny has quit IRC19:30
*** bpokorny has joined #openstack-meeting-319:31
*** VW has joined #openstack-meeting-319:32
*** piet has quit IRC19:32
*** emagana has joined #openstack-meeting-319:32
*** iyamahat has joined #openstack-meeting-319:34
*** lpetrut has quit IRC19:35
*** bpokorny has quit IRC19:35
*** VW has quit IRC19:36
*** krtaylor has quit IRC19:37
*** bpokorny has joined #openstack-meeting-319:40
*** SumitNaiksatam has quit IRC19:50
*** VW has joined #openstack-meeting-319:56
*** bpokorny has quit IRC19:58
*** bpokorny has joined #openstack-meeting-319:59
*** VW has quit IRC20:00
*** VW has joined #openstack-meeting-320:01
*** bpokorny has quit IRC20:03
*** huanxuan has quit IRC20:08
*** VW_ has joined #openstack-meeting-320:12
*** absubram has joined #openstack-meeting-320:16
*** VW has quit IRC20:16
*** VW_ has quit IRC20:17
*** haleyb_ has joined #openstack-meeting-320:17
*** emagana has quit IRC20:17
*** yamahata has joined #openstack-meeting-320:17
*** haleyb_ has quit IRC20:22
*** spzala has quit IRC20:22
*** SumitNaiksatam has joined #openstack-meeting-320:23
*** mickeys has quit IRC20:26
*** d0ugal has quit IRC20:29
*** d0ugal has joined #openstack-meeting-320:35
*** spzala has joined #openstack-meeting-320:36
*** kzaitsev_mb has quit IRC20:37
*** spzala has quit IRC20:39
*** lblanchard1 has quit IRC20:39
*** VW has joined #openstack-meeting-320:41
*** VW has quit IRC20:43
*** VW_ has joined #openstack-meeting-320:43
*** r1chardj0n3s has left #openstack-meeting-320:44
*** rstarmer has joined #openstack-meeting-320:48
*** emagana has joined #openstack-meeting-320:56
*** emagana has quit IRC20:56
*** mjturek has quit IRC20:56
*** sambetts is now known as sambetts|pto20:56
*** emagana has joined #openstack-meeting-320:56
*** bpokorny has joined #openstack-meeting-320:59
*** bpokorny has quit IRC21:04
*** mjturek has joined #openstack-meeting-321:18
*** haleyb_ has joined #openstack-meeting-321:18
*** haleyb_ has quit IRC21:23
*** mickeys has joined #openstack-meeting-321:27
*** rtheis has quit IRC21:28
*** mickeys has quit IRC21:32
*** mjturek has quit IRC21:39
*** sdake has quit IRC21:40
*** rstarmer has quit IRC21:40
*** revon has joined #openstack-meeting-321:43
*** bpokorny has joined #openstack-meeting-321:44
*** dimtruck is now known as zz_dimtruck21:44
*** emagana has quit IRC21:46
*** Sukhdev has quit IRC21:47
*** rkukura has left #openstack-meeting-321:51
*** zz_dimtruck is now known as dimtruck21:53
*** emagana has joined #openstack-meeting-321:55
*** emagana has quit IRC21:59
*** emagana has joined #openstack-meeting-322:02
*** emagana_ has joined #openstack-meeting-322:05
*** emagana_ has quit IRC22:06
*** emagana has quit IRC22:06
*** emagana has joined #openstack-meeting-322:06
*** sdake has joined #openstack-meeting-322:12
*** gouthamr has quit IRC22:15
*** haleyb_ has joined #openstack-meeting-322:19
*** SumitNaiksatam has quit IRC22:20
*** sdake_ has joined #openstack-meeting-322:23
*** haleyb_ has quit IRC22:24
*** alexismonville has quit IRC22:25
*** emagana has quit IRC22:25
*** lpetrut has joined #openstack-meeting-322:26
*** sdake has quit IRC22:26
*** emagana has joined #openstack-meeting-322:26
*** mickeys has joined #openstack-meeting-322:26
*** kzaitsev_mb has joined #openstack-meeting-322:29
*** emagana has quit IRC22:30
*** baoli has quit IRC22:36
*** srobert_ has joined #openstack-meeting-322:37
*** spzala has joined #openstack-meeting-322:39
*** srobert has quit IRC22:40
*** srobert_ has quit IRC22:41
*** spzala has quit IRC22:44
*** marios has quit IRC22:45
*** sdake_ has quit IRC22:59
*** galstrom is now known as galstrom_zzz23:04
*** david-lyle_ has joined #openstack-meeting-323:05
*** Sukhdev has joined #openstack-meeting-323:07
*** lpetrut has quit IRC23:07
*** rstarmer has joined #openstack-meeting-323:07
*** david-lyle has quit IRC23:07
*** bpokorny has quit IRC23:10
*** bpokorny has joined #openstack-meeting-323:11
*** spotz is now known as spotz_zzz23:11
*** bpokorny_ has joined #openstack-meeting-323:13
*** sdake has joined #openstack-meeting-323:14
*** bpokorny has quit IRC23:15
*** bpokorny_ has quit IRC23:16
*** sdake has quit IRC23:16
*** bpokorny has joined #openstack-meeting-323:16
*** bpokorny has quit IRC23:19
*** bpokorny has joined #openstack-meeting-323:19
*** absubram has quit IRC23:20
*** haleyb_ has joined #openstack-meeting-323:20
*** haleyb_ has quit IRC23:25
*** matjazp has quit IRC23:30
*** rstarmer has quit IRC23:30
*** singlethink has quit IRC23:33
*** kzaitsev_mb has quit IRC23:34
*** david-lyle_ is now known as david-lyle23:35
*** matjazp has joined #openstack-meeting-323:35
*** VW_ has quit IRC23:41
*** VW has joined #openstack-meeting-323:43
*** sdake has joined #openstack-meeting-323:48
*** rbak has quit IRC23:49
*** yamahata has quit IRC23:51
*** sdague has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!