Monday, 2018-01-08

*** Ablu has quit IRC00:05
*** slaweq has joined #openstack-meeting-alt00:11
*** Ablu has joined #openstack-meeting-alt00:15
*** slaweq has quit IRC00:15
*** d0ugal has quit IRC00:15
*** d0ugal has joined #openstack-meeting-alt00:27
*** oikiki has joined #openstack-meeting-alt00:37
*** oikiki has quit IRC00:40
*** oikiki has joined #openstack-meeting-alt00:51
*** caowei has joined #openstack-meeting-alt00:57
*** dave-mccowan has joined #openstack-meeting-alt01:07
*** yangyapeng has joined #openstack-meeting-alt01:10
*** tovin07_ has joined #openstack-meeting-alt01:12
*** junboli has joined #openstack-meeting-alt01:16
*** daidv has joined #openstack-meeting-alt01:20
*** daidv_ has joined #openstack-meeting-alt01:20
*** daidv_ has quit IRC01:24
*** mguiney is now known as help01:31
*** help is now known as valkyrja01:31
*** leakypipes has quit IRC01:39
*** valkyrja is now known as mguiney01:40
*** hongbin has joined #openstack-meeting-alt02:03
*** dalgaaf has quit IRC02:12
*** dalgaaf has joined #openstack-meeting-alt02:14
*** zhurong has joined #openstack-meeting-alt02:46
*** hongbin has quit IRC03:09
*** dave-mccowan has quit IRC03:09
*** hongbin has joined #openstack-meeting-alt03:09
*** hongbin has quit IRC03:10
*** hongbin has joined #openstack-meeting-alt03:10
*** hongbin has quit IRC03:10
*** hongbin has joined #openstack-meeting-alt03:11
*** hongbin has quit IRC03:12
*** hongbin has joined #openstack-meeting-alt03:13
*** hongbin has quit IRC03:14
*** hongbin has joined #openstack-meeting-alt03:15
*** yamahata has joined #openstack-meeting-alt03:16
*** oikiki has quit IRC03:25
*** yamamoto has joined #openstack-meeting-alt03:58
*** yamamoto has quit IRC04:03
*** chhavi has joined #openstack-meeting-alt04:08
*** junboli has quit IRC04:10
*** hongbin has quit IRC04:19
*** bhavik1 has joined #openstack-meeting-alt04:33
*** chhavi has quit IRC04:39
*** gcb has joined #openstack-meeting-alt04:41
*** sridharg has joined #openstack-meeting-alt04:44
*** oikiki has joined #openstack-meeting-alt04:49
*** bhavik1 has quit IRC04:50
*** zhurong has quit IRC04:52
*** caowei has quit IRC04:52
*** anilvenkata has joined #openstack-meeting-alt04:57
*** yamamoto has joined #openstack-meeting-alt05:04
*** yamamoto has quit IRC05:12
*** yangyapeng has quit IRC05:16
*** yangyapeng has joined #openstack-meeting-alt05:17
*** janki has joined #openstack-meeting-alt05:28
*** skramaja has joined #openstack-meeting-alt05:30
*** caowei has joined #openstack-meeting-alt05:30
*** mikal has quit IRC05:33
*** shaohe_feng has quit IRC05:38
*** dsariel has joined #openstack-meeting-alt05:39
*** shaohe_feng has joined #openstack-meeting-alt05:42
*** dsariel has quit IRC05:44
*** oikiki has quit IRC05:50
*** zhurong has joined #openstack-meeting-alt05:51
*** pgadiya has joined #openstack-meeting-alt05:53
*** efried has quit IRC06:08
*** janki has quit IRC06:17
*** janki has joined #openstack-meeting-alt06:18
*** efried has joined #openstack-meeting-alt06:18
*** yamahata has quit IRC06:32
*** chhavi has joined #openstack-meeting-alt06:33
*** florianf has joined #openstack-meeting-alt06:39
*** dsariel has joined #openstack-meeting-alt06:41
*** oikiki has joined #openstack-meeting-alt06:44
*** oikiki has quit IRC06:45
*** jbadiapa has joined #openstack-meeting-alt06:47
*** feldmann has joined #openstack-meeting-alt06:51
*** coolsvap has joined #openstack-meeting-alt06:51
*** liuyulong has joined #openstack-meeting-alt06:54
*** mjura has joined #openstack-meeting-alt06:55
*** reedip has quit IRC06:55
*** mjura has quit IRC06:55
*** mjura has joined #openstack-meeting-alt06:57
*** marios has joined #openstack-meeting-alt07:05
*** reedip has joined #openstack-meeting-alt07:07
*** apopovych has quit IRC07:13
*** ChrisPriceAB has quit IRC07:13
*** jungleboyj has quit IRC07:13
*** aprice has quit IRC07:13
*** margaret has quit IRC07:13
*** aprice has joined #openstack-meeting-alt07:13
*** apopovych has joined #openstack-meeting-alt07:13
*** jungleboyj has joined #openstack-meeting-alt07:13
*** margaret has joined #openstack-meeting-alt07:13
*** ChrisPriceAB has joined #openstack-meeting-alt07:14
*** karthiks has joined #openstack-meeting-alt07:36
*** arnewiebalck_ has joined #openstack-meeting-alt07:41
*** dsariel has quit IRC07:49
*** sridharg has quit IRC07:59
*** sridharg has joined #openstack-meeting-alt08:00
*** sridharg has quit IRC08:08
*** sridharg has joined #openstack-meeting-alt08:08
*** tesseract has joined #openstack-meeting-alt08:09
*** jtomasek has joined #openstack-meeting-alt08:12
*** anilvenkata has quit IRC08:13
*** anilvenkata has joined #openstack-meeting-alt08:13
*** fzdarsky has joined #openstack-meeting-alt08:17
*** pabelanger has quit IRC08:19
*** weshay has quit IRC08:19
*** honza has quit IRC08:20
*** honza has joined #openstack-meeting-alt08:20
*** pabelanger has joined #openstack-meeting-alt08:20
*** weshay has joined #openstack-meeting-alt08:20
*** honza is now known as Guest1450008:20
*** jpena has joined #openstack-meeting-alt08:38
*** oidgar has joined #openstack-meeting-alt08:44
*** gibi_away is now known as gibi08:44
*** MarkBaker has joined #openstack-meeting-alt08:50
*** tobiash has joined #openstack-meeting-alt08:50
*** rossella_s has joined #openstack-meeting-alt08:53
*** skramaja_ has joined #openstack-meeting-alt08:54
*** skramaja has quit IRC08:54
*** skramaja has joined #openstack-meeting-alt08:59
*** skramaja_ has quit IRC08:59
*** bfernando has joined #openstack-meeting-alt09:03
*** dsariel has joined #openstack-meeting-alt09:07
*** rcernin has quit IRC09:07
*** Guest14500 is now known as honza09:14
*** finucannot is now known as stephenfin09:16
*** ircuser-1 has joined #openstack-meeting-alt09:18
*** danpawlik has joined #openstack-meeting-alt09:23
*** fzdarsky has quit IRC09:39
*** derekh has joined #openstack-meeting-alt09:46
*** erlon has joined #openstack-meeting-alt09:54
*** ganso has joined #openstack-meeting-alt09:56
*** rossella_s has quit IRC09:59
*** rossella_s has joined #openstack-meeting-alt09:59
*** gcb has quit IRC10:02
*** zhurong has quit IRC10:02
*** pbourke has quit IRC10:12
*** pbourke has joined #openstack-meeting-alt10:12
*** tovin07_ has quit IRC10:21
*** egallen has joined #openstack-meeting-alt10:38
*** rossella_s has quit IRC10:46
*** rossella_s has joined #openstack-meeting-alt10:46
*** rochapor1o has quit IRC10:50
*** sambetts|afk is now known as sambetts10:50
*** caowei has quit IRC11:00
*** numans has quit IRC11:06
*** numans has joined #openstack-meeting-alt11:08
*** rfolco has joined #openstack-meeting-alt11:21
*** zhurong has joined #openstack-meeting-alt11:35
*** fzdarsky has joined #openstack-meeting-alt11:36
*** chhavi has quit IRC11:38
*** chhavi has joined #openstack-meeting-alt11:39
*** anilvenkata has quit IRC11:50
*** jkilpatr has quit IRC11:50
*** sdague has joined #openstack-meeting-alt12:00
*** zhongjun has quit IRC12:06
*** raildo has joined #openstack-meeting-alt12:09
*** dave-mccowan has joined #openstack-meeting-alt12:09
*** gcb has joined #openstack-meeting-alt12:13
*** jkilpatr has joined #openstack-meeting-alt12:22
*** liuyulong has quit IRC12:24
*** janki has quit IRC12:24
*** MarkBaker has quit IRC12:30
*** jpena is now known as jpena|lunch12:33
*** julim_ has quit IRC12:37
*** julim has joined #openstack-meeting-alt12:38
*** julim has quit IRC12:42
*** dave-mccowan has quit IRC12:47
*** dave-mccowan has joined #openstack-meeting-alt12:49
*** rcernin has joined #openstack-meeting-alt13:00
*** zhurong has quit IRC13:01
*** MarkBaker has joined #openstack-meeting-alt13:01
*** hieulq has quit IRC13:04
*** skramaja has quit IRC13:05
*** hieulq has joined #openstack-meeting-alt13:05
*** chhavi has quit IRC13:08
*** chhavi has joined #openstack-meeting-alt13:10
*** rcernin has quit IRC13:16
*** chhavi has quit IRC13:22
*** chhavi has joined #openstack-meeting-alt13:23
*** anilvenkata has joined #openstack-meeting-alt13:24
*** cleong has joined #openstack-meeting-alt13:28
*** yamamoto has joined #openstack-meeting-alt13:28
*** jpena|lunch is now known as jpena13:31
*** jkilpatr has quit IRC13:31
*** diga has joined #openstack-meeting-alt13:35
*** coolsvap has quit IRC13:36
*** jkilpatr has joined #openstack-meeting-alt13:45
*** brault has joined #openstack-meeting-alt13:48
*** dprince has joined #openstack-meeting-alt13:51
*** jaypipes has joined #openstack-meeting-alt13:55
*** yamamoto has quit IRC13:56
*** yamamoto has joined #openstack-meeting-alt13:57
*** cdent has joined #openstack-meeting-alt13:57
*** takashin has joined #openstack-meeting-alt13:57
*** GeraldK has joined #openstack-meeting-alt13:59
efried#startmeeting nova_scheduler14:00
openstackMeeting started Mon Jan  8 14:00:00 2018 UTC and is due to finish in 60 minutes.  The chair is efried. 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
efriedhttps://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:00
takashino/14:00
efriedGreetings all.  Welcome to the first Nova Scheduler meeting of the year.14:00
alex_xu_o/14:00
* bauzas waves back from the sloppy snowy hills14:00
efriedI'll be your host, while edleafe is somewhere on I-3514:00
*** yamamoto has quit IRC14:01
cdento/14:01
efriedThere's some interesting stuff on the agenda today.  jaypipes around?  (It'd be nice to have dansmith, but it's 6am for him, so...)14:02
jaypipesI am14:02
efriedCool, let's get started.14:02
efriedReviews: Nested RPs.14:03
efriedComputeDriver.update_provider_tree() series starting with: https://review.openstack.org/#/c/521685/14:03
efriedThis has prompted some discussion topics which we'll get to later.14:03
jaypipesI'm three patches deep in the nested with allocation candidates series. making decent progress.14:03
efried^^ Nested affordance in GET /allocation_candidates series starting with: https://review.openstack.org/#/c/531443/14:04
* jaypipes puts on brakes14:04
efriedGranular resource requests (https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/granular-resource-requests) waiting for ^^14:04
efriedAnyone have anything they want to bring up on those?14:04
efried...other than the "open discussion" stuff14:05
bauzasI need to review the nested RP stuff14:05
bauzasI see the update_provider_tree() changes as WIP, correct ?14:05
efriedbauzas Only the top couple of patches.  The bottom two or three are ready.14:05
bauzasefried: those aren't the driver side14:05
bauzasamirite ?14:06
* alex_xu_ happy to review more sql14:06
efriedCorrect; they're in report client and its helpers.14:06
bauzask14:06
efriedAll framework needed to get support in the driver side.14:06
efriedBut yeah, bauzas I noticed you were looking to use this stuff for libvirt vgpu work.14:06
bauzasI'm cool with that, just wanted to make things clear, since you were pointing out14:07
bauzas(15:03:27) efried: ComputeDriver.update_provider_tree() series starting with: https://review.openstack.org/#/c/521685/14:07
bauzasefried: definitely Rocky for me14:07
efriedokay.14:07
bauzasefried: I'm still beating with loving libvirt and nvidia fancy popping up issues14:07
bauzastl:dr: no docs, just words of mouth14:07
efriedGood times.  "Someone" should write the docs :)14:08
efriedAnything else on NRP?14:08
efriedMoving on.14:08
efriedAlternate hosts (edleafe):14:08
efriedSeries now starts with test case patch https://review.openstack.org/#/c/531022/14:08
efriedRevealed bug: https://bugs.launchpad.net/nova/+bug/174112514:08
openstackLaunchpad bug 1741125 in OpenStack Compute (nova) "Instance resize intermittently fails when rescheduling" [High,In progress] - Assigned to Ed Leafe (ed-leafe)14:08
bauzasthe Xen folks are probably the best customers for the NRP usecase14:08
bauzasthey are way more advanced than me14:08
efriedbauzas Noted.  They're on my radar.14:09
alex_xu_efried: does nrp still target to this release?14:09
bauzasthe more we can merge, the better it will be14:09
efriedalex_xu_ As far as I know, yes.14:09
bauzasat least the compute side is critical14:09
bauzasnot the scheduling one14:10
alex_xu_efried: ok, just looks like the time is tight14:10
bauzasalex_xu_: aaaaand I haven't harassed you with beggy asks for reviews on my VGPU changes :p14:10
efriedI believe the scope of the work is limited to what's described above, which I feel is doable if we stay aggressive.14:10
efriedjaypipes Thoughts on that?14:11
alex_xu_bauzas: heh :)14:11
* cdent gets up on the balls of his feet14:11
*** yangyapeng has quit IRC14:11
efriedAnything on alt hosts?14:12
jaypipesefried: I believe we can get n-r-p in reportclient, n-r-p in alloc candidates, and xen as first client/consumer done in Queens.14:12
efriedjaypipes ++14:12
bauzasI agree14:12
alex_xu_\o/14:12
jaypipesefried: what I *don't* believe will be done is the crazy-pants numa/pci stuff.14:13
jaypipesefried: that will need more extensive testing14:13
*** julim has joined #openstack-meeting-alt14:13
efriedjaypipes Agree.  That is driver consumption of the stuff we're putting into Queens, yes?14:13
jaypipesefried: so we will continue to need both the PciPassthroughFilter and the NUMATopologyFilter in the scheduler for at least Queens.14:13
cdentI think on alt hosts, the only pending thing is fixing that bug (on the agenda). And any subsequent fall out from it existing14:13
jaypipesefried: yes, xactly.14:13
bauzasdriver consumption or inventory ?14:14
alex_xu_is granular request part of nrp?14:14
bauzasI thought the former14:14
bauzasoops14:14
efriedalex_xu_ yes14:14
bauzasI thought the /latter/14:14
alex_xu_efried: cool14:14
jaypipesbauzas: driver consumption *is* inventory :)14:14
bauzasdammit, speak French folks14:14
jaypipesbauzas: by "driver consumption", we're referring to the virt driver API's proposed update_provider_tree() method, which is responsible for inventory tracking.14:15
bauzasthe driver will *provide* the inventory ala new way, better ?14:15
jaypipes++14:15
efriedbauzas jaypipes It's two-pronged, really.  The driver will have to supply the RP picture via update_provider_tree; and will also have to have the code to do the device creation/assignment to the VM based on the allocations from the scheduler.14:15
bauzasjaypipes: that looks like a provider terminology to me, not a consumer, but meh :p14:16
jaypipesefried: sure, yes.14:16
bauzasanyway, I'm seriously diverting14:16
* bauzas shuts up14:16
jaypipesbauzas: agreeed.14:16
efriedProviding inventory by consuming new interfaces :)14:16
jaypipesok, moving on...14:16
* efried realizes total failure to use #topic thus far14:17
efried#topic Bugs14:17
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:17
efriedhttps://bugs.launchpad.net/nova/+bugs?field.tag=placement14:17
jaypipesno bugs. ever. next topic.14:17
efried25 of these, probably a good time to do a scrub.14:18
efriedMake sure the status is appropriate.  E.g. the other day I found a moldy one (but I only looked at the one).14:18
efriedVolunteers?14:18
efried<crickets>14:19
jaypipesnot me, sorry. I need to focus on reviews this week.14:19
efriedI'll try to skim through them.14:19
efriedAnything else on bugs?14:19
cdenti look every week, but usually the status hasn't changed much. will continue to do so14:19
efriedThanks14:19
efried#topic Open discussion14:20
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:20
efriedFirst on the list: Using the limits recently made available on GET /allocation_candidates.14:20
efriedDan put up a WIP on Friday:  https://review.openstack.org/#/c/531517/14:20
efriedSo I guess any discussion can happen on that review.14:21
efriedAnything to talk about here & now on that?14:21
jaypipesnope14:22
efriedNext.14:22
efriedThere's been lots of words in the reviews of  https://review.openstack.org/#/c/52653914:23
cdent"careful handling of conflicts" is a) probably right, b) scary, c) sigh making because b14:23
cdentefried: can you expand on generation handing on aggregates?14:23
cdent(the necessity thereof)14:24
efriedSure.14:24
cdent(for sake of completeness)14:24
efriedIf we want to allow multiple threads, possibly/usually on different hosts, to manage the same RP, we need a way to handle race conditions.14:25
efried...a way that isn't process/thread level locking.14:25
efriedSo the db record of a provider includes a 'generation', which is a monotonically increasing integer indicating the "revision" of the RP.14:26
bauzasnot sure I get the problem and/or the context of that conversation14:26
efriedYou GET the provider, change something about it, and PUT it back.  You don't change the generation in that payload.14:26
efriedbauzas It's this: If thread A GETs the provider and makes a change, and thread B GETs the provider and makes a change, then thread A PUTs it back, then thread B puts it back, thread B's changes will overwrite thread A's changes.14:27
cdentthat part's mostly understood, but with aggregates we had originally decided not to. What's different? Instead of generation, do we need a way to add/remove a single member from an aggregate collection?14:27
jaypipescorrect.14:27
cdent(if it's already there or already not there, do nothing, it's OK)14:28
jaypipescdent: no, I think we just need to do the exact same thing we do with the traits collection of an rp.14:28
efriedbauzas Is it clear how generation fixes that, or should I explain further?14:28
bauzasI know why we have the generation bit, so I guess the problem is with aggregates that *don't* have this ?14:28
cdentjaypipes: that's fine, just trying to make sure the picture is clear14:28
jaypipescdent: the trick is we need to deprecate the old API (that doesn't supply a generation) and add a new microversion that supplies a generation for PUT /aggregates14:29
efriedbauzas Right, today if you change the aggregates associated with a provider, that provider's generation is *not* incremented.14:29
efriedbauzas We're suggesting that's a bad thing, and needs to be fixed.14:29
jaypipesefried: right. it's the only rp-related endpoint (that modifies something) that doesn't have a generation marker.14:29
*** sean-k-mooney has joined #openstack-meeting-alt14:30
*** ktibi has joined #openstack-meeting-alt14:30
bauzaswell, if the RP doesn't change, why should we increment the generation bit ?14:30
efriedbauzas Changing aggregate associations *is* changing the RP.14:30
efriedJust like changing the traits is changing the RP.14:30
jaypipesbauzas: because the rp's generation is the lock for all things related to the rp. inventory, allocations, traits, etc14:30
bauzasI'm maybe missing something, but if that's just a matter of incrementing the gen bit, why should we need to modify the REST API ?14:31
bauzasfor passing the new generation bit ?14:31
bauzassorry, see, I'm rusty14:31
*** lpetrut has joined #openstack-meeting-alt14:31
efriedNo, the payload structures don't change.14:31
jaypipesbauzas: because we need the thing that is attempting to change the rp to say what its latest view of the rp was.14:32
jaypipesefried: yes, they do.14:32
efriedOh yeah14:32
jaypipesefried: unless you plan on passing the generation in a header...14:32
bauzasjaypipes: right, we need to pass the index where we are14:32
efriedcause right now GET /rp/{uuid}/aggs doesn't include generation.14:32
bauzasgotcha14:32
jaypipesefried: which I don't recommend.14:32
cdentit will make cdent very fussy14:33
efriedBecause why?14:33
jaypipesand we don't want that.14:33
cdenttwo ways to do the same thing: bad14:33
jaypipesefried: because it would be very inconsistent.14:33
cdentjinx14:33
jaypipesefried: so let's move on :)14:33
bauzasdo we consider those race conditions as being often ?14:33
bauzasafter all, Nova aggregates don't have any concurrency management in place14:34
efriedOkay, I got confused.  We *do* want to include the generation in the payload?14:34
cdentwe consider them to be very possible when bring up several pieces of new hardware, especially in clustered envs, but then stabilize14:34
jaypipesbauzas: originally, cdent and I did not envision aggs changing a) often or b) by the compute virt driver. but drivers like PowerVM and vCenter apparently have designs to do this.14:34
*** ktibi has left #openstack-meeting-alt14:34
bauzasjaypipes: I thought the former as well, so I'm surprised14:34
jaypipesbauzas: which is why we need to solve this problem now and not later with some distributed locking hacky thing14:34
bauzasokay, is that a thing for now or Rocky?14:35
bauzasbecause that's an API microversion bump, right?14:35
bauzasI mean, surely we can14:35
cdentwe've bumped the placement microversion 6 times this cycle, we can afford a few more14:35
bauzasbut I just know we have a shit number of other things to merge14:36
cdent(6 is a guesstimate)14:36
bauzasthen, Just Do It (c)14:36
efried++14:36
bauzasand see when we can merge14:36
jaypipesbauzas: yeah, I'm in the just do it camp.14:36
efriedWho would like to propose this patch?14:36
jaypipesso... *who* should do it?14:36
jaypipesjinx14:36
bauzasa-ha!14:36
cdentI can do the placement side14:36
jaypipes++14:37
jaypipesexcellent.14:37
efriedThanks cdent14:37
* cdent adds to to do likst14:37
gibiI have one silly question14:37
efried#action cdent to propose generations-on-aggregate placement microversion14:37
gibiWhen adding an aggregate to an RP we will increase the generation of that RP or every RP that aggregate is connected to?14:37
* efried finds the #action keyword14:37
efriedgibi Excellent question, as always.14:38
jaypipesgibi: no, only update generation when *that* RP's set of aggs changes14:38
efriedThat seems reasonable to me.14:38
sean-k-mooneygibi: i would guess the generation number of the aggregate and the RP added but not other RPs in that aggregate14:38
efried(sean-k-mooney the aggregate doesn't have a generation)14:38
efried(but yeah)14:38
cdentgibi: clearly not a silly question gibi, especially since there's no such thing as a silly question14:39
gibiOK, the answer seems consistent :)14:39
efriedOkay, so cdent pointedly said "placement side".  The client side...14:39
efriedThat's probably on me, unless someone else wants to volunteer.14:39
cdentI figured splitting it up was probably better to avoid serializing.14:40
efriedsuresure14:40
efriedRight now the report client doesn't have any kind of retry on 409.14:40
cdentand also since my savvy of the ProviderTree stuff is limited14:40
efriedcdent Actually I don't think ProviderTree enters into it much or at all for this.14:41
cdentthere's code in there somewhere for the Retry exception that jaypipes (I think?) created14:41
efriedoh?14:41
* efried looks14:41
cdentwhich can probalby be reused14:41
cdent(with some tweaks)14:41
efriedreport.py has class Retry and a @retries decorator.  Will investigate.14:42
efriedSo now the big question:14:42
cdentI realize that the ProviderTree just uses the report client, but the larger context is the ProviderTree doing an effectivce sync of whatever the virt driver tells it14:42
*** yamamoto has joined #openstack-meeting-alt14:42
cdentthat's the part I haven't got close knowledge of, and is the driver for all this stuff, and the part that we want to be the working result14:42
jaypipescdent: you talking about reportclient or ProviderTree? ProviderTree does not interface with placement API.14:43
efriedcdent That's an interesting point.  I had been thinking we would do the retry logic at the low level report client methods that do the PUTs.14:43
cdentefried: yes, so would I14:43
efriedi.e. ProviderTree not involved - it calls those guys and they just work, with however many retries they need.14:43
jaypipescdent: ProviderTree doesn't use reportclient :)14:44
cdenta thing which uses ProvideerTree and reportclient is trying to manage the picture of the world14:44
cdentthe picture of the world is the thing I'm trying to say we should care most about14:44
efriedagreed14:44
cdentthat is: I'm trying to say: it's not the unit tests that matter here14:44
cdentit's the end result14:44
jaypipescdent: reportclient builds the ProviderTree. ProviderTree simply implements thread-safe ability to set traits and inventory information for providers, and then we can pass that ProviderTree to the reportclient and reportclient will inspect it and call the placement REST API accordingly.14:45
*** feldmann has quit IRC14:45
cdentyes, that's been my understanding all along14:45
jaypipesk14:45
efriedIt'll be a report client method that diffs two ProviderTrees and flushes the changes back to placement.  I'm saying that method will call the low-level PUT wrappers, and those wrappers will have the retry logic in 'em.14:45
cdentso the provider tree is the central/key data structure that drivers the pictuyre of the world14:45
cdentefried: yes14:46
jaypipescdent: yes.14:46
* cdent is apparently more data structure oriented than he thought14:46
efriedThe diff/flush method is the to-be-written one here: https://review.openstack.org/#/c/520246/19/nova/compute/resource_tracker.py@88614:46
*** yamamoto has quit IRC14:47
cdentsee above about "scary"14:47
cdentI know it is just a simple matter of programming14:47
efried#action efried to start on conflict retry logic.14:47
efriedSo the big question:14:47
efriedCan we do this in report client in such a way that it works for all (reasonable) use cases?14:48
efriedSee the most recent review missive on https://review.openstack.org/#/c/526539/714:48
efriedIt is not always definitely clear how a conflict should be handled.14:49
efriedConsider especially the case where two hosts are creating the aggregate for a shared provider.14:49
efriedIt's certainly legal for a shared provider to be a member of multiple aggregates.14:49
efriedSo when we retry, how do we know whether to add our aggregate to the mix, or see that the aggregate was created by the "other thread" and just skip?14:50
jaypipesthat's the issue with >1 thing creating aggregates :)14:52
efriedIn the general view, I contend that only the specific virt driver can know this answer for a specific shared provider.14:52
efried...assuming the picture where it's the virt driver controlling the shared provider.14:52
jaypipesefried: yes, I think that's the case...14:52
efriedIf so, then how do we manage this without giving virt the reins to do the placement update & conflict resolution itself?14:53
sean-k-mooneyefried: you are assuming that the virt driver will always know. if the shared resouce is not a compute releated resouce will it have that knoladge14:53
jaypipesefried: the virt driver needs to be the thing that answers the question "ok, so the state of things changed. check if my desired state is now in play before I go trying to create that new desired state"14:53
efriedjaypipes So maybe if conflict is detected, reinvoke update_provider_tree?14:54
jaypipesefried: all the generation change stuff means is "*something changed*!". it doesn't mean "this thing changed".14:54
bauzasFWIW, 5 mins left-ish14:54
jaypipesefried: I think it depends. certainly if you get a 409, then I would re-read all the provider's information (traits, inventory, etc)14:55
efriedSo perhaps where this leads us is actually a lot broader and simpler than I had been thinking.14:55
jaypipesefried: and then check to see if the desired state is already existing. and if so, do nothing. if not, then call the update/set again.14:55
*** yamahata has joined #openstack-meeting-alt14:56
efriedInstead of having the low-level PUT method detect 409s and redrive, have the resource tracker trap the 409 and reinvoke update_provider_tree.14:56
efriedThat gives the driver the control it needs.14:56
jaypipesefried: that "desired state" is going to be different depending on the virt driver and depending on what the virt driver is attempting to do (for example, changing a provider's inventory is different from changing the provider's set of traits)14:56
jaypipesefried: yes, precisely what you said.14:56
efriedBecause update_provider_tree is always doing as jaypipes says: checking whether the "current" state is the "desired" state.14:56
jaypipesefried: that is the original design.14:56
jaypipesefried: client-driven state retries, that is.14:57
efriedDig.14:57
efriedWell, that was the only real-world case where I had thought there might be a reason for virt to talk directly to placement.14:59
efriedThe last open discussion topic is on that point in general.14:59
cdentIf a ProviderTree has state A, with hierarchy, and there is a conflict, such that it should be reset to state B, if that leaves orphans in the hierarchy, who/what cleans up those orphans and how does anything know?14:59
*** yangyapeng has joined #openstack-meeting-alt14:59
efriedcdent The aforementioned method.14:59
cdentit deletes resource providers?15:00
efriedYes15:00
cdentmaybe something else wants them too?15:00
efriedWe're over time.  Continue in -nova?15:00
* cdent nods15:00
efried#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Mon Jan  8 15:00:29 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-01-08-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-01-08-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-01-08-14.00.log.html15:00
*** takashin has left #openstack-meeting-alt15:01
*** hongbin has joined #openstack-meeting-alt15:01
*** sean-k-mooney has left #openstack-meeting-alt15:01
*** manjeet has joined #openstack-meeting-alt15:01
*** Guest8485 is now known as dansmith15:02
*** dansmith is now known as Guest6250115:02
*** fzdarsky has quit IRC15:03
*** fzdarsky has joined #openstack-meeting-alt15:03
*** sdague has quit IRC15:04
*** Guest62501 is now known as dansmith15:05
*** pgadiya has quit IRC15:07
*** gouthamr has joined #openstack-meeting-alt15:11
*** cdent has left #openstack-meeting-alt15:12
*** felipemonteiro has joined #openstack-meeting-alt15:15
*** yamamoto has joined #openstack-meeting-alt15:27
*** markstur has joined #openstack-meeting-alt15:29
*** rmart04 has joined #openstack-meeting-alt15:31
*** yamamoto has quit IRC15:32
*** ssathaye has joined #openstack-meeting-alt15:34
*** diga has quit IRC15:34
*** gcb has quit IRC15:48
*** matrohon has joined #openstack-meeting-alt15:52
*** yamamoto has joined #openstack-meeting-alt15:53
*** yamamoto has quit IRC15:53
*** felipemonteiro has quit IRC15:54
*** felipemonteiro has joined #openstack-meeting-alt15:55
*** TxGirlGeek has joined #openstack-meeting-alt15:59
*** shamail has joined #openstack-meeting-alt16:01
*** ijw has joined #openstack-meeting-alt16:03
*** rmart04 has quit IRC16:03
*** chyka has joined #openstack-meeting-alt16:05
*** sridharg has quit IRC16:06
*** manjeet has quit IRC16:06
*** shamail has quit IRC16:08
*** mjura has quit IRC16:12
*** feldmann has joined #openstack-meeting-alt16:18
*** anilvenkata has quit IRC16:19
*** anilvenkata has joined #openstack-meeting-alt16:21
*** krtaylor has quit IRC16:27
*** felipemonteiro has quit IRC16:27
*** krtaylor_ has joined #openstack-meeting-alt16:27
*** ijw has quit IRC16:29
*** kumarmn has joined #openstack-meeting-alt16:29
*** ganso has left #openstack-meeting-alt16:30
*** feldmann has quit IRC16:31
*** d0ugal has quit IRC16:35
*** chhavi has quit IRC16:38
*** kmalloc has joined #openstack-meeting-alt16:38
*** gyee has joined #openstack-meeting-alt16:39
*** GeraldK has quit IRC16:43
*** jkilpatr has quit IRC16:44
*** jpena is now known as jpena|brb16:44
*** david-lyle has quit IRC16:47
*** david-lyle has joined #openstack-meeting-alt16:48
*** yamahata has quit IRC16:48
*** david-lyle has quit IRC16:52
*** yamamoto has joined #openstack-meeting-alt16:53
*** Leo_m has joined #openstack-meeting-alt16:55
*** d0ugal has joined #openstack-meeting-alt16:59
*** jkilpatr has joined #openstack-meeting-alt17:00
*** slaweq has joined #openstack-meeting-alt17:00
*** iyamahat has joined #openstack-meeting-alt17:01
*** yamamoto has quit IRC17:02
*** oidgar has quit IRC17:06
*** bhavik1 has joined #openstack-meeting-alt17:10
*** TxGirlGeek has quit IRC17:11
*** bhavik1 has quit IRC17:11
*** slaweq has quit IRC17:11
*** egallen has quit IRC17:11
*** d0ugal has quit IRC17:11
*** egallen has joined #openstack-meeting-alt17:12
*** dsariel has quit IRC17:16
*** TxGirlGeek has joined #openstack-meeting-alt17:16
*** ijw has joined #openstack-meeting-alt17:17
*** yamahata has joined #openstack-meeting-alt17:20
*** egallen has quit IRC17:22
*** jpena|brb is now known as jpena17:24
*** oikiki has joined #openstack-meeting-alt17:25
*** fzdarsky is now known as fzdarsky|afk17:28
*** matrohon has quit IRC17:31
*** david-lyle has joined #openstack-meeting-alt17:34
*** egallen has joined #openstack-meeting-alt17:42
*** yamamoto has joined #openstack-meeting-alt17:43
*** yamamoto has quit IRC17:43
*** felipemonteiro has joined #openstack-meeting-alt17:45
*** egallen has quit IRC17:47
*** egallen_ has joined #openstack-meeting-alt17:47
*** david-lyle has quit IRC17:47
*** marios has quit IRC17:49
*** derekh has quit IRC18:01
*** slaweq has joined #openstack-meeting-alt18:05
*** rmascena has joined #openstack-meeting-alt18:05
*** raildo has quit IRC18:08
*** bfernando has quit IRC18:16
*** slaweq has quit IRC18:17
*** jpena is now known as jpena|off18:18
*** jkilpatr has quit IRC18:19
*** slaweq has joined #openstack-meeting-alt18:21
*** egallen_ has quit IRC18:24
*** slaweq has quit IRC18:31
*** jkilpatr has joined #openstack-meeting-alt18:33
*** slaweq has joined #openstack-meeting-alt18:34
*** beekneemech is now known as bnemec18:34
*** tesseract has quit IRC18:35
*** corey_ has joined #openstack-meeting-alt18:39
*** cleong has quit IRC18:40
*** lpetrut has quit IRC18:41
*** Leo_m has quit IRC18:43
*** yamamoto has joined #openstack-meeting-alt18:44
*** Leo_m has joined #openstack-meeting-alt18:44
*** Leo_m has quit IRC18:49
*** yamamoto has quit IRC18:52
*** TxGirlGeek has quit IRC18:55
*** TxGirlGeek has joined #openstack-meeting-alt18:56
*** TxGirlGeek has quit IRC18:56
*** oikiki has quit IRC18:58
*** oikiki has joined #openstack-meeting-alt18:59
*** TxGirlGeek has joined #openstack-meeting-alt18:59
*** slaweq has quit IRC19:01
*** yamamoto has joined #openstack-meeting-alt19:01
*** slaweq has joined #openstack-meeting-alt19:02
*** TxGirlGeek has quit IRC19:04
*** slaweq has quit IRC19:06
*** slaweq has joined #openstack-meeting-alt19:09
*** harlowja has joined #openstack-meeting-alt19:19
*** slaweq has quit IRC19:19
*** TxGirlGeek has joined #openstack-meeting-alt19:22
*** slaweq has joined #openstack-meeting-alt19:28
*** jkilpatr has quit IRC19:33
*** lpetrut has joined #openstack-meeting-alt19:41
*** felipemonteiro_ has joined #openstack-meeting-alt19:41
*** david-lyle has joined #openstack-meeting-alt19:43
*** felipemonteiro has quit IRC19:45
*** dmsimard has joined #openstack-meeting-alt19:48
*** Leo_m has joined #openstack-meeting-alt19:49
*** yamamoto has quit IRC19:53
*** fzdarsky|afk has quit IRC20:00
*** sdague has joined #openstack-meeting-alt20:00
dave-mccowan#startmeeting barbican20:01
openstackMeeting started Mon Jan  8 20:01:35 2018 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: barbican)"20:01
openstackThe meeting name has been set to 'barbican'20:01
dave-mccowan#topic roll call20:01
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:01
dave-mccowano/20:01
*** yamamoto has joined #openstack-meeting-alt20:04
*** dsariel has joined #openstack-meeting-alt20:06
*** yamamoto has quit IRC20:09
ssathayeo/20:10
ssathayeHi Dave20:10
dave-mccowanHi ssathaye20:10
ssathayeThought at least I will show up...still continue to look for b/w to contribute.20:11
ssathayeHopefully soon.20:11
dave-mccowanLooks like a short meeting today.20:11
*** jkilpatr has joined #openstack-meeting-alt20:11
ssathayeok20:11
dave-mccowan#topic Queens Deadlines20:12
*** openstack changes topic to "Queens Deadlines (Meeting topic: barbican)"20:12
dave-mccowanjust in case people read these logs....20:12
dave-mccowanQueens deadlines are coming up.20:12
ssathayeok20:12
dave-mccowanDeadline for Queens release of Castellan and python-barbicanclient patches will be week of Jan 1520:13
dave-mccowan https://releases.openstack.org/queens/schedule.html20:13
dave-mccowanFeb 5 is feature freeze for Barbican service, Feb 28 is release candidate date.20:13
dave-mccowanAnyone with patches that should go in Queens, please get our attention for reviews.20:14
dave-mccowanthat's all i have.20:14
dave-mccowananything you want to bring up ssathaye ?20:14
ssathayenot really. One little patch that I submitted to the docs - I got feedback on. Now need to re-submit.20:15
ssathayeWill do this week.20:15
dave-mccowanssathaye sounds good.  thanks!20:16
dave-mccowansee you later....20:17
dave-mccowan#endmeeting20:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:17
openstackMeeting ended Mon Jan  8 20:17:10 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2018/barbican.2018-01-08-20.01.html20:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2018/barbican.2018-01-08-20.01.txt20:17
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2018/barbican.2018-01-08-20.01.log.html20:17
ssathayethanks Dave!20:18
*** openstack has quit IRC20:38
*** openstack has joined #openstack-meeting-alt20:42
*** ChanServ sets mode: +o openstack20:42
*** TxGirlGeek has quit IRC20:45
*** TxGirlGeek has joined #openstack-meeting-alt20:46
*** feldmann has joined #openstack-meeting-alt20:49
*** TxGirlGeek has quit IRC20:51
*** egallen has quit IRC20:53
*** TxGirlGeek has joined #openstack-meeting-alt20:54
*** egallen has joined #openstack-meeting-alt20:54
*** TxGirlGeek has quit IRC20:55
*** TxGirlGeek has joined #openstack-meeting-alt20:56
*** jtomasek has quit IRC20:58
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:01
Arkady_Kanevskyhello PWG21:01
*** alee has joined #openstack-meeting-alt21:02
*** dprince has quit IRC21:06
*** matrohon has joined #openstack-meeting-alt21:07
*** MeganR has joined #openstack-meeting-alt21:11
*** rcernin has joined #openstack-meeting-alt21:18
*** gouthamr has quit IRC21:22
*** egallen has quit IRC21:24
*** corey_ has quit IRC21:25
*** julim has quit IRC21:27
*** david-lyle has quit IRC21:28
*** alee has left #openstack-meeting-alt21:29
*** rcernin has quit IRC21:33
*** Arkady_Kanevsky has quit IRC21:35
*** gouthamr has joined #openstack-meeting-alt21:37
*** yamamoto has joined #openstack-meeting-alt21:39
*** yamamoto has quit IRC21:47
*** MeganR has quit IRC21:49
*** slaweq has quit IRC21:50
*** TxGirlGeek has quit IRC21:50
*** feldmann has quit IRC21:55
*** Shrews has joined #openstack-meeting-alt21:57
*** TxGirlGeek has joined #openstack-meeting-alt21:58
*** TxGirlGeek has quit IRC21:59
*** matrohon has quit IRC22:00
mrhillsmano/22:00
corvusany zuul folks around?22:00
clarkbhello22:00
mrhillsmanyar22:00
tobiashhi22:00
pabelangero/22:00
fungii'm around, but about to not be. sorry :/22:00
corvus#startmeeting zuul22:01
openstackMeeting started Mon Jan  8 22:01:07 2018 UTC and is due to finish in 60 minutes.  The chair is corvus. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
dmsimard\o22:01
*** openstack changes topic to " (Meeting topic: zuul)"22:01
openstackThe meeting name has been set to 'zuul'22:01
Shrewshey22:01
corvus#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:01
* mordred waves to humans22:02
corvus#link release roadmap https://storyboard.openstack.org/#!/board/5322:02
corvuslet's go through the 3.0 things real quick --22:02
corvusdid someone pick up the github ingestion via zuul-web yet?22:03
corvusi guess that's the last thing that's still in the old webapp, and once we get rid of that we can drop it entirely?22:03
tobiashI picked this up before christmas22:04
corvustobiash: ah great -- it's https://review.openstack.org/504267 right?22:04
tobiashWhat's missing is an end to end test yet22:04
pabelangercorvus: I thought was assigned jlk, but seen he's moved onto new job recently.22:04
corvuspabelanger: jlk handed it off to tobiash22:05
tobiashcorvus: yes22:05
SpamapSo/22:05
pabelangerack, I missed that22:05
corvustobiash: i agree with your last comment there -- we probably only need one or a few explicit tests for this22:05
corvustobiash: are you planning on finishing it up like that?22:05
corvus(i updated the assignment in storyboard)22:06
tobiashProbably not this week as we're going productive this week22:06
tobiashBut I hope next week22:06
corvustobiash: congrats and good luck :)22:06
corvustobiash: that sounds great, thanks22:06
corvusdmsimard: are you still planning on fixing the zuul_json issue?22:06
*** rcernin has joined #openstack-meeting-alt22:06
tobiashthanks22:07
Shrewsoh, we lost jlk as a contributor?  :(22:07
tobiash:-)22:07
dmsimardyes, in fact I rebased the patch last week in order to reproduce the issue (which would have been easier to troubleshoot, now that I'm root) but for some reason it did not trigger22:07
corvusShrews: i haven't heard that from jlk22:07
dmsimardI've looked around and saw some fixes in upstream ansible for that issue but it is confusing since we should not have those fixes yet in our version of Ansible.22:08
*** egallen has joined #openstack-meeting-alt22:08
* dmsimard gets link22:08
pabelanger Shrews: he just posted on twitter he is working as SRE at github.com :)So, hope not.22:08
SpamapSI think jlk is just busy getting inserted into his new job matrix.22:08
SpamapSLast we talked, he hoped to continue Zuul'ing in some capacity.22:08
mordredthat is also what I have heard from jlk22:08
dmsimardhttps://github.com/ansible/ansible/commit/c30ee42fe1f0a9666a90f4d63121780f2a186c54 should fix our issue22:08
fungihopefully he's busy inserting zuul into his new job matrix ;)22:09
corvusi see no reason why working at github would preclude contributing to zuul -- in fact, it's a position uniquely suited to doing so.  i hope he will continue.  :)22:09
dmsimardit also claims performance and memory improvements but I dunno.22:09
mordredwe have a human on the inside now to bug with API questions :)22:09
pabelangermordred: ++22:09
dmsimarddidn't know he was at github now, grats him22:09
Shrewsyes, let us all infiltrate all the places22:09
corvusalso, the big thing jlk is working on right now is getting github3.py released so we can release.  that seems very likely to meet with github.com supervisory approval, i'd think :)22:10
mordreddmsimard: well, today is his first day, so not knowing is totally fair :)22:10
mordredcorvus: I certainly hope so!22:10
dmsimardcorvus: in summary, I don't know whether or not there is something to fix yet since I am now unable to reproduce the issue and there has been an (unreleased) fix upstream.22:10
dmsimardI'll add my findings in the story.22:10
corvusdmsimard: do you mean you've been unable to repro using our production zuul, or locally?22:11
dmsimarddoing a recheck/rebase on https://review.openstack.org/#/c/504238/ typically reproduced the issue22:11
dmsimardit no longer does22:11
* fungi has to disappear now, but will catch up on the rest of the meeting from the log later tonight22:11
corvusdmsimard: oh interesting.  okay.  so maybe we can drop this from the 3.0 blockers?22:12
dmsimardit's possible a change occurred in zuul-stream fixed it22:12
dmsimardcorvus: I don't know yet -- I could try reproducing the issue without the patch (that was supposed to address the issue..) and see what happens.22:12
*** egallen has quit IRC22:12
dmsimardshould be fairly easy22:12
corvusdmsimard: okay.  if you decide it's no longer an issue, go ahead and drop the zuulv3.0 tag from the story when you update it, please22:13
dmsimardack22:13
corvusmordred: did i see you post something about a zuul-stream refactor?22:13
corvushttps://review.openstack.org/531171 looks like22:13
corvusmordred: is that a start to addressing the 'refactor zuul-stream and add testing' story?22:14
corvusthe story for that is "It's currently largely untested and difficult to make changes to."22:14
*** TxGirlGeek has joined #openstack-meeting-alt22:14
corvusmordred: please let me know when you are back22:15
mordredcorvus: it's sort of a patch related to that - but that's a little bit more about changing how the log stream data gets schelpped around to be potentially more something we could upstream22:16
corvusoh hai!22:16
mordredI also wrote up a proposal here: https://github.com/ansible/proposals/issues/9222:16
clarkband I guess it could help testing because we could have it log to a file/buffer in tests and check the contents rather than needing to build up a full on daemon process and listener and all that22:17
corvusclarkb: well, spinning things up and tearing them down isn't really a problem for the test runner22:18
*** florianf has quit IRC22:18
corvusi think it's more that there's a structural issue with the fact that most of this behaves differently if you are sshing into a remote node vs locally22:18
mordredyah - and also things like rebooting a test node will kill the zuul_console process22:19
corvusmordred: well, i'm talking about unit tests22:19
mordredso the aim here is that we won't need a zuul_console process, and also that the surface area for things breaking will reduce22:19
mordredcorvus: ah- yes, well, that as well :)22:19
mordredamongst the issues with the current system are surprise, fear and an almost fanatical devotion to the pope ...22:20
corvusthe reason this story was created was because there are, even now, still a lot of times we put something in the console log that we shouldn't, or don't put something in that we should.  and we have zero testing for any of that, and any time we try to change it, we break production, so it's effectively frozen..22:20
corvusso that's the thing that we need to get unblocked before the v3.0 release22:21
corvuswe need to be able to accept a bug report from someone saying "this should have been in the console log" and act on it22:21
mordredyup. and that refactor is still on the todo-list - and is largerly orthogonal to the above patch22:21
Shrewsmmm, largerly22:21
corvusokay that's helpful22:21
mordredor, I *believe* it's orthogonal22:21
mordredit's possible we'll discover that the other patch enables the refactor in important ways22:22
corvusmordred: yeah, i could see it interseting if testing somehow becomes more feasible with the above, otherwise, i'd be terrified to land the above anyway22:22
mordred++22:22
SpamapS+1 for not needing zuul_console process! I've been having reboot issues actually. :)22:22
dmsimardDo we no longer have a zuulv3-dev node that we could test sensitive things on ?22:23
pabelangerno, we deleted it22:23
dmsimardWe could hook it up to openstack-dev/sandbox or something22:23
corvuspabelanger, leifmadsen_: i see you're working on the docs -- anything blocking you there?22:23
*** erlon has quit IRC22:24
clarkbdmsimard: for stuff like this I think the effort is likely better spent adding tests to the test suite22:24
corvusyeah, we're not landing anything else without tests :)22:24
pabelangercorvus: just discussing where we want the example config project repo to live, that was about it. We should have some rst docs up this week I believe22:24
corvuspabelanger: example config project repo?22:25
pabelangercorvus: some of the discussions were just about having something existing online, so we can use the git driver connection for it. But, possible we want to docs to also include more details how to build that out22:26
corvuspabelanger: since we don't expect anyone to actually reuse that, how about we just inline the content into the docs and walk people through creating their own?22:26
pabelangercorvus: yah, that is an option for sure.22:26
*** rcarrillocruz has joined #openstack-meeting-alt22:26
corvusi mean, we should document using zuul-base-jobs (which will need to be a config repo -- but it only holds jobs).  and zuul-jobs, of course.22:26
corvusbut i don't think we have plans for a reusable repo with, say, pipelines at the moment.22:27
*** lpetrut has quit IRC22:27
corvusthat's still something everyone will need to create locally.  for now.  :)22:27
pabelangerokay, I'll bring it up with leifmadsen_ tomorrow and we can discuss it more in #zuul22:28
tobiashMaking that more generic would ne cool22:28
corvusyep, but a very long-term task :)22:28
corvuspabelanger, mordred: what's the status of reporting on github from openstack-infra?22:28
pabelangerI last tested it before holiday break, but haven't progressed more due to upcoming refactor of things into zuul-web. But it was working, except for 1 thing I cannot remember ATM22:29
corvuspabelanger: were there any errors in the logs?22:30
pabelangercorvus: nope22:30
mordredcorvus: I was waiting for the injest patches to land before moving forward22:30
corvuspabelanger: ok.  mordred: maybe you want to turn on your shade test?22:30
mordredcorvus: it's possible I didnt communicate that to anyone ...22:30
corvuswhy is that a blocker?22:30
mordredcorvus: it's not - I just figured that scalability was one of the larger concerns and the injest patch changes the structure of how that works...22:31
mordredcorvus: BUT- can *totally* turn on the shade patch very easily and we can see how it goes22:31
pabelangeryah, I think getting more data from shade patch works for me22:32
corvusmordred: i'm not going to say 'no' to more data :)  i say go for it whenever you're ready :)22:32
corvusand hopefully we'll have the injest patch in next week too22:32
corvusi'm far enough with the cross-source deps work (which is the next item on the list) to say i think we can have it landed in the next few days / end of week at latest.22:33
mordredcorvus: kk. I'll get that going22:33
corvusso once that lands, we'll have some *really fun* things to test22:33
pabelangerYay22:33
corvusmordred: istr you said your shade job could be used to verify the cross-source work as well?22:34
*** chhavi has joined #openstack-meeting-alt22:34
corvusmordred: also, i think you were 90% of the way through js tooling patches before the holidays -- i've added a patch to your series which we can use to validate that all the URLs that we expect to work do work22:36
Shrewswould that be the whole "changes to ansible openstack modules triggers shade tests and reporting" thing? b/c that would be exciting22:36
corvusShrews: yep22:36
* Shrews is giddy with excitement22:37
*** dave-mccowan has quit IRC22:37
corvusmordred: so when you pick that up, we can test the three different ways of serving the webapp that we know about22:37
mordredcorvus: yup!22:37
mordred(to all of the things)22:37
corvuscool22:37
corvusthe nodepool static driver from tristanC is in review22:38
corvusShrews: are we running the finger gw in openstack prod now?22:38
Shrewscorvus: yes22:38
corvusShrews: \o/22:38
pabelangerOh, nice!22:38
*** chhavi has quit IRC22:38
Shrewsfinger UUID@zuulv3.openstack.org works22:39
clarkbI think we are still running the executors on a low port right?22:39
pabelangerare we at a point to remove root user from zuul-executor now?22:39
Shrewspabelanger: yes22:39
corvusShrews: do you want to delete all the special user handling code from the executors, and have them serve finger on port XX79 by default?22:39
pabelangerShrews: awesome22:39
Shrewscorvus: sure22:39
Shrewsi love deleting code22:39
corvusShrews: cool, i think that's probably the last thing there and we can clear that from the list22:39
corvuspabelanger, leifmadsen_: ^ fyi quickstart docs change :)22:39
pabelangercorvus: ++22:40
corvusas mentioned, jlk is working on getting github3.py released...22:40
corvusand finally, clarkb put 2 new things on the list about secrets and branches22:40
clarkbthese came out of the zuulv3-issues etherpad22:41
*** kumarmn has quit IRC22:41
clarkbmy understanding of this is that without fixing this you cannot use the same secret name on different branches?22:41
*** TxGirlGeek has quit IRC22:41
clarkbwhich seems like something we should fix22:41
*** kumarmn has joined #openstack-meeting-alt22:42
clarkbI want to say it was kolla that ran into this and they worked around it by using different names22:42
corvusclarkb: yeah, i agree these seem like release-blocking bugs22:42
corvusokay.  that's the list.  i won't go through it again next meeting, but i thought it would be good to reset after the holiday break.22:43
corvus#topic  RAM governor for the executors22:44
*** openstack changes topic to "RAM governor for the executors (Meeting topic: zuul)"22:44
corvusdmsimard: i think this is your topic?22:44
*** hongbin has quit IRC22:45
corvusdmsimard: lemme know when you're back22:46
corvus#topic mailing lists22:46
*** openstack changes topic to "mailing lists (Meeting topic: zuul)"22:46
*** kumarmn has quit IRC22:46
*** TxGirlGeek has joined #openstack-meeting-alt22:46
corvusi'll send out an email about this, but while (most of us) are here... we should now have the infrastructure in place to host mailing lists at lists.zuul-ci.org22:47
corvusi would like to have a zuul-announce list, where we make release announcements and notifications about changes to job syntax/deprecation/etc (which will be important for things like the shared zuul-jobs repo)22:47
SpamapS+122:48
corvusand obviously, we need at least one other list for discussion... should we create a zuul-discuss list?  or a zuul-dev list?  or both?22:48
mordredI kind of think both22:48
corvus(ie, do we need a dev/other split, or can we start without that and just have a combined list?)22:48
pabelangerzuul-discuss for end user support?22:48
mordredcorvus: but I could see starting with zuul-discuss and splitting a zuul-dev later if it gets too much for people22:49
* fungi returns early and catches up22:49
pabelangerwhat about zuul-users22:50
clarkbI really don't like the dev/general split we have for openstack22:50
clarkband also ops.22:50
clarkbIt creates a ton of cross posting confusion and also easy ways to ignore important threads22:50
corvusthere's a lot of overlap -- any dev work we do will affect users and could benefit from general discussion, so for that, i like having one list.  i don't want people to feel like they're "bothering the devs" though if they have questions like "how should i write a job that does ..."22:50
mordredcorvus: yes - those are both sides of my thoughts :)22:51
mordredI think there are at *least* 3 personas "I am running a zuul" "I am writing jobs for a zuul" and "I am developing zuul" - many of us here are all three22:52
corvusi feel like maybe it's safer to start with one, and create more if needed -- so maybe we should have "zuul-announce" and "zuul-discuss" for now?22:52
mordredwfm22:52
clarkbsounds good22:52
pabelangersure22:52
*** TxGirlGeek has quit IRC22:53
corvusok, i'll email the infra list with that as a proposal, get feedback from folks not here ("we decided in irc what the mailing lists should be!" is especially ironic), then make lists in a day or 2.22:53
corvus#topic open discussion22:53
*** openstack changes topic to "open discussion (Meeting topic: zuul)"22:53
SpamapSI had one question come into my mind this last week22:54
*** kumarmn has joined #openstack-meeting-alt22:54
mordredcorvus: mentioned in #openstack-infra, but as a followup from earlier, https://review.openstack.org/#/q/topic:turn-on-ansible has the patches to start running stuff on ansible patches22:54
clarkbhttps://etherpad.openstack.org/p/zuulv3-issues is almost cleared out of active items. I've marked things as fixed that were fixed, gotten a few things fixed that weren't, and filed bugs for items that need longer term tracking22:54
corvusmordred: thx22:54
SpamapSIIRC we had some kind of plan to merge feature/zuulv3 into master before the 3.0 release. I don't recall what the prereqs for that were.22:55
clarkbit would be great if everyone could take a look over that and make sure their items are accurate and possibly open bugs for them if they need longer term tracking22:55
clarkbthen I can unpin the tab in my browser :)22:55
clarkbSpamapS: we need to update the puppet-openstackci deployment tooling to handle master as v322:55
*** david-lyle has joined #openstack-meeting-alt22:55
corvusSpamapS: yes! it's still imminent -- we want to land something to puppet-openstackci like https://review.openstack.org/523951 first22:55
corvusso that we don't introduce zuulv3 to the world of openstack third-party ci ops by automatically upgrading them22:56
SpamapSOk, just looking for targets of opportunity. :)22:56
SpamapSbut a puppeteer.. I am not22:56
corvusafaik that's the only thing blocking that, as soon as it lands we'll merge22:56
corvusand then i will need to unlearn 2 years of "git reset --hard origin/feature/zuulv3"22:57
clarkbthats ok I always check out master first then have to switch to feature/zuuvl322:57
fungithat'll unlearn itself pretty quickly when we delete the branch22:57
fungifatal: ambiguous argument 'origin/feature/zuulv3': unknown revision or path not in the working tree.22:58
*** slaweq has joined #openstack-meeting-alt22:58
*** kumarmn has quit IRC22:59
corvusthe stuff of dreams22:59
SpamapS:-D23:00
corvustime's up, thanks everyone!23:00
corvus#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"23:00
openstackMeeting ended Mon Jan  8 23:00:28 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
fungithanks!23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-01-08-22.01.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-01-08-22.01.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-01-08-22.01.log.html23:00
*** Shrews has left #openstack-meeting-alt23:00
*** slaweq has quit IRC23:00
*** gcb has joined #openstack-meeting-alt23:01
*** chyka_ has joined #openstack-meeting-alt23:06
*** kumarmn has joined #openstack-meeting-alt23:09
*** chyka has quit IRC23:09
*** jaypipes has quit IRC23:12
*** david-lyle has quit IRC23:12
*** david-lyle has joined #openstack-meeting-alt23:13
*** chyka_ has quit IRC23:13
*** chyka has joined #openstack-meeting-alt23:14
*** TxGirlGeek has joined #openstack-meeting-alt23:14
*** kumarmn has quit IRC23:20
*** gcb has quit IRC23:20
*** kumarmn has joined #openstack-meeting-alt23:21
*** sambetts is now known as sambetts|afk23:22
*** rmascena has quit IRC23:29
*** kumarmn has quit IRC23:29
*** chyka_ has joined #openstack-meeting-alt23:32
*** chyka has quit IRC23:35
*** felipemonteiro_ has quit IRC23:46
*** kumarmn has joined #openstack-meeting-alt23:47
*** chyka_ has quit IRC23:48
*** chyka has joined #openstack-meeting-alt23:49
*** kumarmn has quit IRC23:52
*** kumarmn has joined #openstack-meeting-alt23:53
*** Leo_m has quit IRC23:55
*** chyka_ has joined #openstack-meeting-alt23:55
*** chyka has quit IRC23:55

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