17:00:19 <jroll> #startmeeting ironic
17:00:23 <openstack> Meeting started Mon Aug 15 17:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:24 <vdrok> o/
17:00:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:25 <devananda> o/
17:00:27 <openstack> The meeting name has been set to 'ironic'
17:00:28 <mariojv> o/
17:00:28 <NobodyCam> o/
17:00:28 <jroll> hey everyone
17:00:29 <jlvillal> o/
17:00:31 <lucasagomes> o/
17:00:32 <mjturek1> o/
17:00:40 <blakec> o/
17:00:49 <jroll> as always, the agenda is here:
17:00:51 <jroll> #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
17:00:52 <rpioso> o/
17:00:55 <Madasi> o/
17:01:04 <alineb> o/
17:01:05 <jroll> pretty light today, this should be quick
17:01:07 <jroll> :)
17:01:11 <NobodyCam> :)
17:01:15 <jroll> #topic announcements and reminders
17:01:16 <dtantsur> o/
17:01:17 <rloo> o/
17:01:28 <jroll> so we got 6.1.0 release last week with a TON of features
17:01:35 <jroll> thanks so much to everyone for your hard work on that
17:01:41 <lucasagomes> w00t
17:01:47 <jroll> #link http://docs.openstack.org/releasenotes/ironic/newton.html#id2
17:01:51 <rloo> yay
17:01:56 <jroll> release notes are there if you want to see just how much :)
17:02:22 <sambetts> o/
17:02:32 <jroll> reminder that non-client library final release is next week - if we need something in ironic-lib let's get that done now
17:02:41 <devananda> woot!
17:02:43 <jroll> ditto for client final releases the following week
17:03:14 <jroll> anyone have anything else for announcement/reminders?
17:03:16 <dtantsur> a reminder: the libraries and clients deadlines are coming soon, please review their changes (especially OSC commands in ironicclient)
17:03:24 <dtantsur> hmm, you beat me to it, right?
17:03:26 <jroll> :D
17:03:31 <jroll> ++ for osc changes though
17:03:45 <jroll> #link http://releases.openstack.org/newton/schedule.html
17:03:46 <lucasagomes> jroll, there's a patch to make parse_root_device_hints() work with operators in ironic-lib, currently IPA because I need to finish the IPA bits
17:03:49 <jroll> (for the full schedule)
17:03:54 <lucasagomes> but yeah, will be available for review this week
17:04:13 <jroll> lucasagomes: got it, thanks
17:04:17 <rloo> jroll: do we want to try for the deadlines in the beginning of the week?
17:04:39 <JayF> I will also try to get a patch up for ironic-lib to add dev docs, mainly so we can have dev docs for Metrics, but I don't think that'd neccessarily need to be released
17:04:41 <jroll> rloo: yes, the earlier the better
17:04:41 <rloo> jroll: cuz they're always 'the week of...'
17:05:01 <jroll> rloo: I want to get the release requests submitted on the wednesday of those weeks
17:05:12 <jroll> maybe tuesday
17:05:24 <jroll> the note on the schedule says, "All deadlines are generally the Thursday of the week on which they are noted above"
17:05:32 <rloo> jroll: ok, i'll look forward to your 'fix up reno' patch for the client ;)
17:05:40 <jroll> rloo: yay :(
17:05:51 * jroll makes a note to do that
17:05:57 <davidlenwell> o/
17:06:12 <dtantsur> heh, it's still better than trying to collect everything in the wiki in the end of the cycle
17:06:16 <dtantsur> :)
17:06:18 <jroll> +1
17:06:23 <jroll> anything else here?
17:06:38 <TheJulia> o/ (sorry, was on a phone call)
17:07:11 <jroll> #topic subteam status reports
17:07:17 <jroll> as always, those are here:
17:07:19 <jroll> #link https://etherpad.openstack.org/p/IronicWhiteBoard
17:07:25 <jroll> starts at line 80 this time
17:07:46 <jroll> some of those things are done or just have a couple follow up patches \o/
17:07:55 <mat128|afk> o/
17:08:10 * jroll gives folks a few minutes to review/update those
17:08:18 <devananda> jroll: I'd like to get the api-ref update for api v1.22 landed. I had hoped for that to be in 6.1, but we should at least get the website up to date
17:08:33 <jroll> devananda: ditto
17:08:36 <rloo> jroll: wrt multiple compute hosts -- do we (you) need to explain how that was solved?
17:09:03 <jroll> rloo: I've explained it in the mailing list and the commit message for the change, I'd rather not do it again :)
17:09:17 <rloo> jroll: oh, i missed the email (sorry, am behind). thx.
17:09:35 <jroll> rloo: the email was after nova midcycle a few weeks ago
17:09:57 <rloo> jroll: oh, right. so long ago i had forgotten :)
17:10:29 <jroll> :D
17:10:47 <rloo> software metrics is almost done?
17:11:01 <jroll> yep
17:11:26 * jroll made a note
17:11:50 <dtantsur> a small reminder: please do not leave bugs in "Fix Committed" state
17:12:01 <jroll> dtantsur: so, you want to freeze at normal FF time? do we think that will actually help get more bugs done?
17:12:12 <JayF> rloo: I'd call it "done" sans the dev docs
17:12:16 <dtantsur> in this state a bug is not considered closed, and there is no longer a procedure to move such bugs to "released" state
17:12:26 <rloo> dtantsur: what do you mean? we need to update the bugs after they are fixed?
17:12:52 <rloo> dtantsur: what should we do? (or is it the release manager that should do whatever?)
17:12:56 <dtantsur> rloo, gerrit does the right thing (use Fix Released), but I've seen a couple of folks putting bugs in Fix Committed
17:13:19 <dtantsur> the latter does not mean "closed", and it requires manual fixing
17:13:21 <rloo> dtantsur: Fix Released == an ironic release?
17:13:29 <dtantsur> Fix Released = Closed
17:13:34 <dtantsur> treat it this way :)
17:13:39 <jroll> ++
17:13:46 <rloo> dtantsur: OH. ok. I thought it was only when the release happened.
17:13:51 <dtantsur> jroll, not sure about normal FF time, but maybe allocate a some time to clean it up
17:13:51 <JayF> rloo: it used to be "Fix Committed -> software released -> Fix Released" but then we moved to just "Fix Released ~= Closed"
17:13:58 <dtantsur> rloo, it used to be the case, it's no longer though
17:14:06 <dtantsur> yes, as JayF explained
17:14:11 <rloo> why don't we just get rid of fixed release then?
17:14:34 <rloo> or have some bot change fix commited to fix released?
17:14:36 <jroll> dtantsur: there's only four weeks between FF and final release, so "extra time" seems like FF time
17:14:43 <vdrok> I thought that they can just be moved them from fix committed to fix released?
17:14:46 <dtantsur> rloo, we can't get rid of stuff built into launchpad :)
17:14:53 <lucasagomes> not sure we can, it's launchpad
17:15:13 <dtantsur> it does not happen too often though, I'm just reminding the folks :)
17:15:15 * JayF waits for someone to perk up and sell us on storyboard ;)
17:15:24 <rloo> dtantsur: it just seems to be one extra manual thing that we humans shouldn't need to remember to do.
17:15:38 <dtantsur> JayF, the last time I tried it, it was not ready yet (politely speaking). but it was some time ago
17:15:48 <JayF> rloo: it's only "manual" if you close the bug manually. Gerrit will automatically put it in Fix Released if you tag everything right.
17:16:00 <JayF> rloo: this is just if you go to manually change the status of a bug, make sure to go all the way to "Fix Released"
17:16:22 * rloo thinks we ask too much of our developers
17:16:23 <dtantsur> jroll, maybe then FF, yes. with exceptions, as usual, but still
17:16:52 <jroll> dtantsur: yeah, I'll think about it, it's close to time to start saying 'yes' or 'no' to features anyway
17:17:09 <dtantsur> yeah, it's pretty clear (IMO) which priorities land and which don't
17:17:29 <dtantsur> we still can be pretty liberal towards vendor changes (for those vendors who have CI working ;)
17:17:37 <jroll> dtantsur: yeah, I think so. went through trello this morning so I have a good idea of where we're aty
17:17:39 <jroll> at*
17:18:16 <dtantsur> yep
17:18:55 <jroll> anyone else have subteam question things or should I open up the floor?
17:19:36 <jroll> #topic open discussion
17:19:40 <jlvillal> I was just wondering when we start working on the Barcelona Summit sessions?
17:19:52 <jlvillal> Or the schedule for them.
17:20:00 <jroll> so just wanted to point out this cinder thread about deprecation process and driver removal for third party CI:
17:20:01 <jlvillal> And what we will discuss
17:20:02 <jroll> #link http://lists.openstack.org/pipermail/openstack-dev/2016-August/101428.html
17:20:11 <JayF> I suspect we might want to wait until the talks for summit are accepted/rejected
17:20:12 <jroll> worth a read, it's relevant to us. I still am taking it all in
17:20:22 <jroll> jlvillal: I haven't heard much on it yet
17:20:25 <JayF> as that might help decide who ends up in barcelona and who doesn't :(
17:20:47 <jroll> I'd assume we'll chat about it in september
17:21:00 <jroll> JayF: I don't think "who is there" really changes much about what we need to discuss in person :)
17:21:01 <jlvillal> Okay, thank you.
17:21:17 <vdrok> the accepted talks will be known in the beginning of september iirc?
17:21:24 <JayF> jroll: eh, we tend to not put topics on the agenda unless someone will champion it though
17:21:49 * jlvillal does wonder when they will announce the accepted summit talks
17:21:54 <jroll> JayF: sure, I guess I think we have enough big things to get through
17:23:35 <dtantsur> Driver composition: episode 4 (or 5?)  :D
17:23:37 <jroll> anything else folks want to talk about?
17:23:41 * dtantsur hopes it no longer needs a discussion though
17:23:45 <jroll> heh
17:24:07 <dtantsur> this last for so long that Disney soon will buy rights on it from me :D
17:24:16 <jroll> yay for quick meetings, thanks everyone :)
17:24:18 <NobodyCam> thank you all
17:24:18 <jroll> dtantsur: LOL
17:24:23 <jroll> #endmeeting