15:01:21 #startmeeting ironic 15:01:23 Meeting started Mon Sep 30 15:01:21 2019 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:26 The meeting name has been set to 'ironic' 15:01:28 o/ 15:01:29 \o 15:01:31 o/ 15:01:33 o/ 15:01:33 \o 15:01:34 o/ 15:02:03 BjoernT, let's discuss about that after the meeting :) 15:02:14 Thanks 15:02:20 Hello everyone, dtantsur|afk is on a train, and TheJulia is on a plane, so I'm stepping in again 15:02:33 o/ 15:02:46 I will try to rhyme for the whole meeting, but I can't promise anything 15:03:13 o/ 15:03:38 #topic announcements 15:04:06 #info All train deliverables have now been released \o/ 15:04:17 nice :) 15:04:23 chooo chooo!!! 15:04:35 \o/ 15:04:54 #undo 15:04:55 Removing item from minutes: #info All train deliverables have now been released \o/ 15:05:07 #info Most train deliverables have now been released \o/ 15:05:18 I see there are a couple that need prodding :) 15:05:26 oh 15:06:01 actually, maybe it's just ironic-python-agent-builder 15:06:11 mgoddard: which one are wwe missing? 15:06:12 oh ok 15:06:17 and that's independent 15:06:22 #undo 15:06:22 Removing item from minutes: #info Most train deliverables have now been released \o/ 15:06:25 #info All train deliverables have now been released \o/ 15:06:31 hooray! 15:06:35 all aboard! 15:06:48 indeed 15:06:51 o/ 15:06:52 Any others? 15:07:25 so from now on verything goes into Ussuri, unless it's a very urgent ifx 15:07:29 fix* 15:07:55 rpittau: we can always backport fixes (subject to stable policy) 15:08:01 yup ok 15:08:12 #info Master branches are now unfrozen 15:08:26 On with Ussuri 15:08:41 #topic Review action items from last meeting 15:08:50 There were none 15:09:01 #topic Review subteam status reports (capped at ten minutes) 15:09:17 https://etherpad.openstack.org/p/IronicWhiteBoard 15:09:22 starting at L241 15:10:19 at what point do we normally go and reset these for the next release? 15:10:54 I'm not sure we actually reset them 15:11:01 i know we review/reset after we've agreed on priorities for the next cycle. 15:11:13 i suspect in between, we kind of 'continue' with work 15:11:42 that's not for a while, assuming we do it at PTG again 15:12:22 that might be worth a discussion, but i think the user feedback at the forum is meant to help drive the priorities 15:12:43 or, if not drive, be taken into consideration when deciding on priorities 15:12:46 true 15:13:14 i think we have some idea of what we need/ought to continue to do? 15:13:50 I expect so - continue with work that didn't make train 15:14:07 anything we need to discuss here 15:14:10 ? 15:14:52 i am going to clean this up a bit. delete 'redfish sensor data collection', that looks like it is all done. L309 15:15:34 are we safe to remove PDF generation too then? 15:15:49 mgoddard: i was just about to ask that. 15:16:14 mgoddard: i think we can delete that. it sez 'done' :) 15:16:15 mgoddard: yes, that's all done 15:16:45 goen 15:16:48 gone 15:17:29 ok, it's a little cleaner now 15:17:43 Onto priorities? 15:18:17 #topic Deciding on priorities for the coming week 15:18:43 L151 15:22:16 as a note, for backport candidates (L189). I added that PR cuz it needs someone to do the backport. 15:22:33 I've cleaned the priorities up 15:22:51 rloo: you mean it's not a clean backport ? 15:23:11 we're backporting to train, stein, & rocky, right? 15:23:14 rpittau: yes 15:23:18 rloo: yeah, ok 15:23:53 oh, i answered my question, and noted it in the whiteboard last week! so much for my memory :D 15:24:52 are there any other patches that need adding to priorities this week? 15:25:12 rloo: I might get to it tomorrow, unless someone else doesn't do it before :) 15:25:32 rpittau: no hurry. i suggest putting your name down. well, i'll do it :) 15:25:41 I guess we should focus on specs now? 15:26:33 i think (not totally sure) the focus is meant to be... test out rc1 candidate before final release. 15:26:49 rloo: we've released 15:27:14 no candidates here, straight to release 15:27:41 testing still encouraged, in case we need to roll another 15:28:10 mgoddard: i thought we've released a rc1; if there are issues, we can release an rc2... Final RCs are week of oct7. What that really means, i don't know. 15:28:25 https://releases.openstack.org/train/schedule.html 15:28:28 rloo: we released 13.0.0 15:28:41 maybe it is paperwork. 15:28:42 we're cycle-with-intermediary, so do it a little differently 15:29:24 paperwork -- announcing *which* release is the one to be associated with Train. 15:29:53 how do we do that? 15:30:17 we've already created stable/train 15:30:24 I think that's done by it being in the releases repo 15:30:27 https://docs.openstack.org/releasenotes/ironic/train.html 15:30:31 i have no idea. i know we have, in the past, done an rc1 (ie, branched), and had to backport fixes and announce some other version (besides rc1) as *the* release. 15:30:37 e.g. this shows the available versions in train: https://releases.openstack.org/train/index.html 15:31:39 so eg, python-ironicclient shows as 3.1.0, not 3.0.0 even though we branched with 3.0.0 15:32:03 yeah, that's the latest release on the stable/train branch 15:32:26 I believe the latest release on the train branch, at the time of the "global" release, will be communicated as "train" 15:32:36 right, makes sense 15:32:43 yep, that should be it 15:33:05 #topic Open discussion 15:33:34 Anyone have something for discussion today? 15:35:03 If I forgot to mention this before, THANKS to everyone for helping out with the Train release(es) 15:35:27 ++ 15:36:32 thanks all :) 15:36:52 Let's leave it there for today then 15:37:00 hey folks, ironic devstack plugin appears to be broken since the removal of coreos support 15:37:15 hi cdearborn 15:37:21 i posted about it earlier 15:37:24 that doesn't sound good 15:37:45 ramdisk pxe boots to shell prompt and sits there 15:38:36 cdearborn: I think dtantsur|afk would be the best person to ask about the latest state of coreos removal 15:38:49 i would greatly appreciate some help resolving this. no idea where to go from here other than falling back to an older version of ironic 15:38:54 is it something you're investigating? 15:39:44 i honestly don't know where to start - not even sure if pxe booting tinyipa to a shell prompt is expected behavior or if that's broken 15:40:40 cdearborn: if you think coreos removal is the culprit, you could try reverting that patch 15:40:52 coreos ramdisk booted to a login prompt 15:41:35 well, this is the 1st time i've tried tinyipa ramdisk, so not sure if this didn't work in the past or not 15:42:02 the only thing i can say is that coreos ramdisk worked, and tinyipa/dib ramdisks don't 15:42:07 CI tests use tinyipa and devstack, so I'd not expect it to be completely broken 15:42:15 cdearborn: that's kind of weird considering that the entire CI is based on devstack with tinyipa 15:42:51 shall we take it out of the meeting? 15:42:54 cdearborn: running devstack on ubuntu or something else? 15:42:56 ++ 15:42:59 xenial 15:43:01 ++ 15:43:01 mgoddard: yeah 15:43:05 ok, thanks everyone 15:43:07 #endmeeting