15:00:09 <TheJulia> #startmeeting ironic
15:00:10 <openstack> Meeting started Mon Jun 18 15:00:09 2018 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:14 <TheJulia> rloo: agree
15:00:14 <openstack> The meeting name has been set to 'ironic'
15:00:17 <TheJulia> o/ everyone
15:00:23 <jroll> already meeting time? :o
15:00:26 <NobodyCam> o/
15:00:27 <rloo> o/
15:00:39 <stendulker> o/
15:00:40 <bdodd> o/
15:00:50 <vdrok> o/
15:01:01 <baha> o/
15:01:15 <hshiina> o/
15:01:31 <TheJulia> Our agenda looks rather quiet today.
15:01:33 <TheJulia> #link https://wiki.openstack.org/wiki/Meetings/Ironic
15:01:39 <openstackgerrit> Vladyslav Drok proposed openstack/ironic-specs master: Add synchronize-events-with-neutron spec  https://review.openstack.org/343684
15:02:05 <TheJulia> #topic Announcements/Reminders
15:02:10 <mjturek> o/
15:02:26 <vpc> o/
15:02:50 <TheJulia> Two things. The first is that I believe we're ?R-6? Which means we will need to finish up/polish up things for our release for this cycle relatively soon
15:03:21 <rpioso> o/
15:03:43 <TheJulia> The second... I'm on the road again this week departing tomorrow. I believe the total time shift for me will be 12 hours, so expect odd hour replies if you ping me
15:04:17 <TheJulia> Does anyone have anything they would like to announce or remind us of?
15:04:26 <rloo> did you/we do any releases last week?
15:04:43 * TheJulia looks at dtantsur
15:05:06 <rloo> (or err are we planning any this week?)
15:05:52 <TheJulia> Looks like we only cut queens releases last week
15:06:36 <dtantsur> we did, but only queens
15:06:39 <dtantsur> yes
15:06:53 <dtantsur> ironic is blocked by https://review.openstack.org/575113 from my pov :)
15:06:54 <patchbot> patch 575113 - ironic - Remove the remaining fake drivers
15:07:09 <TheJulia> I think that is a reasonable block
15:07:09 <dtantsur> I can request releases after that
15:07:19 <dtantsur> we also need someone to go over release notes, ideally not me
15:07:42 <TheJulia> I can give it a try, but the whole information processing disorder can make that slightly difficult
15:07:57 <TheJulia> Then again, I'll be on a plane for how many hours?
15:08:13 <TheJulia> dtantsur: I'll try to do a pass on the renos tomorrow
15:08:20 <dtantsur> great, thanks!
15:08:26 <TheJulia> Anyway, we're at nearly 10 minutes and we should move on
15:09:10 <TheJulia> #topic Review Action Items for prior week
15:09:12 <TheJulia> #link http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-06-11-15.00.txt
15:09:32 <TheJulia> Looks like the only one was for dtantsur for IPA python3
15:10:35 <TheJulia> dtantsur: Any update?
15:10:52 <dtantsur> nope, lost track of it, sorry
15:11:19 <TheJulia> Okay, Are you going to try again for this week?
15:11:21 <dtantsur> well, one thing I figured out is that we don't track Pike goals on SB
15:11:27 <dtantsur> so we have to track it outselves?
15:11:45 <TheJulia> pike goals?
15:12:08 <dtantsur> python 3 was from pike, no?
15:12:09 <TheJulia> the whiteboard has been what we've been using for the current cycle
15:12:12 <TheJulia> oh!
15:12:33 <TheJulia> uhh... it was tracked under changesets to the governance repo I believe
15:12:52 <dtantsur> yep, but that's not visible for us too much
15:13:01 * dtantsur creates a story right now
15:13:05 <jroll> ++
15:13:05 <TheJulia> okay
15:13:11 <TheJulia> Anyway, moving along!
15:13:15 <TheJulia> #topic Review subteam status reports
15:13:31 <TheJulia> #link https://etherpad.openstack.org/p/IronicWhiteBoard
15:13:57 <TheJulia> Status reports start at line 146
15:14:15 <rloo> dtantsur: wrt the bugs/stats. what does 'fetching stories from board 83' mean?
15:14:33 <dtantsur> rloo: exhaustive copy-paste, sorry
15:14:48 <dtantsur> ehmm, excessive?
15:14:59 * dtantsur wonders why all words look so similar
15:15:23 <rloo> the number of RFEs is catching up to the number of bugs...
15:16:14 <rloo> i just updated the HIGH bug ... (L160).
15:16:21 <dtantsur> #link https://storyboard.openstack.org/#!/story/2002598 IPA python 3 story
15:17:58 <rloo> TheJulia: wrt nova-flexible-with-ironic-API-version. we need to do a client release first?
15:18:22 * dtantsur suspects yes
15:18:25 <TheJulia> rloo: was that the take-away from the notes I added moments ago?
15:18:39 <dtantsur> I can request a release once we have everything merged
15:19:04 <rloo> TheJulia: well, it looks like all the client patches have merged, and it sez 'next logical step is to change nova'. which means it needs a client release, right?
15:19:12 <TheJulia> As the rescue patch is presently, it does it non-invasively using what was released last cycle
15:19:19 <TheJulia> but yes, we should go ahead and release the client
15:19:47 <TheJulia> we have two possible paths we can take that end up in roughly the same place in the grand scheme of the universe.
15:20:09 * rloo confused. why did we make those client changes, if we don't need it for nova.
15:20:38 <jroll> also confused - do we have a plan written down somewhere on that?
15:21:06 <TheJulia> because we had pushback about not following or being able to follow api sig recommendations and doing explicit call level handling
15:21:17 <TheJulia> the state of the rescue patch just graefully permits both
15:21:47 <TheJulia> which is not ideal to land in nova, but it would reach the same basic result
15:22:21 <rloo> but don't we want the 'ideal' thing to land in nova. 'ideal' == nova folks are happy with, and to be used as a model for future ironic features?
15:23:06 <rloo> i haven't looked at nova's rescue patch though, so maybe i shouldn't ask w/o looking...
15:23:51 <TheJulia> Ideally, to make everyone as happy as possible, we would do the ideal thing, it would also merge conflict with the rescue patch
15:24:49 <TheJulia> Since it requires an API version bump, and the same areas of code will be impacted. I don't think this should prohibit us doing so and writing a nova patch to take the ideal route, but we need to be mindful of the rescue patch in all of that.
15:25:16 <jroll> this is only going to be used by rescue at first, right?
15:25:24 <TheJulia> yes
15:25:47 <jroll> any reason not to just stack the patches then?
15:26:21 <TheJulia> None really, someone just needs to do it
15:26:30 <TheJulia> once we have a release that is
15:26:36 <jroll> mel was pretty supportive of getting the versioning thing in, seems we should just agree with her on the right thing to do, line it up, and go
15:26:38 <jroll> ok
15:27:20 <TheJulia> jroll: yeah, The last time it was discussed in irc, she was pretty much along the same lines of even if it a list of versions, which is what the rescue patch does
15:27:22 <TheJulia> currently
15:27:39 <jroll> ok
15:27:49 <jroll> we could stack the better way to do it on top of rescue
15:28:24 <TheJulia> Yeah, likely would be best to do that that way we merge rescue first and if the version patch doesn't get reviews or land then we're still in a semi-happy place
15:29:02 <TheJulia> Anyway, anything else for status updates? Or shall we go to priorities for the next week?
15:29:03 <jroll> yep, it isn't critical to clean it up this cycle, could merge early in stein
15:29:14 <TheJulia> jroll: ++
15:30:17 <rloo> dtantsur: i put your storyboard link at L301. We can delete that from the whiteboard before next meeting
15:30:48 <TheJulia> #topic Priorities for the next week
15:30:55 * TheJulia cleans up the merged items from the list
15:31:21 <dtantsur> rloo: it's also on line 295
15:31:24 <rloo> dtantsur: oh wait, is that storyboard link only for the IPA python3 jobs?
15:31:39 <dtantsur> rloo: well, it's the last remaining bit for python 3 IIRC
15:32:02 <rloo> dtantsur: all the stuff below your TODO is included in the storyboard?
15:32:26 <dtantsur> rloo: not swift, but that's not really an action item for us
15:32:26 <TheJulia> does anyone care enough about the secure erase stuff besides myself for it to be a priority for htis week?
15:32:35 <dtantsur> TheJulia: I guess we have to
15:32:44 <dtantsur> bricking hard drives is not a great thing to do
15:32:48 <rloo> is that the patch that i just reviewed?
15:32:55 <rloo> just need to update the reno, right?
15:33:09 <rloo> i don't care if you put as a priority, after you update, let me know and I'll review :)
15:34:09 <TheJulia> rloo: yeah, that one
15:34:38 <TheJulia> well, there are a total of four patches all mixed together, seems one of them breaks the gate that needs to be investigated
15:35:16 <TheJulia> This seems reasonable to add for python-ironicclient (it is small)
15:35:16 <rloo> TheJulia: oh, we need all 4 of them? Then yeah, guess it is a priority :)
15:35:17 <TheJulia> https://review.openstack.org/#/c/508330/
15:35:18 <patchbot> patch 508330 - python-ironicclient - Allow to use none auth in functional tests
15:35:28 <dtantsur> TheJulia: as for Nova patches, maybe put the patch using "reserved" instead of 0 for inventory?
15:35:53 <TheJulia> dtantsur: I'm not mentally aware of that one, got a link handy?
15:36:12 <dtantsur> #link https://review.openstack.org/#/c/517921/
15:36:13 <patchbot> patch 517921 - nova - ironic: Report resources as reserved when needed
15:37:08 <TheJulia> Yeah, a few eyes would help for that one I think
15:37:23 <TheJulia> Is anyone aware of anything else that must get some eyes this week?
15:37:25 <vdrok> I'll take a look at the failures and recheck if these are temporary issues
15:37:38 <TheJulia> vdrok: thanks!
15:38:34 <TheJulia> Well, I think the list looks decent if nobody has anyting else that needs to be added
15:39:31 <TheJulia> Everyone good with the list for the week?
15:39:34 <dtantsur> TheJulia: added a hidden dependency, otherwise LGTM
15:39:54 <TheJulia> dtantsur: thanks!
15:40:26 <rloo> +good
15:40:38 <TheJulia> oh, great catch, thanks dtantsur
15:41:26 <TheJulia> rloo: Are there any RFE's you wish to discuss today?
15:41:41 <rloo> TheJulia: nope
15:41:45 <TheJulia> okay
15:41:57 <TheJulia> Anyone else with RFEs that they would like to discuss today?
15:42:18 <TheJulia> Otherwise next stop is Open Discussion
15:42:51 <dtantsur> people asked me if we could return 503 instead of 400 if no conductors are alive at all
15:43:06 <dtantsur> currently we return "No conductor registered which supports driver <xxx>"
15:43:14 <dtantsur> which is technically correct, but can be misleading in this case
15:43:27 <jroll> I've always kind of idly wondered the same
15:43:29 <TheJulia> could we add logic to catch that, and double check?
15:43:29 <dtantsur> the primary case is non-rolling upgrade
15:44:00 <dtantsur> I can work on it if there are no objections (no RFE formally posted yet)
15:44:12 <TheJulia> I'd treat it as a bugfix to be honest
15:44:12 <rloo> looks like there are two cases. if there are conductors alive but none support the driver, then 400, if no conductors alive, then 503
15:44:35 <dtantsur> rloo++
15:44:42 <rloo> and yeah, that seems more like a bug. regardless, i approve :)
15:44:42 <dtantsur> TheJulia: bugfix with a microversion? ;)
15:45:00 <TheJulia> dtantsur: It is prefectly acceptable to have a bugfix force a microversion increment
15:45:26 <dtantsur> I guess the real question is: should we hide the change behind a microversion?
15:45:49 <dtantsur> or should we fix all versions?
15:45:52 <jroll> dtantsur: while we're at it, I wonder if the error should be "No conductor registered which supports driver <xxx> for this node" or "for node foo". that message has always seemed confusing to me if you aren't interacting with a driver resource
15:45:59 <rloo> i think we have to. cuz folks might have scripts looking for 400 for those cases.
15:46:02 <TheJulia> I'm fairly sure, to address where this error is encountered today in nova, we would need to patch nova regardless
15:46:18 <jroll> nova?
15:46:20 <TheJulia> so a microversion, in my mind seems cleaner
15:46:21 <dtantsur> rloo: well, we can return 503 already from any call involving conductor
15:46:32 <dtantsur> at least any async call
15:46:39 <dtantsur> because of "no free conductor threads"
15:46:53 <TheJulia> jroll: the specific case was restart of nova-compute w/o any conductors running.... and nova-compute trying to restand-up networking with no conductors, and thinking everything is broken
15:46:53 <rloo> dtantsur: true, but we don't know if anyone has some script looking for 400 and then doing something based on no conductors being alive.
15:46:56 <jroll> I would prefer a microversion, I don't see much reason not to
15:47:07 <dtantsur> jroll: nova tries to attach VIFs on nova-compute start-up
15:47:15 <jroll> ok, thanks for the context
15:47:15 <dtantsur> if it fails, it moves instances to ERROR
15:47:18 <jroll> wait
15:47:20 <jroll> on startup?
15:47:21 <dtantsur> which is.. ugly :(
15:47:22 <TheJulia> yup
15:47:23 <jroll> wat
15:47:23 <dtantsur> yep
15:47:28 <jroll> waaaaaaat
15:47:34 * TheJulia hands jroll a beer
15:47:35 <jroll> I guess I get it for virt, but... sigh
15:48:00 <dtantsur> jroll: some ppl want to fix it and make driver-specific
15:48:01 * jroll accepts and returns the favor
15:48:05 <dtantsur> but we have what we have
15:48:21 <TheJulia> #topic Open Discussion
15:48:23 <jroll> yes, this feels like a startup=True on plug_vifs or something
15:48:31 <TheJulia> ++
15:48:37 <jroll> I do think the 503 thing would still be useful
15:48:52 <dtantsur> jroll: long-read for background: https://bugzilla.redhat.com/show_bug.cgi?id=1590297
15:48:54 <openstack> bugzilla.redhat.com bug 1590297 in openstack-ironic "[UPDATE][SCALE-UP] After update and scale up all origin node are in ERROR status" [Unspecified,New] - Assigned to rhos-maint
15:48:56 <jroll> since we shouldn't be running that code at startup anyway
15:48:56 <TheJulia> That was kind of what I was thinking when I was looking at the nova code earlier this morning
15:49:18 <jroll> who knows what third party network drivers might break on if they "re-attach" vifs
15:49:51 <TheJulia> I'm unaware of any third party network interfaces for ironic, but... yeah :\
15:50:17 <jroll> sam has one
15:50:31 <TheJulia> :(
15:50:39 <jroll> he can make NICs from thin air
15:50:48 <TheJulia> Magical nics
15:51:11 <sambetts> *poof*
15:51:14 <TheJulia> heh
15:51:31 <TheJulia> So anything else for us to chat about this week? Anything for me to do on my flights this week?
15:51:40 <jroll> anyway, I'd like the change to 503. it would be nice to microversion it. I think the nova thing shouldn't rely on that, but rather have some "startup" argument on whatever method does the thing
15:51:50 <jroll> (I think it already has that, but maybe not at the driver layer)
15:52:12 * jroll has nothing, is still in greenfield land collecting todos for ironic to do wild secureboot things
15:52:59 <TheJulia> jroll: is there any discussion upstream needed? I've not gotten to sending out anything from the summit yet
15:53:27 * dtantsur filed https://storyboard.openstack.org/#!/story/2002600
15:53:27 <jroll> TheJulia: not yet - doing a POC thing outside of ironic, then I'll be working on how we would do it with ironic
15:53:45 <TheJulia> jroll: ack
15:55:02 <TheJulia> jroll: I wrote up a thing for opencit integration w/r/t attestation, that might also be useful, but it would be interesting to see what your perspective reaches at your scale and needs as opposed to what was created at intel w/r/t secure boot/attestation
15:55:35 <jroll> TheJulia: cool, will let you know when I have a writeup of sorts. probably on the order of weeks
15:55:42 <TheJulia> jroll: cool
15:55:55 <TheJulia> Okay, we've got five minutes left, anyone have anything else to discuss?
15:56:38 * TheJulia hears crickets
15:56:44 * rloo thinks i hear crickets in the pouring rain
15:57:10 * TheJulia now hears a chorus of crickets
15:57:10 <dtantsur> heh
15:57:21 <TheJulia> Thanks everyone!
15:57:24 <TheJulia> Have a wonderful week!
15:57:28 <dtantsur> ++ thanks TheJulia
15:57:44 <rpioso> TheJulia: Safe travels
15:57:46 <jroll> thanks TheJulia :)
15:57:47 <TheJulia> #endmeeting