22:01:19 <corvus> #startmeeting zuul
22:01:20 <openstack> 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 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:23 <openstack> The meeting name has been set to 'zuul'
22:01:30 <corvus> #link agenda https://wiki.openstack.org/wiki/Meetings/Zuul
22:01:36 <corvus> #topic Release update
22:01:53 <corvus> this is not going to be a long boring list of all the things we need to do before release...
22:02:03 <corvus> because we have a *short* list of things to do before release!  :)
22:02:06 <jlk> haha
22:02:09 <corvus> https://storyboard.openstack.org/#!/board/53
22:02:12 * jlk hides before the github3 question
22:02:20 <fungi> short and *exciting*?
22:02:30 <corvus> the left column is current, afaik
22:02:54 <fungi> i could almost count those on one hand
22:03:01 <corvus> 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 <jlk> We just need a 6 fingered man
22:03:10 <jlk> but I hear he killed somebody's father.
22:03:13 <pabelanger> corvus: +1
22:03:22 <pabelanger> we've worked well without it so far
22:03:26 <corvus> i believe *everything* on that list is being worked
22:03:32 <fungi> jlk: inconceivable!
22:04:32 <corvus> 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 <jlk> 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 <corvus> jlk: i think we specify the 'develop' branch in requirements
22:05:32 <jlk> oh, I thought we were pinned to a specific hash.
22:05:37 <corvus> jlk: so we're continuously testing it in unit tests at least
22:05:51 <jlk> oh hey look at that
22:05:58 <corvus> though.. i guess unit tests probably don't really test very much
22:06:03 <jlk> I was worried because some fairly significant things have landed recently
22:06:18 <jlk> with how github3 objects are manipulated.
22:06:37 <corvus> 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 <jlk> that's fantastic news.
22:06:54 <corvus> i can confirm that at least works well enough to enqueue events and receive reports
22:07:06 <corvus> i didn't do anything fancy with reviews
22:07:21 <jlk> what version is running in prod against Ansible GitHub?
22:07:51 <corvus> hrm, pip3 freeze reports github3.py==1.0.0a4 but that doesn't seem right
22:08:12 <jlk> I think the numbering is funky
22:08:25 <jlk> but, that's only just a tickle in my brain, I could be very wrong.
22:08:48 <corvus> i'll try to dig into that more later and get a more confident answer
22:09:53 <corvus> jlk: do you have a feeling for whether github3.py release within the next 2 weeks is feasible?
22:10:24 <jlk> I have a feeling, and it's maybe a 25% chance?
22:10:48 <jlk> 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 <fungi> 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 <fungi> so that is probably correct
22:11:06 <jlk> given how much has changed though, the release process may be a while
22:11:20 <corvus> fungi: cool, we probably need to figure out how to get the sha we installed...
22:11:30 <fungi> if only they used pbr! ;)
22:11:31 <jlk> 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 <corvus> 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 <jlk> yeah, seems like a reasonable thing.
22:12:36 <jlk> I promise I'll have a better answer before PTG
22:12:57 <corvus> jlk: cool, thanks muchly!
22:13:21 <corvus> any other comments or questions around the 3.0 blocker list?
22:14:07 <corvus> #topic  PTG discussion topics
22:14:18 <corvus> my link in the agenda was wrong
22:14:25 <corvus> #link https://etherpad.openstack.org/p/infra-rocky-ptg ptg discussion topics
22:14:59 <corvus> are there more zuul-specific discussion topics we'd like to have?
22:15:21 <corvus> i'm pretty sure i can think of enough to fill 3 days :)
22:15:58 <fungi> so far there are three from tobiash and one more from corvus/mordred in there
22:16:04 * jlk looks again
22:16:11 <fungi> plus the ci/cd focus area is fairly zuul-related
22:16:14 <corvus> 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 <corvus> i think i'll add one on future direction for the dashboard
22:17:37 <fungi> oh, also jlk talking about github things on monday, looks like
22:17:46 <pabelanger> I have to drop early today, I'll catch up on meeting logs this evening
22:17:52 <dmsimard> 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 <jlk> yes, Monday. Because my family is dragging me away (to Belfast) on Tuesday I believe.
22:18:45 <fungi> jlk: wow, that's actually in a different country altogether!
22:19:11 <jlk> yeah, but that's like saying another state on the east coast. It's 2 hours north :D
22:19:30 <corvus> or 'counties' as we call them in ca
22:20:01 <corvus> #info add zuul-related topics to https://etherpad.openstack.org/p/infra-rocky-ptg
22:20:16 <corvus> anyway, if folks think of things, add them there soon please, that will help us schedule
22:20:45 <corvus> 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 <corvus> also, feel free to put your name on any of those topics and any schedule restrictions you might have
22:21:34 <corvus> jlk: so if there's something you really want to talk about on monday, let us know :)
22:21:48 <jlk> Just the GitHub use case.
22:22:14 <corvus> that's all i had on the agenda...
22:22:18 <corvus> #topic Open discussion
22:22:41 <corvus> anything else?
22:23:01 <dmsimard> Did anyone submit any Zuul things for Vancouver ?
22:23:05 <dmsimard> I know pabelanger submitted a workshop
22:23:30 <dmsimard> corvus: I would love a refresh of the Barcelona Zuul v3 talk :)
22:24:15 <corvus> dmsimard: i'll see if i can oblige :)
22:25:17 <dmsimard> 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 <corvus> i'll be giving a zuul talk at scale shortly after the ptg... i wonder if they're available online
22:25:47 <jlk> lol yeah, I prepped many pages of notes to explain it to some folks at GitHub
22:26:02 <jlk> I had to walk through 3 or 4 base "assumptions" about the desires of developers/reviewers.
22:26:06 <dmsimard> jlk: "let me explain why Zuul is so awesome"
22:26:07 <fungi> 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 <corvus> fungi: fortunately, 'be less openstack-focused' aligns with our strategic goals for zuul :)
22:26:40 <dmsimard> +1
22:26:40 <fungi> yep!
22:28:50 <corvus> well, let's wrap it up then
22:28:54 <corvus> thanks everyone!
22:28:58 <corvus> #endmeeting