Monday, 2016-11-14

*** cknight has quit IRC00:09
*** arnaud__ has joined #openstack-meeting-alt00:14
*** neilus has quit IRC00:19
*** neilus has joined #openstack-meeting-alt00:20
*** bana_k has quit IRC00:20
*** bana_k has joined #openstack-meeting-alt00:25
*** vijendar has joined #openstack-meeting-alt00:33
*** vijendar has quit IRC00:35
*** vijendar has joined #openstack-meeting-alt00:37
*** bana_k has quit IRC00:51
*** tonanhngo has joined #openstack-meeting-alt00:53
*** tonanhngo has quit IRC00:56
*** bobmel has quit IRC00:58
*** bobmel has joined #openstack-meeting-alt01:00
*** bobmel has quit IRC01:04
*** neiljerram has joined #openstack-meeting-alt01:05
*** EricGonczer_ has joined #openstack-meeting-alt01:07
*** tovin07_ has joined #openstack-meeting-alt01:11
*** vijendar has quit IRC01:16
*** markvoelker has joined #openstack-meeting-alt01:19
*** qwebirc4460 has joined #openstack-meeting-alt01:23
*** markvoelker has quit IRC01:23
*** vijendar_ has joined #openstack-meeting-alt01:26
*** xek has quit IRC01:27
*** tonanhngo has joined #openstack-meeting-alt01:27
*** EricGonczer_ has quit IRC01:29
*** tonanhngo has quit IRC01:30
*** zhurong has joined #openstack-meeting-alt01:30
*** qwebirc4460 has quit IRC01:31
*** fnaval_ has joined #openstack-meeting-alt01:33
*** gcb has joined #openstack-meeting-alt01:36
*** mickeys has joined #openstack-meeting-alt01:36
*** fnaval has quit IRC01:36
*** mickeys has quit IRC01:41
*** tonanhngo has joined #openstack-meeting-alt01:44
*** noslzzp has quit IRC01:44
*** noslzzp has joined #openstack-meeting-alt01:45
*** tonanhngo has quit IRC01:45
*** fnaval has joined #openstack-meeting-alt01:46
*** fnaval_ has quit IRC01:48
*** bobmel has joined #openstack-meeting-alt02:01
*** vijendar_ has quit IRC02:01
*** tonanhngo has joined #openstack-meeting-alt02:04
*** bobmel has quit IRC02:05
*** tonanhngo has quit IRC02:06
*** noslzzp has quit IRC02:11
*** vijendar_ has joined #openstack-meeting-alt02:12
*** tonanhngo has joined #openstack-meeting-alt02:24
*** tonanhngo has quit IRC02:26
*** TommyLikeHu has quit IRC02:36
*** TommyLikeHu has joined #openstack-meeting-alt02:36
*** dims has quit IRC02:43
*** tonanhngo has joined #openstack-meeting-alt02:54
*** tonanhngo has quit IRC02:55
*** vijendar_ has quit IRC02:55
*** vijendar_ has joined #openstack-meeting-alt03:05
*** tonanhngo has joined #openstack-meeting-alt03:13
*** tonanhngo has quit IRC03:15
*** markvoelker has joined #openstack-meeting-alt03:20
*** markvoelker has quit IRC03:24
*** yamamot__ has joined #openstack-meeting-alt03:26
*** tonanhngo has joined #openstack-meeting-alt03:34
*** tonanhngo has quit IRC03:36
*** neiljerram has quit IRC03:47
*** vijendar_ has quit IRC03:48
*** tonanhngo has joined #openstack-meeting-alt03:54
*** tonanhngo has quit IRC03:55
*** vijendar_ has joined #openstack-meeting-alt03:55
*** arnaud__ has quit IRC04:00
*** bobmel has joined #openstack-meeting-alt04:02
*** bobmel has quit IRC04:06
*** tonanhngo has joined #openstack-meeting-alt04:14
*** links has joined #openstack-meeting-alt04:15
*** tonanhngo has quit IRC04:15
*** zhurong has quit IRC04:37
*** vijendar_ has quit IRC04:38
*** tonanhngo has joined #openstack-meeting-alt04:43
*** tonanhngo has quit IRC04:46
*** vijendar_ has joined #openstack-meeting-alt04:47
*** janki has joined #openstack-meeting-alt04:49
*** bana_k has joined #openstack-meeting-alt04:59
*** pgadiya has joined #openstack-meeting-alt05:04
*** reedip has quit IRC05:12
*** markvoelker has joined #openstack-meeting-alt05:21
*** coolsvap has joined #openstack-meeting-alt05:23
*** markvoelker has quit IRC05:25
*** amotoki has joined #openstack-meeting-alt05:31
*** prateek has joined #openstack-meeting-alt05:31
*** zhurong has joined #openstack-meeting-alt05:33
*** EricGonczer_ has joined #openstack-meeting-alt05:34
*** EricGonczer_ has quit IRC05:38
*** vijendar_ has quit IRC05:39
*** reedip has joined #openstack-meeting-alt05:40
*** tonanhngo has joined #openstack-meeting-alt05:44
*** yamamot__ has quit IRC05:45
*** tonanhngo has quit IRC05:45
*** vijendar_ has joined #openstack-meeting-alt05:49
*** bana_k has quit IRC05:50
*** bobmel has joined #openstack-meeting-alt05:50
*** mickeys has joined #openstack-meeting-alt05:51
*** gongysh has joined #openstack-meeting-alt05:53
*** bobmel has quit IRC05:55
*** mickeys has quit IRC05:56
*** skramaja_ has quit IRC05:59
*** vijendar_ has quit IRC06:01
*** vijendar has joined #openstack-meeting-alt06:02
*** skramaja has joined #openstack-meeting-alt06:03
*** hyakuhei has quit IRC06:04
*** tonanhngo has joined #openstack-meeting-alt06:04
*** tonanhngo has quit IRC06:06
*** sridharg has joined #openstack-meeting-alt06:17
*** tonanhngo has joined #openstack-meeting-alt06:24
*** tonanhngo has quit IRC06:26
*** anilvenkata has joined #openstack-meeting-alt06:31
*** vijendar has quit IRC06:34
*** yamamot__ has joined #openstack-meeting-alt06:35
*** MarkBaker has joined #openstack-meeting-alt06:36
*** cartik has joined #openstack-meeting-alt06:38
*** dsariel has joined #openstack-meeting-alt06:38
*** vijendar_ has joined #openstack-meeting-alt06:43
*** tonanhngo has joined #openstack-meeting-alt06:44
*** tonanhngo has quit IRC06:44
*** belmoreira has joined #openstack-meeting-alt06:45
*** bobmel has joined #openstack-meeting-alt06:51
*** mjura has joined #openstack-meeting-alt06:54
*** bobmel has quit IRC06:58
*** yamamot__ has quit IRC07:08
*** yamamot__ has joined #openstack-meeting-alt07:11
*** bana_k has joined #openstack-meeting-alt07:11
*** vijendar_ has quit IRC07:18
*** jprovazn has joined #openstack-meeting-alt07:19
*** neilus has quit IRC07:25
*** neilus has joined #openstack-meeting-alt07:25
*** gongysh2 has quit IRC07:26
*** andreas_s has joined #openstack-meeting-alt07:26
*** neilus has quit IRC07:26
*** TommyLikeHu has quit IRC07:28
*** TommyLikeHu has joined #openstack-meeting-alt07:28
*** vijendar_ has joined #openstack-meeting-alt07:29
*** bana_k has quit IRC07:32
*** florianf has joined #openstack-meeting-alt07:33
*** yamamot__ has quit IRC07:36
*** mickeys has joined #openstack-meeting-alt07:37
*** gongysh2 has joined #openstack-meeting-alt07:37
*** fzdarsky has joined #openstack-meeting-alt07:39
*** mickeys has quit IRC07:42
*** korzen has joined #openstack-meeting-alt07:42
*** yamamot__ has joined #openstack-meeting-alt07:42
*** dtardivel has joined #openstack-meeting-alt07:42
*** korzen has quit IRC07:43
*** korzen has joined #openstack-meeting-alt07:43
*** tonanhngo has joined #openstack-meeting-alt07:44
*** dsariel has quit IRC07:44
*** tonanhngo has quit IRC07:45
*** pnavarro has joined #openstack-meeting-alt07:45
*** yamamot__ has quit IRC07:55
*** dsariel has joined #openstack-meeting-alt07:56
*** yamamot__ has joined #openstack-meeting-alt07:56
*** vijendar_ has quit IRC07:59
*** ccamacho has joined #openstack-meeting-alt08:01
*** neilus has joined #openstack-meeting-alt08:01
*** ralonsoh has joined #openstack-meeting-alt08:03
*** neilus has quit IRC08:06
*** rarcea has joined #openstack-meeting-alt08:08
*** vijendar_ has joined #openstack-meeting-alt08:09
*** dimtruck is now known as zz_dimtruck08:10
*** tellesnobrega has quit IRC08:13
*** bana_k has joined #openstack-meeting-alt08:14
*** dsariel has quit IRC08:14
*** matrohon has joined #openstack-meeting-alt08:17
*** arxcruz has joined #openstack-meeting-alt08:23
*** bfernando has joined #openstack-meeting-alt08:23
*** dsariel has joined #openstack-meeting-alt08:27
*** kaisers has quit IRC08:27
*** kaisers has joined #openstack-meeting-alt08:28
*** bana_k has quit IRC08:29
*** mickeys has joined #openstack-meeting-alt08:35
*** jpena|off is now known as jpena08:37
*** tremble has joined #openstack-meeting-alt08:40
*** mickeys has quit IRC08:40
*** d0ugal has joined #openstack-meeting-alt08:42
*** tonanhngo has joined #openstack-meeting-alt08:44
*** gcb has quit IRC08:46
*** tonanhngo has quit IRC08:46
*** cartik has quit IRC08:50
*** cknight has joined #openstack-meeting-alt08:51
*** cknight has quit IRC08:52
*** bobmel has joined #openstack-meeting-alt08:54
*** vijendar_ has quit IRC08:54
*** bobmel has quit IRC08:58
*** gcb has joined #openstack-meeting-alt08:59
*** cartik has joined #openstack-meeting-alt09:03
*** vijendar_ has joined #openstack-meeting-alt09:04
*** tonanhngo has joined #openstack-meeting-alt09:04
*** tonanhngo has quit IRC09:06
*** MarkBaker has quit IRC09:10
*** jtomasek has joined #openstack-meeting-alt09:12
*** tuanluong has joined #openstack-meeting-alt09:12
*** MarkBaker has joined #openstack-meeting-alt09:15
*** tonanhngo has joined #openstack-meeting-alt09:24
*** tonanhngo has quit IRC09:26
*** strigazi_AFK is now known as strigazi09:26
*** gongysh has quit IRC09:30
*** zhurong has quit IRC09:34
*** yamamot__ has quit IRC09:36
*** dizquierdo has joined #openstack-meeting-alt09:36
*** yamamoto has joined #openstack-meeting-alt09:36
*** yamamoto has quit IRC09:38
*** bogdando has quit IRC09:38
*** ccamacho is now known as ccamacho|afk09:39
*** vijendar_ has quit IRC09:42
*** MarkBaker has quit IRC09:42
*** tonanhngo has joined #openstack-meeting-alt09:43
*** tonanhngo has quit IRC09:44
*** dizquierdo has quit IRC09:46
*** gouthamr has joined #openstack-meeting-alt09:48
*** lpetrut has joined #openstack-meeting-alt09:50
*** vijendar has joined #openstack-meeting-alt09:51
*** iberezovskiy|off is now known as iberezovskiy09:53
*** neiljerram has joined #openstack-meeting-alt09:56
*** gouthamr has quit IRC09:58
*** derekh has joined #openstack-meeting-alt09:59
*** msimonin has joined #openstack-meeting-alt09:59
*** tovin07_ has quit IRC10:03
*** sambetts|afk is now known as sambetts10:03
*** tonanhngo has joined #openstack-meeting-alt10:05
*** aarefiev has joined #openstack-meeting-alt10:06
*** tonanhngo has quit IRC10:07
*** dizquierdo has joined #openstack-meeting-alt10:07
*** numans has joined #openstack-meeting-alt10:11
*** panda|Zz is now known as panda10:14
*** gouthamr has joined #openstack-meeting-alt10:18
*** aarefiev has quit IRC10:22
*** tonanhngo has joined #openstack-meeting-alt10:24
*** tonanhngo has quit IRC10:25
*** tuanluong has quit IRC10:26
*** gouthamr has quit IRC10:32
*** nkrinner_afk has quit IRC10:35
*** aarefiev has joined #openstack-meeting-alt10:37
*** vijendar has quit IRC10:39
*** tonanhngo has joined #openstack-meeting-alt10:44
*** liuyulong has joined #openstack-meeting-alt10:46
*** tonanhngo has quit IRC10:46
*** baoli has joined #openstack-meeting-alt10:46
*** nkrinner_afk has joined #openstack-meeting-alt10:47
*** vijendar_ has joined #openstack-meeting-alt10:48
*** gouthamr has joined #openstack-meeting-alt10:49
*** ccamacho|afk is now known as ccamacho10:49
*** baoli has quit IRC10:50
*** bogdando has joined #openstack-meeting-alt10:52
*** bobmel has joined #openstack-meeting-alt10:55
*** d0ugal has quit IRC10:56
*** bobmel has quit IRC10:59
*** panda is now known as panda|afk10:59
*** d0ugal has joined #openstack-meeting-alt11:04
*** ansmith has quit IRC11:27
*** yamamoto has joined #openstack-meeting-alt11:31
*** zhurong has joined #openstack-meeting-alt11:36
*** mickeys has joined #openstack-meeting-alt11:36
*** bfernando has quit IRC11:38
*** vijendar_ has quit IRC11:38
*** gongysh has joined #openstack-meeting-alt11:39
*** mickeys has quit IRC11:41
*** zhurong has quit IRC11:42
*** MarkBaker has joined #openstack-meeting-alt11:44
*** vijendar_ has joined #openstack-meeting-alt11:48
*** panda|afk is now known as panda11:53
*** tonanhngo has joined #openstack-meeting-alt11:55
*** tonanhngo has quit IRC11:57
*** kaisers has left #openstack-meeting-alt11:59
*** kaisers has joined #openstack-meeting-alt12:00
*** dave-mccowan has joined #openstack-meeting-alt12:01
*** julim has joined #openstack-meeting-alt12:05
*** tonanhngo has joined #openstack-meeting-alt12:13
*** egallen has quit IRC12:15
*** tonanhngo has quit IRC12:15
*** egallen has joined #openstack-meeting-alt12:15
*** yuanying_ has joined #openstack-meeting-alt12:15
*** zhurong has joined #openstack-meeting-alt12:16
*** zhurong has quit IRC12:19
*** gouthamr has quit IRC12:19
*** dprince has joined #openstack-meeting-alt12:21
*** zhurong has joined #openstack-meeting-alt12:21
*** gcb has quit IRC12:22
*** cartik has quit IRC12:24
*** neilus has joined #openstack-meeting-alt12:25
*** MarkBaker has quit IRC12:27
*** neilus has quit IRC12:29
*** tonanhngo has joined #openstack-meeting-alt12:34
*** tonanhngo has quit IRC12:35
*** EricGonczer_ has joined #openstack-meeting-alt12:38
*** thrash|g0ne is now known as thrash12:41
*** julim has quit IRC12:51
*** vijendar_ has quit IRC12:52
*** ayoung has quit IRC12:54
*** bobmel has joined #openstack-meeting-alt12:55
*** belmorei_ has joined #openstack-meeting-alt13:00
*** bobmel has quit IRC13:00
*** belmoreira has quit IRC13:01
*** vijendar_ has joined #openstack-meeting-alt13:02
*** pgadiya has quit IRC13:04
*** gouthamr has joined #openstack-meeting-alt13:10
*** ccamacho is now known as ccamacho|lunch13:11
*** jianghuaw has joined #openstack-meeting-alt13:12
*** jtomasek has quit IRC13:14
*** neiljerram has quit IRC13:15
*** neilus has joined #openstack-meeting-alt13:16
*** janki has quit IRC13:16
*** bfernando has joined #openstack-meeting-alt13:17
*** neilus has quit IRC13:19
*** _degorenko|afk is now known as degorenko13:19
*** janki has joined #openstack-meeting-alt13:21
*** neilus has joined #openstack-meeting-alt13:21
*** jprovazn has quit IRC13:23
*** haleyb_ has joined #openstack-meeting-alt13:24
*** ansmith has joined #openstack-meeting-alt13:25
*** figleaf is now known as edleafe13:29
*** gouthamr has quit IRC13:30
*** hoangcx has joined #openstack-meeting-alt13:30
*** neilus has joined #openstack-meeting-alt13:30
*** neilus has quit IRC13:35
*** dims has joined #openstack-meeting-alt13:35
*** yuanying_ has quit IRC13:41
*** baoli has joined #openstack-meeting-alt13:41
*** baoli has quit IRC13:42
*** markvoelker has joined #openstack-meeting-alt13:46
*** ccamacho|lunch is now known as ccamacho13:47
*** jpena is now known as jpena|lunch13:48
*** yuanying_ has joined #openstack-meeting-alt13:48
*** dsariel has quit IRC13:48
*** jcoufal has joined #openstack-meeting-alt13:48
*** gouthamr has joined #openstack-meeting-alt13:55
*** gongysh has quit IRC13:56
*** gouthamr has quit IRC13:57
*** cdent has joined #openstack-meeting-alt13:58
*** vijendar_ has quit IRC13:59
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Nov 14 14:00:15 2016 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
*** jprovazn has joined #openstack-meeting-alt14:00
edleafeHello! Who's here today?14:00
macsz\o14:00
*** fnaval has quit IRC14:01
macszwell, it seems the room is empty14:01
alex_xuo/14:01
* edleafe has room to stretch his legs14:01
*** moshele has joined #openstack-meeting-alt14:01
*** gcb has joined #openstack-meeting-alt14:01
edleafeLet's wait a little bit for the latecomers14:02
cdento/14:03
cdentthis is what happens when I show up early, forget to actually show up14:04
edleafeheh14:04
bauzasholy snap14:04
bauzas\o14:04
bauzasagain, I should departure in 20 mins14:04
edleafebauzas: ack14:04
bauzassadly14:05
edleafeAs usual, the agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaScheduler14:05
edleafe#topic Specs and Reviews14:05
*** openstack changes topic to "Specs and Reviews (Meeting topic: nova_scheduler)"14:05
edleafeI stole cdent's summary of outstanding things to review, and included in the agenda14:05
edleafeHas everyone had a chance to look those over?14:06
cdentedleafe: you can't steal what is given freely14:06
edleafeNote that today is a Spec Review day, so we should focus on getting the specs done first14:06
*** gouthamr has joined #openstack-meeting-alt14:06
*** gouthamr has quit IRC14:06
edleafecdent: I can and I did!14:06
cdentAnd I left one thing out: https://review.openstack.org/#/c/382640/14:06
*** xyang1 has joined #openstack-meeting-alt14:06
*** julim has joined #openstack-meeting-alt14:07
edleafe#link https://review.openstack.org/#/c/382640/14:07
*** gouthamr has joined #openstack-meeting-alt14:07
edleafeSo... we could go through them one by one, but that doesn't sound very efficient14:07
*** yamamoto has quit IRC14:08
edleafeInstead, does anyone have any issues or problems with any of those specs/reviews?14:08
cdentno sir14:08
johnthetubaguyquick questions on calling placement14:08
*** yamamoto has joined #openstack-meeting-alt14:08
*** zhurong has quit IRC14:08
johnthetubaguyI was thinking about the caching scheduler14:08
johnthetubaguyI assume we just leave that doing what it does today, probably14:09
johnthetubaguybasically it works because we get the full list of nodes from the DB14:09
bauzasjohnthetubaguy: well, given the placement API is still optional, my answer would be yes14:09
johnthetubaguyif we don't get the full list, it doesn't really have anything it can cache14:09
edleafejohnthetubaguy: I would think so, at least until we can get the placement API to perform better than the caching scheduler14:09
bauzasyeah that14:09
johnthetubaguyI think we probably need the claims before we can drop it14:10
cdentjohnthetubaguy: yeah, my recollection was we just wouldn't change the caching scheduler14:10
edleafeagreed14:10
bauzasyou can have operators not wanting to use the placement engine and keep the caching scheduler14:10
*** vijendar_ has joined #openstack-meeting-alt14:10
johnthetubaguyso the caching scheduler is a subclass of the filter scheduler14:10
johnthetubaguyis implementation wise, its not as easier as that14:10
johnthetubaguybut agreed with the direction there14:10
johnthetubaguyits just not noted in the spec14:10
bauzasjohnthetubaguy: that wouldn't change, the use-filters spec doesn't impact it14:10
johnthetubaguyso I am on the wrong spec...14:11
johnthetubaguysorry14:11
johnthetubaguyhttps://review.openstack.org/#/c/30017814:11
johnthetubaguymissread the UURL14:11
bauzasjohnhttps://review.openstack.org/#/c/300178/4 yeah14:11
* johnthetubaguy should get his post lunch coffee quickly14:11
* edleafe needs his morning coffee too14:12
bauzashttps://review.openstack.org/#/c/385618/1 is a prereq tho14:12
* cdent needs his post coffee coffee14:12
edleafeSo the point is that we have to allow for an override of the DB filtering for subclasses, right?14:12
* alex_xu just needs to go to bed14:12
bauzasedleafe: you mean, other resources ?14:13
bauzasedleafe: there are a lot of things in the HostState object that filters use, that are not provided by the current placement resource classes14:13
johnthetubaguyI think we could just do a "skip_resource_filters=True" or something14:13
edleafe14:14
bauzasfeel free to comment on the spec, I'll appreciate ideas for turning off the placement call if needed14:14
johnthetubaguyif we are clear on the behaviours, I think the code structure should drop out from that, I just want to see a note about the need to adress it really14:14
*** baoli has joined #openstack-meeting-alt14:14
johnthetubaguyyeah, adding comments right now14:14
bauzasedleafe: I agree14:14
edleafejohnthetubaguy: yes, but there will have to be something about not removing those filters14:14
edleafejohnthetubaguy: the spec talks about deprecating them14:14
cdentI think we're describing this backwards14:15
bauzasedleafe: http://starecat.com/content/wp-content/uploads/i-love-unicode-mug.jpg14:15
cdentthe use of the placement api to narrow available resources happens before any filters are every called, it is before entering the filtering loop14:15
bauzasedleafe: it's the operator's responsibility to have the flags being consistent14:15
cdentso for things like the caching scheduler we need to not do whatever is doing the narrowing, and just call the filtering loop as before14:15
cdents/every/ever/14:15
bauzasie. having the legacy filters being either turned on and placement off, or the legacy being turned off14:16
jaypipesedleafe: sorry for being late14:16
edleafecdent: agreed. But we should change the spec to remove the wording about deprecating the filters in that case14:16
cdentedleafe: yes14:16
*** EricGonczer_ has quit IRC14:16
edleafejaypipes: go sit in the corner!14:16
* jaypipes dons duncecap14:16
bauzasedleafe: it's all about *deprecating*, not removing14:16
jaypipesedleafe: so, a quick update from me...14:16
edleafebauzas: 'deprecating' means 'stop using this thing ASAP'14:17
jaypipesedleafe: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/inventory-allocations-ocata14:17
*** noslzzp has joined #openstack-meeting-alt14:17
jaypipesedleafe:  I rebased and fixed up a few things from that series ^14:17
bauzasedleafe: if you use the placement API, those legacy filters should be disabled ASAP, indeed14:18
jaypipesedleafe: would appreciate some reviews on that if possible. We should be able to close that out in a day or two unless someone has any major objections.14:18
edleafejaypipes: great. Will review that series14:18
bauzasjaypipes: spec review day14:18
jaypipesbauzas: ya, I know.14:18
jaypipesedleafe: cheers14:18
bauzasjaypipes: k., just wanted to make sure you being aware :)14:18
edleafebauzas: What I'm talking about is this sentence: "Legacy filters (CoreFilter, RAMFilter and DiskFilter) that have corresponding14:18
edleaferesource classes will be considered deprecated and will be removed in the next14:18
edleafecycle."14:18
bauzasedleafe: given my very short time left, can we postpone that discussion ?14:19
jaypipesedleafe: on another note, I will be pushing code that adds the Ironic custom resource class handling today.14:19
edleafebauzas: sure14:19
bauzasedleafe: just make a comment in the spec, and I'll engage with you14:19
*** tonytan4ever has joined #openstack-meeting-alt14:19
edleafebauzas: do you have a specific topic you'd like to discuss before you go?14:19
bauzasedleafe: nothing really14:19
edleafebauzas: ok cool14:19
jaypipesedleafe: do we have an etherpad with current highest priority specs to review?14:19
bauzasedleafe: well, I won't be able to join next week's meeting14:20
alex_xujaypipes: https://etherpad.openstack.org/p/nova-ocata-spec-review-sprint there is one from Matt14:20
edleafejaypipes: There is the pad that mriedem posted: https://etherpad.openstack.org/p/nova-ocata-spec-review-sprint14:20
bauzasjaypipes: cdent amended the priorities etherpad14:20
edleafealex_xu: damn! You're too fast for me! :)14:20
bauzasand that, yes14:20
alex_xuedleafe: :)14:21
cdentbauzas: that was quite a while ago, but yeah. I think the email that I sent, and thus the agenda (since edleafe is a self-confessed thief) is most up to date?14:21
bauzascdent: you mean the priorities etherpad ?14:22
edleafeI haven't cross-checked, but if any of our specs aren't on Matt's list, let's be sure to add them14:22
bauzascdent: if so, yes14:23
cdentthe next time I send that email (presumably friday, I can also update the priority etherpad if that's what people want)14:23
*** florianf has quit IRC14:23
cdentedleafe: custom resource classes and nested resource providers were not on matt's etherpad last I checked but I didn't add things because I thought I recalled matt saying he didn't want people to do that (but since then people have)14:24
edleafedidn't want people to add specs to the etherpad? Or just those specs?14:24
*** dsariel has joined #openstack-meeting-alt14:25
cdentdidn't want people to add things, but I'm probably misremembering, or conflating something with the wrong thing14:25
bauzasfolks, \o14:25
cdentbut given the bubble has burst we should add14:25
bauzastime is flying14:25
johnthetubaguyyou are right cdent, he said ask him for adds14:25
* bauzas runs errand14:25
* cdent is relieved, not yet totally brain dead14:25
edleafeOK, we ask for Matt's blessing on any specs we need reviewed14:26
*** ddmitriev has joined #openstack-meeting-alt14:26
edleafe#action edleafe to ask mriedem to add any placement specs to the review etherpad14:27
edleafeI'll take that one14:27
*** yuanying_ has quit IRC14:28
edleafeAnything else to discuss for specs/reviews?14:28
johnthetubaguydid we want to cover14:28
johnthetubaguyPOST vs GET?14:28
edleafeI'd rather cover tabs vs. spaces :)14:29
cdentjohnthetubaguy: we were going to do that on the spec and poc, I think14:29
johnthetubaguyOK, cool14:30
edleafeLet's move on14:30
edleafe#topic Open Discussion14:30
*** openstack changes topic to "Open Discussion (Meeting topic: nova_scheduler)"14:30
edleafeFirst up: Ocata Upgrade Plans14:30
edleafeWe aren't clear on just what steps operators will have to take as the placement API is rolled out14:31
cdentmatt r wrote some useful stuff about that in response to my email14:31
edleafecdent: yes, I saw that14:31
cdentand also in his (excellent) start on the docs14:32
edleafeSo I guess we need to officialize the upgrade steps14:32
edleafeSince bauzas isn't here, let's assign it to him!!14:32
edleafe(jk)14:32
edleafeSo should we build on Matt's response?14:33
*** tellesnobrega has joined #openstack-meeting-alt14:33
cdentseems like a reasonable plan14:34
edleafe#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107177.html14:34
edleafe^^ Matt's response14:34
*** gcb has quit IRC14:35
*** tonanhngo has joined #openstack-meeting-alt14:35
cdentthis has two +2 but no +W can somebody kick it in, unless there are objections: https://review.openstack.org/#/c/395971/14:36
*** tonanhngo has quit IRC14:36
*** ayoung has joined #openstack-meeting-alt14:37
johnthetubaguyhmm, I didn't +W, thats odd14:37
johnthetubaguyah, I was kinda waiting for dan to respond14:37
edleafejohnthetubaguy: so can you follow with dan about that?14:38
*** florianf has joined #openstack-meeting-alt14:38
johnthetubaguyyeah, its my bad for not adding that in my vote14:38
edleafejohnthetubaguy: thanks14:39
edleafeNext up: documentation14:39
*** dsariel has quit IRC14:39
*** isq has quit IRC14:39
edleafemriedem already gave us an excellent start: https://review.openstack.org/#/c/396761/14:39
*** neiljerram has joined #openstack-meeting-alt14:40
*** isq has joined #openstack-meeting-alt14:40
edleafeI see a TODO for api-ref. That can get started while we settle more bits in the API14:40
edleafeAny comments / suggestions?14:41
cdentone of the open questions on that is how to source some of the info for the api-ref, as I guess in compute-api the api-samples are used for that14:41
*** noslzzp has quit IRC14:41
cdentwe can probably figure out a way to use the gabbits but it may not be worth the effort: the api is pretty simple and hopefully will stay that way14:41
cdent(we should fight hard to keep it that way)14:41
*** noslzzp has joined #openstack-meeting-alt14:42
edleafealex_xu: any ideas of this? (If you're still awake :)14:42
edleafecdent: +1 on not mucking up the API14:42
alex_xuedleafe: agree with cdent, the api is pretty simple, so it is ok without some automatically14:42
*** haleyb__ has joined #openstack-meeting-alt14:43
edleafealex_xu: ok, good to know14:43
*** haley__ has joined #openstack-meeting-alt14:44
edleafeAnything else to discuss for Opens?14:44
alex_xuactually the api-ref of compute isn't generated from anything also. only the api sample files are generated from api sample tests. and add refer link to the api-ref14:44
*** haleyb has quit IRC14:44
*** haleyb_ has quit IRC14:44
*** fnaval has joined #openstack-meeting-alt14:46
*** vijendar_ has quit IRC14:46
*** vijendar_ has joined #openstack-meeting-alt14:47
edleafeLooks like we're done.14:47
edleafeThanks everyone!14:47
edleafe#endmeeting14:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:47
openstackMeeting ended Mon Nov 14 14:47:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-11-14-14.00.html14:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-11-14-14.00.txt14:47
cdentthanks edleafe14:47
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-11-14-14.00.log.html14:47
*** hurricanerix has left #openstack-meeting-alt14:49
*** cdent has left #openstack-meeting-alt14:49
*** moshele has left #openstack-meeting-alt14:50
*** kfarr has joined #openstack-meeting-alt14:51
*** dsariel has joined #openstack-meeting-alt14:52
*** jpena|lunch is now known as jpena14:53
*** matrohon has quit IRC14:56
*** bobmel has joined #openstack-meeting-alt14:56
*** electrocucaracha has joined #openstack-meeting-alt14:59
*** ihrachys has joined #openstack-meeting-alt15:00
ihrachys#startmeeting neutron_upgrades15:00
*** tonanhngo has joined #openstack-meeting-alt15:00
openstackMeeting started Mon Nov 14 15:00:34 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. 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_upgrades)"15:00
openstackThe meeting name has been set to 'neutron_upgrades'15:00
ihrachyshey folks15:00
electrocucarachahola15:00
dasanind_Hi15:00
korzenhello15:01
*** bobmel has quit IRC15:01
ihrachys#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam Agenda15:01
ndahiwadeHi15:01
ihrachys#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:02
asingh_Hello15:02
*** dsariel has quit IRC15:02
ihrachysO-1 is this week15:02
ihrachysalso, some folks are working on switching gate to all Xenial15:02
*** tonanhngo has quit IRC15:02
ihrachysfrom upgrades standpoint, the most interesting of the latter is the following: Newton/Ocata branches will run on Xenial15:03
sshankHello.15:03
ihrachysBUT: grenade jobs will still run on Trusty (for Newton)15:03
ihrachysthis is because grenade for Newton validates Mitaka -> Newton upgrade, and Mitaka is supposed to be Trusty15:03
*** haleyb_ has joined #openstack-meeting-alt15:03
sindhuHi15:03
ihrachysyou may notice some reshuffling of gate jobs in all branches in next days15:03
ihrachysactually, it already occurs :)15:03
ihrachysI don't have any more public announcements for you15:04
*** Leo_ has joined #openstack-meeting-alt15:04
ihrachys#topic Partial Multinode Grenade15:04
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:04
ihrachysok, that one, I actually looked at logs and made some progress (I hope)15:04
ihrachysfirst thing I noticed was that for some reason, we were starting OVS agent on the new side of grenade15:04
ihrachysI came up with a simple patch for that issue: https://review.openstack.org/#/c/396658/15:05
electrocucarachaihrachys: is it the reopened bug of the other day?15:05
ihrachyselectrocucaracha: I don't know what you refer to15:05
ihrachyselectrocucaracha: if you mean ryu one, no15:05
*** haleyb__ has quit IRC15:05
electrocucarachaihrachys: yeah, that one... ok15:06
ihrachyselectrocucaracha: but that's a good call, I will touch it later15:06
ihrachysso, with the patch above, I triggered experimental tests again at: https://review.openstack.org/#/c/396659/15:06
ihrachysand it's actually very promising15:06
ihrachysthe test results for the run: http://logs.openstack.org/59/396659/1/experimental/gate-grenade-dsvm-neutron-linuxbridge-multinode-nv/97289d8/logs/testr_results.html.gz15:06
*** vijendar_ has quit IRC15:07
ihrachysnote there is a single test that actually failed15:07
ihrachystest_schedule_to_all_nodes15:07
ihrachysI *suspect* there is some setup error where nova maybe tries to schedule an instance for a node that does not run a neutron l2 agent15:07
ihrachysmore investigation is needed though15:08
ihrachysjschwarz: will you have time this week to look at the failure in linuxbridge grenade multinode job?15:08
ihrachyswith that remaining failure fixed, I believe we will be able to fix the job and move it into check queue15:08
ihrachysactually, anyone interested may step in and try to fix the failure15:09
*** bobmel has joined #openstack-meeting-alt15:09
*** janki has quit IRC15:09
ihrachysok seems like no one is truly interested ;)15:10
ihrachysmoving on15:10
* electrocucaracha would like but he'll be bug deputy this week15:10
ihrachys#topic Object implementation15:10
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:10
ihrachys#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db15:10
ihrachyswe landed some patches the previous week15:11
ihrachysmost notably, dns integration: https://review.openstack.org/38133315:11
ihrachyssome preparations for adoption of objects in tree: https://review.openstack.org/357787 and https://review.openstack.org/363206 and https://review.openstack.org/39462715:11
ihrachysfinally, DuplicateEntry is now retriable on API/plugin level: https://review.openstack.org/37708415:12
ihrachysthanks the authors and reviewers15:12
electrocucarachaihrachys: there are several patches that depends on router and agent ovo, not sure if we can consider them for high priority?15:13
*** watanabe_isao has joined #openstack-meeting-alt15:13
ihrachyselectrocucaracha: yes. links?15:13
electrocucarachahttps://review.openstack.org/#/c/307964/ Router15:13
electrocucarachahttps://review.openstack.org/#/c/297887/ Agent15:13
*** bobmel has quit IRC15:13
*** links has quit IRC15:13
* ihrachys copied the links into his trello board and will give them priority15:14
*** edtubill has joined #openstack-meeting-alt15:14
korzenI have a question, about adoption and TODOs on port and network OVOs15:15
korzenI will take care of Network OVO adoption15:15
korzenanyone is interested in port?15:15
ihrachysI probably won't be able to give it a run this week15:16
ihrachysdo we have a WIP at least? or it's all new work?15:16
*** coolsvap has quit IRC15:17
*** tonanhngo has joined #openstack-meeting-alt15:17
korzenall new15:17
* electrocucaracha is reviewing https://docs.google.com/spreadsheets/d/1FeeQlQITsZSj_wpOXiLbS36dirb_arX0XEWBdFVPMB8/edit#gid=143417011215:17
*** dsariel has joined #openstack-meeting-alt15:17
ihrachysmy more humble plan for the next steps is to land all binding related objects15:17
*** watanabe_isao has quit IRC15:17
ihrachysbecause work that will involve them is in line for Ocata15:17
*** pradk has joined #openstack-meeting-alt15:18
*** tonanhngo has quit IRC15:18
ndahiwadeihrachys:korzen: https://review.openstack.org/#/c/382567/15:18
korzenihrachys, what do you mean by bondings?15:19
korzenbindings*15:19
ihrachyskorzen: port binding objects like the one specified by ndahiwade above. remember the design session where changes to bindings API were discussed? that will involve change in db schema.15:20
korzenok15:21
korzenthat one15:21
*** jtomasek has joined #openstack-meeting-alt15:21
korzenI have reviewed the spec and patches from andreas_s but I did not have time to contact with him15:22
ihrachysoh that's cool. you are a lot more rapid than me.15:22
ihrachysdo you see any issues with the approach proposed that could affect us?15:22
*** cleong has joined #openstack-meeting-alt15:23
*** tellesnobrega has quit IRC15:23
korzenit is not clear to be which way we should go15:23
*** prateek has quit IRC15:23
*** zz_dimtruck is now known as dimtruck15:23
korzenbecause we should use the distributed port binding instead of port regular binding?15:24
andreas_shi korzen, brianstajkowski and his team will take over the work on the portbinding item, so for future question, please take him into the loop15:24
ihrachysandreas_s: oh. are you pulled from neutron or just this specific thing?15:24
ihrachyskorzen: from our POV it should not matter as long as we are ready with objects and integration for both?15:25
andreas_sandreas_s, just this specific thing, but I'm getting more involved into other projects, so I very welcomed that :)15:26
korzenI mean that there is no sense to add new attributes for port binding, if we have distribted port binding fitting the job nearly perfectly15:26
ihrachyskorzen: oh you suggest that no new model will show up?15:27
korzenihrachys, that is my understanding15:27
ihrachyskorzen: we still probably need to support the flow where you have a legacy binding, then add a new host to it.15:27
korzenfomr DB and OVO15:27
korzenfrom db and ovo point of view15:27
ihrachysbut that may be just business logic messing with two types of objects I guess15:28
ihrachyswith no facade hiding transition15:28
*** dsariel has quit IRC15:28
ihrachysok let's move on15:29
ihrachys#topic Other patches on review15:29
*** openstack changes topic to "Other patches on review (Meeting topic: neutron_upgrades)"15:29
*** spotz_zzz is now known as spotz15:29
ihrachysnot a patch exactly, but probably relevant, something that electrocucaracha mentioned already15:30
ihrachysthere is a bug where agent restart fails15:30
ihrachysthat affects grenade jobs in gate15:30
ihrachysit's not specifically upgrade related15:30
ihrachysit fails to start the agent because the new instance of the agent fails to start Ryu controller15:30
ihrachysand this is because the old one is left running15:31
ihrachysthe bug is https://bugs.launchpad.net/neutron/+bug/161123715:31
openstackLaunchpad bug 1611237 in neutron "Restart neutron-openvswitch-agent get ERROR "Switch connection timeout"" [High,Confirmed]15:31
ihrachysturned out that's some bug in 'psmisc' package actually15:31
ihrachysthat is not going to be fixed in trusty15:31
ihrachysthat should be fixed for Newton+ with the Xenial switch, hopefully15:31
ihrachysas for Mitaka, well... the bug shows up only with of_interface = native that was CLI by default back then, so it's not hitting us in gate15:32
ihrachysso we are probably ok-ish15:32
sshankihrachys, korzen Can you please review patch: https://review.openstack.org/#/c/395748/ . It was introduced since it was asked to be introduced in patch: https://review.openstack.org/#/c/361303/20/neutron/db/provisioning_blocks.py@16915:32
*** numans has quit IRC15:33
*** sridharg has quit IRC15:33
ihrachyssshank: ack15:33
korzenyes I wanted to discuss it15:33
korzenmeaning the 'any_object' new method name15:33
*** anilvenkata has quit IRC15:33
korzenbut we can continue on gerrit15:34
sshankAs korzen mentioned, I find possible usages of this in 2 places. Here: https://review.openstack.org/#/c/381209/14/neutron/db/l3_hamode_db.py@762 and the above provisioning block patch.15:34
*** tonanhngo has joined #openstack-meeting-alt15:34
*** kfarr has quit IRC15:34
ihrachyswhy isn't count() enough?15:34
*** spotz is now known as spotz_zzz15:34
*** tonanhngo has quit IRC15:34
*** gcb has joined #openstack-meeting-alt15:35
*** spotz_zzz is now known as spotz15:36
ihrachysok nevermind, let's discuss on gerrit15:36
sshankihrachys, Ok. Thanks.15:36
ihrachysI don't know of any more patches requiring particular attention.15:36
dasanind_ihrachys: korzen: need some reviews for the OVO patches :)(https://review.openstack.org/#/c/356660/, https://review.openstack.org/#/c/362508/, https://review.openstack.org/#/c/360908/)15:36
ihrachysof course you we do need, yes!15:36
ihrachys*you we -> we15:36
dasanind_thank you :)15:37
korzenI have lost the count of how many reviews are in queue15:37
korzen;)15:37
ihrachyshaha15:37
ihrachysit scares me too15:37
korzenso yes, please ping me if you have something urgent15:37
korzenI have 800+ messages in my review mailbox15:38
*** jmckind has joined #openstack-meeting-alt15:38
ihrachysright, I find it beneficial if people ping me on irc from time to time with things they believe are ready15:38
*** matrohon has joined #openstack-meeting-alt15:38
ihrachysof course I already have enough for a next day15:38
ihrachysbut you can pull me into more later in the week :)15:38
ihrachys#topic Open discussion15:38
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:38
dasanind_:)15:39
ndahiwadeihrachys: korzen: Can you guys take a look at this error:http://paste.openstack.org/show/589137/?15:39
electrocucarachawell, regarding Allocation and  Endpoint objects I consoled them in a single patch https://review.openstack.org/#/c/396327/15:39
ndahiwadeIn this patch:https://review.openstack.org/#/c/382567/15:39
ndahiwadeIt persists after vif_details was changed in PortBinding and DistributedPortBinding Objects15:41
electrocucarachandahiwade: that sounds familiar to me, maybe it's the way the it's parsing the vif_details property15:41
*** dsariel has joined #openstack-meeting-alt15:41
korzenndahiwade, it looks like in OVO there is dict but code is passing string15:41
ndahiwadekorzen:electrocucaracha: ack,not sure how to solve this one15:42
ihrachysright. we should find where it hits the object (it's in stack trace) and see if we need to convert json into a dict at that point15:42
ndahiwadeDebugging leads me to PortBinding OVO integration15:43
korzenmaybe adoption code should pass dict, and before OVO core code was using the JSON in string15:43
korzenndahiwade, I will take a look tomorrow15:43
ndahiwadekorzen:Thanks:)15:43
ihrachysyeap. I think we should convert somewhere in line 507 of plugin.py15:44
korzenanyone is interested in docs: https://review.openstack.org/#/c/336518/15:45
ihrachysooooh right15:45
ihrachysI completely forgot about it15:45
* ihrachys adds another link into his todo list15:45
korzenI will need to update it a bit but please review until it will be obsolete15:45
korzenagain15:45
korzen:)15:46
ihrachys:)15:46
sshankihrachys, korzen, Patch: https://review.openstack.org/#/c/382037/ is related to port binding levels. Can you please review it?15:46
ihrachysyou don't sound too optimistic15:46
ihrachysI should prove you wrong!!15:46
ihrachysok, do we have any specific team wide topic to run, or we call it a day?15:46
electrocucaracharegarding the patch that I mentioned before(https://review.openstack.org/#/c/396327/), I created to make easier the integration15:46
ihrachysack15:47
ihrachysok, let's end the meeting then15:47
sshankkorzen, Any idea how to go about the standard attribute OVO?15:47
* ihrachys holds back15:47
korzensshank, not yet15:48
*** john-davidge has joined #openstack-meeting-alt15:48
korzenI guess that we can try some private OVO using the db_obj stored15:48
korzenin every object15:48
korzenbut it can be specific for only Port15:49
korzenor maybe not standard-attr ovo but only property15:49
*** Sukhdev has joined #openstack-meeting-alt15:49
korzenthat would be easier15:49
*** jmckind_ has joined #openstack-meeting-alt15:49
korzenif we care only on standard-attr-id15:49
*** tellesnobrega has joined #openstack-meeting-alt15:49
korzens/on/about15:50
sshankkorzen, yes only the ID is necessary.15:50
*** kgiusti has joined #openstack-meeting-alt15:50
*** jmckind has quit IRC15:50
*** lpetrut has quit IRC15:50
korzenso it can be added as property returning self.db_obj.standard_attr_id15:50
ihrachysyeap.15:51
korzenif we are going to use property, it can be added to every object15:51
ihrachysor just make it base but exposed only for objects with stdattr.15:51
korzenyes15:51
korzenthat is what I meant15:52
*** hoangcx has quit IRC15:52
ihrachysif anyone wants to send such a patch, I am happy to jump there with reviews.15:53
*** bobmel has joined #openstack-meeting-alt15:53
ihrachysok thanks for joining, again15:53
ihrachysand keep up15:53
ihrachys#endmeeting15:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:53
openstackMeeting ended Mon Nov 14 15:53:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-11-14-15.00.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-11-14-15.00.txt15:53
korzenthanks, bye15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-11-14-15.00.log.html15:53
sshankThank you.15:53
ndahiwadeThanks15:53
*** electrocucaracha has left #openstack-meeting-alt15:53
dasanind_Thank you15:53
asingh_thank you15:53
sindhuthanks :)15:53
*** tonanhngo has joined #openstack-meeting-alt15:54
*** rpodolyaka is now known as rpodolyaka_afk15:55
*** tonanhngo has quit IRC15:55
*** dgonzalez is now known as dgonzalez__15:55
*** dgonzalez__ is now known as dgonzalez15:55
*** john-davidge has quit IRC15:56
*** jaugustine has joined #openstack-meeting-alt15:57
*** yamahata has quit IRC15:57
*** tonytan4ever has quit IRC15:58
*** yamahata has joined #openstack-meeting-alt15:58
*** tonytan4ever has joined #openstack-meeting-alt15:58
*** sankarshan_away is now known as sankarshan15:59
*** rloo has joined #openstack-meeting-alt16:00
*** neilus has joined #openstack-meeting-alt16:00
amrith...16:01
amrithanyone here for oslo meeting?16:01
kgiustio/16:01
johnsomo/16:01
amritho/16:01
gcbo/16:01
rlooo/16:01
HenryGo/16:01
amrith#startmeeting openstack-oslo16:02
openstackMeeting started Mon Nov 14 16:02:09 2016 UTC and is due to finish in 60 minutes.  The chair is amrith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: openstack-oslo)"16:02
openstackThe meeting name has been set to 'openstack_oslo'16:02
*** korzen has quit IRC16:02
amrith#chair harlowja16:02
openstackCurrent chairs: amrith harlowja16:02
amrithharlowja, ping16:02
amrithyou have a meeting -2 minutes from now ...16:02
amrithwho'd like to run the meeting (since harlowja appears to be currently not around)16:03
ansmitho/16:03
amrithlet's give harlowja 1 minute then we can get started16:04
*** haleyb_ has quit IRC16:04
amrithcourtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims16:05
amrithcourtesy ping for dougwig, e0ne, flaper87, garyk, gcb, GheRivero, haypo16:05
amrithcourtesy ping for HenryG, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz16:05
amrithcourtesy ping for lifeless, lintan, lxsli, Nakato, ozamiatin, rbradfor, redrobot16:05
amrithcourtesy ping for rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar16:05
*** neilus has quit IRC16:05
amrithcourtesy ping for therve, thinrichs, toabctl, viktors, zhiyan, zzzeek16:05
stevemaro/16:05
stevemaramrith: hola16:05
stevemaramrith: you're running the meeting now :O16:05
amrithhi stevemar I'd wanted to discuss something today and no one else started the meeting :)16:05
amrithstill waiting for our fearless leader16:05
amrithBut since he's not here and it is five minutes past the top of the hour16:06
amrith#topic Red flags for/from liaisons16:06
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: openstack-oslo)"16:06
johnsom Nothing to report in LBaaS land16:06
amrithi have nothing from trove16:06
*** jaugustine has quit IRC16:07
rloonothing from ironicland16:07
gcboslo.db master breaks nova unit test , Fixing in https://review.openstack.org/397144 ,so need skip oslo.db release this week16:07
*** jaugustine has joined #openstack-meeting-alt16:07
*** tonanhngo has joined #openstack-meeting-alt16:07
amrith#info (from gcb) oslo.db master breaks nova unit test , Fixing in https://review.openstack.org/397144 ,so need skip oslo.db release this week16:08
*** haleyb_ has joined #openstack-meeting-alt16:08
amrithany others ... also still looking for an alternate chair; any oslo cores wishing to drive, please let me know.16:08
amrithAny other red flags from liaisons?16:09
*** mjura has quit IRC16:09
gcbamrith, I can help go through the agenda16:09
amrith#chair gcb16:10
openstackCurrent chairs: amrith gcb harlowja16:10
amrithgcb has the con16:10
amrithgo ahead gcb16:10
amrith#agenda https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_Template16:10
gcb#topic Releases for Ocata16:11
*** openstack changes topic to "Releases for Ocata (Meeting topic: openstack-oslo)"16:11
gcbDoes anyone need oslo.* release this week ?16:11
*** corey_ has joined #openstack-meeting-alt16:11
*** belmorei_ has quit IRC16:11
*** edtubill has quit IRC16:12
gcbok, I will talk with harlowja to check if we need release something this week16:12
*** reedip_outofmemo has joined #openstack-meeting-alt16:12
gcb#topic Ocata specs16:13
*** openstack changes topic to "Ocata specs (Meeting topic: openstack-oslo)"16:13
*** belmoreira has joined #openstack-meeting-alt16:13
gcbhttps://review.openstack.org/#/q/status:open+project:openstack/oslo-specs,n,z16:13
*** edtubill has joined #openstack-meeting-alt16:13
*** cleong has quit IRC16:13
gcbIs there any spec or commit which needs review ?16:14
gcb#topic Open discussion16:15
*** openstack changes topic to "Open discussion (Meeting topic: openstack-oslo)"16:16
amrithI have one ...16:16
amrith#link https://review.openstack.org/#/c/394667/16:16
gcbamrith , it's your turn16:16
amriththx gcb16:16
amrithso we discussed having a more intrusive way of doing message checksum in the meeting last week16:16
amrithand the consensus was that the oslo team did not want to implement message checksum for the use-case that I have and instead suggested that I use a decorator on *ALL* API methods16:17
amrithand pass a signature down as a formal parameter to the RPC call.16:17
amriththis is very disruptive to the code in the consuming project (like trove)16:17
amrithand so I was hoping I could minimize the disruption by wrapping the dispatcher as proposed in https://review.openstack.org/#/c/394667/16:18
amrithsileht observes that the dispatcher is not in __all__ and while it has no _ in the name it is still considered private16:18
amrithwrapping the dispatcher in this way is very beneficial to trove as we can localize the change for signing messages into two places.16:18
*** cknight has joined #openstack-meeting-alt16:18
amrithone on the caller side, where we can wrap cast() or call() and one on the server side where we wrap the dispatcher.16:19
amriththe dispatcher wrapper as shown in this change will verify the signature and pop the signature argument16:19
amriththerefore requiring no further code on the server side16:19
*** m-greene has quit IRC16:19
*** tremble has quit IRC16:19
amrithsileht ^^16:20
gcbamrith ,  method with prefix '_'  will not be allowed in the future . Do you want kgiusti and silent's more input here ?16:21
amrithyes please16:21
amrithwould like a decision one way or the other16:21
amrithI'd of course prefer that the decision be to allow this kind of wrapping16:21
amrithas it would make o.m.rpc easier to use16:21
*** alij has joined #openstack-meeting-alt16:21
amrithespecially because the project (oslo) has not shown an interest in taking on the bigger project of implementing message signing.16:22
gcbkgiusti ^^16:22
kgiustiSo what's the argument against making dispatcher public?  Or at least some small base class of dispatcher with the methods exposed?16:23
*** cknight1 has joined #openstack-meeting-alt16:23
amrithkgiusti, other than what sileht said in the comments on the review, I have heard of none16:23
amrithOn Nov 8, 1:38pm he wrote "What if this object is modified outside ? I don't think we want to support that."16:24
amrithto be clear, I don't agree with the point of view; just relaying it since he isn't here.16:24
*** absubram has joined #openstack-meeting-alt16:24
*** neilus has joined #openstack-meeting-alt16:24
silehto/16:24
amrithhi sileht16:24
gcbthe code about disallowing private method in oslo.messaging,  https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/dispatcher.py#L10316:25
silehtthis is not the first time people want to have a custom Dispatcher16:25
*** bfernando has quit IRC16:25
*** cknight has quit IRC16:25
silehtI'm not against making it private, but that need some works because we can't expose it as-is16:25
gcbamrith , you still can pass LegacyRPCAccessPolicy to make private method exposed16:26
amrithIn question (for Trove) is the issue that if this dispatcher wrapping is not allowed, I have to decorate over 100 individual API calls and will have to deal with version mismatches in a more painful way than if I could abstract it into oslo.16:26
amrithsorry gcb I don't think that's the same thing.16:26
silehtBecause the 'incoming' parameter of the method dispatch is a 'driver' object and must not be exposed outside16:26
amrithsileht, how do we do that additional work to make this expose'able.16:26
silehtI have no idea, I just don't want to expose it until driver stuff are correclty hidden16:27
amrithcould we then provide a callback that would only get the arguments and allow the callback to manipulate those?16:27
kgiustican IncomingMessage present both context and message in it's original form as published by the user?16:27
amriththe arguments (and context) are not driver stuff ...16:27
amrithso could we agree to register a callback that would receive args and context which it can modify and the RPC dispatcher would then dispatch with those modified parameters and context16:28
*** haley__ is now known as haley16:28
amrithand if no callback is provided, proceed as currently16:28
amrithi.e no change16:28
kgiustiHave a minimal public incomingmessage, internally wrap it per driver impl?16:28
silehtkgiusti, that the idea a object with only ctxt/message without driver method16:29
kgiustisileht: gotcha - encoding the meth+args in internal16:29
kgiustiis internal I mean16:29
silehtbut again this allows to sign only a subset of what will be passed to rabbit...16:30
*** haleyb_ has quit IRC16:31
amrithbut since oslo isn't doing the signing (the client is) what is oslo's issue with what actually is signed?16:31
silehtthe message have also a serialisation format, a version...16:31
amrithif oslo wants to stipulate what is signed, fine. let oslo do the signing and verification16:31
silehtalso only the call will be signed not the answer ...16:31
amrithbut barring that, the client is the one doing the signing (not oslo) and so whatever the client can do is all that it can do.16:32
*** haley is now known as haleyb16:33
*** rarcea has quit IRC16:33
*** belmoreira has quit IRC16:33
*** jmckind_ has quit IRC16:33
*** jmckind has joined #openstack-meeting-alt16:34
silehtso currently we are here: the client sign a partial msg, the server check the sig on part of the message, send a unsigned reply, the client accept it16:34
silehtthis is not want I call security ...16:34
kgiustican the serializer/deserializer play a role here?16:34
*** rossella_s has joined #openstack-meeting-alt16:34
*** gcb has quit IRC16:34
amrithsileht, let me see if I can restate this. oslo doesn't want to implement signing in the library (o.m.rpc) but wants to question the level of signing that the client can implement with the limited resources at the clients disposal?16:35
amrithkgiusti, yes it can but that would be implementing signing and verification in the library.16:35
amrithwhich it seemed like no one wanted to sign up for in the two times that it has come up so far.16:35
*** SotK has joined #openstack-meeting-alt16:35
kgiustinot if the application provides serialization/deserialization16:36
amrithyet, no one seems to object if the client uses a decorator to verify signatures.16:36
*** neilus has quit IRC16:36
amrithkgiusti, the serialization and deserialization are (if I recall correctly) per argument and for the context at this point.16:36
kgiustiunfortunately that wouldn't protect the protocol headers added by the driver16:36
amrithnot for the whole lot in a single call.16:36
amriththerefore computing signatures in the serialization/deserialization layer may be problematic.16:37
silehtwe have two layer of serialization, the one we expose to the API to get serializable object16:37
silehtand the one driver use to send the msg to the network (json/msgpack/...)16:37
*** pnavarro has quit IRC16:39
*** amotoki has quit IRC16:39
*** yuanying_ has joined #openstack-meeting-alt16:39
*** beekneemech is now known as bnemec16:40
amrithso where do we go from here?16:40
silehtI don't known, I'm open to proposal, I will just take care that we do not expose internal stuffs16:41
amrithwell, I've made two proposals and so far I've been told 'not that one, not that one'16:41
silehtI don't want to question the level of signing, I just raise 'warning' about this falsy secure thing16:41
amrithwell, yes, I know that. but the proposal to do the signing in oslo was not acceptable (see last weeks meeting).16:42
silehtI known I see your effort to find a solution16:42
silehtI haven't enouth time to thing about his unfortunatly16:42
kgiustime either, sadly....16:43
kgiustiDid anyone ever write a formal spec on adding message signing in o.m.?16:43
*** lpetrut has joined #openstack-meeting-alt16:43
amritha couple of years ago, yes. markmc16:44
*** yuanying_ has quit IRC16:44
kgiustiI'd like to take a look at that - understand the reasons it was rejected.16:44
silehtsigning was implemented as experimental before oslo.messaging exists and dropped during the creation of the new lib16:45
silehtand infortunatly nobody I have reintroduce this16:45
amriththe implementation there was RPC message signing per the RFC16:45
*** weshay is now known as weshay_brb16:46
silehtthe old/previous oslo-rpc layer was offer hook to sign messages16:46
amrithso what's the collective wisdom of the group? y'all have no time, I have the time and inclination to do this but I'd need some direction because clearly I can't come up with something that meets your approval.16:47
*** rloo has quit IRC16:47
silehtand the project 'kite' was implementing this hooks (this project was abandoned, end of the story)16:47
kgiustiI'd still be in favor of having the actual signing and verification happen "outside" the library.... somehow.16:49
*** rloo has joined #openstack-meeting-alt16:49
*** EricGonczer_ has joined #openstack-meeting-alt16:50
kgiustimanaging the security creds and such - is that something the library proper should do?16:50
silehtme too, I think the best way is to refactor the dispather and expose a hook that take only the ctxt, method, args16:50
kgiustisileht: +1 agreed16:50
amrithguys, I proposed that last week and I was told no.16:50
amrithI guess I'll wait for y'all to come up with a proposal of how to do this and I'm happy to implement it.16:51
amrithif you want.16:51
silehtamrith, no for the current implementation, not for the idea itself16:51
*** alij has quit IRC16:51
kgiustiI think the argument against was that only the app data would be verified, other fields could be hijacked.16:52
amrithwell sileht that wasn't what was said last week. it was go away and implement it as a decorator like your sample showed. but no matter, if you are open to having the library do it with callbacks or hooks, let me know how you'd like it done and I'll write it16:52
silehtkgiusti, yeah but if the app what to do not secure sign with this hook, do we care ?16:52
amrithkgiusti, verifying other fields would mean exposing internals; you decide what you want :)16:52
*** m-greene has joined #openstack-meeting-alt16:52
silehtamrith, this why using oslo.messaging for a secure thing sucks and you should not16:53
silehtusing it for this16:53
silehtamrith, and we have recommanded to use REST API last week too16:54
amrithgreat, that's the other answer I got. don't use o.m and you won't have this problem. easy for you to say, that was decided 4 years ago by some other people who converted from RPC to oslo.messaging.16:54
silehtbut that a much bigger change16:54
amrithso yes, the answer I've been getting is consistently that the problem is something trove is doing, so go do it some other way.16:54
amrithfine, I'll do that.16:54
*** alij has joined #openstack-meeting-alt16:55
amrithI have my answer. thanks sileht16:55
*** gouthamr has quit IRC16:55
*** sankarshan is now known as sankarshan_away16:55
amrithI'm done with this issue, does anyone else have something for open discussion?16:55
amrithif not, maybe we can end the meeting early16:55
*** sankarshan_away is now known as sankarshan16:56
*** gouthamr has joined #openstack-meeting-alt16:56
amrithgcb said he'd have to step away as it is close to midnight his time.16:56
amrithif there's nothing else for this meeting, I propose we end ...16:56
amrithgoing once16:57
amrithgoing twice16:58
*** HeOS has quit IRC16:58
amriththanks all16:58
amrith#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Mon Nov 14 16:58:29 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_oslo/2016/openstack_oslo.2016-11-14-16.02.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_oslo/2016/openstack_oslo.2016-11-14-16.02.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_oslo/2016/openstack_oslo.2016-11-14-16.02.log.html16:58
*** andreas_s has quit IRC16:59
*** alij has quit IRC17:00
*** rloo has left #openstack-meeting-alt17:00
*** gouthamr has quit IRC17:02
*** ayoung has quit IRC17:02
*** lin_yang has joined #openstack-meeting-alt17:02
*** matrohon has quit IRC17:03
*** Sukhdev has quit IRC17:04
*** gouthamr has joined #openstack-meeting-alt17:05
*** sankarshan is now known as sankarshan_away17:12
*** m-greene has left #openstack-meeting-alt17:14
*** ayoung has joined #openstack-meeting-alt17:17
*** panda is now known as panda|bbl17:18
*** dimtruck is now known as zz_dimtruck17:19
*** dizquierdo has quit IRC17:20
*** jmckind_ has joined #openstack-meeting-alt17:21
*** szaher has quit IRC17:21
*** jmckind has quit IRC17:22
*** lpetrut has quit IRC17:23
*** rossella_s has quit IRC17:24
*** xek has joined #openstack-meeting-alt17:25
*** alij has joined #openstack-meeting-alt17:25
*** msimonin has quit IRC17:26
*** bana_k has joined #openstack-meeting-alt17:27
*** knangia has joined #openstack-meeting-alt17:28
*** zz_dimtruck is now known as dimtruck17:28
*** weshay_brb is now known as weshay17:29
*** ihrachys has quit IRC17:30
*** alij has quit IRC17:30
*** dsariel has quit IRC17:30
*** enriquetaso has joined #openstack-meeting-alt17:30
*** m-greene_ has joined #openstack-meeting-alt17:32
*** m-greene_ is now known as m-greene17:33
*** iberezovskiy is now known as iberezovskiy|off17:33
*** m-greene has quit IRC17:34
*** lpetrut has joined #openstack-meeting-alt17:38
*** bfernando has joined #openstack-meeting-alt17:39
*** alij has joined #openstack-meeting-alt17:42
*** gouthamr has quit IRC17:42
*** alij has quit IRC17:46
*** vijendar has joined #openstack-meeting-alt17:47
*** armax has joined #openstack-meeting-alt17:49
*** jmckind_ has quit IRC17:49
*** yamahata has quit IRC17:50
*** cknight1 has quit IRC17:50
*** liuyulong has quit IRC17:52
*** liuyulong has joined #openstack-meeting-alt17:52
*** tnarg has joined #openstack-meeting-alt17:54
*** ayoung has quit IRC17:55
*** mbirru has joined #openstack-meeting-alt17:57
*** jmckind has joined #openstack-meeting-alt17:58
*** mariannelm has joined #openstack-meeting-alt18:00
*** julen has joined #openstack-meeting-alt18:00
*** derekh has quit IRC18:01
*** sambetts is now known as sambetts|afk18:01
*** mariannelm has quit IRC18:01
*** mariannelm has joined #openstack-meeting-alt18:01
*** mariannelm has quit IRC18:01
*** mariannelm has joined #openstack-meeting-alt18:02
*** reedip_outofmemo has quit IRC18:02
*** ralonsoh has quit IRC18:02
*** mariannelm has quit IRC18:03
*** mariannelm has joined #openstack-meeting-alt18:03
*** reedip_outofmemo has joined #openstack-meeting-alt18:04
*** lpetrut has quit IRC18:06
*** haleyb_ has joined #openstack-meeting-alt18:07
*** ayoung has joined #openstack-meeting-alt18:08
*** msimonin has joined #openstack-meeting-alt18:09
*** mickeys has joined #openstack-meeting-alt18:10
julenofficial or unofficial meeting?18:16
*** rluethi has joined #openstack-meeting-alt18:16
julenofficial or unofficial meeting?18:17
rluethijulen: unofficial, we're not allowed to have that many official meetings anymore :)18:17
julenpranav just wrote saying that he can't make it18:17
julenok18:17
rluethiso, regarding testing:18:18
julenso, first of all: congratulations!! that python port is impressive!18:18
rluethiI have a simple initial testing patch on top of the python port.18:18
rluethithanks :)18:18
julenis it somewhere in the folder?18:19
rluethiI don't know what's the best way to go forward: tox, nosetests, ...18:19
rluethino, I removed it from the patch and put it into a separate patch.18:19
rluethireason 1: pranav wanted to do the testing part.18:19
*** s3wong has joined #openstack-meeting-alt18:20
rluethireason 2: my testing code is just a proof of concept, it's not working well enough.18:20
rluethibut it could serve as a starting point for you.18:20
julenend functionality testing or just about the code?18:20
rluethimaybe :)18:20
julensure18:20
*** rossella_s has joined #openstack-meeting-alt18:21
rluethiI was more concerned about infrastructure: where do we put tests, how do we call and automate them etc.18:21
rluethiit could be any kind of tests.18:21
julenrluethi: no problemo18:22
rluethitox didn't work for me, nosetest and py.test did.18:22
julenmy stuff should be arriving in a few days, and then I should just build something18:22
rluethinot sure why. like I said, I never got it finished.18:22
julenhmm.. is that tox something like pep?18:22
rluethitox is an automation tool that we already use for some things.18:23
rluethicheck out the tox.ini file in the repo.18:23
julenaha...18:23
*** jpena is now known as jpena|off18:23
julenwell, let me get the stuff up and running and there won't be infrastructure problems anymore ;)18:24
*** cartik has joined #openstack-meeting-alt18:24
rluethi:)18:24
rluethiwrt to the python port: I tested some scenarios (virtualbox, kvm, pxe etc.), but I am sure I did not test all combinations.18:25
*** anilvenkata has joined #openstack-meeting-alt18:25
rluethialso, PXE booting with KVM does not work on my ancient Debian system, the code needs a later version of libvirt.18:26
julenwell... I just tested the basic cluster on VB18:26
rluethithe most simple smoketest :).18:26
julenuff.. testing all those functionalities on different platforms takes for ever!18:26
*** DavidPurcell has joined #openstack-meeting-alt18:27
rluethione reason for test automation. have it done on the openstack CI infrastructure.18:27
julenwell... as I mentioned in the e-mail, I guess 90% of training-labs users are interested on just the cluster option... don't you think so?18:27
rluethiyou mean what you said about skipping the snapshots?18:28
julenyes18:28
julenI guess 90% of the users just do ./st.py -b cluster18:28
rluethiI agree, it makes sense.18:28
julenand play with horizon18:28
julenor the CLI18:28
rluethimost will want the cluster to build as fast as possible.18:29
rluethiand of course correctly.18:29
julendefinitely18:29
rluethiAs far as I am concerned, we can make that the default.18:29
julenI vote for that :)18:30
rluethiWe need to think about how we implement it, though.18:30
rluethiRight now, there's the -q option and the SNAP_CYCLE env variable.18:30
julenimplement what? speeding up in general?18:30
*** bfernando has quit IRC18:30
julenwell... the SNAP_CYCLE thing is a very geek thing18:30
rluethiIIRC, SNAP_CYCLE=yes is not even handled because it's the default.18:31
julenif someone is geek enough to want snapshots every step, he is also to set an env var before he executes the thing18:31
rluethiSNAP_CYCLE=no was only a quick hack to speed up debugging.18:31
*** alij has joined #openstack-meeting-alt18:32
rluethiI think Pranav agrees with the new default, so we can implement it and submit a patch.18:32
julenand remember my first commit to training-labs ;)18:33
julenadd the actual command ;)18:33
julenin the -h18:33
rluethi:)18:33
*** rcernin has joined #openstack-meeting-alt18:33
rluethiRight. I also agree with your request to add more information to the help message.18:34
rluethianything else you'd like to discuss?18:36
julenwell.. so if there is no urgent request, I will focus my next week(s) on getting my home infrastructure ready, so that I (or we) can test all those combinations of op-sys and targets with a single command18:36
julenotherwise, I'm good18:36
rluethiokay. if you have any further comments re: python port, please let me know.18:36
julennot so far18:37
*** alij has quit IRC18:37
julenbut I will18:37
julenthen, let us meet again next week (or by e-mail)18:37
rluethiokay. see you around.18:37
*** rluethi has quit IRC18:37
julensee you18:37
*** morgan_ has joined #openstack-meeting-alt18:48
*** lpetrut has joined #openstack-meeting-alt18:53
*** jmckind_ has joined #openstack-meeting-alt18:54
*** florianf has quit IRC18:54
*** jmckind has quit IRC18:56
*** m-greene has joined #openstack-meeting-alt18:59
*** lpetrut has quit IRC19:00
*** egallen has quit IRC19:07
*** jmckind has joined #openstack-meeting-alt19:11
*** Sukhdev has joined #openstack-meeting-alt19:12
*** jmckind_ has quit IRC19:12
*** haleyb_ has quit IRC19:17
*** yamamoto has quit IRC19:20
*** dprince has quit IRC19:22
*** belmoreira has joined #openstack-meeting-alt19:23
*** myoung|afk is now known as myoung19:23
*** phschwartz has joined #openstack-meeting-alt19:23
*** belmoreira has quit IRC19:27
*** Swami has joined #openstack-meeting-alt19:30
*** bana_k has quit IRC19:32
*** yuanying_ has joined #openstack-meeting-alt19:40
*** yuanying_ has quit IRC19:45
*** hongbin has joined #openstack-meeting-alt19:45
*** diazjf has joined #openstack-meeting-alt19:48
*** enriquetaso has quit IRC19:52
*** rossella_ has joined #openstack-meeting-alt19:54
*** cartik has quit IRC19:56
*** rossella_s has quit IRC19:56
*** cathy_ has joined #openstack-meeting-alt19:56
*** cathy_ has quit IRC19:56
*** thrash is now known as thrash|biab19:57
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon Nov 14 20:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
*** arxcruz has quit IRC20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
dave-mccowan#topic roll call20:00
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:00
dave-mccowan\o/20:00
*** arunkant has joined #openstack-meeting-alt20:00
redroboto/20:00
arunkanto/20:00
dave-mccowanhi arunkant redrobot20:00
*** alee has joined #openstack-meeting-alt20:01
aleeo/20:01
*** woodster_ has joined #openstack-meeting-alt20:01
diazjfo/20:01
*** bobmel_ has joined #openstack-meeting-alt20:02
dave-mccowanthe faithful barbicaneers have gathered :-)20:02
dave-mccowan#topic Patches for CLI Updates20:03
*** openstack changes topic to "Patches for CLI Updates (Meeting topic: barbican)"20:03
dave-mccowanredrobot has done some great work on this.  what's the latest?20:03
redrobotI was waiting on reviews20:04
redrobotlooks like Kaitlin left a review since last I checked20:04
woodster_o/20:04
redrobotI'll try to address Kaitlin's comments asap20:05
dave-mccowanthere are 3 patches?20:05
redrobothttps://review.openstack.org/#/c/388267/20:05
redrobot#link https://review.openstack.org/#/c/388267/20:05
*** bobmel has quit IRC20:05
redrobot^^ adds the field name renames20:05
redrobotand20:05
redrobot#link https://review.openstack.org/#/c/388981/20:05
redrobot^^ adds --file20:06
dave-mccowanis https://review.openstack.org/382643 part of it as well (secret.id property)20:06
redrobotdave-mccowan it's unrelated... I have to go back and fix that older patch, but it's lower priority than the CLI patches20:07
*** cartik has joined #openstack-meeting-alt20:07
redrobotI think we may want to add ID to the Service API first instead of just adding .id to the python lib20:07
dave-mccowanredrobot cool.  thanks.  i'll review those first two today as well.20:08
*** iyamahat has joined #openstack-meeting-alt20:08
dave-mccowanis there any other CLI improvement work that should be done this cycle?20:08
redrobotI think containers are kind of a pain, but I haven't thought about how to fix them20:10
dave-mccowansomething to think about, maybe we can brainstorm on it in the channel sometime.20:13
dave-mccowan#topic certificate order api deprecation20:13
dave-mccowanwe've made some progress on this.20:13
*** openstack changes topic to "certificate order api deprecation (Meeting topic: barbican)"20:13
dave-mccowandiazjf committed doc changes to alert a reader of docs.20:13
*** haleyb_ has joined #openstack-meeting-alt20:14
dave-mccowanat the summit we discussed adding a config switch to turn off the API.  the owner is listed as: redrobot or "new contributor"20:14
*** kfarr has joined #openstack-meeting-alt20:14
*** dtardivel has quit IRC20:14
dave-mccowanany updates or volunteers for this one?20:14
redrobotno updates from me, busy with other stuff atm20:15
redrobotI could maybe help any new contributors who may want to start chipping away at this20:15
dave-mccowanwe had a few new contributors at the summit.  has anyone been in touch with them?20:16
*** vijendar has quit IRC20:16
*** vijendar has joined #openstack-meeting-alt20:17
dave-mccowan#topic returning entity_id property20:17
*** openstack changes topic to "returning entity_id property (Meeting topic: barbican)"20:17
dave-mccowanat summit we discussed adding returning entity_id properties in our response bodies.  in the past we've returned full entity_refs. (full URIs)20:18
dave-mccowanthis was redrobot's item too20:18
*** haleyb_ has quit IRC20:18
*** ijw has quit IRC20:18
redrobotI think we need a spec first?20:19
dave-mccowanredrobot  that makes sense.20:19
*** DavidPurcell has quit IRC20:19
redrobotI haven't started a spec on this20:19
dave-mccowando we need to bump our API version to do this?20:19
redrobotno, it's just adding a new property20:20
*** beisner has joined #openstack-meeting-alt20:20
redrobotand we would not remove the secret_ref or xxx_ref properties20:20
*** yamamoto has joined #openstack-meeting-alt20:21
dave-mccowancool.  so this should be a straightforward implementation20:21
*** bana_k has joined #openstack-meeting-alt20:21
dave-mccowan#topic congrats to arunkant20:22
*** openstack changes topic to "congrats to arunkant (Meeting topic: barbican)"20:22
diazjfcongrats!!! arunkant :)20:22
dave-mccowancongrats to arun and welcome to barbican-core.  his vote last week was unanimous20:22
redrobot\o/20:22
dave-mccowan#topic any other business20:23
*** openstack changes topic to "any other business (Meeting topic: barbican)"20:23
dave-mccowanour review backlog is shrinking.  thanks everyone; we've been making steady progress on it.20:23
woodster_+1 congrats20:23
dave-mccowannext i'd like to shrink our bugs backlog.  we have over 70 open bugs.  i'm sure many are invalid/dups/user error, etc.20:24
woodster_word of caution about adding fields to responses....Dev core has been restrictive/prescriptive on doing this without a version bump. Not a barbican concern until they are part of def core I suppose :)20:24
dave-mccowanif we each grab one or two launchad bug a week to triage, we'll be able to shrink that to a more manageable level20:25
*** yamamoto has quit IRC20:25
*** panda|bbl is now known as panda20:25
dave-mccowando we want to bump the version this release for any other reason?20:26
dave-mccowanlast chance for any other topics today...20:28
woodster_I'd say if we aren't part of def core yet, probably not an issue20:28
* woodster_ lost track of if barbican is included in def core or not20:29
dave-mccowanwoodster_ we're not.20:29
woodster_cool, make it easier then :)20:29
*** cartik has quit IRC20:29
*** ianychoi has quit IRC20:29
dave-mccowandeprecating certificate orders will involve a version bump.20:30
dave-mccowani think?20:30
*** bana_k has quit IRC20:31
redrobotwhat version are we talking about?20:31
aleedave-mccowan, redrobot api version?20:31
redrobotthe version in the api routes or the release version?20:31
dave-mccowani could use a refresher on each of them, i guess.  which ones do we need to worry about?20:33
redrobotapi routes are the /v1/blah versions20:35
redrobotrelease version is the version that the rel team gives us20:35
*** rcernin has quit IRC20:35
redrobotseems to go up every release20:35
redrobotcurrently it's 3.0.0.020:35
redrobotThere's also the API version which we use in the root response20:36
*** thrash|biab is now known as thrash20:38
*** anilvenkata has quit IRC20:38
*** mariannelm has quit IRC20:38
dave-mccowanis the v1 in /v1/orders always the same /v1/secrets, or would they be different?20:38
*** tellesnobrega has quit IRC20:38
dave-mccowani guess something to work out in the spec...20:40
redrobotv1 shouldn't change until we make a v220:40
redrobotbut the home response may say something like "version": "1.3" or whatever20:41
*** dprince has joined #openstack-meeting-alt20:41
*** mariannelm has joined #openstack-meeting-alt20:42
dave-mccowanthanks for coming everyone. :-)20:43
dave-mccowan#endmeeting20:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:43
openstackMeeting ended Mon Nov 14 20:43:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-11-14-20.00.html20:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-11-14-20.00.txt20:43
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-11-14-20.00.log.html20:43
kfarrthanks dave-mccowan20:43
*** CarolBarrett has joined #openstack-meeting-alt20:49
*** GeraldK has joined #openstack-meeting-alt20:49
*** yamahata has joined #openstack-meeting-alt20:50
*** yamahata has quit IRC20:50
*** yamahata has joined #openstack-meeting-alt20:53
*** rossella_ has quit IRC20:53
*** arunkant has left #openstack-meeting-alt20:55
*** hichihara has joined #openstack-meeting-alt20:57
*** jamemcc has joined #openstack-meeting-alt20:57
*** MeganR has joined #openstack-meeting-alt20:57
*** ijw has joined #openstack-meeting-alt20:58
*** tellesnobrega has joined #openstack-meeting-alt20:59
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:00
*** HeOS has joined #openstack-meeting-alt21:01
CarolBarrett#startmeeting product_working_group21:01
openstackMeeting started Mon Nov 14 21:01:30 2016 UTC and is due to finish in 60 minutes.  The chair is CarolBarrett. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: product_working_group)"21:01
openstackThe meeting name has been set to 'product_working_group'21:01
*** rcernin has joined #openstack-meeting-alt21:01
CarolBarrettHi - Who's here for the Product WG meeting?21:01
Arkady_Kanevskyme21:02
MeganRHi21:02
GeraldKGerald21:02
*** alee has left #openstack-meeting-alt21:02
jamemccHi21:02
kencjohnstono/21:02
*** ijw has quit IRC21:02
CarolBarrett#link https://wiki.openstack.org/wiki/Meetings/product-team21:02
*** pabelanger has joined #openstack-meeting-alt21:03
CarolBarrettYou can find the agenda for today's meeting at the link21:03
tnarghi, Grant here21:03
CarolBarrettHi Grant21:03
CarolBarrettLet's get started.21:03
CarolBarrett#topic Review Ocata Goals & Finalize leads21:03
*** openstack changes topic to "Review Ocata Goals & Finalize leads (Meeting topic: product_working_group)"21:03
CarolBarrett#link: https://wiki.openstack.org/wiki/ProductTeam21:03
CarolBarrettI updated our wiki page with our discussion from last week21:04
*** KrishR has joined #openstack-meeting-alt21:04
*** pchadwick has joined #openstack-meeting-alt21:04
*** MadhuKashyap has joined #openstack-meeting-alt21:04
pchadwicko/21:04
CarolBarrettHi pchadwick21:04
*** hurricanerix has joined #openstack-meeting-alt21:04
pchadwickthanks carolbarrett21:04
CarolBarrettAny comments/suggestions on the goals themselves?21:04
*** Rockyg has joined #openstack-meeting-alt21:04
MadhuKashyapHi21:04
Arkady_Kanevskywhere is the pointer to goals page?21:05
jamemccSame as the Ocata Cycle Priorities?21:05
RockygO/21:05
CarolBarretthere's a link to the goals: https://wiki.openstack.org/wiki/ProductTeam21:05
*** shamail has joined #openstack-meeting-alt21:06
CarolBarrettThey are on our wiki page under meeting and communication info21:06
shamailHi everyone21:06
*** rossella_ has joined #openstack-meeting-alt21:06
CarolBarrettyes goals/priorities are the same21:06
CarolBarretthi Shamail21:06
Arkady_Kanevskyso we need leads for each project we want to move forward21:06
Arkady_Kanevskyand usual questionare to drive?21:07
Arkady_KanevskyDo we want to do video intreview in this cycle?21:07
CarolBarrettarkady_kanevsky: I'm not following your comments21:07
shamailHi Arkady_Kanevsky: We are not doing a design series interview for this cycle since it is a short one21:07
shamailWe will instead use this cycle to make the roadmap process more efficient21:08
Arkady_Kanevskyfor last cycle we interviewed PTL on video and then updated roadmap slides based on it21:08
pchadwickRight - but the assumption this time is that not much will happen on the roadmaps.21:08
shamailThe goals/priorities are the overall objectives of our WG, the roadmap is a task we conduct but it is not one of the goals per se.21:08
Arkady_Kanevskydo we want to do that deep level again. Or something lighter like email or call with PTL?21:08
shamailpchadwick: +1 except process re-definition21:08
pchadwickshamail: understood21:09
Arkady_KanevskyI expect that some project will reduce their deliveries based on resource reductions...21:09
Arkady_KanevskyI went to Rally planning in Barcelona for it.21:09
CarolBarrettGood discussion21:10
Arkady_KanevskyAgree Ocata is short cycle - so fewer deliveries21:10
CarolBarrettAny changes that we want to consider?21:11
shamailFor the goals/objectives?21:11
CarolBarrettyes21:11
RockygI think we do need to poll the PTLs at about milestone 2 to see whether they will do all the maintenance they had hoped.21:11
Arkady_KanevskyDo we need to review https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group - to see if the people are still in place for it?21:11
CarolBarrettrockyg: why?21:11
shamailI think they look good, I think kencjohnston volunteered to also start a sub-team for creating a primer on containers in OpenStack21:11
CarolBarrettShamail, kencjohnston: should we add that to our priorities for this cycle?21:12
kencjohnstonshamail: +1, not much progress in the last week but on my list.21:12
RockygLike Arkady_Kanevsky said, to be able to broadcast where on the Ocata plans the various projects will land21:12
kencjohnstonshamail: CarolBarrett I also wanted to be clear that this is likely a refresh of the existing Containers Guide21:12
*** diazjf has quit IRC21:12
shamailCarolBarrett: I think we should (mainly for tracking purposes)21:12
kencjohnston#link OpenStack Containers Guide http://www.openstack.org/assets/pdf-downloads/Containers-and-OpenStack.pdf21:13
shamailUnderstood kencjohnston, any material is useful in this space… even refreshing existing stuff21:13
CarolBarrettShamail: I agree, will add it21:13
*** alij has joined #openstack-meeting-alt21:13
jamemccTHe 2nd goal is "Complete the User Story Tracker" - was it already started? Possibly it could overlap our work on something similar for the LCOO working group..21:13
CarolBarrett#agreed at another priority to the Ocata set for updating the Containers Guide with kencjohnston as lead21:13
Arkady_Kanevsky+121:14
CarolBarrett#action Carolbarrett update PWG wiki to include add'l priority21:14
GeraldKif you are about adding new prios for Ocata, what about adding the capacity mgmt user story. unfortunately, I think I had missed last week's meeting where this was discussed and not put among the prios.21:14
*** uxdanielle has joined #openstack-meeting-alt21:14
CarolBarrettjamemcc: Yes, the user story tracker is generally done and now needs to get hosted on OpenStack infrastructure and have some add'l testing to check for robustness21:15
Arkady_KanevskyShamail, what do you need for projects roadmap update?21:15
shamailjamemcc: Yes, it has already been started… the prototype is built using this ref. doc: https://drive.google.com/file/d/0B_yCSDGnhIbzRUxQUE5LYWswN2M/view?usp=sharing21:15
shamailArkady_Kanevsky: Nothing on project roadmaps for now… we are skipping the video interview for Ocata21:15
*** EricGonczer_ has quit IRC21:15
*** spzala has joined #openstack-meeting-alt21:15
*** m-greene has quit IRC21:15
*** EricGonczer_ has joined #openstack-meeting-alt21:16
*** julim has quit IRC21:16
Arkady_KanevskyOK. just 1K view update slide?21:16
CarolBarrettGeraldK: We had a lot of discussion about adding specific user stories to our goals and decided against it. The teams working on them should have goals,but not the overall WG21:16
shamailArkady_Kanevsky: We might do roadmap slides again near the end of the release but we haven’t kicked off the sub-team yet… Nothing on roadmap has been decided yet for the next 3-4 months.21:17
*** m-greene has joined #openstack-meeting-alt21:17
GeraldKCarolBarrett: okay. thanks for clarification21:17
*** alij has quit IRC21:17
CarolBarrettjamemcc: Would you be interested in joining/leading this effort? There is a team to partner with....more resources are always welcome!21:17
shamailWe will revisit near the end of the release cycle to discuss whether we will publish a roadmap this cycle or not.21:17
Arkady_KanevskyOK. keep me posted. Where do you want to update project liason ownership?21:17
jamemccYes - please put me in contact21:18
Arkady_KanevskyCarol ready to move to next topic21:18
CarolBarrettThanks jamemcc - don't know if I have your email address - can you send me an email: carol.l.barrett@intel.com?21:19
*** rossella__ has joined #openstack-meeting-alt21:19
*** gyee has joined #openstack-meeting-alt21:19
CarolBarrett#agreed jamemcc will take lead on user story tracker priority21:20
*** fnaval has quit IRC21:20
Arkady_KanevskyLooking at https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group. we are missing a few projects we are tracking.21:20
shamailThanks jamemcc!21:20
Arkady_KanevskyCan everybody check if they are still covering projects they are sign in there.21:21
*** jaugustine has quit IRC21:21
*** fnaval has joined #openstack-meeting-alt21:21
CarolBarrettarkady_kanevsky: Can you send a note on the ML asking people to review/update this? My guess is not everyone is here today.21:21
Arkady_KanevskyI will add Rally and me covring them21:21
*** rossella_ has quit IRC21:22
CarolBarrett#action arkady_kanevsky send a note on the ML asking people to review/update Cross project liason list21:22
CarolBarrettLet's move on21:22
CarolBarrett#topic Definition of Done21:22
*** openstack changes topic to "Definition of Done (Meeting topic: product_working_group)"21:22
CarolBarrettIn our BCN working session we had a good discussion on this.21:22
CarolBarrettthe etherpad link is here21:23
CarolBarrett#link https://etherpad.openstack.org/p/PWG_Session_Oct16_BCN21:23
*** Shrews has joined #openstack-meeting-alt21:23
Arkady_KanevskyCarol - Done. email sent21:24
GeraldKbasically we have 2 stages "done": first, after having agreed in the user story and second, after having it address to our satisfaction21:24
CarolBarrettThoughts on this?21:24
pchadwickDo the PTLs use and DoD for blueprints/specs?21:25
pchadwicks/and/a/21:25
Arkady_Kanevskynot sure. they do link patches to blueprints and specs and keep thme open.21:26
Arkady_KanevskyNot sure what is their process for done.21:26
Arkady_KanevskyI can ask a couple of PTLs21:26
CarolBarrettpchadwick: sorry, don't understand your comment21:26
pchadwickI was wondering if the development teams already have a definition of done (DoD) in their process?21:27
Arkady_Kanevsky<GeraldK> - my understaning we have two options.21:27
CarolBarrettgotcha21:27
pchadwickIf we can say that ours is "It's in the repos and specs are defined" then we only need to have that.21:28
Arkady_KanevskyOne is when all the blueprints and specs we create for a user story are full completed.21:28
pchadwickThe second level is tracked by the dev teams.21:28
*** uxdanielle has quit IRC21:28
Arkady_KanevskySecond is when we created them and projects accept them. We will still to track thme but we do not need the same level of resourecs to drive them.21:28
*** lpetrut has joined #openstack-meeting-alt21:28
shamailWe have concept validation (meaning we think we have captured all perspectives) and then implementation (which is when it has moved into project-level artifacts and is being worked on)21:29
RockygThe specs are done when they are approved.  When the BPs associated with the spec are done, then the implementation of the spec is done21:29
shamailI think our view of done should be once the technical teams have picked it up… We still have to track it but we shouldn’t be editting the story any more.  Thoughts?21:29
CarolBarrettI think lines 97 thru 101 was the definition that the group in BCN landed on - we wanted to make sure Done was in our control21:29
GeraldKIMHO, DoD is usually applied when things are implemented. so, what term could we use for the "specs ready" stage?21:29
pchadwickshamail: +121:30
jamemccCarol, Seems correct to have 2 phases to done. Want to be able to proceed past User Story with some confidence.  I can see missing criteria in the PWG defination - basically that it needs multiple reviewers and some consideration of alternatives.  That may be deeper in the process.21:30
Arkady_KanevskyI think we still need to definitions. One internal to the team when we can move resources.21:30
*** diazjf has joined #openstack-meeting-alt21:30
shamailThe definition in the the etherpad also aligns with this view of “done"21:30
Arkady_KanevskyAnother is externa;l to community - when we can report back that user story is completed and functionality is availavbe21:30
jamemccI think the 2nd Done is still our to make - Development teams can be done with 1 item in a release but we need to decide when it all comes together.21:31
*** diazjf has quit IRC21:31
Arkady_KanevskyThere is also still expectation whne we put blueprint/spec on their board and they approve it - we provide resources to implement it.21:31
Arkady_KanevskyWe is collective product WG member companies folks21:32
CarolBarrettarkady_kanevsky: I agree  that when the user story is implemented is the ultimate done. We can't control that, only support with resources and ability to track status21:32
Arkady_Kanevskyagree with jamescc - that is our external done definition21:32
GeraldKI agree to the definition of Done as in the Etherpad. After we have filed the specs it is somehow out of our control. still, how would we call the stage when we can close the user story as implementation is complete?21:32
GeraldK"internal done" and "external done" doesn't sound well21:33
CarolBarrettGeraldK: I think we call that implemented. Our "done" would refer to the completion of the requirements gathering, documentation and providing actionable input and resources to the project development teams21:33
*** mariannelm has quit IRC21:33
GeraldKokay.21:34
*** mariannelm has joined #openstack-meeting-alt21:34
Arkady_Kanevskysuggestions for 2 stage completions?21:34
Arkady_Kanevskynameing ofr 2 stages?21:34
RockygTo paraphrase lots of devs -- if it isn't tested, it doesn't work so our definition of "delivered" should be that th implementation passes  acceptance (scenario) tests21:34
shamailWhat about “validated story” and “user story complete”21:35
shamailafter its delivered (from a code perspective), we could say “implemented"21:35
jamemcc@shamail +121:35
shamailWe own the first two milestones; delivery owns third21:35
CarolBarrettshamail: What would need to be completed for validated? ditto for complete?21:36
Arkady_Kanevskyhow aboud defined and delivered?21:36
shamailFor validated = PWG members have added their feedback… we have reached out to other WGs for feedback… and it is all merged into the story21:36
Arkady_Kanevskyboth start on D which is not great21:36
GeraldKwhat about "accepted/agreed story" instead of "validated story". what kind of "validation" do we do on a user story that we agree on?21:36
shamailUser Story Complete = Implementation plan has been established, specs/bps created21:36
*** mordred has joined #openstack-meeting-alt21:36
Arkady_KanevskyI like accepted and completed.21:37
shamailValidation was implying needs have been validated by market-centric WGs21:37
CarolBarrettI think that works too21:37
shamailbut agreed works too21:37
CarolBarrettAny one have comments on that?21:37
GeraldKokay. so validated is already one step ahead of PWG agreement on a story21:37
*** ijw has joined #openstack-meeting-alt21:38
GeraldKagreed -> validated -> done -> implemented21:38
GeraldK?21:38
CarolBarrettGeraldK: I view is as the steps on line 98 and 99 in the etherpad21:38
*** bana_k has joined #openstack-meeting-alt21:39
Arkady_Kanevskywhat does done represent?21:39
*** kgiusti has left #openstack-meeting-alt21:39
Arkady_Kanevskyagreed - user story approved21:39
CarolBarrettGeraldK: I thought it would be validated (User Story Definition is Complete & Merged into Repo, json file created)21:39
shamailDone IMHO represents when the capability is actually available in OpenStack-Powered clouds.21:40
Arkady_Kanevskyvalidated - json file created & gap analysis done21:40
shamailCarolBarrett: Your definition + we have sent notice of the user story to other WGs21:40
Arkady_Kanevskydone - all specs/blueprints/projects created and approved21:40
shamailand merged their comments (if applicable) as well21:40
CarolBarrettShamail: +1 on real definition of done.21:41
*** Shuo_ has joined #openstack-meeting-alt21:41
Arkady_Kanevskyimplemented - user story support delivred to Customers21:41
*** diazjf has joined #openstack-meeting-alt21:41
Arkady_KanevskyGeraldK - are these definitions you are using?21:41
CarolBarrettValidated = User Story Definition is Complete & Merged into Repo, json file created, sent notice of the user story to other WGs and merged their comments21:41
*** mariannelm has quit IRC21:41
GeraldKArkady_Kanevsky: no. just trying to summarize the milestones we had been discussing about21:42
*** diazjf has quit IRC21:43
CarolBarrettUser Story Complete = Implementation plan has been established, specs/bps created and json file updated21:43
Arkady_KanevskyCarolBarrett - so gap analysis and spec/blueprints/etc are part of done definition?21:43
CarolBarrettarkady_kanevsky: Yes, this is done from PWG point of view21:43
Arkady_KanevskyCarol I do not like the ter, User Story Complete.21:43
CarolBarrettUser Story Done = User Story Tracker shows all required elements are complete21:43
*** rossella__ has quit IRC21:44
Arkady_KanevskyIt has implication that story has been done and ready for Customers to use.21:44
CarolBarrettarkady_kanevsky: propose another name, I'm fine with changing it21:44
Arkady_KanevskyCan we use different term for it?21:44
Arkady_Kanevskyuser story defined?21:44
*** tonytan4ever has quit IRC21:45
pchadwick+121:45
CarolBarrettThere are 3 milestones we're trying to define21:45
jamemccFor me the name isn't yet as critical as that there is a 3rd Done - after the multiple Dev done - when the Product Manager says it's all ready for the customer.  All this dicussion is making me realize I can see 3 dones.21:45
CarolBarrettIf the 1st one is User Story Defined, what is the 2nd one (with specs/blueprints/etc)?21:46
jamemccUser Story Ready21:46
Rockygthird done is passes prod mgr's acceptance tests21:46
CarolBarrettjamemcc: that's right. There's the actual implementation and release of code that enables someone to achieve the user story21:46
Arkady_Kanevskythat actually raised a question for me if we want to define 4th - for gap analysis21:46
Arkady_Kanevskyespecially if need to propose new project.21:46
CarolBarrettUser Story Defined, User Story Ready, User Story Implemented?21:47
jamemcc+121:47
CarolBarrettarkady_kanevsky: the gaps analysis is part of the 2nd phase (ie. ready for project team implementation)21:47
Arkady_KanevskyI suggest we add one more ahead of them - User Story Accepted or use story approved21:48
* shamail has to drop (sorry)21:48
*** shamail has quit IRC21:48
Arkady_Kanevskycarol i think it is too much for one phase.21:48
CarolBarrettAlrighty - this was a more lively discussion that I thought it would be. Can we take this to the ML? Will someone volunteer to summarize this discussion and start the thread?21:48
Arkady_Kanevskysuggest we split it into 2 phases21:48
pchadwickcarolbarrett: I will send the email21:48
CarolBarrettpchadwick: Thanks!21:49
Arkady_Kanevskythanks pete21:49
*** uxdanielle has joined #openstack-meeting-alt21:49
CarolBarrett#action pchadwick summarize the Done discussion and send to ML for further refinement21:49
CarolBarrettWe've got 10 mins left21:49
CarolBarrett#topic Roadmap refresh plans21:49
*** openstack changes topic to "Roadmap refresh plans (Meeting topic: product_working_group)"21:49
CarolBarrettI know we touched on this earlier, but think it's good to make sure we all have the same understanding21:50
CarolBarrettShamail: Can you summarize the plans for this cycle?21:50
Arkady_Kanevskysuggest we postpone it to next week when Shamail is back21:50
Rockygshamail dropped off...21:50
CarolBarrettsorry - didn't see he dropped.21:50
Arkady_Kanevskyfinish early?21:50
CarolBarrett#action Carol move Roadmap topic to next week's agenda21:50
CarolBarrett#topic Opens21:50
*** openstack changes topic to "Opens (Meeting topic: product_working_group)"21:50
CarolBarrettWill people be working next monday 11/21?21:51
CarolBarrettWant to make sure we'll have critical mass for a meeting21:51
Arkady_Kanevskyyes for 21th21:51
Arkady_Kanevskybut I iwll miss 28th21:51
Rockygcan be...21:51
pchadwickI should be available.21:52
jamemccI should be21:52
CarolBarrettSounds like most people will be here - I'll be gone, but Shamail has said he could run the meeting on the 21st21:52
GeraldKI will be there21:52
CarolBarrett#agree keep the team meeting on the 21st21:52
Arkady_Kanevsky+121:53
MeganR I will be here for both21:53
CarolBarrettI'm going to pass on the swift discussion and push to next week21:53
Arkady_Kanevskyneed to drop.21:53
Arkady_Kanevskyhave a good week21:53
*** Arkady_Kanevsky has quit IRC21:53
*** julen has quit IRC21:53
CarolBarrettThe last think I wanted to pass along was a summary of the Work Flow changes happneing within the Community21:53
MadhuKashyap+121:53
CarolBarrettWhen the PTG registration opened there were a lot of questions in my company, so I worked with Thierry to create a summary to help people plan what events they should attend21:54
CarolBarrettyou can find it here21:54
CarolBarrett#link https://docs.google.com/document/d/1zC9I5rR8-Cv8S9Qlt8e8eLxi3CC0JuzsCNH1fZWdRYg/edit?usp=sharing21:54
*** mariannelm has joined #openstack-meeting-alt21:54
CarolBarrettIf you have questions pls send them via the ML - others are likely to have the same questions/21:54
MeganRCarol: thank you for putting this together!21:54
CarolBarrettAnyone else have Opens?21:54
MeganRI'm good21:55
GeraldKthanks Carol for this summary21:56
*** corey_ has quit IRC21:56
Rockygyeah.  Thanks!21:56
*** kjw3 has joined #openstack-meeting-alt21:56
CarolBarrettGlad to do it, hope it's helpful21:56
*** olaph has joined #openstack-meeting-alt21:56
*** rossella__ has joined #openstack-meeting-alt21:56
CarolBarrettLet's call it a wrap for today. Have a good week!21:56
CarolBarrett#endmeeting21:56
MeganRthank you - you too!21:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:57
openstackMeeting ended Mon Nov 14 21:56:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-11-14-21.01.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-11-14-21.01.txt21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-11-14-21.01.log.html21:57
*** GeraldK has quit IRC21:57
*** MadhuKashyap has quit IRC21:57
*** jlk has joined #openstack-meeting-alt21:57
*** jamielennox has joined #openstack-meeting-alt21:57
*** rcarrillocruz has joined #openstack-meeting-alt21:58
*** Shuo_ has quit IRC21:58
*** CarolBarrett has quit IRC21:59
*** qwebirc85330 has joined #openstack-meeting-alt21:59
*** ansmith has quit IRC21:59
*** bana_k has quit IRC21:59
*** rmoe has joined #openstack-meeting-alt21:59
*** rattboi has joined #openstack-meeting-alt22:00
*** Swami has quit IRC22:00
jeblairhowdy zuulish people!22:00
fungimmm meetings...22:00
pabelangero/22:00
olapho/22:00
* morgan_ lurks22:01
* mordred hands everyone a fish from this bucket he found22:01
phschwartzo/22:01
morgan_mordred: uh...22:01
jeblairwhat do we call ourselves?  minions of gozer?  i dunno.22:01
fungii started using remind and wyrd specifically so i wouldn't forget to attend this meeting22:01
fungiand it reminded me!22:01
*** adam_g has joined #openstack-meeting-alt22:01
jeblairfungi: word.22:01
*** pchadwick has left #openstack-meeting-alt22:01
qwebirc85330hi22:01
mordredjeblair: we coudl all just call each other sigourney22:01
phschwartzfungi: lucky you, they never work for things related to my kids school O.o22:01
*** qwebirc85330 has quit IRC22:01
Shrewszuul ghouls22:01
SpamapSo/22:01
docaedojeblair: pipefitters seems an appropriate name IMO22:01
jamielennoxo/22:02
* SpamapS will be driving for a few minutes, and then at the doctor's office, so my latency will be high for responses. Sorry... :-P22:02
adam_ghiya22:02
fungithere is no meeting, only zuul22:02
*** Shuo_ has joined #openstack-meeting-alt22:02
jeblair#startmeeting zuul22:02
openstackMeeting started Mon Nov 14 22:02:23 2016 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: zuul)"22:02
openstackThe meeting name has been set to 'zuul'22:02
jeblairhi!  this is our first meeting22:02
jeblairour agenda is:22:02
jeblairto make an agenda22:02
jlko/22:02
fungihow meta22:03
rcarrillocruzo/22:03
jeblairhere's an etherpad: https://etherpad.openstack.org/p/TyJWrHtk1w22:03
jeblairit's blank22:03
jeblairwhat do we want to get out of this meeting?22:03
*** MeganR has quit IRC22:03
Shrewstotal enlightenment22:04
jeblairplease add your name to the etherpad by clicking in the top right22:04
Shuo_I make one subject on the etherpad22:04
Shuo_:-)22:04
jeblairShuo_: that's a good topic, but i want to set it aside right now22:04
jeblairbecause first i want to know what kind of structure we want to this meeting22:04
phschwartzmore organization then the past along with universal guidance for bug management for zuul ( I think storyboard is the choice right not)22:04
*** rbergeron has joined #openstack-meeting-alt22:04
Shuo_jeblair: agreed22:05
jeblairphschwartz: should we discuss bugs in the meeting?22:05
fungicould probably crib some meeting structure from the infra meetings (announcements, action items, specs, priority efforts, general topics, open discussion)22:05
jeblairfungi: yep, that's an option22:05
rcarrillocruzi think a tasks status update would be good22:05
jeblairjust didn't want to assume that's what people wanted22:05
rcarrillocruzto know what everyone is doing , who's stuck, etc22:05
phschwartzjeblair: At the moment, I would not say bugs directly but make sure everyone knows how we want to manage them and is on the same page.22:05
jeblairphschwartz: is that something we should cover every week, or a topic that we should put on an early meeting agenda?22:06
mordredrcarrillocruz: yah - I think making sure we know who is stuck and on what is quite important22:06
phschwartzjeblair: and early meeting agenda I think would do it.22:06
jeblairrcarrillocruz, mordred: yes.  part of that should be discoverable in storyboard, but we're probably not there yet.  so for now, should we put an "everyone update status" item on the agenda?22:07
jeblairdo we want to organize that by person, or topic area, or ...?22:07
*** kaisers has quit IRC22:08
rcarrillocruzmaybe topics? cos we have a lot of people getting stuff done, by person may get the section a bit long imho22:08
mordredjeblair: maybe by topic area? the nodepool builder work is parallel to the zuul-tests-enablement work, for instance22:08
fungigoing around the table and getting a brief update from each involved participant could be a good way to bootstrap some shared understanding, though doing that every week starts to get cumbersome and rote22:08
mordredyah - 10 people saying "churning on tests" is likely boring22:08
mordredfungi: that22:09
pabelanger+1 for topics22:09
jeblairhow about topic area, and at the end, we'll say 'anyone working on something not covered'?22:09
rcarrillocruz++ ^22:09
fungiseems as good a plan as any to start, and then can tweak once it's apparent whether or not it's helpful22:10
*** dimtruck is now known as zz_dimtruck22:10
jeblairwe'll put a list of topics on the agenda, roughly corresponding with the things we think are currently 'in progress', people can report status and discuss each22:10
phschwartz++22:10
*** zz_dimtruck is now known as dimtruck22:10
*** kaisers has joined #openstack-meeting-alt22:11
SotKsounds sensible22:11
fungithat's relatively similar to how we've been handling our priority efforts portion of the infra weekly meetings22:11
jeblairyeah, though i think in this case, we'll probably hit each item every week, so we can easily detect lack of progress22:11
jeblairare there any other goals people have for this meeting?22:12
SpamapSI'd like to make sure we have an overall status report after the story statuses22:13
phschwartz++22:13
*** hyakuhei has joined #openstack-meeting-alt22:13
jeblairSpamapS: what does that look like?22:13
fungilike a status summary as an outcome of each meeting, or what/>22:13
fungi?22:13
*** clarkb has joined #openstack-meeting-alt22:13
SpamapSAlso more of an operators report. "How close are we to doing useful things?"22:13
morgan_SpamapS: ++22:14
SpamapSSo after the stories, there's an overall strategy that they're all part of. After they're discussed, it's good to evaluate the strategy, and how the overall current goals are progressing.22:14
Shuo_jeblair: it would be great to find a platform for project lead to discuss/share some tech design and roadmap. For potential non-openstackers to not only input but alos consider whether their scenario is covered here.22:15
*** haleyb_ has joined #openstack-meeting-alt22:15
SpamapSShuo_: yes! That's exactly what I mean. A place to discuss the future, since a story by story review is mostly about the past and present.22:16
fungilike a q&a where you can identify whether a given use case is covered in the current roadmap for the v3 release vs a backlog wishlist item?22:16
Shuo_jeblair: we can find people to host a face-to-face design meetup (with virtual attendenace capability for remote folks)22:16
jeblairokay, hang on a sec22:16
jeblairSpamapS: i agree that a summary checkpoint after we cover what we're working on might be useful.  i don't know what that would look like in practice but we can try it out22:17
SpamapSIt shouldn't be q&a. Just a place to surface strategic status while a quorum of zuul community members are here to comment and absorb22:17
jeblairSpamapS, Shuo_: i heard you two say very different things22:17
*** jhesketh has joined #openstack-meeting-alt22:17
jeblairi heard Shuo_ asking about future design work, which is very different from progress22:18
*** KrishR has quit IRC22:18
SpamapSjeblair: a tech design and roadmap is a large part of the strategy.22:18
jeblairSpamapS: sure, but i think Shuo_ is asking about making changes past the end of our current roadmap22:18
*** kjw3 has quit IRC22:18
jeblairwe do have a roadmap now (the zuulv3 spec, plus some follow on specs), and it extends quite a ways22:19
jeblairi believe Shuo_ is asking about taking that even farther22:19
jeblair(which is a great thing to talk about, but i don't think it's "How close are we to doing useful things?"22:19
fungithe official roadmap mostly ends with the implementation of the v3 spec and associated pieces afaik, so it's a sort of event horizon right now (which in some ways is helpful to keep us from getting bogged down designing more features before we're done making the ones we've currently identified into reality)22:19
SpamapSOK yeah. I think the mailing list and spec review are the best places to discuss new ideas. IRC meeting is too real time for that IMO22:20
*** haleyb_ has quit IRC22:20
Shuo_jeblair: what I meant is what you just said here, agreed. Here is my reason behind that: if a company wants to commit resource, it needs to understand the scope of the project (this is the product management / roadmap side of work)....22:20
SpamapSI thought Shuo_ was more talking about documenting and adjusting the current road map22:20
fungiadjusting the current track to v3 to account for unforeseen problems makes sense, but i'm wary of encouraging too much goalpost-moving22:21
jeblairfungi: right22:21
pabelangeragreed22:21
jeblairso i think i need to write some of this out22:22
mordredperhaps a portion in the meeting for new people to wave, say hi and what their long-term goals are (best as possible) so that we can all be aware of people who may want to do large and exciting things, even if we're not in a place to directly work on those things yet?22:22
Shuo_jeblair: along with roadmap side, finding a time/platform for newbies to understand the project (code etc.) a bit at early stage, it helps better participation/contribution.22:22
Shuo_jeblair: this is the next level of explanation/education after roadmap heads up.22:22
jeblairi should make sure this is written up well so it's clear where we think Shuo_ can get answers for what we have now, and how we will handle future development once v3 is out the door22:22
SpamapSThere are something like three goal posts, and a golden snitch22:23
jeblairi will follow up on that later22:23
mordredSpamapS: don't forget the bludgers22:23
clarkbmordred: and the beaters22:23
jeblair#action jeblair work with Shuo_ to document roadmap location / process22:23
*** diazjf has joined #openstack-meeting-alt22:23
jeblairokay so back to SpamapS's thing -- we'll try to produce some kind of summary after our status updates?22:23
jeblairand we'll just see how that goes?22:24
jeblairwe might have to invent that process22:24
*** tnarg has quit IRC22:24
morgan_jeblair: likely we will need to invtent a process, but that is far from the worst thing :)22:24
SpamapSSummary + goal status22:24
* morgan_ learns to type.22:24
fungiwe've definitely had lots of feature requests come up that we've punted to a nebulous post-v3 backlog, so i guess having some means to collect those in a more coherent manner might be nice22:24
jeblairyeah, so to mordred's suggestion, which i think is related to Shuo_'s...22:25
*** rossella__ has quit IRC22:26
fungithe status summary, unless i'm misunderstanding, seems more like an outcome of the meeting (whether it's some formal summary prose or just trying to make sure the meeting minutes for the task updates make a coherent whole)?22:26
*** ianw has joined #openstack-meeting-alt22:27
morgan_fungi: i think starting with something like the meeting minutes after the infra meeting would be a good starting place22:27
morgan_more formal prose can be developed as needed22:27
jeblairmordred: i put some stuff on the etherpad, how's it look?22:27
fungithe "how close are we to being able to do useful thing x" bit doesn't seem like it would necessarily be easily extracted from individual status updates on the parts of teh codebase being worked on22:28
morgan_making sure it's coherant will be part of the write up, but it can be simple to start.22:28
morgan_fungi: sure, but it shouldn't need to be too in depth to start.22:28
jeblairfungi: yes, though the exercise of synthesising that, and articulating it may be useful22:28
fungimy thinking exactly22:28
jeblairso, i reckon we can try it and see what comes out of it22:29
mordredjeblair: yah22:29
fungiwhich is why it seems more like an outcome of the meeting rather than a part of the agenda, though i guess it could be a wrap-up collaborative drafting of that summary in-meeting22:29
morgan_fungi: ++22:29
jeblairi'm adding an 'other topics' section where we can talk about specific one-time topics22:31
*** kfarr has quit IRC22:32
jeblairshould we put the agenda in the wiki and manage it like we do for the infra meeting?22:32
phschwartzjeblair: ++22:32
rcarrillocruzthat works for me, i like that workflow22:32
fungii'm all for consistency (though i've been toying with the idea of making meeting agenda worklists in storyboard)22:32
jeblairfungi: that's a good idea, but atm, we have a lot of storyboard experimentation going on and i don't want to overdo it :)22:33
morgan_jeblair: my only concern with the wiki is it was hard to edit for many folks.22:33
*** jcoufal has quit IRC22:33
morgan_jeblair: if that has become less of an isuse, wiki is a good place for now22:33
morgan_until we have something like storyboard.22:33
morgan_(if it is needed/materializes)22:34
jeblairif anyone has a problem editing the wiki, please either ask in #openstack-infra or let me know privately22:34
fungiyeah, my storyboard idea was more a long-term thought about being able to get rid of one of our wiki use-cases community-wide22:34
Shrewsplease, keep it on the wiki22:34
fungibut i agree for this, wiki22:35
jeblair(etherpad is an alternative as well, of course)22:35
jeblair#action jeblair set up meeting agenda wiki page22:35
fungithe downside to etherpads is that it's harder to piece together the update history22:35
*** tnarg has joined #openstack-meeting-alt22:35
jeblairyeah, the wiki is a little cleaner for this22:35
*** KrishR has joined #openstack-meeting-alt22:35
morgan_jeblair: keystone went to etherpad because of the issues with the wiki. but that may not be an issue if the spam + new account limiting has been resolved22:36
jeblairokay, any other meta-topics?22:36
morgan_i prefer wiki ftr.22:36
fungimorgan_: "resolved" insofar as that we turned new account creation back on a few months ago22:36
morgan_fungi: then i see wiki as being a better choice than etherpad22:36
morgan_since this is a new setup.22:37
jeblairhow about we jump into some status updates then?22:37
pabelanger++22:37
jeblair#topic Status updates: Nodepool Zookeeper work22:38
*** openstack changes topic to "Status updates: Nodepool Zookeeper work (Meeting topic: zuul)"22:38
* fungi is thrilled that the meeting about meeting was limited to only 35 minutes22:38
*** dave-mccowan has quit IRC22:38
jeblairShrews and i have been tag teaming this a bit.  mostly shrews.  but i totally tagged in for a bit.22:38
mordredfungi: I'm sure we could lengthen that unnecessrily22:38
jeblairi think we're ready to proceed with re-incorporating the builder into nodepool22:39
*** ayoung has quit IRC22:39
fungithe22:39
fungigrrr, i hate where my enter key is22:39
Shrewsnodepool builder is now zookeeper enabled (http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html). jeblair has begun enabling tests22:40
fungithe "Nodepool: Use Zookeeper for Workers" spec?22:40
fungiahh, yep, that's what i was hoping22:40
jeblairi think further work should be based on https://review.openstack.org/396719 and https://review.openstack.org/39674922:40
*** edtubill has quit IRC22:40
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html "Nodepool: Use Zookeeper for Workers" spec22:40
*** baoli has quit IRC22:40
jeblairwhich are substantial changes -- they set us up for progress on this, but are conflict magnets22:41
mordredit's maybe worth putting in our mythical future-work idea-pile that at least one human has indicated desire for re-introducing snapshot-based builders in the future22:41
jeblairthey are also both things that we didn't really spell out as tasks22:41
mordred(mentioning because one of the patches removes that)22:41
mordredjeblair: ++22:41
jeblairyep22:41
fungiwe never actually filled the "Work Items" section of that spec. should it be retroactively fleshed out?22:41
*** hyakuhei has quit IRC22:42
*** hyakuhei has joined #openstack-meeting-alt22:42
*** hyakuhei has quit IRC22:42
*** hyakuhei has joined #openstack-meeting-alt22:42
jeblairfungi: maybe just put things in storyboard as we think of them?22:42
pabelangerShrews: jeblair: how many tests are left to enable? Do you need volunteers to help with enabling?22:42
fungiwfm22:42
*** tnarg has quit IRC22:42
jeblairi should add tasks for those two things, there are significant enough to mention, even though the changes are written22:42
*** tnarg has joined #openstack-meeting-alt22:42
clarkbdon't forget to get the integration jobs working again as part of reenabling tests22:42
*** noslzzp has quit IRC22:42
jeblairclarkb: of course :)22:42
clarkbjeblair: I don't want them to be overlooekd because they are non voting (they are expected to pass on master)22:43
jeblairso i think it was implied that we would not have snapshot builders, and we have been talking about it for a long time22:43
jeblairclarkb: they will not be overlooked22:43
fungimordred: where did reintroduction of snapshot-based image creation come up? on the removal review?22:43
mordredfungi: in #zuul earlier today22:44
pabelangerhttps://review.openstack.org/#/c/325339/ too22:44
jeblairi think this might be worth a mailing list thread22:44
jeblairto communicate why/how/when we are removing them22:44
fungimordred: thanks22:44
pabelangerI know there is some negative reaction to the removal22:44
mordredjeblair: ++22:44
jeblairand also, alternatives available22:44
jeblairwhich include better diskimage support22:45
jeblairand, writing a snapshot builder22:45
*** diazjf has quit IRC22:46
*** Swami has joined #openstack-meeting-alt22:46
*** lpetrut has quit IRC22:46
jeblairwe won't be using it (in fact we haven't used it in a long time) so it's not a priority for us.  i also don't think it's a good option if there are alternatives22:46
*** Swami has quit IRC22:46
*** spotz is now known as spotz_zzz22:47
*** Swami has joined #openstack-meeting-alt22:47
jeblairbut the model does allow for it, and i think we can support it (in much the same way that we will allow for support of aws, etc, in the future)22:47
*** Swami_ has joined #openstack-meeting-alt22:47
jeblairanyway, i'll send out an email about that22:47
fungiremoval of teh feature means much less complication with the port to support combined nodepool + zuul v3, and i wouldn't want to delay having a usable v3 so that snapshot support can get dragged along for the ride22:48
mordredjeblair: I think an email is a great idea. also in the alternatives list is "do nothing- custom images not needed for $usecase"22:48
mordredfungi: +10022:48
jeblairmordred: yeah.  there is a small gap in that right now, we have no way of saying "just use a base image".  but i consider that more of a bug that we can address any time.22:49
Shrewspabelanger: re: np tests... that's now at the top of my list. if you want to dig in to, that's great. but it now has my attention22:49
*** DavidPurcell has joined #openstack-meeting-alt22:49
*** MarkBaker has joined #openstack-meeting-alt22:50
Shrewspabelanger: i may need help w/ the integration stuff22:51
pabelangerShrews: great, I can start poking tomorrow too.22:51
*** uxdanielle has quit IRC22:51
fungiagreed, simply adding trivial support to use a specified existing image without needing to build it would open up to being able to replace image building automation with whatever you want if dib is unsuitable for any reason22:51
jeblairShrews, pabelanger: the best path for that is to get all of the command unit/func tests working first22:51
pabelanger++22:51
jeblairShrews, pabelanger: because the integration test needs all of those to operate22:52
mordredpabelanger, Shrews: integration is mainly adding zk to the devstack plugin and updating config, yeah?22:52
Shrewsjeblair: yeah, that's where i planned to start22:52
mordredfungi: yes22:52
mordredjeblair: yay irc lag - you replied before I said something! :)22:52
Shrewsmordred: no idea, which is why i might need pabelanger's help  :)22:52
*** ccamacho has quit IRC22:53
jeblaircool, i'm going to see if we can squeeze one more topic from our sample agenda in here...22:53
jeblair#topic Status updates: Zuul test enablement22:53
*** openstack changes topic to "Status updates: Zuul test enablement (Meeting topic: zuul)"22:53
*** knangia has quit IRC22:53
jeblairpabelanger: has done many... :)22:54
* mordred hands pabelanger the Chalice of Test Re-enablement Freight-train-ness22:54
pabelangermany indeed22:54
* mordred is bad at naming things22:54
jeblairi expect a merge-flood soon on those22:54
rcarrillocruzhah22:54
mordredjeblair: I think I remember phschwartz asking earlier today in channel about process for grabbing a re-enablement task ...22:55
mordredbut it might not have been phschwartz22:55
pabelangerThe tests that are left, have required me to dive more into zuul to better understand why things don't work. Likely possible regressions in our v3 code path22:55
jeblairah, the process is to check https://storyboard.openstack.org/#!/story/2000773 to see if there is a task for the test you want22:56
jeblairif someone is working on that test, pick another one or ask to help them :)22:56
*** spzala has quit IRC22:56
jeblairotherwise, create a task for that test and assign it to yourself22:56
*** edtubill has joined #openstack-meeting-alt22:56
jeblair#info to work on a zuul v3 test re-enablement, use https://storyboard.openstack.org/#!/story/200077322:56
*** neiljerram has quit IRC22:57
jeblairpabelanger: are those complicated tests assigned to you?22:57
pabelangeryes, each test should have a task now22:57
pabelangerI tried to stay a top of adding them into storyboard before I did git-review22:58
jeblairpabelanger: oh, i meant the ones you haven't pushed up changes for22:58
jeblairpabelanger: "The tests that are left, have required me to dive more into zuul to better understand why things don't work. Likely possible regressions in our v3 code path"  <-- those tests22:58
pabelangerjeblair: https://review.openstack.org/#/c/393887/ is the only 1 right now22:59
pabelangerso far, if I do, I WIP it22:59
jeblairpabelanger: okay.  well, what i'm hoping is to find out what tests you're talking about, and to work out how to make progress on them.  but we're out of time.  so we'll have to take it to #zuul.22:59
jeblairthanks everyone!23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
mordredyay first meeting!23:00
openstackMeeting ended Mon Nov 14 23:00:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2016/zuul.2016-11-14-22.02.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2016/zuul.2016-11-14-22.02.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2016/zuul.2016-11-14-22.02.log.html23:00
rcarrillocruz\o/23:00
*** Shuo_ has quit IRC23:00
*** vijendar has quit IRC23:01
*** vijendar has joined #openstack-meeting-alt23:01
olaphthanks jeblair !23:01
*** s3wong_ has joined #openstack-meeting-alt23:02
*** jlk has left #openstack-meeting-alt23:02
*** rcarrillocruz has quit IRC23:03
*** pabelanger has left #openstack-meeting-alt23:04
*** KrishR has quit IRC23:04
*** xyang1 has quit IRC23:04
*** jprovazn has quit IRC23:04
*** s3wong has quit IRC23:05
*** hongbin has quit IRC23:05
*** dprince has quit IRC23:06
*** noslzzp has joined #openstack-meeting-alt23:07
*** vijendar has quit IRC23:08
*** edtubill has quit IRC23:11
*** DavidPurcell has quit IRC23:13
*** msimonin has quit IRC23:18
*** jamielennox has left #openstack-meeting-alt23:19
*** absubram has quit IRC23:21
*** ijw_ has joined #openstack-meeting-alt23:22
*** yamamoto_ has joined #openstack-meeting-alt23:24
*** ijw has quit IRC23:24
*** pradk has quit IRC23:25
*** EricGonczer_ has quit IRC23:28
*** dkehn__ is now known as dkehn_23:28
*** EricGonczer_ has joined #openstack-meeting-alt23:28
*** jmckind has quit IRC23:32
*** hoangcx has joined #openstack-meeting-alt23:32
*** dtrainor has quit IRC23:34
*** dtrainor has joined #openstack-meeting-alt23:37
*** EricGonczer_ has quit IRC23:37
*** ansmith has joined #openstack-meeting-alt23:38
*** noslzzp has quit IRC23:44
*** noslzzp has joined #openstack-meeting-alt23:45
*** dtrainor has quit IRC23:46
*** phschwartz has quit IRC23:49
*** yamamoto_ has quit IRC23:50
*** ayoung has joined #openstack-meeting-alt23:51
*** dtrainor has joined #openstack-meeting-alt23:55
*** panda is now known as panda|Zz23:59

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