Monday, 2018-04-02

*** EmilienM_ has joined #openstack-meeting-alt00:04
*** ianychoi has quit IRC00:14
*** ianychoi has joined #openstack-meeting-alt00:17
*** markvoelker has joined #openstack-meeting-alt00:24
*** hongbin has joined #openstack-meeting-alt00:24
*** edmondsw has joined #openstack-meeting-alt00:25
*** edmondsw has quit IRC00:29
*** d0ugal has quit IRC00:35
*** shu-mutow-AWAY is now known as shu-mutow00:40
*** markvoelker has quit IRC00:42
*** markvoelker has joined #openstack-meeting-alt00:42
*** d0ugal has joined #openstack-meeting-alt00:44
*** EmilienM_ is now known as EmilienM00:48
*** EmilienM has joined #openstack-meeting-alt00:48
*** dizquierdo has quit IRC01:03
*** yangyapeng has joined #openstack-meeting-alt01:21
*** caowei has joined #openstack-meeting-alt01:23
*** salv-orl_ has joined #openstack-meeting-alt01:24
*** salv-orlando has quit IRC01:26
*** mhen has quit IRC01:28
*** mhen has joined #openstack-meeting-alt01:33
*** d0ugal has quit IRC01:35
*** spzala has joined #openstack-meeting-alt01:38
*** david-lyle has quit IRC01:40
*** dklyle has joined #openstack-meeting-alt01:40
*** d0ugal has joined #openstack-meeting-alt01:43
*** spzala has quit IRC01:47
*** yamahata has joined #openstack-meeting-alt02:02
*** iyamahat has joined #openstack-meeting-alt02:03
*** chkumar246 has quit IRC02:03
*** dklyle has quit IRC02:05
*** david-lyle has joined #openstack-meeting-alt02:05
*** edmondsw has joined #openstack-meeting-alt02:13
*** edmondsw has quit IRC02:17
*** chandankumar has joined #openstack-meeting-alt02:21
*** spzala has joined #openstack-meeting-alt02:23
*** dalgaaf has quit IRC02:25
*** dalgaaf has joined #openstack-meeting-alt02:26
*** dsariel has quit IRC02:26
*** cloudrancher has quit IRC02:27
*** spzala has quit IRC02:27
*** cloudrancher has joined #openstack-meeting-alt02:28
*** janki has joined #openstack-meeting-alt02:29
*** d0ugal has quit IRC02:37
*** gcb has joined #openstack-meeting-alt02:40
*** d0ugal has joined #openstack-meeting-alt02:43
*** ianychoi has quit IRC02:48
*** janki has quit IRC02:57
*** ianychoi has joined #openstack-meeting-alt02:58
*** pgadiya has joined #openstack-meeting-alt03:08
*** spzala has joined #openstack-meeting-alt03:11
*** spzala has quit IRC03:11
*** ianychoi has quit IRC03:12
*** ianychoi has joined #openstack-meeting-alt03:13
*** janki has joined #openstack-meeting-alt03:22
*** janki has quit IRC03:23
*** janki has joined #openstack-meeting-alt03:23
*** yamamoto has joined #openstack-meeting-alt03:26
*** rwsu has joined #openstack-meeting-alt03:26
*** pgadiya has quit IRC03:29
*** zhongjun_ has quit IRC03:39
*** caowei has quit IRC03:41
*** pgadiya has joined #openstack-meeting-alt03:41
*** Zames has joined #openstack-meeting-alt03:49
*** hongbin has quit IRC03:49
*** Zames has quit IRC03:51
*** caowei has joined #openstack-meeting-alt04:15
*** d0ugal has quit IRC04:23
*** ianychoi has quit IRC04:35
*** ianychoi has joined #openstack-meeting-alt04:36
*** Sukhdev has joined #openstack-meeting-alt04:43
*** d0ugal has joined #openstack-meeting-alt04:46
*** links has joined #openstack-meeting-alt04:46
*** jchhatbar has joined #openstack-meeting-alt04:51
*** jchhatbar has quit IRC04:51
*** jchhatbar has joined #openstack-meeting-alt04:52
*** janki has quit IRC04:54
*** ianychoi has quit IRC05:00
*** ianychoi has joined #openstack-meeting-alt05:02
*** links has quit IRC05:04
*** chandankumar has quit IRC05:04
*** links has joined #openstack-meeting-alt05:05
*** Sukhdev has quit IRC05:13
*** iyamahat has quit IRC05:21
*** chkumar246 has joined #openstack-meeting-alt05:22
*** yangyapeng has quit IRC05:23
*** pgadiya has quit IRC05:30
*** jbadiapa has joined #openstack-meeting-alt05:35
*** trinaths has joined #openstack-meeting-alt05:40
*** jchhatbar has quit IRC05:43
*** jchhatbar has joined #openstack-meeting-alt05:43
*** d0ugal has quit IRC05:48
*** anilvenkata has joined #openstack-meeting-alt05:50
*** marios has joined #openstack-meeting-alt05:50
*** pgadiya has joined #openstack-meeting-alt05:51
*** d0ugal has joined #openstack-meeting-alt05:55
*** lpetrut has joined #openstack-meeting-alt06:09
*** dsariel has joined #openstack-meeting-alt06:13
*** yamamoto_ has joined #openstack-meeting-alt06:18
*** yamamoto has quit IRC06:21
*** yamamoto has joined #openstack-meeting-alt06:29
*** chkumar246 is now known as chandankumar06:29
*** chandankumar has quit IRC06:29
*** chandankumar has joined #openstack-meeting-alt06:30
*** pgadiya has quit IRC06:31
*** yamamoto_ has quit IRC06:32
*** pgadiya has joined #openstack-meeting-alt06:40
*** armaan has joined #openstack-meeting-alt06:44
*** HeOS has joined #openstack-meeting-alt06:55
*** chandankumar has quit IRC06:57
*** chandankumar has joined #openstack-meeting-alt07:04
*** alexchadin has joined #openstack-meeting-alt07:07
*** tesseract has joined #openstack-meeting-alt07:12
*** jchhatba_ has joined #openstack-meeting-alt07:12
*** jchhatba_ has quit IRC07:15
*** jchhatbar has quit IRC07:15
*** jchhatba_ has joined #openstack-meeting-alt07:15
*** jchhatba_ has quit IRC07:17
*** sridharg has joined #openstack-meeting-alt07:23
*** jtomasek has joined #openstack-meeting-alt07:42
*** jtomasek has quit IRC07:50
*** jtomasek has joined #openstack-meeting-alt07:52
*** armaan has quit IRC07:59
*** zhurong has joined #openstack-meeting-alt08:02
*** marius1 has joined #openstack-meeting-alt08:03
*** gcb has quit IRC08:03
*** pgadiya has quit IRC08:11
*** dsariel has quit IRC08:14
*** armaan has joined #openstack-meeting-alt08:15
*** gcb has joined #openstack-meeting-alt08:17
*** pgadiya has joined #openstack-meeting-alt08:19
*** marius1 has quit IRC08:20
*** alexchadin has quit IRC08:22
*** alexchadin has joined #openstack-meeting-alt08:25
*** d0ugal has quit IRC08:39
*** shu-mutow is now known as shu-mutow-AWAY08:42
*** jtomasek has quit IRC08:44
*** yamamoto has quit IRC08:51
*** ianychoi has quit IRC08:52
*** ianychoi has joined #openstack-meeting-alt08:54
*** numans has quit IRC08:57
*** numans has joined #openstack-meeting-alt08:58
*** yamamoto has joined #openstack-meeting-alt09:00
*** HeOS has quit IRC09:01
*** zhurong has quit IRC09:02
*** d0ugal has joined #openstack-meeting-alt09:03
*** HeOS has joined #openstack-meeting-alt09:20
*** ianychoi has quit IRC09:24
*** dsariel has joined #openstack-meeting-alt09:25
*** ianychoi has joined #openstack-meeting-alt09:25
*** alexchadin has quit IRC09:36
*** alexchadin has joined #openstack-meeting-alt09:38
*** armaan has quit IRC09:40
*** chandankumar has quit IRC09:40
*** armaan has joined #openstack-meeting-alt09:40
*** Zames_ has joined #openstack-meeting-alt09:41
*** chandankumar has joined #openstack-meeting-alt09:42
*** ianychoi has quit IRC09:44
*** ianychoi has joined #openstack-meeting-alt09:45
*** alexchadin has quit IRC09:51
*** Zames_ has quit IRC09:52
*** Zames_ has joined #openstack-meeting-alt09:53
*** Zames_ has quit IRC09:53
*** Zames_ has joined #openstack-meeting-alt09:55
*** Zames_ has joined #openstack-meeting-alt09:55
*** armaan has quit IRC09:56
*** armaan has joined #openstack-meeting-alt09:56
*** trinaths has quit IRC09:57
*** anilvenkata has quit IRC09:57
*** Zames_ has quit IRC10:08
*** anilvenkata has joined #openstack-meeting-alt10:09
*** anilvenkata has quit IRC10:11
*** anilvenkata has joined #openstack-meeting-alt10:11
*** armaan has quit IRC10:15
*** ianychoi has quit IRC10:16
*** armaan has joined #openstack-meeting-alt10:16
*** ianychoi has joined #openstack-meeting-alt10:17
*** ianychoi has quit IRC10:31
*** ianychoi has joined #openstack-meeting-alt10:38
*** caowei has quit IRC10:43
*** ianychoi has quit IRC10:43
*** pbourke has quit IRC10:46
*** pbourke has joined #openstack-meeting-alt10:47
*** ganso has joined #openstack-meeting-alt10:56
*** chhagarw has joined #openstack-meeting-alt10:59
*** ianychoi has joined #openstack-meeting-alt10:59
*** d0ugal has quit IRC11:00
*** alexchadin has joined #openstack-meeting-alt11:04
*** chandankumar has quit IRC11:04
*** links has quit IRC11:04
*** links has joined #openstack-meeting-alt11:05
*** trinaths has joined #openstack-meeting-alt11:10
*** zhurong has joined #openstack-meeting-alt11:19
*** chkumar246 has joined #openstack-meeting-alt11:21
*** tpsilva has joined #openstack-meeting-alt11:21
*** ianychoi has quit IRC11:26
*** ianychoi has joined #openstack-meeting-alt11:27
*** d0ugal has joined #openstack-meeting-alt11:29
*** toscalix_ has joined #openstack-meeting-alt11:31
*** toscalix_ has quit IRC11:45
*** toscalix_ has joined #openstack-meeting-alt11:48
*** dprince has joined #openstack-meeting-alt11:53
*** rfolco has joined #openstack-meeting-alt11:54
*** rfolco is now known as rfolco|ruck11:59
*** jaypipes has joined #openstack-meeting-alt12:01
*** lbragstad has joined #openstack-meeting-alt12:03
*** raildo has joined #openstack-meeting-alt12:06
*** pgadiya has quit IRC12:11
*** weshay_mod is now known as weshay12:12
*** jcoufal has joined #openstack-meeting-alt12:13
*** alexchadin has quit IRC12:20
*** pgadiya has joined #openstack-meeting-alt12:24
*** d0ugal has quit IRC12:25
*** d0ugal has joined #openstack-meeting-alt12:25
*** d0ugal has quit IRC12:25
*** d0ugal has joined #openstack-meeting-alt12:25
*** pgadiya has quit IRC12:28
*** zhurong has quit IRC12:34
*** kumarmn has quit IRC12:41
*** edmondsw has joined #openstack-meeting-alt12:43
*** trinaths has quit IRC12:43
*** toscalix_ has quit IRC12:43
*** gouthamr has joined #openstack-meeting-alt12:47
*** vgreen has joined #openstack-meeting-alt12:51
*** dustins has joined #openstack-meeting-alt12:53
*** toscalix_ has joined #openstack-meeting-alt12:53
*** toscalix_ has quit IRC12:56
*** david-lyle has quit IRC12:58
*** david-lyle has joined #openstack-meeting-alt12:59
*** kumarmn has joined #openstack-meeting-alt13:00
*** kumarmn has quit IRC13:00
*** kumarmn has joined #openstack-meeting-alt13:00
*** cloudrancher has quit IRC13:02
*** cloudrancher has joined #openstack-meeting-alt13:03
*** david-lyle has quit IRC13:09
*** jroll has quit IRC13:19
*** jroll has joined #openstack-meeting-alt13:20
*** fnaval has joined #openstack-meeting-alt13:28
*** julim has quit IRC13:31
*** julim has joined #openstack-meeting-alt13:32
*** felipemonteiro__ has joined #openstack-meeting-alt13:32
*** yamamoto has quit IRC13:37
*** yamamoto has joined #openstack-meeting-alt13:37
*** _pewp_ has quit IRC13:39
*** felipemonteiro_ has joined #openstack-meeting-alt13:39
*** felipemonteiro__ has quit IRC13:42
*** links has quit IRC13:48
*** yangyapeng has joined #openstack-meeting-alt13:52
*** gouthamr has quit IRC13:53
*** gouthamr has joined #openstack-meeting-alt13:54
*** yangyapeng has quit IRC13:56
*** takashin has joined #openstack-meeting-alt13:56
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Apr  2 14:00:12 2018 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
edleafeWho's here?14:00
*** gouthamr has quit IRC14:00
alex_xu_o/14:00
takashino/14:00
fried_bunnyรถ/14:00
*** gouthamr has joined #openstack-meeting-alt14:00
edleafeMight be a light crowd, since many have off for the fried_bunny holiday14:01
jaypipeso/14:01
* alex_xu_ just found that it is not only Chinese eat bunny14:02
edleafe:)14:02
fried_bunny"Mississippi Fried Bunny to compete with KFC"14:03
*** hongbin has joined #openstack-meeting-alt14:04
edleafealex_xu_: https://www.youtube.com/watch?v=Yxiv3CBMS4M14:04
*** lpetrut has quit IRC14:05
edleafeOK, let's start14:05
alex_xu_haha14:05
edleafecdent put together a frighteningly long list of what's on our plate in his last placement update email14:05
edleafeSo I'm gonna paste 'em here14:05
fried_bunny+1 to frightening14:06
edleafe#topic Specs14:06
*** openstack changes topic to "Specs (Meeting topic: nova_scheduler)"14:06
edleafe#link VMware: place instances on resource pool (using update_provider_tree) https://review.openstack.org/#/c/549067/14:06
edleafe#link Provide error codes for placement API https://review.openstack.org/#/c/418393/14:06
edleafe#link mirror nova host aggregates to placement API https://review.openstack.org/#/c/545057/14:06
edleafe#link Proposes NUMA topology with RPs https://review.openstack.org/#/c/552924/14:06
edleafe#link Account for host agg allocation ratio in placement https://review.openstack.org/#/c/544683/14:06
edleafe#link Spec for isolating configuration of placement database https://review.openstack.org/#/c/552927/14:06
edleafe#link Support default allocation ratios https://review.openstack.org/#/c/552105/14:06
edleafe#link Spec on preemptible servers https://review.openstack.org/#/c/438640/14:06
edleafe#link Handle nested providers for allocation candidates https://review.openstack.org/#/c/556873/14:06
edleafe#link Add Generation to Consumers https://review.openstack.org/#/c/556971/14:06
edleafe#link Mention (no) granular support for image traits https://review.openstack.org/#/c/554305/14:06
edleafe#link Update the vGPU spec https://review.openstack.org/#/c/557912/14:06
edleafe#link Proposes Multiple GPU types https://review.openstack.org/#/c/557065/14:06
edleafe#link Standardize CPU resource tracking https://review.openstack.org/#/c/555081/14:06
edleafe#link NUMA-aware live migration https://review.openstack.org/#/c/552722/14:06
edleafe#link Network bandwidth resource provider https://review.openstack.org/#/c/502306/14:06
edleafe#link Propose counting quota usage from placement https://review.openstack.org/#/c/509042/14:07
edleafe#link Fix endpoint URI /allocation_requests (reality fix) https://review.openstack.org/#/c/557580/14:07
edleafe(whew!)14:07
fried_bunnyTBC, this is doesn't include specs we've *already approved* (and thus slated for Rocky).14:07
edleafeWe couldn't go through them 1-by-1 if we wanted to. So are there any that we need to discuss?14:07
edleafefried_bunny: true dat14:07
*** gouthamr has quit IRC14:09
edleafeOK, I guess nothing too controversial in specs.14:09
edleafe#topic reviews14:09
*** openstack changes topic to "reviews (Meeting topic: nova_scheduler)"14:09
fried_bunnyexcept for there being too many for us to possibly handle in Rocky14:09
*** gouthamr has joined #openstack-meeting-alt14:09
edleafefried_bunny: yeah, that will be discussed in Opens14:09
edleafeOnce again, we can't handle them individually, so here are all of them:14:10
edleafe#link Update Provider Tree https://review.openstack.org/#/q/topic:bp/update-provider-tree14:10
edleafe#link Neste resource providers htttps://review.openstack.org/#/q/topic:bp/nested-resource-providers14:10
edleafe#link Nested providers in allocation candidates htttps://review.openstack.org/#/q/topic:bp/nested-resource-providers-allocation-candidates14:10
edleafe#link Request Filters htttps://review.openstack.org/#/q/topic:bp/placement-req-filter14:10
edleafe#link Mirror nova host aggregates to placement htttps://review.openstack.org/#/q/topic:bp/placement-mirror-host-aggregates14:10
edleafe#link Forbidden Traits htttps://review.openstack.org/#/q/topic:bp/placement-forbidden-traits14:10
edleafe#link Consumer Generations htttps://review.openstack.org/#/q/topic:bp/add-consumer-generation14:10
edleafe#link Extraction htttps://review.openstack.org/#/q/topic:bp/placement-extract14:10
edleafe#link Optional Placement DB htttps://review.openstack.org/#/c/552927/14:10
edleafe#link Purge comp_node and res_prvdr records during deletion of cells/hosts https://review.openstack.org/#/c/546660/14:10
edleafe#link A huge pile of improvements to osc-placement https://review.openstack.org/#/q/topic:bp/placement-osc-plugin-rocky14:10
edleafe#link Add compute capabilities traits (to os-traits) https://review.openstack.org/#/c/546713/14:11
edleafe#link General policy sample file for placement https://review.openstack.org/#/c/524425/14:11
edleafe#link Provide framework for setting placement error codes https://review.openstack.org/#/c/546177/14:11
edleafe#link Get resource provider by uuid or name (osc-placement) https://review.openstack.org/#/c/527791/14:11
edleafe#link Fix comments in get_all_with_shared() https://review.openstack.org/#/c/533195/14:11
edleafe#link Fixes related to shared providers https://review.openstack.org/#/q/topic:bug/173273114:11
edleafe#link placement: Make API history doc more consistent https://review.openstack.org/#/c/477478/14:11
edleafe#link Add to contributor docs about handler testing https://review.openstack.org/#/c/557355/14:11
edleafe#link doc: Upgrade placement first https://review.openstack.org/#/c/556631/14:11
edleafe#link Handle agg generation conflict in report client https://review.openstack.org/#/c/556669/14:11
edleafe#link Slugification utilities for placement names https://review.openstack.org/#/c/556628/14:11
edleafe#link Remove usage of [placement]os_region_name https://review.openstack.org/#/c/557086/14:11
edleafe#link Get rid of 406 paths in report client https://review.openstack.org/#/c/556633/14:11
edleafe#link Add unit test for non-placement resize https://review.openstack.org/#/c/537614/14:11
edleafe#link Address issues raised in adding member_of to GET /a-c https://review.openstack.org/#/c/554357/14:11
edleafe#link Fix allocation_candidates not to ignore shared RPs https://review.openstack.org/#/c/533396/14:11
edleafe#link Sharing-related bug fixes https://review.openstack.org/#/q/topic:bug/172461314:11
edleafe#link More sharing related bug fixes https://review.openstack.org/#/q/topic:bug/173273114:11
edleafe#link Cover migration cases with functional tests https://review.openstack.org/#/c/493865/14:11
edleafeAre there any of these reviews we need to discuss individually here?14:11
fried_bunnyI'd like to discuss the series starting at https://review.openstack.org/#/c/558044/14:12
fried_bunnyMainly to get advice on where microversions are or aren't needed.14:12
*** dsariel has quit IRC14:12
fried_bunnyThis has three patches that change behavior.14:12
fried_bunnyhttps://review.openstack.org/#/c/558045/ changes the provider_summaries to include *all* the resources in a provider, not just the ones relating to the request.14:12
fried_bunnyjaypipes: We decided we wanted to do that, right?14:13
edleafefried_bunny: what was the reason for that change?14:13
fried_bunnyI don't remember the rationale, to be honest.  I imagine it could be useful for a weigher.14:14
*** gouthamr has quit IRC14:14
edleafeOIC. Well, if we do make that change, it's definitely a new microversion14:15
fried_bunnyI know that it helped me with something later in the series.  But that doesn't mean we couldn't filter 'em back out before returning, I suppose.14:15
alex_xu_yes, I also think about that14:15
fried_bunnyokay, that's what I thought for that one.  And tetsuro has done so (since last night).  So cool there.14:15
fried_bunnyNext14:15
fried_bunnyhttps://review.openstack.org/#/c/533437/ now allows you to have an "anchor" provider in play.  I sent email about this.14:15
alex_xu_fried_bunny: we required spec for new microversion14:16
fried_bunnyTL;DR: if you have a CN that doesn't provide resources itself, but is agg-associated with sharing providers that do provide resource to the request, you should be able to get results there.14:16
fried_bunnyToday, you get no results.14:16
fried_bunnyThat patch fixes it so you do get results.14:16
fried_bunnyIMO, this one's fixing broken behavior, so doesn't need a microversion.14:16
fried_bunnybut... thoughts?14:17
fried_bunnyalex_xu_: That's a good point.  I'd like to come back to whether we actually want/need that first behavior at all.14:17
edleafeThis also touches on the notion that every API change must be a separate microversion. I don't agree with that approach, since microversions are made on a per-call basis14:17
edleafeI'd rather see related changes in a single microversion14:18
*** gouthamr has joined #openstack-meeting-alt14:18
alex_xu_there are a lot of breaking case in the shard rp14:18
alex_xu_I also remember we fixed few cases for shared rp, and we didn't bump microversion last release14:18
jaypipesalex_xu_: example?14:18
jaypipesfried_bunny: I still haven't gotten through your anchor providers ML post.14:19
edleafewere they bug fixes, or just behavior changes?14:19
* alex_xu_ find the link14:19
alex_xu_jaypipes: https://review.openstack.org/48037914:19
*** gouthamr has quit IRC14:19
alex_xu_fried_bunny told me that already fixed by the refactor you done last release14:20
*** chkumar246 has quit IRC14:20
alex_xu_the refactor of shared and non-shared code in the allocation candidates14:20
*** gouthamr has joined #openstack-meeting-alt14:21
fried_bunnyedleafe: That's often debatable.  As is the case here, I think.14:22
alex_xu_I also remember we said we didn't support shared rp offcially14:23
alex_xu_maybe we can bump a microversion when we fix all the cases, that microversion is signal the shared rp works now14:23
jaypipesalex_xu_: well, a) we haven't merged any of that code and b) I don't see how any code that has merged already has affected the public API?14:24
fried_bunnyFinally, https://review.openstack.org/#/c/558014/ makes it so that, in the "anchor" case, the anchor RP actually shows up in the allocation request (with empty resources) and provider summaries (with, because of that first patch, *all* of its resources, even though none were used in the request).14:25
alex_xu_ok, acutally I didn't check that code again14:25
alex_xu_I should verify the testcase fried_bunny mentioned, but didn't get a chance yet14:26
fried_bunnyIn this case, if we go for that second one as it is, we would arguably need a microversion for this third one.  BUT if we squash 2 & 3 together, we can probably get away with *no* microversion, because the behavior change as a whole is enabling a broken behavior.14:26
*** dsariel has joined #openstack-meeting-alt14:26
fried_bunnyNow, as alex_xu_ suggests, it's possible we should roll 2&3 into a microversion where we declare support for sharing providers.  And basically we can do whatever we want up until then with sharing providers because we don't claim to support them at all.14:27
* fried_bunny steps back14:27
fried_bunnyIt's also possible we just want to punt this whole series to Stein...14:28
fried_bunny...and focus on nrp, granular, upt, forbidden, member_of, etc.14:28
edleafefried_bunny: that's kind of my thinking. Sure, it would be great to get this, but we keep finding more important things to work on14:29
fried_bunnybasically continue declaring no official support for sharing providers.14:29
*** yangyapeng has joined #openstack-meeting-alt14:29
fried_bunnyjaypipes: What's your take on the first part - including all resources in provider summaries?  Do you remember why we wanted to do that?14:30
fried_bunny...or even IF we wanted to do that?  Maybe tetsuro and I just made it up in our heads.14:30
jaypipesfried_bunny: you mean why we *didn't* do that, right?14:30
fried_bunnyshrug, I suspect the reason it is the way it is is more of a side effect of the impl than a conscious design decision.14:31
jaypipesfried_bunny: not sure there was a deliberate thought behind that. probably just that we already had the resources dict representing the resources that are requested and we simply just put a WHERE condition on the keys in that dict.14:31
fried_bunnyexactly14:31
fried_bunnyI think perhaps I extrapolated something we said about NRP, which was that we want p_s to show all the RPs in the tree, even the ones not providing resource.14:32
jaypipesfried_bunny: "Give me all your things that have oranges. OK, here they are, and some also have apples"14:32
fried_bunnyjaypipes: IMO, provider_summaries answers "what's in the grove?".14:32
jaypipesfried_bunny: is it useful information? maybe... is it a priority right now? not sure about that.14:32
edleafefried_bunny: was there a use case that precipitated this work?14:33
fried_bunnyedleafe: I was reviewing tetsuro's work on anchor providers, which I think he was doing in response to open bugs.14:33
fried_bunnyIt was complicated code he was modifying in complicated ways, so I got really deep into it and I guess lost perspective on whether it meshed with our current priorities.14:34
*** gouthamr has quit IRC14:34
fried_bunnyHaving had this discussion now, given that one of the things we want to get out of this meeting is, "how do we manage scope?" I can be convinced that we should table the series for Stein.14:34
*** gouthamr has joined #openstack-meeting-alt14:35
jaypipesfried_bunny: ++14:35
fried_bunnyPerhaps a procedural -2 jaypipes?14:35
edleafemakes sense14:35
jaypipeswe have plenty of other things to focus on.14:35
fried_bunny...with a link to this discussion14:35
jaypipesfried_bunny: after I fully consume your ML post about it, sure.14:35
fried_bunnyBit of a shame since it's pretty much working at this point.  But for sake of reviewer bandwidth, microversion noise, spec requirements, etc...14:36
fried_bunnyLet's move on.14:36
fried_bunnyI have one other thing I'd like to call attention to.14:36
edleafego for it14:37
fried_bunnybug 176032214:37
openstackbug 1760322 in OpenStack Compute (nova) "Traits not synced if first retrieval fails" [Undecided,In progress] https://launchpad.net/bugs/1760322 - Assigned to Eric Fried (efried)14:37
fried_bunnytest case: https://review.openstack.org/#/c/558066/14:37
fried_bunny(bad, horrible) fix: https://review.openstack.org/#/c/558068/14:37
jaypipescurrently reviewing that...14:37
fried_bunnyjaypipes: I think the right fix is to make _ensure_trait_sync run in its own transaction, regardless of the context around it.  Is that possible?14:38
fried_bunny(btw, I agree with tetsuro's comment on the test case patch, and got that all fixed up only to mess up the rebase locally, so Ima have to redo it)14:38
jaypipesfried_bunny: not sure that is possible. at least, not if we want to trigger that being run from our context-decorated staticmethods...14:39
fried_bunnyokay.  Well, consider your attention done broughten to it.  We can finish the discussion in the review.  And it's probably something cdent will want to look at.14:40
edleafefried_bunny: why wouldn't you do the sync check in _ensure_trait_sync, and set the global there accordingly?14:40
*** david-lyle has joined #openstack-meeting-alt14:40
jaypipesalex_xu_: do NOT copy fried_bunny's use of wrong English above.14:40
jaypipesalex_xu_: "broughten" is not a word.14:40
*** namnh has joined #openstack-meeting-alt14:41
fried_bunnyedleafe: That's what's being done.  And it turns out wrong when the encompassing method raises an exception, because the db transaction gets rolled back, but the global doesn't get unset.14:41
fried_bunnyAt least I think that's what's going on.14:41
alex_xu_jaypipes: ok...14:42
edleafeI'd have to look at it more closely, but it seems like the check is in the wrong place.14:42
fried_bunnyPerhaps there's a way to set a flag to say "commit the transaction even when I raise an exception from here"?14:42
jaypipesfried_bunny: I'll comment on the review.14:42
edleafeme too14:42
fried_bunnyA provably correct way to do it would be to have the _TRAITS_SYNCED flag in the database itself.  So it's part of the transaction.  But that's a tad icky.14:42
*** tesseract has quit IRC14:42
*** tesseract-RH has joined #openstack-meeting-alt14:42
edleafeick ick ick14:43
fried_bunnyokay, triple icky.14:43
fried_bunnycool, moving on.14:43
fried_bunnythanks for indulging me, y'all.14:43
* alex_xu_ still can stop google https://en.wiktionary.org/wiki/broughten14:43
edleafeAny other reviews to discuss?14:43
*** dtrainor has joined #openstack-meeting-alt14:43
fried_bunnyhttps://www.youtube.com/watch?v=tq08yOneY_014:44
edleafealex_xu_: it's considered "substandard": https://www.merriam-webster.com/dictionary/broughten14:44
*** david-lyle is now known as dklyle14:44
edleafeok, let's move on14:45
edleafe#topic Bugs14:45
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:45
edleafe#link Placement Bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement&orderby=-id14:45
edleafe3 new ones this week14:45
edleafewe've already discussed 2 of 'em14:46
edleafethe third has to do with some doc errors14:46
*** cloudrancher has quit IRC14:46
edleafeSo let's move on to the main topic14:46
edleafe#topic Open Discussion14:47
*** openstack changes topic to "Open Discussion (Meeting topic: nova_scheduler)"14:47
*** markstur has joined #openstack-meeting-alt14:47
*** markstur has quit IRC14:47
edleafeWe're taking on a *lot* of stuff14:47
*** markstur has joined #openstack-meeting-alt14:47
*** cloudrancher has joined #openstack-meeting-alt14:47
edleafecdent mentioned this in his last placement update14:47
edleafe#link cdent's email on Placement Overload http://lists.openstack.org/pipermail/openstack-dev/2018-March/128924.html14:48
fried_bunnyOne thing we can do is start looking at specs from a perspective of "Can we do this in Rocky" as opposed to "Do we want this and is it workable".  I think we've been doing pretty much exclusively the latter thus for.14:48
fried_bunnyfar14:48
edleafeI don't know about that. Having a spec approved and then punting the development makes it simpler to revist in the next cycle14:49
fried_bunnyWe may even consider re-evaluating blueprints we've already approved in that light.14:49
edleafePerhaps we should have some sort of "priorities list"14:49
fried_bunnyedleafe: Yeah, we can mark a blueprint approved for next cycle.14:49
edleafe:)14:49
fried_bunnybut not sure how the paperwork works out for the spec being in specs/rocky/approved14:49
fried_bunnyPerhaps we want to introduce a specs/future/approved14:50
fried_bunnyand then they move into specs/<currentrelease>/approved when the bp gets approved for that release.14:50
edleafefried_bunny: it has to be re-proposed in Stein, taking into account any changes that will be needed14:50
fried_bunnyokay; specs/rocky/approved-but-not-for-this-release/ ?14:50
*** takashin has quit IRC14:50
fried_bunnysomething to separate 'em out.14:51
edleafeIOW, I propose to do X by changing Y in a certain way, but before the next cycle, other things have changed Y.14:51
edleafefried_bunny: that's14:51
fried_bunnyyeah, I get it.14:51
edleafethat's "backlog"14:51
fried_bunnySure.  So what I'm saying is that right now we don't have a good demarcation of backlog vs nowlog14:52
edleafe:)14:52
fried_bunnywhich makes it hard to understand the content of a release.14:52
fried_bunnyand makes it look like we don't get done what we say we're going to get done.  Which we *also* don't.14:52
*** Sukhdev_ has joined #openstack-meeting-alt14:53
fried_bunnyThis is probably something to discuss in the nova meeting, with more cores and the PTL at hand.14:53
fried_bunnydo we have anything specifically in the scheduler area that we can do to limit scope?14:54
edleafeBut that's not unexpected. I don't think we have ever finished all our specs before the end of the cycle, and then sat around wondering how we will occupy our time14:54
fried_bunnyI assert that's a problem.14:54
fried_bunnyNot that we don't have spare time, but that we *never* finish the specs we approved for a cycle.14:54
fried_bunnyor even come close.14:55
*** Leo_m has joined #openstack-meeting-alt14:55
fried_bunnyIt's become the expectation, the status quo.14:55
edleafefried_bunny: yes, we have an etherpad14:55
edleafe#link Rocky priority etherpad https://etherpad.openstack.org/p/rocky-nova-priorities-tracking14:55
*** spotz_ has joined #openstack-meeting-alt14:55
edleafeWe need to get better about updating that sucker14:55
fried_bunny4 minutes.14:56
*** lpetrut has joined #openstack-meeting-alt14:57
edleafeok, I'll put an item on next week's agenda to work on the etherpad. In the meantime, let's add the specs/reviews we feel are important to the etherpad, and we can order them next week14:58
*** spotz_ is now known as spotz14:59
edleafeAny last-minute (literally) items?14:59
edleafe#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Mon Apr  2 14:59:40 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-04-02-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-04-02-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-04-02-14.00.log.html14:59
*** Zames has joined #openstack-meeting-alt14:59
fried_bunnyedleafe: While you're working the agenda, fix those htttps links?15:00
*** manjeet has joined #openstack-meeting-alt15:01
*** takashin has joined #openstack-meeting-alt15:02
*** Zames has quit IRC15:02
*** anilvenkata has quit IRC15:04
*** takashin has left #openstack-meeting-alt15:05
edleafefried_bunny: which links?15:08
fried_bunnyedleafe: About a third of the spec links aren't showing up as hyperlinks because https is misspelled htttps15:09
fried_bunnyedleafe: Sorry, review links, not specs links.15:09
*** manjeet has quit IRC15:11
*** iyamahat has joined #openstack-meeting-alt15:16
*** cloudrancher has quit IRC15:17
*** cloudrancher has joined #openstack-meeting-alt15:18
*** _pewp_ has joined #openstack-meeting-alt15:21
*** gouthamr has quit IRC15:23
*** gouthamr has joined #openstack-meeting-alt15:27
*** armaan has quit IRC15:28
*** armaan has joined #openstack-meeting-alt15:29
*** jcoufal has quit IRC15:33
*** ircuser-1 has quit IRC15:34
*** ianychoi has quit IRC15:34
*** jcoufal has joined #openstack-meeting-alt15:36
*** jcoufal has quit IRC15:40
*** cloudrancher has quit IRC15:40
*** bhavik1 has joined #openstack-meeting-alt15:43
*** armaan has quit IRC15:47
*** jcoufal has joined #openstack-meeting-alt15:48
*** gouthamr has quit IRC15:48
*** gouthamr has joined #openstack-meeting-alt15:49
*** felipemonteiro_ has quit IRC15:50
*** bhavik1 has quit IRC15:52
*** felipemonteiro has joined #openstack-meeting-alt15:55
*** felipemonteiro_ has joined #openstack-meeting-alt15:57
*** yangyapeng has quit IRC15:58
*** ianychoi has joined #openstack-meeting-alt15:58
*** felipemonteiro has quit IRC16:01
*** ianychoi has quit IRC16:06
*** armaan has joined #openstack-meeting-alt16:06
*** ianychoi has joined #openstack-meeting-alt16:07
*** gouthamr has quit IRC16:07
*** lpetrut has quit IRC16:08
*** gouthamr has joined #openstack-meeting-alt16:09
*** georgelorch has quit IRC16:19
*** Sukhdev has joined #openstack-meeting-alt16:23
*** dprince has quit IRC16:26
*** marios has quit IRC16:27
*** felipemonteiro_ has quit IRC16:29
*** felipemonteiro__ has joined #openstack-meeting-alt16:29
*** HeOS has quit IRC16:31
*** gouthamr has quit IRC16:33
*** yamamoto has quit IRC16:33
*** toscalix has joined #openstack-meeting-alt16:35
*** armaan has quit IRC16:35
*** clopez_ has quit IRC16:41
*** yamamoto has joined #openstack-meeting-alt16:42
*** clopez has joined #openstack-meeting-alt16:46
*** cloudrancher has joined #openstack-meeting-alt16:50
*** david-lyle has joined #openstack-meeting-alt16:51
*** dklyle has quit IRC16:51
*** yamamoto has quit IRC16:59
*** ganso has left #openstack-meeting-alt17:04
*** david-lyle has quit IRC17:06
*** david-lyle has joined #openstack-meeting-alt17:06
*** david-lyle has quit IRC17:07
*** david-lyle has joined #openstack-meeting-alt17:07
*** namnh has quit IRC17:12
*** david-lyle has quit IRC17:13
*** david-lyle has joined #openstack-meeting-alt17:18
*** felipemonteiro_ has joined #openstack-meeting-alt17:18
*** lpetrut has joined #openstack-meeting-alt17:19
*** felipemonteiro__ has quit IRC17:22
*** david-lyle has quit IRC17:23
*** lpetrut has quit IRC17:26
*** lpetrut has joined #openstack-meeting-alt17:26
*** dsariel has quit IRC17:32
*** tobiash has joined #openstack-meeting-alt17:34
*** felipemonteiro_ has quit IRC17:41
*** felipemonteiro_ has joined #openstack-meeting-alt17:41
*** Sukhdev has quit IRC17:46
*** dprince has joined #openstack-meeting-alt17:48
*** lpetrut has quit IRC17:52
*** dprince has quit IRC17:54
*** lpetrut has joined #openstack-meeting-alt17:54
*** toscalix has quit IRC17:59
*** yamamoto has joined #openstack-meeting-alt18:00
*** yamamoto has quit IRC18:06
*** vgreen has quit IRC18:09
*** dprince has joined #openstack-meeting-alt18:10
*** cloudrancher has quit IRC18:14
*** armaan has joined #openstack-meeting-alt18:18
*** dprince has quit IRC18:19
*** armaan has quit IRC18:27
*** armaan has joined #openstack-meeting-alt18:28
*** dprince has joined #openstack-meeting-alt18:32
*** vgreen has joined #openstack-meeting-alt18:35
*** yamamoto has joined #openstack-meeting-alt18:37
*** Swami has joined #openstack-meeting-alt18:42
*** yamamoto has quit IRC18:45
*** sridharg has quit IRC18:58
*** tesseract-RH has quit IRC19:01
*** namnh has joined #openstack-meeting-alt19:13
*** david-lyle has joined #openstack-meeting-alt19:14
*** david-lyle is now known as dklyle19:16
*** namnh has quit IRC19:17
*** jcoufal has quit IRC19:27
*** Leo_m_ has joined #openstack-meeting-alt19:36
*** Leo_m has quit IRC19:38
*** chhagarw has quit IRC19:38
*** harlowja has joined #openstack-meeting-alt19:38
*** spzala has joined #openstack-meeting-alt19:39
*** spzala has quit IRC19:39
*** gouthamr has joined #openstack-meeting-alt19:42
*** armaan has quit IRC19:43
*** armaan has joined #openstack-meeting-alt19:43
*** yamamoto has joined #openstack-meeting-alt19:45
*** marius1 has joined #openstack-meeting-alt19:50
*** yamamoto has quit IRC19:51
*** lpetrut has quit IRC19:51
*** armaan has quit IRC19:54
*** dsariel has joined #openstack-meeting-alt19:54
*** armaan has joined #openstack-meeting-alt19:54
*** armaan has quit IRC19:56
*** armaan_ has joined #openstack-meeting-alt19:56
*** vgreen has quit IRC20:03
*** rockyg has joined #openstack-meeting-alt20:08
*** Sukhdev_ has quit IRC20:12
*** iyamahat has quit IRC20:16
*** dprince has quit IRC20:16
*** yamahata has quit IRC20:17
*** raildo has quit IRC20:19
*** iyamahat has joined #openstack-meeting-alt20:30
*** rcernin has joined #openstack-meeting-alt20:31
*** dustins has quit IRC20:32
*** namnh has joined #openstack-meeting-alt20:35
*** namnh has quit IRC20:40
*** namnh has joined #openstack-meeting-alt20:46
*** yamahata has joined #openstack-meeting-alt20:46
*** yamamoto has joined #openstack-meeting-alt20:47
*** namnh has quit IRC20:50
*** matrohon has joined #openstack-meeting-alt20:51
*** yamamoto has quit IRC20:52
*** rockyg has quit IRC21:07
*** rockyg has joined #openstack-meeting-alt21:07
*** rockyg has quit IRC21:07
*** markstur has quit IRC21:12
*** dlenrow has quit IRC21:17
*** dlenrow has joined #openstack-meeting-alt21:18
*** gouthamr has quit IRC21:30
*** cloudrancher has joined #openstack-meeting-alt21:34
*** matrohon has quit IRC21:36
*** cloudrancher has quit IRC21:44
*** iyamahat_ has joined #openstack-meeting-alt21:44
*** iyamahat has quit IRC21:44
*** rfolco|ruck is now known as rfolco|off21:47
*** yamamoto has joined #openstack-meeting-alt21:48
*** HeOS has joined #openstack-meeting-alt21:52
*** yamamoto has quit IRC21:54
*** Shrews has joined #openstack-meeting-alt21:58
*** jlk has joined #openstack-meeting-alt21:59
corvushowdy zuul folks22:00
clarkbhello22:01
ianwo/22:01
Shrewssup22:01
pabelangero/22:01
* mordred waves22:01
corvus#startmeetign zuul22:01
jheskethMorning22:01
corvus#startmeetin' zuul22:02
corvus#startmeeting zuul22:02
openstackMeeting started Mon Apr  2 22:02:05 2018 UTC and is due to finish in 60 minutes.  The chair is corvus. 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
corvus#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:02
corvus#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-26-22.01.html22:02
corvus#topic action items22:02
*** openstack changes topic to "action items (Meeting topic: zuul)"22:02
corvuscorvus write automated query for private zuul stories (to find security issues)22:02
corvusnope didn't do that22:03
corvus#action corvus write automated query for private zuul stories (to find security issues)22:03
corvusmordred propose release-blocking javascript patches22:03
corvusdone!22:03
corvustobiash test most recent github3.py to see if it's ready to release22:03
corvusdone!22:03
corvusand... those being done... we released 3.0.022:03
corvus#topic Open discussion22:03
*** openstack changes topic to "Open discussion (Meeting topic: zuul)"22:03
mordred\o/22:03
pabelangeryay22:03
jlko/22:03
jheskethWoo!22:03
corvusso i'm not going to pester anyone about release blocking things this week :)22:03
corvusif you really want me to do some pestering, i'll say: weigh in on the meeting time vs abandon meeting thread :)22:04
corvusi've been going through the backlog of patches i've deferred reviewing until the v3 release22:05
corvusi'm up to early march now22:05
corvusit'll probably be a few more days before i get all the way through22:05
mordredif anyone wants to review some more javascript, https://review.openstack.org/#/c/551987/ and https://review.openstack.org/#/c/551989 are ready and the previews of them should be functional (thanks for the reviews on those jhesketh)22:05
Shrewscorvus: is there any sort of priority for nodepool features/reviews?22:06
corvusone common theme in my reviews is 'add a release note please' which, of course, we didn't have until recently, so it's natural changes will need updating for that.  hopefully folks have seen the note about using reno22:06
mordredreno++22:06
clarkbI recently used the docs we just merged about using reno and they worked for me22:07
Shrewsand i think we need a group decision on the zk retry stuff22:07
corvusShrews: i don't think so; hopefully our 'always be ready to release' approach makes that not entirely necessary.22:07
corvusShrews: can we distill that into a simple question?22:08
*** kumarmn has quit IRC22:08
Shrewscorvus: umm... i don't think so? (other than "do we use it or not"?)22:08
*** kumarmn has joined #openstack-meeting-alt22:08
corvusShrews: i haven't been convinced that we should use it in general.22:09
pabelangeryah, we had an issue on nb03.o.o over the weekend losing its connection to zookeeper and never reconnecting. Had to stop / start to fix it22:09
corvuspabelanger: *that* is a bug22:09
corvusbut that's not solved by "use retries everywhere"22:09
ianwthat is probably a good tester cause it's on a distant server on a sometimes unreliable network.  i feel like i've had to restart that before for similar reasons22:10
*** markstur has joined #openstack-meeting-alt22:10
corvusShrews: my understanding is that the retry discussion uncovered some places where we need to do some things differently, but that you and i both remain skeptical that using them globally is the right approach.22:11
Shrewscorvus: the discussion uncovered some things that had not been considered by tristanC. he proposed ways around them (sequences and ephemeral nodes). those ways to change the way we deal with session errors, but are untested22:12
*** markstur_ has joined #openstack-meeting-alt22:13
Shrewss/ways to/way/22:13
corvusShrews: oh, i thought i remember you saying you found a case unhandled by the current code.22:13
Shrewscorvus: ephemeral nodes are not handled well i think22:14
corvusShrews: what do you mean?22:14
*** kumarmn has quit IRC22:14
Shrewswell, i misspoke when i said there was a solution for ephemeral nodes. the final email on that was22:15
Shrews"they aren't used that much"22:15
Shrewsbut i think it affects zuul more than nodepool, so you'd need to weigh in on that i think22:16
Shrewsso i don't have a warm fuzzy feeling about dealing with those moving forward in the retry world22:16
*** markstur has quit IRC22:16
corvusi don't think the big issues have been addressed at all22:17
Shrewshttp://lists.zuul-ci.org/pipermail/zuul-discuss/2018-March/000079.html22:17
* fungi sneaks in late and sits in the back22:20
corvusShrews: what i'm concerned with is the behavior change.  i keep seeing things like "if zk disconnects then we don't upload a build" as a bug22:20
corvusit's not a bug, it's a feature22:20
corvusthis is a distributed system that is designed for parts to fail.  that means if we lose a builder, we expect another to take its place.  zk, for better or worse, is the way we decide that.22:21
corvusso, when we have issues like "a builder doesn't connect to zk after disconnect"  that's a bug that needs fixing.  when we have an issue like "my builder disconnected and didn't upload the thing it built" that is not a bug, it's the system working as designed22:22
corvusShrews: anyway, maybe this will shake out once we get around to reviewing the actual proposed patches?  or do you think we need to discuss on the ml more?22:23
Shrewscorvus: i've pretty much exhausted my concerns on the ML22:24
corvusShrews: what would you like to happen next?22:25
Shrewscorvus: i don't know. i'm happy with the current code. i just don't know the next steps with this22:25
Shrewsif it is "leave it the way it is", then i'm satisfied22:26
Shrewsif it is "let's try it", then we need to spend time rethinking our current code and session handling22:27
corvusShrews: then i think the immediate thing is to continue to maintain the current code.  we should take pabelanger's bug report and try to fix that.22:27
Shrewssure thing22:28
corvusShrews: meanwhile, i'll soon take a closer look at what tristan has actually written, and reply to the ml thread.  that'll probably be in a few days.  he should have all of our concerns so he can decide if he wants to continue to push for a redesign.22:28
corvusanyone else have anything to discuss?22:31
Shrewsmaybe if we make zk retry use containers, we can get more input!  :)22:31
corvusmordred: tell Shrews he's not helping22:31
mordredShrews: in soviet russia, containers use zk retry22:31
Shrews\o/22:31
mordredcorvus: oh, wait, maybe I did the opposite thing22:32
* fungi did not have anything to discuss22:33
clarkbI've pushed an infra-spec update to mark zuul v3 spec as done22:33
fungithe how-to-report-security-bugs change is up for review, and i'm still drafting the vulnerability management guidelines for zuul projects22:33
corvusfungi: thanks!22:33
corvusclarkb: that reminds me -- i need to send a msg to the ml asking about future design docs22:34
corvusbut while we're here -- maybe we can brainstorm22:34
*** kumarmn has joined #openstack-meeting-alt22:34
corvusif we wanted to make a big change to zuul (say, implement container support like Shrews is always going on about)22:34
corvuswhere should we write that document?22:34
corvusinfra-specs is where it would have previously gone, but seems weird to put it there now.22:35
corvusshould we put it in the zuul repo in a special section of the docs?22:35
corvusor should we make a zuul-specs repo?22:35
corvusor...?22:35
clarkbmaybe a specs doc dir in zuul itself? though that may cause confusion over what is and isn't implemented22:35
clarkbbut that way the existing zuul docs hosting will just work22:36
corvusi feel like if we put it in zuul docs, we could do it in a way that makes it clear.  though, obviously, folks working on openstack came to the opposite conclusion.22:36
corvusan advantage of that is that it's closer to the thing being modified.22:36
clarkbcorvus: ya, in general I've not liked how we split oepnstack docs into like 4 different locations22:36
corvusit might be a good idea not to land things there if no one is working on them though.  :)22:36
clarkbcorvus: its hard to navigate through the different locations that way whereas having a single tree amkes it more strightforward22:36
mordredcorvus: I've always liked the idea of a specs dir in the docs dir personally, so I'd be in favor of that ... at least until such a time as it becomes an issue22:37
*** gouthamr has joined #openstack-meeting-alt22:37
mordredcorvus: otoh - a single specs dir for the collection of zuul repos might be nicer22:38
mordredcorvus: so that there's a single place for zuul and nodepool and zuul-jobs things22:38
*** kumarmn has quit IRC22:38
mordred(unless we wanted that place to be the zuul repo - I just don't think having a separate set of specs in the nodepool repo would be a benefit)22:39
*** felipemonteiro_ has quit IRC22:39
corvusmordred: you make a compelling argument.  for both options.  :)22:40
corvusgood thing is -- it's easy to change22:40
corvusit's probably easier to start with them in-repo.  so i think i'll propose we do that for starters, unless someone objects.  we can make zuul-specs later if we don't like it.22:40
fungiyeah, putting them with the docs is a fine solution to start22:41
fungidoesn't involve inventing new repos22:41
mordred++22:41
*** namnh has joined #openstack-meeting-alt22:42
corvusi think that's everything from the previous last call... unless anyone has more last-call topics...22:43
Shrewsviva la containers!!22:43
corvus#endmeeting22:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:44
corvus:)22:44
openstackMeeting ended Mon Apr  2 22:44:07 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-04-02-22.02.html22:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-04-02-22.02.txt22:44
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-04-02-22.02.log.html22:44
corvusthanks everyone!22:44
*** yamamoto has joined #openstack-meeting-alt22:50
*** yamamoto has quit IRC22:56
*** namnh has quit IRC23:01
*** namnh has joined #openstack-meeting-alt23:05
*** kumarmn has joined #openstack-meeting-alt23:09
*** fnaval has quit IRC23:13
*** namnh has quit IRC23:17
*** hongbin has quit IRC23:17
*** iyamahat_ has quit IRC23:18
*** yamahata has quit IRC23:19
*** fnaval has joined #openstack-meeting-alt23:23
*** kumarmn has quit IRC23:24
*** namnh has joined #openstack-meeting-alt23:29
*** lbragstad has quit IRC23:31
*** iyamahat has joined #openstack-meeting-alt23:36
*** gouthamr has quit IRC23:41
*** namnh has quit IRC23:43
*** apetrich has quit IRC23:43
*** kumarmn has joined #openstack-meeting-alt23:44
*** namnh has joined #openstack-meeting-alt23:45
*** namnh has quit IRC23:45
*** Swami has quit IRC23:51
*** markstur_ has quit IRC23:51
*** yamamoto has joined #openstack-meeting-alt23:52
*** yamahata has joined #openstack-meeting-alt23:55
*** yamamoto has quit IRC23:56

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