15:00:23 <TheJulia> #startmeeting ironic
15:00:24 <openstack> Meeting started Mon Jun 17 15:00:23 2019 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:27 <TheJulia> o/
15:00:28 <openstack> The meeting name has been set to 'ironic'
15:00:30 <cdearborn> \o
15:00:35 <rpittau> o/
15:00:37 <bdodd> o/
15:00:44 <kaifeng> o/
15:00:45 <mgoddard> \o
15:00:47 <etingof> \o
15:00:52 <arne_wiebalck> o/
15:01:01 <jungleboyj> o/
15:01:03 <TheJulia> Good Morning everyone!
15:01:09 <rpioso> \o
15:01:27 <TheJulia> Today's agenda can be found on the wiki page.
15:01:29 <TheJulia> #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
15:01:33 <rloo> o/
15:01:41 <TheJulia> I don't have much, so hopefully this will proceed quickly
15:01:43 <TheJulia> *hopes*
15:01:57 <TheJulia> #topic Announcements/Reminders
15:02:05 <jroll> \o
15:02:23 <baha> o/
15:02:26 <TheJulia> I'm hoping to cut a release of ironic 12.2 today or tomorrow. Afterwards we should be able to go ahead and begin merging the more breaking changes for the cycle.
15:03:22 <arne_wiebalck> TheJulia: Do you need the s/w RAID docs for this?
15:03:24 <TheJulia> Does anyone have anything else to remind us about today?
15:03:43 <TheJulia> arne_wiebalck: to release, no. It would be nice though to get something into master branch soon-ish
15:03:45 <mgoddard> TheJulia: is that something I can help with? I did offer to help with releases at the PTG, although I've not been much help so far
15:03:54 <TheJulia> mgoddard: it is!
15:04:00 <arne_wiebalck> TheJulia: ack
15:04:16 <TheJulia> Although I think at this point it would just be picking the hash number and putting the commit up for review in openstack/releases
15:04:33 <mgoddard> TheJulia: great. Just ironic or other repos too?
15:04:37 <dnuka> o/
15:04:46 <TheJulia> I think dtantsur was only thinking https://review.opendev.org/#/c/665635/ needed to merge first. I think
15:04:47 <patchbot> patch 665635 - ironic - devstack: add missing variables for ironic-python-... - 1 patch set
15:05:06 <TheJulia> mgoddard: just ironic, dtantsur already cut some releases for libs and other programs so far this cycle
15:05:11 <mgoddard> ok
15:05:47 <TheJulia> Well if nobody has anything to announce or remind us of, we can carry on.
15:06:25 <TheJulia> #topic Review action items from previous meeting
15:06:53 <TheJulia> We had one action item last week which was to get a release note update to indicate that smartnic functionality is available with a Train Neutron.
15:07:00 <TheJulia> I proposed that and it merged so \o/
15:07:04 <TheJulia> Moving on
15:07:21 <TheJulia> #topic Review subteam status reports
15:07:29 <TheJulia> #link https://etherpad.openstack.org/p/IronicWhiteBoard
15:08:41 * TheJulia skims down the list
15:08:44 <TheJulia> mkrai: thanks for the update :)
15:08:45 <dtantsur> yep, I did some releases, only ironic (I think) is pending
15:09:35 <rloo> dtantsur: did you see the question from kaifeng wrt bugs (L233)
15:09:36 <TheJulia> arne_wiebalck: Any continuation on the retirement discussions?
15:09:54 <arne_wiebalck> not yet, will pick this up again
15:10:15 <dtantsur> kaifeng: the data is pulled from https://storyboard.openstack.org/#!/board/83
15:10:24 * dtantsur did not have time to update it this time - sorry
15:10:49 <kaifeng> oh, I am not sure how to triage a rfe
15:11:11 <dtantsur> kaifeng: use "rfe" tag (in addition to "ironic-triaged")
15:11:20 <dtantsur> as always with triaging, make sure it makes any sense :)
15:11:36 <dtantsur> if some RFE is ready for discussion, feel free to raise it on the next meeting
15:11:46 <kaifeng> so the ironic-triaged tag is a mandatory tag
15:11:48 <TheJulia> dtantsur: any update on mdns stuffs this week?
15:12:08 <dtantsur> TheJulia: we're largely done for now. The next patches will come when/if we get IPv6 support in python-zeroconf.
15:12:12 <kaifeng> dtantsur got it, thanks!
15:13:19 <TheJulia> kaifeng: I think I saw you proposed a few patches for the single doc generation work?
15:13:24 <dtantsur> FYI, I'm here till Wednesday, then I have a short PTO (for my German exam), then I'm on an onsite meeting for a week, then I'm on PTO for a week
15:13:40 <kaifeng> TheJulia, right, some repos with simple docs
15:14:04 <kaifeng> I tried ironic, inspector, IPA, they have issues currently
15:14:06 <TheJulia> kaifeng: if you could keep a running list, I think that would help us tracking wise, or if you already have a list :)
15:14:10 <TheJulia> yay!
15:14:12 <TheJulia> Okay
15:14:43 <kaifeng> sure, I will update in the whiteboard, since riccardo is also working on it
15:14:49 <rpittau> pdf docs generation in ironic would work only converting svg to png, and the final result is very bad :/
15:15:05 <TheJulia> One thing worth noting, rpittau has been kind enough to hunt deprecations for Python 3.8. He created an etherpad and listed it under the python3 second on the whiteboard.
15:15:27 <TheJulia> rpittau: how bad? unusable bad?
15:15:39 <rpittau> TheJulia: unreadable in some sections, format is completely off
15:16:18 <TheJulia> https://media1.giphy.com/media/g9OLSjrWHJQRi/giphy.webp?cid=790b76115d07aeb07944554663d2e870&rid=giphy.webp
15:16:28 <rloo> if it is bad for ironic, wouldn't it be a similar situation for other projects' docs? or maybe ours is more sophisticated...
15:16:34 <rpittau> lol that's exactly my expression
15:16:40 <TheJulia> Ours are a bit more complex
15:16:47 <kaifeng> kind of compromise between typesetting and html I guess
15:16:53 <rpittau> rloo: we're kind of early for that, I didn't see other projects doing it
15:17:03 <rpittau> so far
15:17:17 <rloo> rpittau: i'm of the 'wait til closer to the end when others have gotten most bugs out of the system' person
15:17:18 <TheJulia> Better to just get it out of the way sooner and get it into the normal review queues than rush during milestone 3
15:17:40 <rpittau> rloo: I was hoping for that too :D
15:17:41 <rloo> rpittau: maybe reach out to the person that is coordinating the pdf thing?
15:17:50 <TheJulia> I'm good with updates, are we good to proceed once the current docs discussion wraps up?
15:17:53 <kaifeng> rloo: this is a smart move :)
15:17:55 <rpittau> rloo: can do that
15:17:59 <arne_wiebalck> tssurya put up a first patch set for the power state sync with some explicit questions that came up, if anyone wants to have a look (thanks for your feedback, jroll!)
15:18:08 <rloo> TheJulia: one quick question. L 375
15:18:16 <rloo> TheJulia: do we need that? it is from jan?
15:18:16 <rpittau> for the python 3.8 hunt please just be aware of any deprecation message when running tox
15:18:34 <TheJulia> rloo: it is contextual
15:18:35 <rpittau> especially for 'collections'
15:18:53 <TheJulia> Should likely be re-written since it is still true context although I think the focus rihgt now is power
15:19:31 * TheJulia is lost on words at the moment and thinks she can come back to it after the meeting
15:19:36 <rloo> TheJulia: ok, just asking cuz it isn't clear. for those in the audience that don't understand. but then, i'm the only one asking so maybe it is clear to others :D
15:21:24 <rloo> proceed ++
15:21:46 <TheJulia> #topic Deciding on priorities for the coming week
15:22:32 <TheJulia> I already glanced at outstanding patches and didn't see anything that really caught my eye outstanding chagne wise, I think we should just remove the merged patches and carry forward the priorities for this next week. That is unless someone has ones to add?
15:22:43 <TheJulia> #link https://etherpad.openstack.org/p/IronicWhiteBoard
15:22:54 <TheJulia> Line 124
15:22:56 <rpioso> Do we have room for a vendor priority?
15:23:44 <TheJulia> sure
15:24:12 <rpioso> TheJulia: Reviews of https://review.opendev.org/#/c/665576/ would be much appreciated.
15:24:14 <patchbot> patch 665576 - ironic-specs - Add spec for defining idrac support of Redfish - 1 patch set
15:24:46 <dtantsur> rpioso: there is a section for vendor priorities in the whiteboard
15:24:56 <rpioso> dtantsur: It's there :-)
15:24:58 <TheJulia> It is also a spec....
15:25:31 <dtantsur> I could totally use some eyes on https://review.opendev.org/#/c/665632/
15:25:32 <patchbot> patch 665632 - ironic - Add check on get_endpoint returning None - 1 patch set
15:25:51 <dtantsur> overall, I'm starting clean up of keystone related items. My ideal goal is to move from *client to openstacksdk.
15:26:11 <TheJulia> good plan and ugh, yeah I forgot get_endpoint does that
15:27:16 <rpioso> TheJulia: Thank you.
15:27:44 <TheJulia> Anything else for priorities, or are we good to move on?
15:28:42 <rpittau> let's
15:28:50 <rloo> ++ move
15:29:02 <TheJulia> #topic Discussion
15:29:10 <ashtempl_> Sorry for beeing late
15:29:38 <TheJulia> We have one item, and largely it is not in announcements in case anyone wants to discuss it here instead of on the mailing list.... but it is in regards to the topic of changing the format of our meetings.
15:29:40 <ashtempl_> Did you talked about pathes to review already?
15:29:41 <TheJulia> ashtempl_: no worries :)
15:29:47 <ashtempl_> thanks :)
15:30:12 <TheJulia> ashtempl_: yes, but if there is one that needs to be added, we can look at it
15:30:24 <ashtempl_> yep, i have two actually
15:30:33 <ashtempl_> https://review.opendev.org/#/c/650839/
15:30:34 <patchbot> patch 650839 - ironic-tempest-plugin - Single tenant tests: BM to BM and BM to VM - 7 patch sets
15:30:57 <TheJulia> Anyway, going back to the discussion topic. I sent out an email to openstack-discuss summarizing an idea.
15:30:59 <TheJulia> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007038.html
15:31:33 <TheJulia> Dmitry has been the only person to reply so far and I'm hoping for other people to reply.
15:32:03 <rloo> i was hoping to get feedback from the folks that cannot make this meeting. hard to decide w/o their input.
15:32:14 <arne_wiebalck> rloo ++
15:32:40 <rloo> if they don't like the proposal, i don't see why we'd do it, unless we want to try it out.
15:32:44 <jroll> I've been trying to reply for a week and I can't find the right words :/
15:32:45 <rloo> i'm happy with status quo
15:32:51 <ashtempl_> The other one is: https://review.opendev.org/#/c/638932/
15:32:52 <patchbot> patch 638932 - ironic-tempest-plugin - Advanced tests for Networking Ansible feature - 9 patch sets
15:32:58 <rloo> but also happy to do something that works for others :)
15:33:01 <TheJulia> jroll: Perhaps beer will bring them forth?
15:33:15 <jroll> TheJulia: I have drank plenty of beer in that week :P
15:33:26 <TheJulia> oh well, it was a thought.
15:33:28 <ashtempl_> This one is not running by default as you (Julia) and Dmitry have asked.
15:33:53 <rloo> TheJulia: who/how many people wanted a change? I already forgot. Can someone reach out to them directly, or should we assume that we've communicated and ... ?
15:33:55 <TheJulia> Anyway, I concur with rloo, we need their feedback
15:34:16 <rloo> i can reply to your email thread, saying basically ^^ :)
15:34:28 <TheJulia> I think I'll be meeting in-person next week, and I think the other I can just email
15:34:46 <jroll> TheJulia: in short, I don't think "Additional updates, questions, and topical discussion" should wait for a "mailing list meeting" - people should just send the email :)
15:34:51 <jroll> but I'm willing to try the thing
15:34:57 <rloo> TheJulia: ok thx. if you want to reach out to them, this is extra work on your part. would like to see a bit more from their part.
15:35:02 <kaifeng> I think someone created a doodle, and then silent since then
15:35:03 <TheJulia> jroll: +++++++++++++++
15:35:06 <TheJulia> jroll: say that? :)
15:35:20 <TheJulia> kaifeng: yeah, I'll reach out to them directly
15:35:29 <rloo> kaifeng: the 'silence' is this discussion and past discussion in this meeting time.
15:35:40 <jroll> TheJulia: it's so much easier in IRC :) I will attempt to write some words today
15:35:50 <TheJulia> Okay, I just wanted to bring this back up, and I think we can move on
15:35:52 <TheJulia> <3
15:36:03 <TheJulia> ashtempl_: I'll circle back to your patches once we're through our agenda
15:36:21 <TheJulia> #topic Baremetal SIG
15:36:35 <TheJulia> hogepodge o/
15:37:06 <TheJulia> Looks like he is AFK
15:37:16 <TheJulia> client idle for 37 minutes
15:37:20 <hogepodge> hi
15:37:24 <TheJulia> oh hai!
15:37:56 <hogepodge> I have to compose the email to the mailing list talking about the whitepaper and case studies, and coordinate with the rest of the marketing team on it.
15:37:57 <TheJulia> Anything to discuss or bring up regarding the baremetal sig this week?
15:38:15 <hogepodge> That is to say, no movement since last week, but it's on my mind and on my todo list before I head to Shanghai on Saturday.
15:38:23 <hogepodge> Won't be here next Monday because of KubeCon China.
15:38:30 <TheJulia> Okay!
15:38:37 <TheJulia> Speaking of next monday, I'll be on a metal tube to Brno
15:38:45 <TheJulia> dtantsur: can you run the meeting next week?
15:38:55 * TheJulia suspects dtantsur will be on a train
15:39:01 <TheJulia> a train train
15:39:10 <jungleboyj> :-)
15:39:13 * TheJulia giggles and thinks it is time to move on
15:39:14 <dtantsur> TheJulia: I'm afraid I cannot :)
15:39:19 <dtantsur> yes, train train
15:39:46 <TheJulia> Any other volunteers for next week? We can always cancel the meeting... or change our meeting format! #notsubtlehintstodiscussiontopic
15:40:08 <TheJulia> Moving on to RFE review...
15:40:12 <TheJulia> hogepodge: btw, thanks!
15:40:15 <TheJulia> #topic RFE review
15:41:10 <TheJulia> I posted one potential RFE last week for some very simple enhancements to ironic-inspector and ipa to enable updating introspection data after deployment which may be performed by an operator as part of their operational processes.
15:41:27 <TheJulia> #link https://storyboard.openstack.org/#!/story/2005853
15:41:52 <TheJulia> The idea is to keep it super simple and provide another entrypoint that can be used in case people want to do it manually.
15:42:21 * arne_wiebalck thinks the inspector (backend) is becoming a CMDB
15:42:26 <kaifeng> I saw this one, but not clear the use case
15:42:43 <kaifeng> a manual re-inspect?
15:42:46 <TheJulia> All the code is basically there, it is a conditional, a copy of ipa's main() with the API start removed
15:42:49 <TheJulia> kaifeng: basically yes
15:42:50 <dtantsur> my primary concern is creating/updating ports. this may have unpredictable effect on a running node
15:43:18 <rloo> is there a new API to do this?
15:43:26 <TheJulia> rloo: no
15:43:31 <kaifeng> indeed, the trick is inspector will update node
15:43:34 <TheJulia> dtantsur: don't the ports block deletes if there is still a vif?
15:44:20 <TheJulia> kaifeng: fwiw, the use case is non-openstack where we want to be able to spot hardware changes via introspection data.
15:44:34 <dtantsur> TheJulia: I think, yes. I guess we should include in in RFE
15:44:46 <dtantsur> TheJulia: I can imagine TripleO people interested as well
15:44:48 <TheJulia> dtantsur: I can double check the port code today most likely
15:44:52 <TheJulia> dtantsur: yeah
15:45:06 <dtantsur> It's probably useful for any managed infrastructure (as opposed to baremetal-as-a-service) case
15:45:24 <rloo> if someone looks at the introspection data, will they be able to distinguish whether it came from nodes that weren't introspected vs nodes that were? (dunno if that distinction is needed, just wondering)
15:45:47 <kaifeng> do we need to update node to be spotted or just hold in the introspection data backend?
15:46:40 <TheJulia> dtantsur: yeah, very.
15:46:58 <TheJulia> rloo: No, this is much more about gathering the data for other things to be able to use the data
15:47:09 <rloo> sorry to ask cuz it isn't clear to me. is this to update data of nodes that had been introspected before. OR update data of any nodes?
15:47:26 <TheJulia> kaifeng: that is good question.... I think just hold but it is worth pondering....
15:47:33 <kaifeng> rloo it appears the latter one
15:48:46 <TheJulia> The way inspector works, somewhat either because IPA always posts the data anyway. Ironic-inspector may do nothing with it today or it might add a newly discovered node.
15:49:31 <dtantsur> TheJulia: we may want to disable discovery in this mode. Warranting a new API flag?
15:49:50 <TheJulia> why would we want to?
15:49:57 <TheJulia> That is a separate piece of functionality
15:50:28 <TheJulia> maybe we might need to extend the BMC address match code in inspector at worst
15:50:37 <TheJulia> but that would just be a bug fix really
15:50:54 <dtantsur> imagine this feature is used from a node that is not enrolled
15:51:05 <dtantsur> we probably don't want it enrolled after that, do we?
15:51:15 <dtantsur> (think, your laptop where you're testing the application)
15:51:22 <TheJulia> hmmmm
15:51:49 <TheJulia> I feel like maybe this is a "yes i know this machine may be considered discovered" command line flag
15:52:40 <kaifeng> If it's a re-inspect I guess the node is enrolled in ironic already?
15:52:45 <TheJulia> yeah
15:53:12 <TheJulia> and if it is not known to ironic and someone runs the report-to-inspector command (to be named) then it is going to by design discover the machine if not already known to ironic
15:53:21 <dtantsur> right
15:53:29 <TheJulia> when discovery is enabled that is, and I can see reason for both, and even actually teh case of "I want to add this machine now"
15:53:31 <openstackgerrit> Merged openstack/ironic stable/rocky: Ansible module: fix configdrive partition creation step  https://review.opendev.org/664875
15:53:35 <openstackgerrit> Merged openstack/ironic master: redfish: handle missing Bios attribute  https://review.opendev.org/665100
15:53:45 <dtantsur> and the real case is probably running this command via cron, and pre-flashing it on the standard image
15:53:51 <TheJulia> "Hi, I'm done with this box. Let me give it to ironic and someone can reconcile the password later
15:53:59 <TheJulia> dtantsur: yeah
15:54:12 <TheJulia> and CMDB going "oh, wait! That changed!"
15:54:42 <TheJulia> "Oh, smart data about $device says bad things, trigger the alarm!"
15:55:19 <TheJulia> There doesn't really seem to be opposition, more that case handling of discovery and what if ports change
15:56:33 <TheJulia> I can double check the ports code. I feel like we just a safety switch on the footgun and we'll be good for the manual invocations.
15:56:33 <jroll> I agree with arne_wiebalck, so if we merge this, can we start calling inspector or ironic a cmdb?
15:56:41 <jroll> :)
15:56:53 <TheJulia> jroll: it only keeps the latest copy... so CMDB data source
15:57:18 * jroll makes a note to reference this in a year when we add audit logging :P
15:57:32 <TheJulia> lol
15:57:36 <arne_wiebalck> lol
15:57:41 <jroll> :D
15:57:49 <TheJulia> Okay, we have 3 minutes left. Lets go to Open Discussion and glance at ashtempl_'s patches
15:57:52 <TheJulia> #topic Open Discussion
15:58:02 <dtantsur> I hope we keep it as a data source for CMDB :)
15:58:08 <TheJulia> "user jroll deleted node 001"
15:58:16 <TheJulia> :)
15:58:50 <TheJulia> ashtempl_: just the two templest test additions?
15:59:03 <TheJulia> ashtempl_: I think there fine for us to add
15:59:08 <ashtempl_> ok
15:59:12 <ashtempl_> both of them?
15:59:23 <TheJulia> ashtempl_: yeah, if you wouldn't mind just adding them to the whiteboard
15:59:42 <TheJulia> Do we have anything else to discuss today?
15:59:47 <TheJulia> Are we taking over the world yet?
16:00:32 <trandles> I'll be testing standalone ironic as a way to provision a 1600 node HPC cluster in the next month. You might be taking over my world.
16:00:48 <TheJulia> trandles: ohhhhhh! Ahhhhh!
16:01:02 <TheJulia> trandles: good luck, and feel free to ask questions :)
16:01:29 <rpittau> trandles: that sounds fun :)
16:01:39 <trandles> Thanks, will do. I know there was a task from the Denver PTG to work on standalone documentation. Is there some place you can point me so I can contribute?
16:02:27 <rpittau> trandles: this can be a godo starting point: https://docs.openstack.org/ironic/latest/install/standalone.html
16:02:36 <rpittau> ^godo^good
16:03:11 <TheJulia> trandles: /doc/source/install/standalone.rst I believe in the ironic repository if you want to make changes or suggestions
16:03:11 <dtantsur> trandles: also something unfinished here https://review.opendev.org/#/c/641383/
16:03:12 <patchbot> patch 641383 - ironic - [WIP] Reference architecture: expand on networking - 2 patch sets
16:03:22 <mgoddard> trandles: we recently improved support for standalone ironic in kolla-ansible. You might find parts of bifrost useful with it also
16:03:31 <mgoddard> trandles: I did some experimenting here: https://github.com/markgoddard/bikolla
16:03:41 <trandles> mgoddard: thanks
16:04:25 <trandles> I was going to cherry pick ansible from bifrost and drop it into the large collection of stuff we already use.
16:04:40 <TheJulia> awesome
16:04:52 <TheJulia> trandles: patches are always welcome :)
16:05:01 <TheJulia> Anyway, we're over time. Thanks eveyrone
16:05:18 <TheJulia> #endmeeting