15:00:24 #startmeeting ironic 15:00:25 Meeting started Mon Oct 14 15:00:24 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 o/ 15:00:26 o/ 15:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:28 The meeting name has been set to 'ironic' 15:00:29 Ilya Etingof proposed openstack/ironic master: Add `get_node_network_data` to non-Neutron NetworkInterface https://review.opendev.org/688266 15:00:30 \o 15:00:32 etingof: all the rebases :) 15:00:33 o/ 15:00:37 o/ 15:00:38 o/ 15:00:45 Ilya Etingof proposed openstack/ironic master: Make redfish boot interface using network interface metadata https://review.opendev.org/688272 15:00:45 Good morning everyone 15:00:45 o/ 15:00:57 \o 15:01:09 o/ 15:01:14 Our agenda for this meeting is on the wiki. 15:01:16 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:01:28 #topic Announcements / Reminders 15:02:10 o/ 15:02:11 #info PTL will be in Shanghai for the Summit in early November. 15:02:19 #info Summit is in 3 weeks! \o/ 15:02:22 \o 15:02:38 Rachit Kapadia proposed openstack/ironic master: DRAC: Drives conversion from JBOD to RAID https://review.opendev.org/679093 15:02:46 Does anyone have anything else that they wish to announce or remind us of? 15:03:30 I guess that is a no... 15:03:38 Moving on then! 15:03:42 #topic Review action items from previous meeting 15:04:16 o/ 15:04:20 mkrai let me know she was unable to double check the deprecation docs this past week, that it is on her list for this next week. 15:04:33 iurygregory: Any update on 3.8 unit testing? 15:04:40 TheJulia, yes =) 15:04:50 I've summarized the status in https://etherpad.openstack.org/p/ironic_integration_jobs 15:04:52 rpittau: and similarlly 37 and 38 compatability issues 15:05:11 we are in a good shape for all jobs, but ironic-standalone has some problems for the BaremetalIpmiAnsibleWholedisk that is reaching timeout for the ping 15:05:21 TheJulia: I didn't see any other issues on that except what's reported in https://etherpad.openstack.org/p/Python_3.8_Deprecation_Hunt 15:06:00 iurygregory: interesting, sounds like maybe an ansible compatability issue? 15:06:16 rpittau: awesome, thanks 15:06:32 TheJulia, yeah, not much expert in ansible, I'm trying to debug this =) 15:07:44 iurygregory: okay, well if you see anything that has your wondering, please raise visibility in IRC :) 15:07:58 TheJulia, ack 15:08:02 Awesome, well carrying on then! 15:08:21 #topic Review subteam status reports 15:08:29 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:08:38 Line 236 15:10:28 * TheJulia removes hodgepodge from the etherpad :( 15:11:02 regarding faster deployment stuffs, has anyone looked at hacking in support for kexec? 15:11:15 crazy off the wall question, but it has been on my mind 15:12:20 * iurygregory nope 15:12:26 It looks like there is nothing really new to cover 15:12:53 Ilya Etingof proposed openstack/python-ironicclient master: Add `network_data` port/portgroup attribute support https://review.opendev.org/688299 15:18:32 And I got mentally derailed 15:18:34 sorry folks 15:18:39 np 15:18:47 Priorities for the coming week! 15:18:54 #topic Priorities for the coming week 15:19:08 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:19:11 Line 156 15:19:40 I saw two backports were proposed, which seems to make sense to add the backport list 15:21:13 Adding an ironic-tempest-plugin change to the list 15:22:02 etingof: how do you feel about virtual media patches? 15:23:00 TheJulia, would be good to review some, e.g. -- https://review.opendev.org/687250 15:23:01 patch 687250 - ironic - Burn configdrive into virtual media boot ISO - 5 patch sets 15:24:35 we have a chain of 7 ironic patches implementing dhcpless boot 15:24:45 over virtual media 15:24:50 Okay, I added the patches up to the patch you linked 15:24:54 etingof: \o/ 15:24:57 including pxe_append_params use 15:25:52 awesome! pxe_append_params is just a virtual sugar, it's not really required for dhcpless boot as it stand now 15:25:54 I think the list looks good 15:26:05 etingof: it is, but it is in your patch series and it makes sense :) 15:26:17 maybe one day we rename that var 15:26:51 I've removed the old items from that list, Are we good to proceed? 15:26:54 TheJulia: Is a new sushy release for Train on the list? 15:27:11 rpioso: do you need one of us to propose a 1.9.1? 15:27:37 TheJulia: Yes, please. 15:27:51 okay, if you have the link for the patch, please send it over 15:28:02 #action TheJulia will try to get a sushy 1.9.1 out this week 15:28:12 So moving on to Discussion! 15:28:16 #Discussion 15:28:22 #topic Discussion 15:28:23 TheJulia: If memory serves, last Thursday we agreed to create a new sushy release off of an existing patch. 15:28:36 rpioso: k 15:28:52 TheJulia: It would greatly benefit from etingof's input. 15:29:21 One topic for quick discussion: I was looking at the release notes and found things kind of jumbled for vendors and wondering if we should create specific bunched release notes for hardware types? 15:29:51 maybe create a single file and we keep appending to that during the cycle? 15:30:39 TheJulia: is there any ordering to the notes? 15:30:46 could we prefix? 15:30:55 TheJulia: I think this would be handy. 15:30:57 mgoddard: none really, and that is kind of what I'm wondering, how to keep it logically together 15:31:19 I mean in terms of what reno generates based on filenames 15:31:34 the easy way to keep together would be using one file per hardware type maybe 15:31:35 i.e. if you add 99_dell_fancy_feature_3543523.yml 15:31:37 It is worth asking... 15:32:06 I can try to remember and ask this week and hopefully we can do something to keep it a little more sane this cycle 15:32:32 for the main benefit of reno IMO is separating the notes to avoid collisions 15:32:32 TheJulia: Perhaps a PVG topic? 15:33:00 (it's also the main drawback from the perspective of someone tidying notes at the end of the cycle) 15:33:05 #action TheJulia to ask reno authors for providing ordered clarity in overall notes. 15:33:18 Good to proceed to RFE Review? 15:34:17 * TheJulia hears crickets 15:34:22 #topic RFE Review 15:34:23 TheJulia: What about the Baremetal SIG? 15:34:33 TheJulia: Who's now leading it? 15:34:58 rpioso: arne_wiebalck and I are still trying to sort that out 15:35:13 arne_wiebalck, TheJulia: Thank you! 15:35:18 #link https://storyboard.openstack.org/#!/story/2003594 15:35:32 That's mine :-) 15:36:21 The idea of that RFE is to support rapid provisioning of baremetal. 15:37:10 rpioso: is the export intended to be manual? 15:37:24 Port PXE boot enable, BIOS settings, RAID, etc. could be declaratively specified and applied via a clean/deploy step. 15:37:55 TheJulia: Any reason why it couldn't be auto, too? 15:38:18 TheJulia: Couldn't some code in the automatic workflow process it? 15:39:39 rpioso: well, my concern would be if automated export was a thing, having to tool through the path to retrieve that when your working on another machine that you want deployed 15:39:51 granted, maybe one day we'll have snapshot capabilities :) 15:40:33 So fundimentally it is more concerns over lower level interactions, I guess we need more information of the workflow and mechanisms (like flow diagrams) 15:41:18 TheJulia: If the export output were stored in Swift or some other datastore, it could be used by subsequent processing. 15:41:29 absolutely 15:42:01 TheJulia: That data would provide info on what's possible and what already exists. 15:42:29 TheJulia: In terms of hardware, BIOS settings, RAID volumes, etc. 15:42:34 Indeed, and that could be saved from a clean step? 15:42:58 TheJulia: Right. Deploy step could save it, too. 15:43:16 But only for the machine it is working upon 15:43:39 TheJulia: It's specific to the machine being operated on. 15:43:49 As in the one in task.node, no other machine 15:44:00 TheJulia: Yep 15:44:51 TheJulia: Of course, installed hardware components, BIOS config, RAID volumes, and the like are specific to a node. 15:46:38 Okay, I really think some more mechanics information is needed since it is really a whole suite of things 15:46:50 so borderline spec to be honest 15:47:07 But since it is inside your driver's interfaces, rfe I guess is fine 15:48:26 TheJulia: We'd prefer an RFE. I could add more detail to the story, if that would help. 15:48:34 That would help 15:49:37 TheJulia: Could it be tagged rfe-approved, as-is, with a comment asking for more details? 15:50:26 Other cores, what do you think? 15:51:12 I wouldn't tag it approved without all of the information 15:51:20 I'm a little hesitant to mark it approved without some additional details first. I think I understand based on this discussion, but the source of truth for that work is the story without any sort of spec document 15:51:22 I'm all for a detailed RFE 15:51:32 I concur, thanks jroll, rpioso 15:51:37 err, rpioso 15:51:38 gah 15:51:40 rpittau: 15:51:42 that yeah :D 15:51:46 tab autocomplete fail 15:51:56 Anyway! Moving on to Open Discussion 15:51:59 #topic Open Discussion 15:52:06 Do we have anything else to discuss this week? 15:52:17 Thank you for your consideration :) 15:53:39 TheJulia: Would there be any way to include https://review.opendev.org/672498 in a Train release? 15:53:39 patch 672498 - ironic - Add Redfish vmedia boot interface to idrac HW type (MERGED) - 24 patch sets 15:53:40 * TheJulia senses the open discussion crickets 15:53:52 TheJulia: team photo 15:53:53 rpioso: There is not any way 15:54:06 rpittau: best we can do is do a early U cycle release 15:54:11 rpittau: oh yes! 15:54:30 * rpioso considers changing his name ;-) 15:54:48 I could use my alt nickname :D 15:55:03 rpittau: lol 15:55:28 rpittau: set for 11:20-11:30 AM which gives us a quick break before lunch at 12:30 15:55:39 on Thursday 15:55:48 TheJulia: sounds good to me 15:56:19 I guess wear something... ironic :) 15:56:53 so for who's coming to Shanghai, there will be a team photo, keep a 10 minutes slot free for Thursday at 11:20 :) 15:57:08 Do we have baremetal shirts? 15:57:30 * rpittau might consider using a full knight armor 15:57:33 arne_wiebalck: no, but... hmm 15:57:39 rpittau, ++ 15:58:11 arne_wiebalck: Let me see if I can get in touch with the original artist and post soemthing that we can order. Doing distributed that way so nobody runs into any issues with trying to import a quantity of t-shirts 15:58:39 TheJulia: Sounds great! 15:59:22 jroll: JayF: Do you guys remember if it was a racker that did the "how ironic really works" artwork? 16:00:36 Also, topics wise, the etherpad is still open for thoughts/ideas: https://etherpad.openstack.org/p/PVG-Ironic-Planning 16:01:00 I _suspect_ we're going to go through things kind of free form 16:01:02 TheJulia: yeah, it was an intern 16:01:51 dtantsur|brb: do you have the image you had printed on the last round of t-shirts? 16:02:23 #endmeeting