22:03:40 #startmeeting zuul 22:03:41 Meeting started Mon Apr 3 22:03:40 2017 UTC and is due to finish in 60 minutes. The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:03:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:03:45 The meeting name has been set to 'zuul' 22:03:55 #link out-of-date agenda https://wiki.openstack.org/wiki/Meetings/Zuul 22:04:06 #link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-03-27-22.01.html 22:04:19 sorry, i forgot to clean up the agenda from last week 22:04:24 #topic Actions from last meeting 22:04:52 pabelanger look at zk authentication for nodepool 22:05:01 * mordred waves 22:05:16 Yes, I did look at it. No code yet. I plan to do more this week 22:05:16 pabelanger: did you have a chance to start on that? 22:05:25 pabelanger: cool. is there a story for it? 22:05:36 I can check and add it if needed 22:05:50 pabelanger: sounds good 22:06:05 i'll drop the action item then and we can use the task tracker for that :) 22:06:24 wfm 22:06:38 rbergeron try to find someone to work on ansiblification of devstack-gate 22:07:18 i haven't seen rbergeron around today 22:08:00 #topic Status updates (nodepool) 22:08:37 anyone have anything to mention here? 22:09:06 the docs thing from earlier might be worth a mention but less a status update 22:09:49 clarkb: well, docs is a leading edge for nodepool development now, so have at it :) 22:10:22 basically we had a user drop into #openstack-infra with questions about how to delete images and build new ones in the post zk world. 22:10:49 While the user interface hasn't changed all that much from before zk, what we did notice was that we haven't actually documented any of this beyond some basic command docs for image-delete 22:11:07 so we probably want to update the docs to talk about performing management operations with nodepool 22:11:11 (that aren't infra specific) 22:11:14 ++ 22:11:19 Morning 22:11:21 (sorry I'm late) 22:11:39 yeah. we've been saying "we need to make the docs better", but i don't think we've been very specific about what that means. 22:11:55 this is a good example of what i think it should mean :) 22:13:29 task/card for the kanban? could be lhf (maybe?) 22:13:30 just quick brainstorming, deleting images, building images, uplodaing images, holding nodes, and deleting nodes are common things that we've done in infraland 22:13:39 that is probably a good place to start as far as writing betterdocs 22:14:38 clarkb: yes, that and also, we lack a really good explanation of what the components are and what they do (the sort of thing that would help you understand that creating an image is something you might want to do) 22:15:30 fungi: it may not be the lowest hanging fruit, depending on how much the author needs to understand themselves. 22:15:38 true 22:16:01 if lhf means "able to install, run and test nodepool" then maybe 22:16:11 but i agree that's a high-ish bar 22:16:29 Shrews and rbergeron signed up for docs improvement. i don't know if they consider this part of their work. though regardless, it's something we need to have done before we release. it's part of the 'make this so non-infra people can actually use it' feature we promised. :) 22:16:52 that task requires 3 things: good writing skills, working operational experience, and technical knowledge of the code. 22:17:06 i have only the last of those. 22:17:34 i've done all the doc improvement that i had in mind, but willing to collaborate with someone else as needed for the new docs 22:18:17 I can likely stab at it if we don't want to treat it as lhf and have someone dig in as a starting point 22:18:19 i have some non-zero subset of those. i'm happy to help (i would really very much enjoy it actually), but i'm over booked right at this moment. 22:19:21 clarkb: cool, thanks. any progress helps. and this can be pretty iterative. docs are nice like that. :) 22:20:09 and we may want to have a mini-docs-sprint closer to release. 22:20:36 sounds like fun 22:20:42 ++ for a docs-a-thon 22:20:47 yay 22:21:41 #topic Status updates (Devstack-gate roles refactoring) 22:21:52 anyone poke at this? 22:22:22 not that I've seen 22:22:29 #topic Status updates (Zuul test enablement) 22:23:15 jesusaur: your change is almost ready i think 22:23:39 jeblair: yep 22:24:01 and i suspect that will unblock any other tests which might incidentally rely on the merge check 22:24:15 (sorry again about that) 22:24:35 https://review.openstack.org/446275 is passing tests and ready for review \o/ 22:25:39 i believe SpamapS has some changes up to re-enable tests as well 22:25:58 hopefully we can merge those this week 22:26:15 anyone else? 22:27:05 sort of testing https://review.openstack.org/452964 but not tracked by test enablement bceause its actually doc builds 22:27:26 whoops 22:27:27 clarkb: thanks :) 22:27:55 I started back on timedatabase 22:28:01 I should have something in a day or so 22:28:45 ++ 22:28:54 #topic Status updates (Zuul sample jobs) 22:29:23 pabelanger: are we doing anything with these right now, or is it paused while we make zuul do more stuff? 22:30:03 jeblair: we merged a few things 2 weeks ago, and running 22:30:24 I haven't pushed more on them because of security / chroot discussion 22:30:31 but, I can if we want too 22:30:51 pabelanger: oh, i think i noticed recently that we don't have the nice subunit html file for py27 tests? 22:31:03 pabelanger: i think that should be mostly independent? 22:31:05 jeblair: I can see why that is 22:31:11 ya 22:31:26 jeblair: do we think we are really to test with some sort of ansible role? 22:31:39 or add nodepool into zuulv3-dev.o.o? 22:31:40 pabelanger: i think the subunit thing is an extra step/program we run in run-tox.sh 22:32:19 pabelanger: jeblair ya it is, it runs out of the jobs tox dir and executes the conversion program 22:33:00 I'll find out why it is missing 22:33:01 pabelanger: we can probably add the nodepool project now and start working on the zuul-nodepool integration job 22:33:17 okay 22:33:58 #topic Open Discussion 22:34:45 i've been making good progress on the 'canonical hostname for projects' series. it's not quite done yet, but i think much of the general shape is there if folks want to take an early look. 22:34:49 we haven't restarted nl01 and zuulv3-dev in some time. I'd like to update to the latest of everything 22:34:58 and restart 22:35:06 pabelanger: sounds good to me 22:35:59 thanks 22:36:02 ++ 22:36:17 has there been any new developments with bubblewrap? 22:36:53 SpamapS says he's going to make another revision of https://review.openstack.org/444495 22:37:22 but other than that, i think that's getting pretty close to being ready to make a decision and implement 22:37:55 I agree - I'm pretty happy with all of the work and discussion that went in to that 22:38:09 okay, that's part of the reason I haven't pushed more on ansible jobs. Because of our current issues with lookups and breaking out of jobdir 22:38:35 do we know when the next ansible release will be? 22:38:38 pabelanger: oh, well, i think we decided we needed to block lookups? 22:38:42 oh crappit. I knew I had a todo in that area I was supposed to be hacking on 22:38:47 there is at least one bugfix that we can revert a workaround for in zuul around that 22:38:50 yah - that's my bad- I should have already written that patch 22:38:55 clarkb: soon 22:39:04 mordred: that's adding a custom lookup plugin, right? 22:39:16 yup 22:39:18 jeblair: I think so, but didn't follow along much last week 22:39:21 #action mordred add custom path-blocking lookup plugin 22:39:25 and lookie there - it's in the top of my todo list file 22:39:47 mordred: you should put "look at todo list file" at the top of your todo list! :) 22:39:53 jeblair: done! 22:41:34 anyone have anything else, or should we go back to hacking? 22:42:25 thanks all! 22:42:27 #endmeeting