Monday, 2017-11-20

*** salv-orlando has quit IRC00:14
*** hongbin has quit IRC00:31
*** junboli has joined #openstack-meeting-alt00:52
*** hieulq has joined #openstack-meeting-alt00:54
*** tovin07_ has joined #openstack-meeting-alt00:58
*** dsariel has quit IRC01:01
*** hieulq has quit IRC01:02
*** hieulq has joined #openstack-meeting-alt01:04
*** salv-orlando has joined #openstack-meeting-alt01:15
*** hiro-kobayashi has joined #openstack-meeting-alt01:28
*** hongbin has joined #openstack-meeting-alt01:34
*** caowei has joined #openstack-meeting-alt01:41
*** lbragstad has joined #openstack-meeting-alt01:45
*** salv-orlando has quit IRC01:49
*** gcb has joined #openstack-meeting-alt01:52
*** daidv has joined #openstack-meeting-alt02:21
*** dalgaaf has quit IRC02:33
*** dalgaaf has joined #openstack-meeting-alt02:33
*** salv-orlando has joined #openstack-meeting-alt02:46
*** dave-mccowan has quit IRC03:39
*** rcernin has quit IRC03:50
*** rcernin has joined #openstack-meeting-alt03:52
*** anilvenkata has joined #openstack-meeting-alt03:53
*** hongbin has quit IRC03:57
*** hiro-kobayashi has quit IRC04:10
*** hiro-kobayashi has joined #openstack-meeting-alt04:12
*** links has joined #openstack-meeting-alt04:13
*** yamamoto has joined #openstack-meeting-alt04:21
*** coolsvap has joined #openstack-meeting-alt04:22
*** yangyapeng has joined #openstack-meeting-alt04:26
*** janki has joined #openstack-meeting-alt05:03
*** pgadiya has joined #openstack-meeting-alt05:13
*** pgadiya has quit IRC05:13
*** skramaja has joined #openstack-meeting-alt05:13
*** zerick has joined #openstack-meeting-alt05:23
*** caowei has quit IRC05:28
*** d0ugal_ has joined #openstack-meeting-alt05:30
*** dsariel has joined #openstack-meeting-alt05:32
*** d0ugal has quit IRC05:32
*** rcernin has quit IRC05:38
*** macermak has joined #openstack-meeting-alt05:53
*** kumarmn_ has joined #openstack-meeting-alt05:56
*** caowei has joined #openstack-meeting-alt06:03
*** caowei has quit IRC06:04
*** kumarmn_ has quit IRC06:19
*** gouthamr has quit IRC06:20
*** janki is now known as janki|afk06:22
*** lpetrut has joined #openstack-meeting-alt06:27
*** jtomasek has joined #openstack-meeting-alt06:33
*** jbadiapa has joined #openstack-meeting-alt06:35
*** youzp has joined #openstack-meeting-alt06:37
*** salv-orlando has quit IRC06:37
*** salv-orlando has joined #openstack-meeting-alt06:38
*** karthiks has joined #openstack-meeting-alt06:38
*** mjura has joined #openstack-meeting-alt06:38
*** bhavik has joined #openstack-meeting-alt06:47
*** yamamoto has quit IRC06:47
*** gouthamr has joined #openstack-meeting-alt06:55
*** yamamoto has joined #openstack-meeting-alt06:56
*** marios has joined #openstack-meeting-alt07:00
*** jprovazn has joined #openstack-meeting-alt07:07
*** lpetrut has quit IRC07:08
*** lpetrut has joined #openstack-meeting-alt07:08
*** lpetrut has quit IRC07:14
*** jtomasek has quit IRC07:16
*** youzp has quit IRC07:21
*** youzp has joined #openstack-meeting-alt07:22
*** lpetrut has joined #openstack-meeting-alt07:22
*** gcb has quit IRC07:25
*** gcb has joined #openstack-meeting-alt07:26
*** d0ugal_ has quit IRC07:31
*** jtomasek has joined #openstack-meeting-alt07:34
*** janki|afk is now known as janki07:35
*** belmoreira has joined #openstack-meeting-alt07:38
*** caowei has joined #openstack-meeting-alt07:44
*** oidgar has joined #openstack-meeting-alt07:47
*** youzp_ has joined #openstack-meeting-alt07:49
*** youzp_ has quit IRC07:50
*** fzdarsky has joined #openstack-meeting-alt07:50
*** youzp has quit IRC07:50
*** youzp has joined #openstack-meeting-alt07:50
*** fzdarsky has quit IRC07:52
*** lpetrut has quit IRC07:53
*** fzdarsky has joined #openstack-meeting-alt07:54
*** ccha has joined #openstack-meeting-alt08:01
*** youzp_ has joined #openstack-meeting-alt08:03
*** youzp has quit IRC08:08
*** youzp_ has quit IRC08:10
*** alexchadin has joined #openstack-meeting-alt08:11
*** d0ugal_ has joined #openstack-meeting-alt08:14
*** alexchadin has quit IRC08:16
*** alexchadin has joined #openstack-meeting-alt08:17
*** alexchadin has quit IRC08:19
*** danpawlik has quit IRC08:19
*** kumarmn has joined #openstack-meeting-alt08:19
*** alexchadin has joined #openstack-meeting-alt08:19
*** vds has joined #openstack-meeting-alt08:20
*** radeks has joined #openstack-meeting-alt08:23
*** kumarmn has quit IRC08:24
*** gouthamr has quit IRC08:25
*** ircuser-1 has joined #openstack-meeting-alt08:28
*** bfernando has joined #openstack-meeting-alt08:39
*** salv-orlando has quit IRC08:42
*** salv-orlando has joined #openstack-meeting-alt08:43
*** matrohon has joined #openstack-meeting-alt08:45
*** salv-orlando has quit IRC08:47
*** jpena|off is now known as jpena08:48
*** numans has joined #openstack-meeting-alt08:49
*** d0ugal_ has quit IRC08:53
*** d0ugal has joined #openstack-meeting-alt08:53
*** d0ugal has quit IRC08:53
*** d0ugal has joined #openstack-meeting-alt08:53
*** rmart04 has joined #openstack-meeting-alt08:53
*** hiro-kobayashi has quit IRC08:54
*** yamamoto has quit IRC08:54
*** apetrich has quit IRC08:56
*** apetrich has joined #openstack-meeting-alt08:56
*** belmoreira has quit IRC08:58
*** salv-orlando has joined #openstack-meeting-alt08:58
*** MarkBaker has joined #openstack-meeting-alt08:58
*** spectr has joined #openstack-meeting-alt09:07
*** spectr has quit IRC09:07
*** numans has quit IRC09:08
*** numans has joined #openstack-meeting-alt09:10
*** spectr has joined #openstack-meeting-alt09:11
*** spectr has quit IRC09:12
*** danpawlik has joined #openstack-meeting-alt09:18
*** yamamoto has joined #openstack-meeting-alt09:20
*** d0ugal has quit IRC09:24
*** d0ugal has joined #openstack-meeting-alt09:25
*** derekh has joined #openstack-meeting-alt09:26
*** junboli has quit IRC09:34
*** yamamoto has quit IRC09:36
*** yamamoto has joined #openstack-meeting-alt09:37
*** yamamoto has quit IRC09:45
*** lpetrut has joined #openstack-meeting-alt09:50
*** belmoreira has joined #openstack-meeting-alt09:52
*** bhavik has quit IRC09:53
*** lpetrut has quit IRC09:56
*** ccamacho has joined #openstack-meeting-alt10:02
*** bhavik has joined #openstack-meeting-alt10:03
*** tovin07_ has quit IRC10:08
*** lpetrut has joined #openstack-meeting-alt10:13
*** yamamoto has joined #openstack-meeting-alt10:17
*** caowei has quit IRC10:17
*** caowei has joined #openstack-meeting-alt10:18
*** bhavik1 has joined #openstack-meeting-alt10:37
*** bhavik has quit IRC10:39
*** bhavik1 is now known as bhavik10:39
*** bhavik has quit IRC10:55
*** ccamacho has quit IRC10:56
*** ccamacho has joined #openstack-meeting-alt10:57
*** jpena is now known as jpena|off10:57
*** jpena|off is now known as jpena10:58
*** kmalloc has joined #openstack-meeting-alt11:01
*** szaher has quit IRC11:02
*** anilvenkata has quit IRC11:06
*** belmoreira has quit IRC11:21
*** gcb has quit IRC11:24
*** caowei has quit IRC11:28
*** alexchadin has quit IRC11:28
*** rfolco has joined #openstack-meeting-alt11:32
*** szaher has joined #openstack-meeting-alt11:51
*** d0ugal has quit IRC11:51
*** jkilpatr has quit IRC11:52
*** d0ugal has joined #openstack-meeting-alt11:53
*** raildo has joined #openstack-meeting-alt11:59
*** belmoreira has joined #openstack-meeting-alt12:06
*** efried_zzz is now known as efried12:09
*** pbourke has quit IRC12:14
*** pbourke has joined #openstack-meeting-alt12:16
*** jkilpatr has joined #openstack-meeting-alt12:25
*** dsariel has quit IRC12:27
*** sdague has joined #openstack-meeting-alt12:28
*** ccamacho has quit IRC12:28
*** janki has quit IRC12:29
*** links has quit IRC12:31
*** ansmith has quit IRC12:36
*** yamamoto has quit IRC12:39
*** dsariel has joined #openstack-meeting-alt12:42
*** anilvenkata has joined #openstack-meeting-alt12:48
*** jpena is now known as jpena|lunch12:50
*** dprince has joined #openstack-meeting-alt12:58
*** salv-orlando has quit IRC12:59
*** gcb has joined #openstack-meeting-alt12:59
*** salv-orlando has joined #openstack-meeting-alt13:00
*** yamamoto has joined #openstack-meeting-alt13:01
*** salv-orlando has quit IRC13:04
*** ijw has joined #openstack-meeting-alt13:07
*** MarkBaker has quit IRC13:08
*** alexchadin has joined #openstack-meeting-alt13:13
*** yamamoto has quit IRC13:13
*** ijw_ has joined #openstack-meeting-alt13:14
*** ijw has quit IRC13:17
*** links has joined #openstack-meeting-alt13:17
*** toscalix_ has joined #openstack-meeting-alt13:19
*** marios has quit IRC13:20
*** coolsvap has quit IRC13:20
*** MarkBaker has joined #openstack-meeting-alt13:21
*** rossella_s has quit IRC13:22
*** ijw has joined #openstack-meeting-alt13:23
*** marios has joined #openstack-meeting-alt13:23
*** markvoelker has quit IRC13:23
*** markvoelker has joined #openstack-meeting-alt13:24
*** toscalix_ has quit IRC13:24
*** rossella_s has joined #openstack-meeting-alt13:25
*** ijw_ has quit IRC13:26
*** maciejjo1 has joined #openstack-meeting-alt13:29
*** dpawlik has joined #openstack-meeting-alt13:29
*** danpawlik has quit IRC13:30
*** maciejjozefczyk has quit IRC13:30
*** ansmith has joined #openstack-meeting-alt13:34
*** dave-mccowan has joined #openstack-meeting-alt13:36
*** dsariel has quit IRC13:36
*** toscalix_ has joined #openstack-meeting-alt13:37
*** skramaja has quit IRC13:38
*** ijw has quit IRC13:41
*** maciejjo1 is now known as maciejjozefczyk13:44
*** dave-mcc_ has joined #openstack-meeting-alt13:46
*** dave-mccowan has quit IRC13:48
*** dsariel has joined #openstack-meeting-alt13:49
*** jpena|lunch is now known as jpena13:54
*** MarkBaker_ has joined #openstack-meeting-alt13:54
*** takashin has joined #openstack-meeting-alt13:54
*** MarkBaker has quit IRC13:55
*** cdent has joined #openstack-meeting-alt13:56
*** yangyapeng has quit IRC13:59
*** salv-orlando has joined #openstack-meeting-alt13:59
cdent#startmeeting nova_scheduler14:00
openstackMeeting started Mon Nov 20 14:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. 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
cdent#chair efried14:00
openstackCurrent chairs: cdent efried14:00
efried\o14:00
cdent#link agenda https://wiki.openstack.org/wiki/Meetings/NovaScheduler14:00
takashino/14:00
cdentit looks like the agenda hasn’t been recently updated so I think we can probably have a relatively free form catch-up-on-what-matters meeting14:00
efriedI had been in the process of updating the agenda, but didn't finish in time, sorry.14:01
cdentif it had something interesting would you like a moment?14:01
efriednope14:01
cdentor are you happy to continue free form?14:01
cdentOkay in the case:14:01
cdent#topic specs14:01
*** openstack changes topic to "specs (Meeting topic: nova_scheduler)"14:01
efriedBut I can comment on them as we go.14:02
cdentAre there any pending specs14:02
efried#link symmetric GET and PUT of allocations https://review.openstack.org/#/c/508164/ is merged14:02
cdentyeah, and looks like nothing else is pending scheduler/placement-wise14:02
cdentanyone disagree?14:03
cdent#topic pending reviews that need attention14:03
*** openstack changes topic to "pending reviews that need attention (Meeting topic: nova_scheduler)"14:03
cdentThere are lots of things currently under review, efried did a fine job of doing the placement update while I was away, I’ll pick it up again on friday14:03
cdentAre there any reviews that are stuck, or have big questions?14:04
stephenfinefried: oh hai14:04
efriedcdent - stephenfin just said in -nova that he'd get on the nrp series this week.14:04
cdentwell now that it is logged here, he’s forced to do it14:05
cdentno backing out14:05
efriedWhich is great - that's the #1 needs-core-eyeballs series IMO.14:05
stephenfinHurrah!14:05
cdent#action stephenfin going to review the nested resource providers and we are all very grateful14:05
efriedClosely followed by https://review.openstack.org/#/c/516782/ which is now the first in the series (the first four already merged - yay!)14:06
efriedIt's actually the last in the refactor series, but has a couple of additional subseries piled on top of it.14:07
cdent#link lots of allocation candidate clean ups, tests, fixes starting near: https://review.openstack.org/#/c/516782/14:07
efriedAnd traits affordance ^14:07
efriedBasically, both of the above series (serieses??) are prerequisite to getting placement handling traits and granular.14:08
stephenfinSure thing. I'll start with nested RPs first since I know those14:08
efried++14:08
cdent#link selection objects and alt destinations: https://review.openstack.org/#/c/499239/14:09
cdentthat’s the other main theme14:09
* bauzas waves late14:09
cdentanyone else need/want to point out reviews before we move on to bugs?14:10
efried#link Include project_id and user_id in AllocationList.get_all_by_consumer_id https://review.openstack.org/#/c/512420/ <== this guy has *nine* +1s and a +2.  Should be a slam dunk +A for a willing core.14:10
*** dtrainor has joined #openstack-meeting-alt14:11
stephenfinI avoided +2ing that for reasons given in the review. bauzas? ^14:12
stephenfinIf not, I'll take the hit, heh14:13
cdentit’s only in the followin changes that microversions get involved, so it’s not irrevocable14:13
cdent#topic bugs14:14
bauzasstephenfin: will look14:14
*** openstack changes topic to "bugs (Meeting topic: nova_scheduler)"14:14
cdent#link bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=placement&orderby=-id&start=014:14
cdentlooks like people have been finding plenty, which is great14:14
*** yamamoto has joined #openstack-meeting-alt14:14
cdentefried: on the stuff with non-connected RPs and get_by_filters/get_by_requests was there some kind of logic flaw or bogus SQL or ???14:16
efriedcdent As yet unknown.  That bug still exists, even at the top of the series.14:16
cdentoh, bummer14:17
*** julim has joined #openstack-meeting-alt14:17
efriedI think Jay is on the hook to debug that one, or possibly alex_xu14:18
efriedI could try, but my sqla-fu may not be up to the task yet.14:18
cdentbut the failing test exists, right?14:18
efriedcdent Oh, several, yes.14:19
efriedNot merged, but in the aforementioned series.14:20
*** yamamoto has quit IRC14:20
*** yamamoto has joined #openstack-meeting-alt14:20
bauzascdent: note that we have a long list of new bugs14:20
efriedWorth mentioning, btw: GET /allocation_candidates bugs ought to be verified against the top of that series.14:20
efriedBecause some of the "refactoring" also changed logic and fixed some bugs.14:20
bauzascdent: so we could possibly have more placement/scheduler bugs14:20
efriedDo we need to do a placement bug smash?14:22
cdentprobably more important is to do a general untriaged bug triaging14:23
*** yangyapeng has joined #openstack-meeting-alt14:24
efriedThat's probably what I meant, just don't know the right words.14:24
cdentI was effectively agreeing with bauzas’ warning14:25
bauzascdent: I'll look at the new bugs by the week14:25
bauzasbut if people would help me, <314:25
bauzasFWIW, I provided a Summit talk about that in SYD :p14:25
bauzasI mean, me and stephenfin :)14:26
cdent#topic open discussion14:26
*** openstack changes topic to "open discussion (Meeting topic: nova_scheduler)"14:26
cdentanyone have anything else, or should efried just talk to me about what he’s trying to talk to me about in #openstack-nova?14:26
efried(which is a loose debate on the relative merits of a placement client lib.)14:27
*** [HeOS] has quit IRC14:28
cdentI guess you have the floor mr efried14:28
efried...which came from stephenfin posting a link to this review: https://review.openstack.org/#/c/511936/14:28
efriedOkay, so the "ideal world" view is that the placement API should be returning stuff in a form that's consumable as "just json" without having to do a bunch of extra processing.14:29
*** yangyapeng has quit IRC14:29
bauzasefried: what's your concern ?14:30
cdentrather that any complexity is domain specific and should not be built into the client14:30
bauzasI wasn't looking at -nova14:30
efriedIt seems to me as though the current form of the placement API, with respect to querying RPs at least, is much closer to reflecting the database than to being able to get a useful set of information.14:30
efriedFor example, you have to do three or four separate queries to figure out a RP's aggregates, traits, and inventories.14:31
efriedI see clients finding it useful to be able to do one call and get a single blob with all that information collated.14:31
cdentyes, there was an mid stage design that had a more full resource provider representation14:31
efriedWhich may be an argument to add an API for that.14:31
*** gouthamr has joined #openstack-meeting-alt14:32
efriedparticularly to reduce the number of calls, for the sake of efficiency.14:32
bauzaswell14:32
bauzasthat's a reasonable point14:32
bauzasbut14:32
*** pbourke has quit IRC14:32
*** alexchadin has quit IRC14:32
bauzasthe problem is, should we orchestrate more than just providing allocations and inventories ?14:33
bauzasFWIW, we said that placement is just here for providing the above14:33
efriedbauzas Not necessarily, but even within that scope the point remains.14:33
efriedBut I think perhaps the "ideal world" view holds here: if we find ourselves needing a client lib call (i.e. more than one consumer cares about it) to get a certain collected set of information, that's a case for adding an actual API call to do the same.14:33
efriedI cited this as an example: https://review.openstack.org/#/c/521098/4/nova/scheduler/client/report.py14:34
bauzasI think that's probably something that should live on the client side14:34
bauzasfor aggregating all the resources14:34
*** reedip_ has joined #openstack-meeting-alt14:34
*** belmoreira has quit IRC14:34
efriedbauzas So yeah, right now the above is living on the client side.14:34
bauzasI know14:35
cdentyeah, my bone of contention here is resting on the hope that more than one consumer _won’t_ need the call linked in the patchset14:35
bauzasefried: and I think it should stay at least until more than just nova uses placement14:35
bauzasthe API should stay minimalistic and RESTful at least until the above14:36
bauzasthen, we could discuss on how to modify that14:36
efriedI haven't yet looked at the patch stephenfin posted.  I guess I'll reserve judgment until I see how much overlap, if any, that patch presents with what we've built and are building in SchedulerReportClient.14:36
efriedAnyway, it's something we ought to keep an eye on.  In summary: watch for placement consumers doing similar client-side things, and consider whether those things are appropriate for one or both of a) a client lib; b) API adds.14:38
efriedUnless anyone has anything further, we can call it early.14:39
bauzassure14:39
cdentI agree with that summary14:39
bauzaslooks reasonable14:39
cdentalways be watching14:40
cdentanyone have any last words?14:40
bauzasalbeit.14:40
cdentthanks for coming14:40
cdent#endmeeting14:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:40
openstackMeeting ended Mon Nov 20 14:40:22 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-11-20-14.00.html14:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-11-20-14.00.txt14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-11-20-14.00.log.html14:40
*** cdent has left #openstack-meeting-alt14:41
*** takashin has left #openstack-meeting-alt14:42
*** yangyapeng has joined #openstack-meeting-alt14:42
*** yangyapeng has quit IRC14:46
*** pbourke has joined #openstack-meeting-alt14:47
*** manjeets_ has joined #openstack-meeting-alt14:54
*** toscalix_ has quit IRC14:56
*** yamahata has joined #openstack-meeting-alt15:01
*** links has quit IRC15:01
*** yangyapeng has joined #openstack-meeting-alt15:04
*** anilvenkata has quit IRC15:05
*** dave-mcc_ is now known as dave-mccowan15:06
*** fnaval has joined #openstack-meeting-alt15:07
*** gcb has quit IRC15:08
*** yangyapeng has quit IRC15:08
*** hongbin has joined #openstack-meeting-alt15:11
*** links has joined #openstack-meeting-alt15:13
*** jaypipes has joined #openstack-meeting-alt15:15
*** kumarmn has joined #openstack-meeting-alt15:20
*** marst has joined #openstack-meeting-alt15:20
*** d0ugal has quit IRC15:24
*** yangyapeng has joined #openstack-meeting-alt15:24
*** bhavik1 has joined #openstack-meeting-alt15:24
*** kumarmn has quit IRC15:25
*** d0ugal has joined #openstack-meeting-alt15:27
*** links has quit IRC15:27
*** yangyapeng has quit IRC15:28
*** ansmith has quit IRC15:30
*** ansmith has joined #openstack-meeting-alt15:31
*** bhavik1 has quit IRC15:39
*** reedip_ has quit IRC15:53
*** bnemec-pto is now known as bnemec15:54
*** yamamoto has quit IRC16:00
*** manjeets_ has quit IRC16:01
*** mjura has quit IRC16:02
*** chyka has joined #openstack-meeting-alt16:04
*** yamamoto has joined #openstack-meeting-alt16:06
*** rmart04 has quit IRC16:08
*** yamamoto has quit IRC16:11
*** jkilpatr has quit IRC16:13
*** chyka has quit IRC16:14
*** chyka has joined #openstack-meeting-alt16:15
*** jkilpatr has joined #openstack-meeting-alt16:30
*** yamamoto has joined #openstack-meeting-alt16:36
*** jtomasek has quit IRC16:36
*** jtomasek has joined #openstack-meeting-alt16:37
*** salv-orlando has quit IRC16:38
*** macermak has quit IRC16:38
*** salv-orlando has joined #openstack-meeting-alt16:39
*** bhavik1 has joined #openstack-meeting-alt16:39
*** yamamoto has quit IRC16:41
*** jpena is now known as jpena|brb16:43
*** salv-orlando has quit IRC16:43
*** bhavik1 has quit IRC16:50
*** [HeOS] has joined #openstack-meeting-alt16:50
*** bhavik1 has joined #openstack-meeting-alt16:50
*** dsariel has quit IRC16:52
*** oidgar has quit IRC16:53
*** bhavik1 has quit IRC16:59
*** marios has quit IRC17:02
*** yamamoto has joined #openstack-meeting-alt17:05
*** yamamoto has quit IRC17:05
*** jkilpatr has quit IRC17:09
*** jkilpatr has joined #openstack-meeting-alt17:10
*** iyamahat has joined #openstack-meeting-alt17:18
*** lpetrut has quit IRC17:23
*** yamahata has quit IRC17:24
*** iyamahat has quit IRC17:25
*** jpena|brb is now known as jpena17:26
*** matrohon has quit IRC17:30
*** rossella_s has quit IRC17:30
*** rossella_s has joined #openstack-meeting-alt17:33
*** salv-orlando has joined #openstack-meeting-alt17:39
*** yangyapeng has joined #openstack-meeting-alt17:43
*** efried is now known as efried_rollin17:44
*** salv-orlando has quit IRC17:45
*** rwsu has joined #openstack-meeting-alt17:45
*** iyamahat has joined #openstack-meeting-alt17:46
*** yangyapeng has quit IRC17:50
*** derekh has quit IRC18:01
*** yamahata has joined #openstack-meeting-alt18:03
*** radeks has quit IRC18:04
*** yamamoto has joined #openstack-meeting-alt18:05
*** bfernando has quit IRC18:07
*** radeks has joined #openstack-meeting-alt18:09
*** yamamoto has quit IRC18:11
*** yangyapeng has joined #openstack-meeting-alt18:12
*** yangyapeng has quit IRC18:17
*** jpena is now known as jpena|off18:20
*** lpetrut has joined #openstack-meeting-alt18:29
*** yangyapeng has joined #openstack-meeting-alt18:31
*** yangyapeng has quit IRC18:34
*** salv-orlando has joined #openstack-meeting-alt18:40
*** salv-orlando has quit IRC18:42
*** salv-orlando has joined #openstack-meeting-alt18:42
*** lpetrut has quit IRC18:51
*** rmcall_ has joined #openstack-meeting-alt18:52
*** lpetrut has joined #openstack-meeting-alt18:55
*** yangyapeng has joined #openstack-meeting-alt18:57
*** rmcall_ has quit IRC18:58
*** lpetrut has quit IRC19:01
*** yangyapeng has quit IRC19:01
*** lpetrut has joined #openstack-meeting-alt19:01
*** yangyapeng has joined #openstack-meeting-alt19:15
*** rossella_s has quit IRC19:18
*** yangyapeng has quit IRC19:20
*** rossella_s has joined #openstack-meeting-alt19:21
*** kumarmn has joined #openstack-meeting-alt19:29
*** rwsu has quit IRC19:30
*** yangyapeng has joined #openstack-meeting-alt19:36
*** yangyapeng has quit IRC19:41
*** absubram has joined #openstack-meeting-alt19:46
*** Sukhdev has joined #openstack-meeting-alt19:48
*** annabelleB has joined #openstack-meeting-alt19:51
*** tobiash has joined #openstack-meeting-alt19:55
*** radeks has quit IRC19:55
*** yangyapeng has joined #openstack-meeting-alt19:57
*** abishop has joined #openstack-meeting-alt19:59
*** yangyapeng has quit IRC20:01
*** rossella_s has quit IRC20:03
dave-mccowan#startmeeting barbican20:03
openstackMeeting started Mon Nov 20 20:03:48 2017 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: barbican)"20:03
openstackThe meeting name has been set to 'barbican'20:03
dave-mccowan#topic roll call20:03
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:03
dave-mccowano/20:03
abishopo/20:04
*** jtomasek has quit IRC20:09
*** [HeOS] has quit IRC20:11
*** dsariel has joined #openstack-meeting-alt20:13
*** [HeOS] has joined #openstack-meeting-alt20:17
dave-mccowanplease review:  https://review.openstack.org/51473420:17
dave-mccowan#endmeeting20:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:17
openstackMeeting ended Mon Nov 20 20:17:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-11-20-20.03.html20:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-11-20-20.03.txt20:17
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-11-20-20.03.log.html20:17
*** yangyapeng has joined #openstack-meeting-alt20:17
*** abishop has left #openstack-meeting-alt20:18
*** yangyapeng has quit IRC20:22
*** salv-orlando has quit IRC20:24
*** salv-orlando has joined #openstack-meeting-alt20:25
*** salv-orlando has quit IRC20:28
*** rmascena has joined #openstack-meeting-alt20:29
*** raildo has quit IRC20:31
*** matrohon has joined #openstack-meeting-alt20:33
*** salv-orlando has joined #openstack-meeting-alt20:36
*** jprovazn has quit IRC20:41
*** yangyapeng has joined #openstack-meeting-alt20:41
*** efried_rollin is now known as efried20:43
*** yangyapeng has quit IRC20:45
*** rmascena has quit IRC20:46
*** annabelleB has quit IRC20:53
*** rwsu has joined #openstack-meeting-alt20:54
*** annabelleB has joined #openstack-meeting-alt20:55
*** felipemonteiro has joined #openstack-meeting-alt20:57
*** rwsu has quit IRC21:00
*** jkilpatr_ has joined #openstack-meeting-alt21:00
*** dprince has quit IRC21:00
*** jkilpatr has quit IRC21:01
*** rwsu has joined #openstack-meeting-alt21:01
*** jkilpatr_ has quit IRC21:01
*** jkilpatr_ has joined #openstack-meeting-alt21:01
*** krtaylor has quit IRC21:03
*** rwsu has quit IRC21:05
*** rwsu has joined #openstack-meeting-alt21:05
*** rwsu has quit IRC21:06
*** rwsu has joined #openstack-meeting-alt21:06
*** rfolco has quit IRC21:11
*** erlon has joined #openstack-meeting-alt21:12
*** krtaylor has joined #openstack-meeting-alt21:16
*** dave-mccowan has quit IRC21:18
*** markstur has joined #openstack-meeting-alt21:22
*** matrohon has quit IRC21:25
*** rwsu has quit IRC21:29
*** julim has quit IRC21:38
*** Sukhdev has quit IRC21:41
*** ansmith has quit IRC21:42
*** felipemonteiro has quit IRC21:44
*** rcernin has joined #openstack-meeting-alt21:48
*** dsariel has quit IRC21:55
jeblairhi, any zuul folks around?22:04
clarkbI'm here22:04
pabelangerpresent22:04
fungioh, yep22:05
fungi'tis time22:05
*** dmsimard has joined #openstack-meeting-alt22:06
dmsimardhello22:06
*** jlk has joined #openstack-meeting-alt22:06
dmsimardI'll have to fix my calendar notification..22:06
fungican't put it in utc?22:06
dmsimardprobably, yeah, but I guess it defaults to EST/EDT or whatever it is22:06
* fungi wonders how calendar applications deal with mixing timezones22:06
jlkpoorly22:06
jeblairheh22:07
fungiwhether an entry follows dst is hopefully a field ni ical format or something22:07
fungis/ni/in/22:07
jeblair#startmeeting zuul22:07
openstackMeeting started Mon Nov 20 22:07:51 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:07
*** openstack changes topic to " (Meeting topic: zuul)"22:07
openstackThe meeting name has been set to 'zuul'22:07
jlkThe meeting should be stored in UTC, and then display is adjusted by local display zone info22:08
jeblair#link agenda: https://wiki.openstack.org/wiki/Meetings/Zuul22:08
jlkbut people fail at thinking like that, so some events are stored actually in the local timezone, so that the "time" doesn't change when the offset does22:08
jeblair#link last meeting: http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-11-13-22.10.log.html22:08
jeblairThanks to Shrews for chairing the last meeting!22:08
jeblairit was nice and short, so i just linked to the transcript22:08
fungii found it helpful, even if short22:08
jeblairi will only add that the infra+zuul team did not have rotten vegetables thrown at us so i consider it a success (in fact, many nice things were said about v3)22:09
jeblairit=summit22:09
pabelangeryay22:10
*** rwsu has joined #openstack-meeting-alt22:10
fungiyes, none of the vegetable they threw were rotten22:10
pabelangera lot of excitement around zuulv3 at summit22:10
jlkwoo22:10
jeblair#topic Add support for shared ansible_host in inventory (pabelanger)22:10
*** openstack changes topic to "Add support for shared ansible_host in inventory (pabelanger) (Meeting topic: zuul)"22:10
*** rossella_s has joined #openstack-meeting-alt22:10
pabelangerso, this is something I found when trying to convert a zuulv2 job to native zuulv322:11
pabelangerit is more an optimization I think on CI resources and hopefully something we want to consider22:11
jeblair#link https://review.openstack.org/521324/22:11
pabelangerright now, if I use our current nodeset stanza, I'd have to request 6 nodes from nodepool, when in fact, the way the playbooks are written, I really only need 1.22:12
jeblairpabelanger: i take it the zuulv2 job was running ansible within the job, and you're trying to move that ansible up to top-level zuulv3 internal ansible?22:12
pabelangeralso, host groups doesn't work in this case,  because of the way variable scoping is handled22:12
pabelangerjeblair: correct22:12
dmsimardI'm not sure I'm following, have a bad case of mondays22:13
jeblairpabelanger: cool.  so this isn't a regression from v2, more of an impedence mismatch with zuulv3 internal ansible and native ansible.  which is cool -- we want to make it as transparant as possible.22:13
* dmsimard reads review22:13
mordredif there are differences in how variable scoping works, I could see that being something other folks would run in to should they attempt to do what pabelanger is trying to do too22:13
mordredyah - what jeblair said22:13
dmsimardpabelanger: oh, different hosts which lead back to the same host22:13
pabelangerjeblair: Yup, in fact, requesting the 5 nodes from nodepool work fine.  I just didn't want to land it and eat up a bunch of nodes for each patch22:14
pabelangerdmsimard: right22:14
mordred"I want 3 different ansible hosts, but I only need one node"22:14
clarkbwouldn't you put the single node in different groups with zuulv322:14
clarkbthen have your playbooks operate on the various groups?22:14
clarkbbut one node could be in say 6 groups22:14
mordredclarkb: yah - that apparently behaves differently in some ways22:14
dmsimardclarkb: yes and no, you can do both22:14
mordredclarkb: (that was my first suggestion as well)22:15
fungipabelanger: will it run ~5x as fast if scheduled across 5 nodes? if so, the larger node size doesn't sound too terrible22:15
pabelangerclarkb: yes, that is possible but it would require a rewrite in my case22:15
dmsimardclarkb: like, technically, there's nothing that prevents "keystone.domain.tld" "nova.domain.tld" to ultimately resolve to the same IP address while also being different "hosts" in ansible22:15
dmsimardthe problem here is that we use IP addresses, not hostnames22:15
jeblairpabelanger: what's the deficiency with using groups?22:16
jeblairi know "something about var scoping" but is there something more specific i can reference?22:16
dmsimardpabelanger: I think we might break some assumptions in roles if we do this, especially multinode roles22:16
dmsimardjeblair: play host filtering is an example22:16
mordredso if we want to support the story, as much as possible, of "run your existing ansible as part of your testing" - then if there is a semantic distinction between 2 hosts with the same IP and a single host in two groups, then I think we need to allow a user to express which they want22:17
pabelangerjeblair: it is likely better is I work up simple playbook example, because I'm likley not going to explain it very well.22:17
dmsimardjeblair: if you want to do an "all in one" but your playbooks/roles are built to target different hosts22:17
jeblairdmsimard: isn't that an anti-pattern?  (ie, shouldn't you filter plays based on groups or roles anyway?)22:17
mordred(also, yah, having a little clarity on the things that are different between the two would likely be helpful for all of our deeper understanding)22:17
dmsimardI have a (bad) example, one sec22:17
dmsimardhttps://github.com/rdo-infra/rdo-container-registry/blob/master/hosts22:18
dmsimardit so happens that I'm installing everything on the same host, but the playbooks are made to target specific groups to install specific things22:18
dmsimardpabelanger: ^ does that make sense ?22:18
jeblairdmsimard: iiuc, that case should be handled currently with our group support (aside from the openshift_node_labels, but that's only because we don't do any host-specific inventory vars right now.  we could, but that's a different change)22:19
clarkbdmsimard: right but we have different groups ability so your think shoudl work right?22:19
dmsimardand then there's an example of var scoping in that example, if you look at the nodes group22:19
pabelangerright, but more specifically ansible_host seems to create a new SSH connection (which resets variable scope) where using groups doesn't. It will just run everything from start to finish using 1 connection. Based on my local testing22:19
mordredpabelanger: yah - that's, I think, the most important distiction22:20
dmsimardpabelanger: that strangely rings me a bell22:20
jeblairpabelanger: multiple ssh connections make sense, how that's connected to variable scoping i don't understand22:20
pabelangerbut, I'll setup a simple playbook / inventory demonstrate the issue22:20
mordredpabelanger: ++22:20
dmsimardjeblair: hostvars can arguably be workaround by supplying a host_vars directory so it's not a big deal I think22:21
dmsimard(or group_vars)22:21
dmsimardI don't think we need to support providing them in the nodesets (unless we really want to)22:21
jeblairdmsimard: either way, based on my current understanding, i think it's orthogonal to this question, so we can set it aside for now22:21
mordredyah22:22
* dmsimard nods22:22
dmsimarda reproducer would indeed help22:22
pabelangerokay, will get that done for tomorrow and we can discuss more22:22
jeblairokay, my personal summary here is: i'm not opposed to this on principle, but before we proceed, i'd like to understand it a bit more; pabelanger will help by suppling more examples and details.  and if we do need to proceed, we should evaluate dmsimard's concern about assumptions in multinode jobs.22:23
jeblairthat jive for folks?22:23
pabelanger++22:23
mordredI agree22:23
mordredfrom a philosophical point of view, I'd prefer to minimize the number of times we have to say to someone "to use your existing ansible in zuul, you need to rewrite it"22:23
dmsimardyeah.22:23
mordredthere will be some cases in which that is unavoidable, of course22:23
*** yangyapeng has joined #openstack-meeting-alt22:23
fungisgtm22:24
jeblairmordred: ++22:24
pabelangeryah, this was the closes way I could reproduce an existing inventory file I was testing with in v222:24
jeblair#agreed pabelanger will help by suppling more examples and details before we proceed with this.  if we do need to proceed, we should evaluate dmsimard's concern about assumptions in multinode jobs.22:24
jeblairi -1d the change with a quick summary too, so we don't lose it22:25
pabelangerack22:25
jeblair#topic Allow run to be list of playbooks (pabelanger)22:25
*** openstack changes topic to "Allow run to be list of playbooks (pabelanger) (Meeting topic: zuul)"22:25
pabelangerSo, this was actually the first way I solved above, but kept it alive because it might be usefully.  Having a job run multiple playbooks22:26
jeblairthis seems to touch on similar issues...22:26
jeblairah :)22:26
pabelangeryup22:26
jeblairthat was my question22:26
*** pashkin has quit IRC22:26
jeblair#link https://review.openstack.org/51959622:26
jeblairso this is a semi-alternate to the other change22:26
*** jkilpatr_ has quit IRC22:26
pabelangerYah, gave the option to run back to back playbooks with specific hosts22:27
pabelangerkinda like we do on puppetmaster today with ansible22:27
pabelangerso, not sure if we want to consider supporting it or leave until later22:27
clarkbconsidering it is something we already do elsewhere it seems to make sense as a feature22:27
*** yangyapeng has quit IRC22:28
jeblairactually, why do we do that on puppetmaster?22:28
pabelangerI know we wrap each ansible-playbook with timeout, did we break it out due to memory issues?22:29
jeblairis it something about parallelism?  or exiting on failure?22:30
mordredjeblair: I think it's acutlaly just historical22:30
*** pashkin has joined #openstack-meeting-alt22:30
mordredwe had a run_puppet.sh - and we started using ansible to run it by modifying that script one bit at a time22:30
clarkbjeblair: mordred the big reason for it today is decoupling infracloud from everything else22:31
jeblairpabelanger: how would this have solved your problem?  even if zuul ran multiple playbooks in sequence, it would still have the same vars?22:31
*** jlk has quit IRC22:31
clarkbbecause infracloud is more likely to fail and adds a significant time to the round robin22:31
mordredjeblair: vars set by tasks in the plays get reset across playbook invocations22:31
jeblairclarkb: right, but those just operate completely in parallel, right?22:32
clarkbjeblair: yes22:32
jeblairmordred: oh i see22:32
clarkbso ya I guess in the context of a job you'd just have two jobs for that22:32
*** jlk has joined #openstack-meeting-alt22:32
*** jlk has joined #openstack-meeting-alt22:32
mordredyah22:32
pabelangerjeblair: it would be same vars, but multiple ssh connection attempts.  That seems to be the key to resetting them to how I expect them in the playbooks22:32
pabelangeragain, I think a more detailed example playbook might help here22:32
pabelangerand happy to write up22:33
jeblairi'm still questioning the connection between ssh connections and variables22:33
jeblairi'm pretty sure those are two independent concepts22:33
pabelangerthese are group_vars if that helps22:33
jeblairdoes zuul set group vars?22:34
*** jaypipes has quit IRC22:34
dmsimardI don't think so22:34
pabelangerit doesn't, ansible is loading them based on the playbooks/group_vars folder22:34
*** ansmith has joined #openstack-meeting-alt22:34
dmsimardthere's either inventory-wide vars or extra-vars which both apply to everything22:35
jeblairpabelanger: so you're getting different variables because you're running playbooks in different paths?22:35
pabelangerjeblair: I get different variables if I switch to groups in my inventory file22:36
pabelangerwell22:36
pabelangergroups of groups22:36
dmsimardI haven't tested group_vars and host_vars, it'd be interesting to test actually.. typically you'd have host_vars and group_vars inside {{ playbook_dir }}, but in our case those paths aren't "merged". However, I believe you can set group_vars and host_vars inside roles, and that would be more likely to work.22:36
jeblairpabelanger: er, i'm trying to understand how this change solves your variable problem from earlier22:37
pabelangerfor exmaple: http://git.openstack.org/cgit/openstack/windmill/tree/playbooks/inventory is my working v2 inventory file22:37
pabelangerjeblair: bascially, it allows me to stop doing http://git.openstack.org/cgit/openstack/windmill/tree/playbooks/site.yaml22:38
pabelangerand create a run: statement for each playbook22:38
jeblairpabelanger: why is that preferable?22:38
jeblairpabelanger: don't you feel like you're moving too much logic *into* zuul?22:38
dmsimardseems equivalent to me as well22:38
dmsimardFWIW that's exactly what we're doing with the base and multinode integration jobs, we're running "one" playbook that includes multiple playbooks22:39
dmsimardI don't currently see that as a hindrance22:39
pabelangerjeblair: yes, this is a work around, because I created 521324, which I'd much rather have22:39
pabelangerbefore*22:39
pabelangerI'll have to run here in about 5 minutes, but don't want to leave people hanging.  I'm happy if we want to contiune this topic in #zuul too22:41
jeblairpabelanger: to be clear, i'm, again, not permanently opposed to 519596, but before we merge changes like that, i'd like to have a really clear idea of why they are necessary, or what problem they solve, or what situation they improve.  so far we've got the "include list" as one thing, but that seems like an anti-pattern and a mild argument against merging 51959622:41
jeblairif there's a variable aspect to this, i still don't understand it22:41
pabelangersure, I'll get some working examples that better show the issues I ran into converting v2 job to native v3.  These were both my attempts to address some issues I was having22:42
jeblairpabelanger: okay, thanks22:42
jeblair#agreed pabelanger will provide more examples and explanation for this22:43
pabelangerI have to run now, will catch up on minutes when I return22:43
jeblair#topic open discussion22:43
*** openstack changes topic to "open discussion (Meeting topic: zuul)"22:43
jlkI have a topic...22:44
dmsimardFor open discussion, I just wanted to point out that we formally started looking at what it means to run a Zuul v3 that is not the one in OpenStack22:44
clarkbI too have one, but go for it jlk22:44
dmsimardjlk won first :P22:44
jlkdmsimard: who's "we" ?22:44
jlkIIRC there is one at BMW is there not?22:44
*** yangyapeng has joined #openstack-meeting-alt22:44
dmsimardWe is RDO Infra (analogous to openstack-infra) and Software Factory developers22:45
jeblairthere are a few in fact22:45
jlk(and for a hot minute, there was Bonny. Sigh.)22:45
jlkdmsimard: neat!22:45
dmsimardSoftware Factory had arguably been running Zuul v3 for a while22:45
dmsimardBut there's some interesting questions and design challenges in thinking how we want to share configuration between zuuls (zuul-jobs, openstack-zuul-jobs, project-config, and specific project)22:46
*** rwsu has quit IRC22:47
jeblairi think SpamapS was also trying out zuul-jobs sharing22:47
jlkjamielennox had some thoughts in this space as well22:47
dmsimardI started a thread about it in the context of TripleO http://lists.openstack.org/pipermail/openstack-dev/2017-November/124733.html and we also started hunting down issues we come across in zuul-jobs here: https://etherpad.openstack.org/p/downstream-zuul-jobs-issues22:47
clarkbwe probably want to focus on sharing zuul-jobs first and not the others right (they aren't generally supposed to be reconsumable so figuring it out for zuul-jobs where it is is a good start)22:47
jeblairsharing between instances is definitely a design goal for zuul-jobs.22:47
dmsimardclarkb: it's funny that you mention that, because one of the ideas that has been floating around is to centralize the playbooks/roles/jobs/etc for TripleO in tripleo-ci and then use that across all Zuuls22:48
jeblairi think openstack-zuul-jobs and individual openstack projects may be useful for openstack third-party-ci, but that's less of an explicit goal, and i think large amounts of 'shadow' and 'include'/'exclude' may be needed.22:48
mordredyes. I could also imagine that in-repo jobs and possibly openstack-zuul-jobs might be things that OpenStack Third Party Zuuls will want to consume22:48
dmsimardjeblair: yes, in the context of third party CI and such.22:48
*** Sukhdev has joined #openstack-meeting-alt22:48
mordredjeblair: yup22:49
*** yangyapeng has quit IRC22:49
jeblairproject-config definitely isn't meant to be shareable -- *however* -- we do want to have at least a stub/example base job.  that should end up either in zuul-jobs or zuul-base-jobs at some point soon.22:49
mordred++22:49
mordredstarting by figuring out sharing of zuul-jobs and getting it right will go a long way22:49
jeblair++22:50
*** d0ugal has quit IRC22:50
clarkbmordred: ya thats what I'm thinking. Those are the bits that should be reconsumbale so lets start there and learn what we learn22:50
jeblairdmsimard: so thanks for diving in and thanks in advance for your patience :)22:50
jeblair(cause we just *might* have gotten some things wrong in the first pass)22:51
dmsimardno stress22:51
clarkblast week we merged a couple changes that broke Zuuls config and zuul didn't catch them upfront. The one I remember off the top of my head is parenting to a final job. I know that pabelanger ran into something else when he had to restart zuul due to OOM as well.22:51
clarkb^^ is my item22:51
*** lbragstad has quit IRC22:51
clarkbit would be good if we could address those config issues pre merge22:51
dmsimarda couple?22:51
jeblairclarkb: by broke zuul's config... what do you mean?22:51
dmsimardhow did more than one breaking change merge ?22:52
mordredjlk: was thatyour topic? or did we talk over you?22:52
jeblairhow did *one* breaking change merge?22:52
clarkbjeblair: in pabelanger's restart zuul case zuul would not start up again22:52
jlkmordred: I can wait through clarkb's :)22:52
jeblairis there a bug report?22:52
clarkbjeblair: in the job parented to final job zuul kept running but the new jobs that merged would not run22:52
clarkbjeblair: I believe both were added to the zuulv3 issues etherpad22:52
jeblairclarkb: the second sounds like an expected run-time error; the first sounds like a bug.22:53
clarkbok we can followup on them after meeting22:53
* clarkb gets out of jlk's way22:53
jeblairack22:53
* dmsimard has an easy item after jlk22:53
*** julim has joined #openstack-meeting-alt22:53
* jeblair has a quick item after dmsimard22:54
jlkhi there! So tristanC landed a nodepool driver for k8s, and I'm asking if the group collective has the appetite to discuss/debate k8s (and container in general) driver approaches for Zuul/Nodepool.22:54
jlk"is now the time" or should we table this for later?22:54
jlkand by now, I don't mean in this channel now, but on list and in #zuul and whatnot22:54
mordreds/landed/proposed/22:55
jlksorry that's what I meant :(22:55
jlksilly fingers22:55
mordredjlk: yah - just wanted to make sure nobody else was confused :)22:55
dmsimardit's worth discussing not just because it's important but because it'll be a precedent from which the design of other "drivers" will be built from IMO22:55
mordredjlk: I was actually just writing an email to the list on this meta topic actually22:55
jeblairi'd really like to get a v3 release out before we dive into this, because i think it will help get and retain other folks into our community.  also, it's just embarrasing not to release.22:55
dmsimard+122:56
clarkbconsidering the lack of such features isn't a regression I'm on board with that too22:56
* mordred agrees with jeblair - but does think there is at least one facet of the discussion that is worth having pre-release to make sure we don't back ourselves into a corner when we release22:56
jlksame, a release would be good, so long as we don't have to wait for zuul4 to add container support22:56
jeblairmy preferred approach would be to get the release out the door quickly, then start on the next dev cycle.  there are things on the roadmap for release that others can pitch in on (some of them have my name next to them, but they don't have to be me and that would speed things up)22:56
dmsimardok mordred you will start a topic on the ML ?22:57
jeblairi would be really surprised if we are unable to release by februrary, and think earlier is likely (though i caution, there really aren't that many work weeks left in this year)22:57
mordredthe thing I think is worth sanity-checking ourselves on pre-release is making sure we aren't doing anything thatwould fundamentally block the addition of a nodepool driver that produces build resources that do not use ssh22:57
mordreddmsimard: yes, I shall22:57
dmsimardlet's pick up the discussion there22:58
jlkworks for me, thanks!22:58
jeblairthis dovetails into my topic, which is in next week's meeting, i'd like to check in on the release roadmap items22:58
dmsimardThere's only 1:30 left.. but Ansible 2.4.1 is out and addresses most/all of the regressions/issues introduced in 2.4. How do we upgrade without breaking people that have written <2.4 things ?22:58
jeblairi'll add that to the angenda for next, and i expect we'll have the roadmap items in storyboard soon22:59
dmsimardAlternatively, how do we potentially allow different version of Ansible ? Because some things works in one, some in others, etc.22:59
dmsimardAck22:59
mordredjeblair: ++22:59
jlkI really hope that we don't get too deep in "what version of ansible" land for Zuul users.23:00
jlkat least not "choose your own"23:00
mordreddmsimard: most of the 2.3 to 2.4 breakages were in the python layer for us, right?23:00
dmsimardmordred: for ara and zuul themselves, perhaps23:00
dmsimardmordred: there's still some "bug fixes" that broke things23:00
dmsimardsome behavior changes in includes/imports23:00
dmsimardalso variable scopes23:01
dmsimardthey don't really follow semver :(23:01
mordredjlk: I actually have some thoughts on how we might consider doing that without death - but as of right now I agree with that sentiment23:01
jeblairjlk, dmsimard: some folks have expressed a use case for multiple ansible support, and it may be in keeping with our philosohpy of trying to be as transparent as possible with ansible.  for instance, kolla tests all their stuff with all current supported versions of ansible.23:01
jlksure, but I thought at that point, you write a first job that installs the ansible you want to test with, then....23:02
dmsimardthis is a cool topic which I'll continue in #zuul :)23:02
mordreddmsimard: I'm not sure there is a great story yet today for how to upgrade zuul's ansible from 2.3 to 2.4 and verify that people's job ansible doesn't break23:02
jeblairso it may not be out of the question for zuul to maintain compatibility with current supported versions.  but i think that needs a design proposal.  :)23:02
jeblairi think the quick answer to dmsimard's question is --23:02
jeblairwe try using 2.4.1 and fix what's broken :)23:02
mordredyah23:02
dmsimardyuck23:02
dmsimardanyway, we're over time :)23:02
jeblairShrews has done much work on that already, we should be in pretty good shape23:03
jeblairthanks all!23:03
jeblair#endmeeting23:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:03
openstackMeeting ended Mon Nov 20 23:03:13 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-11-20-22.07.html23:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-11-20-22.07.txt23:03
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-11-20-22.07.log.html23:03
mordredmoving *forward* I think getting zuul tests running on upstream ansible changes will be super helpful in at least pointing fingers at breaks that are unintentional23:03
*** jkilpatr_ has joined #openstack-meeting-alt23:03
*** lbragstad has joined #openstack-meeting-alt23:04
*** d0ugal has joined #openstack-meeting-alt23:08
*** fnaval has quit IRC23:09
*** sdague has quit IRC23:09
*** jrist is now known as jrist-afk23:13
*** yamamoto has joined #openstack-meeting-alt23:21
*** marst has quit IRC23:21
*** d0ugal has quit IRC23:24
*** rossella_s has quit IRC23:26
*** rossella_s has joined #openstack-meeting-alt23:26
*** lpetrut has quit IRC23:32
*** bzhao has quit IRC23:36
*** bbzhao has quit IRC23:36
*** rossella_s has quit IRC23:40
*** Sukhdev has quit IRC23:40

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