15:00:10 <dtantsur> #startmeeting ironic
15:00:11 <openstack> Meeting started Mon Sep  9 15:00:10 2019 UTC and is due to finish in 60 minutes.  The chair is dtantsur. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:15 <openstack> The meeting name has been set to 'ironic'
15:00:26 <dtantsur> heya! who's here for the most ironic meeting in the openstack world?
15:00:27 <rpittau> o/
15:00:30 <etingof> o/
15:00:34 <cdearborn> o/
15:00:39 <rloo> o/
15:00:52 <kaifeng> o/
15:01:00 <rpioso> o/
15:01:04 <dtantsur> #link https://wiki.openstack.org/wiki/Meetings/Ironic is our agenda (quite empty)
15:01:20 <dtantsur> #topic Announcements / Reminder
15:01:51 <dtantsur> #info Non-client libraries (metalsmith, ironic-lib and sushy) have been finalized for Train
15:02:06 <dtantsur> all new development there will target U
15:02:12 <dtantsur> (bug fixes are, of course, welcome)
15:02:26 <dtantsur> #info Client libraries release deadline this week
15:02:39 <iurygregory> o/
15:02:43 <dtantsur> actually, python-ironic-inspector-client has been released as well, and I'm about to process python-ironicclient
15:02:50 <openstackgerrit> Ilya Etingof proposed openstack/ironic-prometheus-exporter master: Add metrics descriptions  https://review.opendev.org/681007
15:02:50 <dtantsur> last but not least:
15:03:01 <mgoddard> o/
15:03:11 <dtantsur> #info Soft feature freeze begins on Thursday
15:03:43 <dtantsur> I'd like us to slow down on new features this week, so that we can branch stable/train for all projects in one-two weeks
15:03:55 <dtantsur> #link https://releases.openstack.org/train/index.html
15:04:01 <dtantsur> #undo
15:04:02 <openstack> Removing item from minutes: #link https://releases.openstack.org/train/index.html
15:04:05 <dtantsur> #link https://releases.openstack.org/train/schedule.html
15:04:39 <dtantsur> We must absolutely have stable/train by RC1 deadline, which is the week of Sep 23rd
15:05:08 <dtantsur> better next week, so please plan accordingly
15:05:22 <iurygregory> ack
15:05:33 <dtantsur> if you're planning on feature work for train, let's raise it during the discussion section of this meeting
15:05:49 <dtantsur> anything else to announce? any questions about the deadlines?
15:07:07 <dtantsur> #topic Review subteam status reports (capped at ten minutes)
15:07:22 <dtantsur> #link https://etherpad.openstack.org/p/IronicWhiteBoard around line 217
15:08:46 <rloo> dtantsur: let's be explicit, and mention where we are punting to U
15:09:01 <rloo> eg, deploy steps. ?
15:09:09 <dtantsur> we could do it the other way around and mention what is NOT punted :)
15:09:19 <rloo> dtantsur: true, either way.
15:09:41 <rloo> dtantsur: historically, i think we've mentioned the stuff we've punted, but as long as it is clear to people :)
15:09:42 <dtantsur> so yes, deploy steps are unlikely to make it, except for the vendor implementation patches (e.g. iDrac RAID)
15:10:04 <rloo> idrac raid is WIP in the etherpad
15:10:29 <rloo> i guess what i'd like to know is for deploy steps, there are 4 PRs; which do we think we can get into train?
15:11:10 <dtantsur> most vendor PRs are in good shape, they're likely to make it
15:11:40 <mgoddard> I'm working on the iDRAC RAID deploy step
15:11:45 <rloo> well, it'd help if the status was updated; am doing that now...
15:11:49 <mgoddard> punting other deploy steps work :(
15:11:55 <mgoddard> sure
15:12:17 <openstackgerrit> Richard G. Pioso proposed openstack/ironic master: Add idrac HW type support of Redfish interfaces  https://review.opendev.org/681046
15:12:30 <rpioso> There's one ^^^
15:12:41 <rloo> so for deploy steps, mgoddard is working on idrac raid. what about deploy steps for ilo mgt?
15:13:03 <rloo> shiv doesn't seem to be here.
15:13:03 <dtantsur> rloo: stendulker has patches, I think they're in a good shape and close to approval
15:13:21 <rloo> dtantsur: ok, i see you've looked at it.
15:13:26 <dtantsur> yep
15:13:49 <dtantsur> Indicators API remains unclear
15:14:00 <dtantsur> this is a big chunk of work that has been largely unreviewed
15:15:15 <dtantsur> opinions? etingof, will you have cycles to iterate on it this week? will anybody have time for reviewing it?
15:15:40 <etingof> dtantsur, most certainly!
15:15:58 <rpittau> if it's a priority I can make some time to review them
15:16:25 <rloo> etingof: how close do you think that work is? minor changes or .. ?
15:16:46 <dtantsur> what worries me is that the last time I reviewed we ended up changing the API design :)
15:16:47 <etingof> rloo, it works in devstack!
15:16:52 <dtantsur> \o/ ship it
15:17:07 <rpittau> etingof: I see 3 patches mentioned in the etherpad, is that all?
15:17:10 <rpittau> and lol
15:17:55 <etingof> rpittau, yes, other relevant ones have been merged
15:18:22 <rloo> if etingof is avail to iterate and there are people willing to review, then i'm fine with it in train. we can see where we're at next Monday.
15:18:48 * etingof will do his best
15:18:52 <dtantsur> do we have a *non Red Hat* person to review it?
15:19:31 <rloo> wrt software raid, it is done but there is a comment at L324, 'Finished for Train, small fixes are still being posted'. If there are small fixes, could someone provide the links please?
15:19:32 * rpioso suggests expanding our cores' wardrobe
15:19:46 <rloo> dtantsur: i can try later this week, but no promises
15:19:51 * rpittau still doesn't have a Red Hat :/
15:19:52 <dtantsur> thanks rloo
15:19:58 <dtantsur> I'll add the sw raid links
15:20:15 * iurygregory is sad for rpittau
15:20:23 <rloo> rpittau: don't worry, most of us don't have red hats :D
15:20:41 <rpittau> :D
15:21:15 * dtantsur has probably lost his already
15:21:22 <dtantsur> anyway, are we ready to move on?
15:21:31 <rpioso> I updated the idrac vendor priority. It's the change above. We would like to see it land in Train.
15:21:38 <dtantsur> k
15:22:13 <dtantsur> #topic Deciding on priorities for the coming week
15:22:14 <rloo> tssurya: when you are avail, would you please let us know if there are any more PRs related to power state callbacks to Nova. It is done except for a release note update: https://review.opendev.org/#/c/676400/, yes?
15:22:15 <patchbot> patch 676400 - ironic - Follow-up to power sync reno - 1 patch set
15:22:32 <dtantsur> oh, not ready yet?
15:22:46 <rloo> dtantsur: almost ready i think. just want to verify
15:22:55 <rloo> so ipv6 is not going to get done, right?
15:23:00 <tssurya> rloo: yea that's correct
15:23:09 <tssurya> all done except thta follow-up
15:23:12 <dtantsur> rloo: quite unlikely, yes. but since it's CI work, it's not affected by deadlines.
15:23:12 <rloo> tssurya: thx for confirming!
15:23:12 <tssurya> that*
15:23:22 <dtantsur> (unless it turns into a feature work, of course)
15:23:35 <tssurya> thanks to all of you for the review efforts and time
15:23:43 <rloo> dtantsur: ok. and the doc generation stuff? is that affected by deadline?
15:24:24 <rloo> L356 ^^
15:24:50 <dtantsur> rloo: nope. and it's fine to backport.
15:25:06 <kaifeng> the docs job is basically done except a few patches in the review list
15:25:11 <rloo> good to know dtantsur!
15:25:19 <dtantsur> kaifeng: could you add them to the priority list?
15:25:35 <dtantsur> etingof: same request for indicator patches ^^
15:25:39 <kaifeng> dtantsur: will do
15:25:45 <etingof> dtantsur, ok
15:26:17 <etingof> how about reviewing the latest ironic-prometheus-exporter additions? -- https://review.opendev.org/680731
15:26:17 <patchbot> patch 680731 - ironic-prometheus-exporter - Add Redfish metrics support - 3 patch sets
15:26:39 <dtantsur> we probably have to, yes. if you plan on making it into train.
15:27:50 <etingof> dtantsur, I'd like to
15:29:29 <kaifeng> dtantsur: added at L168, molteniron and virtualpdf are not listed, they don't have doc job so I guess it's not required.
15:29:43 <dtantsur> kaifeng: thanks!
15:30:10 <dtantsur> etingof: when listing patches, could you add a short summary before each?
15:30:18 <etingof> dtantsur, ack
15:31:04 <etingof> we also have a couple of easy fixes for sushy-tools, those are good to merge because then the whole thing actually works
15:31:44 <rloo> mgoddard: dtantsur: this client PR, is that something we want discussed/done in train? https://review.opendev.org/#/c/675940/
15:31:44 <dtantsur> I'd delay them, we already have a huge review backlog
15:31:45 <patchbot> patch 675940 - python-ironicclient - Fix AttributeError in negotiate_version - 1 patch set
15:32:15 <dtantsur> rloo: ideally, although it can (and should) be backported
15:32:56 <rloo> dtantsur: mgoddard: do you two know what the solution is? (I just skimmed the comments)
15:33:08 <dtantsur> I don't
15:33:14 <mgoddard> rloo: it would be nice, although as dtantsur says it's a bug so can be backported
15:33:29 <dtantsur> I'd make it a priority for next week
15:33:40 <dtantsur> and wrap up feature work this week
15:33:42 <rloo> ok, i don't think it'll make it in this week then. the client deadline is this week, right?
15:33:59 <dtantsur> yep
15:34:11 <dtantsur> I actually wanted to request a release today
15:34:44 <rloo> dtantsur: ok, let's try to fix that soon and backport it.  i don't see anything other PRs for client that might need addressing right now, so a release today is fine.
15:35:01 <rloo> dtantsur: we're bumping the major version or ? cuz we deleted ironic CLI, right?
15:35:15 <dtantsur> right
15:35:45 <rloo> dtantsur: yay. although i worry that we'll have broken people that didn't know/didn't get around to switching to openstackclient.
15:36:02 <dtantsur> it would happen whenever we pull the trigger :)
15:36:20 <rloo> dtantsur: yup. so even though i worry... pull the trigger anyway!
15:36:28 <rloo> i'm good with the weekly priorities :)
15:36:36 <dtantsur> now there are talks of migrating for python API to openstacksdk..
15:36:39 <dtantsur> anyway
15:36:50 <dtantsur> any other comments on the priorities? anything to add or (better!) remove?
15:37:27 <rloo> dtantsur: oh, that reminds me. the two PRs at L143 & 144
15:37:59 <rloo> dtantsur: do we want to get them into train? if so we mgiht want to discuss L143, and someone needs to continue L144
15:38:16 <dtantsur> I'd love to get 143 in, it's a constant source of complaints from the customers
15:38:31 <rloo> dtantsur: yeah, me too...
15:39:08 <kaifeng> wrt 144, there is a similar patch already gets in, proposed by mkrai
15:39:50 <dtantsur> rloo: would be great if you could check my responses for L143
15:39:54 <dtantsur> kaifeng: link handy?
15:40:10 <rloo> dtantsur: ok, will discuss with you. prob tomorrow though.
15:40:49 <kaifeng> dtantsur: https://review.opendev.org/#/c/677649/ it's doing the opposite
15:40:50 <patchbot> patch 677649 - ironic - Allow deleting unbound ports on active node (MERGED) - 3 patch sets
15:41:35 <dtantsur> rloo: tl;dr I'm purposely disallowing "provide" action for nodes in maintenance
15:42:00 <dtantsur> kaifeng: not exactly the opposite, although I am somewhat confused by these two patches..
15:42:06 <dtantsur> I have to check with a fresh head tomorrow
15:42:20 <dtantsur> we can leave them on the list, so that we don't forget to follow-up/discuss, wdyt?
15:42:32 <rpittau> makes sense
15:42:49 <rloo> i think mkrai's addresses a subset of the port deletion/with-or-without-vif problem.
15:43:00 <rloo> but yeah, leave on the list.
15:43:13 <dtantsur> okay. moving on?
15:43:20 <mkrai_> mkrai_, I can take a look at the L144 patch tomorrow
15:43:31 <dtantsur> thanks mkrai_
15:43:38 <dtantsur> #topic Open discussion
15:44:07 <dtantsur> anything? I guess we've already discussed the feature freeze
15:44:15 * kaifeng was cheated by the double negative commit message
15:44:46 <dtantsur> heh
15:45:07 <rloo> double negatives are tricky; we should try to avoid them!
15:46:00 <rloo> crickets?
15:46:09 <dtantsur> apparently :)
15:46:17 <dtantsur> it's still sort of summer, right?
15:46:42 <etingof> +15 over here
15:46:48 <dtantsur> sort of
15:46:49 <rpittau> crickets and dragonflies everywhere
15:46:55 <dtantsur> thanks everyone, let's make a rocking train! :)
15:46:58 <iurygregory> not in Brazil XD
15:46:58 <dtantsur> #endmeeting