22:06:06 #startmeeting zuul 22:06:07 Meeting started Mon Jan 22 22:06:06 2018 UTC and is due to finish in 60 minutes. The chair is corvus. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:06:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:06:10 The meeting name has been set to 'zuul' 22:06:33 #link agenda https://wiki.openstack.org/wiki/Meetings/Zuul 22:06:45 #link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-01-15-22.04.txt 22:06:51 #topic open discussion 22:07:15 there are no items on the agenda... 22:07:25 woot. we're done! 22:07:30 are there any pressing items related to v3.0 release blockers? 22:07:46 o/ 22:08:23 #link Zuul roadmap https://storyboard.openstack.org/#!/board/53 22:08:33 nothing pressing from me, but I'm proposing a new nodepool command for cleaning up zk when a provider cannot be cleaned up before removal: https://review.openstack.org/535817 22:08:52 Shrews: thanks, that sounds helpful 22:08:57 oh, i have a 3.0 release related thing 22:09:12 if folks could please see my ML post about the issue that mordred ran into this morning related to job parents 22:09:36 #link http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-January/000014.html 22:09:45 Shrews: thanks for weighing in on that 22:10:11 sure. i hit that with nodepool, which only went away after we merged the feature branch back into master 22:10:17 if anyone else has thoughts on that, let me know soon. otherwise i'll probably implement that very soon (tomorrow?) so we can keep the ansible work moving 22:10:23 Shrews: yeah, and that's not a scalable solution :) 22:11:33 the other release-blocker i have is https://review.openstack.org/535501 22:11:39 and its children 22:12:14 we should merge that asap, as it not only blocks our release, but could end up impacting openstack's release (we can work around it, but it's extra work for the release team, and could be error-prone) 22:12:35 #link https://review.openstack.org/535501 22:13:13 anyone else have anything they'd like to discuss, or should we get back to knocking things off that list? :) 22:13:36 nothing from me 22:13:58 back to knocking things off I think 22:14:08 k, thanks all! :) 22:14:10 #endmeeting