22:01:19 #startmeeting zuul 22:01:20 Meeting started Mon Feb 12 22:01:19 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:20 * SotK lurks in the background 22:01:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:01:23 The meeting name has been set to 'zuul' 22:01:30 #link agenda https://wiki.openstack.org/wiki/Meetings/Zuul 22:01:36 #topic Release update 22:01:53 this is not going to be a long boring list of all the things we need to do before release... 22:02:03 because we have a *short* list of things to do before release! :) 22:02:06 haha 22:02:09 https://storyboard.openstack.org/#!/board/53 22:02:12 * jlk hides before the github3 question 22:02:20 short and *exciting*? 22:02:30 the left column is current, afaik 22:02:54 i could almost count those on one hand 22:03:01 and, i'll be honest, if the last thing on that list is the abstract flag, i don't think we should wait for it. 22:03:04 We just need a 6 fingered man 22:03:10 but I hear he killed somebody's father. 22:03:13 corvus: +1 22:03:22 we've worked well without it so far 22:03:26 i believe *everything* on that list is being worked 22:03:32 jlk: inconceivable! 22:04:32 zuul-stream and javascript are assigned to mordred. he has WIP patches for both of those. he's on vacation this week, but hopefully by next week (possibly earlier if he needs a vacation from his vacation), we'll have those 22:04:35 AFAIK there's one open issue blocking a potential github3 release, and that's https://github.com/sigmavirus24/github3.py/pull/773 -- that said, I don't think we've tested devel branch against zuul in a while, and there may be more to get done there. I was planning to do that before heading out to PTG, and if nothing else give me something to work on while not talking at PTG 22:05:19 jlk: i think we specify the 'develop' branch in requirements 22:05:32 oh, I thought we were pinned to a specific hash. 22:05:37 jlk: so we're continuously testing it in unit tests at least 22:05:51 oh hey look at that 22:05:58 though.. i guess unit tests probably don't really test very much 22:06:03 I was worried because some fairly significant things have landed recently 22:06:18 with how github3 objects are manipulated. 22:06:37 i just ran through the zuul-from-scratch doc, and so i would have gotten the version as of friday with that 22:06:49 that's fantastic news. 22:06:54 i can confirm that at least works well enough to enqueue events and receive reports 22:07:06 i didn't do anything fancy with reviews 22:07:21 what version is running in prod against Ansible GitHub? 22:07:51 hrm, pip3 freeze reports github3.py==1.0.0a4 but that doesn't seem right 22:08:12 I think the numbering is funky 22:08:25 but, that's only just a tickle in my brain, I could be very wrong. 22:08:48 i'll try to dig into that more later and get a more confident answer 22:09:53 jlk: do you have a feeling for whether github3.py release within the next 2 weeks is feasible? 22:10:24 I have a feeling, and it's maybe a 25% chance? 22:10:48 I've reached out once more to see if I can do anything to help that last PR, since I got done the things I was told about last time I asked. 22:10:55 i just checked out the tip of develop and a `python setup.py sdist` creates github3.py-1.0.0a4.tar.gz 22:11:00 so that is probably correct 22:11:06 given how much has changed though, the release process may be a while 22:11:20 fungi: cool, we probably need to figure out how to get the sha we installed... 22:11:30 if only they used pbr! ;) 22:11:31 we're not seeing much change since we've been on the develop branch since basically the beginning of our use, but in the wild it's a fair jump from the last release to this pending one. 22:12:04 jlk: okay, so assuming we wrap up the rest of the stuff in 2 weeks (i think that's plausible), we'll need to think about whether we should delay our release, or, i guess, vendor github3.py until it's released... 22:12:20 yeah, seems like a reasonable thing. 22:12:36 I promise I'll have a better answer before PTG 22:12:57 jlk: cool, thanks muchly! 22:13:21 any other comments or questions around the 3.0 blocker list? 22:14:07 #topic PTG discussion topics 22:14:18 my link in the agenda was wrong 22:14:25 #link https://etherpad.openstack.org/p/infra-rocky-ptg ptg discussion topics 22:14:59 are there more zuul-specific discussion topics we'd like to have? 22:15:21 i'm pretty sure i can think of enough to fill 3 days :) 22:15:58 so far there are three from tobiash and one more from corvus/mordred in there 22:16:04 * jlk looks again 22:16:11 plus the ci/cd focus area is fairly zuul-related 22:16:14 i think things where we can discuss and agree on a direction so that folks can go off and implement without a lot of back and forth will be nice 22:17:33 i think i'll add one on future direction for the dashboard 22:17:37 oh, also jlk talking about github things on monday, looks like 22:17:46 I have to drop early today, I'll catch up on meeting logs this evening 22:17:52 I won't be at the PTG but FWIW I have nested Zuul jobs in my fairly-short-term-todo-list -- basically a 2 node job where one node is the zuul/nodepool and the other node is a nodepool static slave 22:18:17 yes, Monday. Because my family is dragging me away (to Belfast) on Tuesday I believe. 22:18:45 jlk: wow, that's actually in a different country altogether! 22:19:11 yeah, but that's like saying another state on the east coast. It's 2 hours north :D 22:19:30 or 'counties' as we call them in ca 22:20:01 #info add zuul-related topics to https://etherpad.openstack.org/p/infra-rocky-ptg 22:20:16 anyway, if folks think of things, add them there soon please, that will help us schedule 22:20:45 of course, the schedule is flexible, but it's still nice to have some things set aside in advance so we aren't scrambling the *whole* time 22:21:07 also, feel free to put your name on any of those topics and any schedule restrictions you might have 22:21:34 jlk: so if there's something you really want to talk about on monday, let us know :) 22:21:48 Just the GitHub use case. 22:22:14 that's all i had on the agenda... 22:22:18 #topic Open discussion 22:22:41 anything else? 22:23:01 Did anyone submit any Zuul things for Vancouver ? 22:23:05 I know pabelanger submitted a workshop 22:23:30 corvus: I would love a refresh of the Barcelona Zuul v3 talk :) 22:24:15 dmsimard: i'll see if i can oblige :) 22:25:17 It's a great resource when you want to explain someone what Zuul does, turns out it's not so simple to explain 22:25:33 i'll be giving a zuul talk at scale shortly after the ptg... i wonder if they're available online 22:25:47 lol yeah, I prepped many pages of notes to explain it to some folks at GitHub 22:26:02 I had to walk through 3 or 4 base "assumptions" about the desires of developers/reviewers. 22:26:06 jlk: "let me explain why Zuul is so awesome" 22:26:07 we'll want to do our best to avoid being particularly openstack-focused with vancouver proposals since the ci/cd track has been folded into the separate non-openstack "opendev" conference running alongside the summit 22:26:35 fungi: fortunately, 'be less openstack-focused' aligns with our strategic goals for zuul :) 22:26:40 +1 22:26:40 yep! 22:28:50 well, let's wrap it up then 22:28:54 thanks everyone! 22:28:58 #endmeeting