15:00:06 #startmeeting ironic 15:00:06 Meeting started Mon Jul 13 15:00:06 2020 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:09 The meeting name has been set to 'ironic' 15:00:09 o/ 15:00:12 #chair dtantsur 15:00:12 o/ 15:00:12 Current chairs: TheJulia dtantsur 15:00:16 \o 15:00:16 o/ 15:00:21 oh, the meeting. yayyy \o/ 15:00:27 o/ 15:00:36 and they walked up 15:00:48 #link https://wiki.openstack.org/wiki/Meetings/Ironic is our agenda 15:01:02 o/ 15:01:16 #topic Announcements / Reminder 15:01:24 o/ 15:01:31 dtantsur, we are ironic and ironic is us 15:01:34 #info The main news: we have done our first batch of releases according to the new model 15:01:47 o/ 15:01:59 The bugfix/X.Y branches have been created, but the devstack jobs need some care on them 15:02:08 (bifrost seems to work normally, good job bifrost!) 15:02:22 we probably need to pin on the zuul config... 15:02:43 for the jobs we have the bugfix branches 15:03:02 set some overrides, I guess 15:03:11 \o 15:03:19 #link https://www.eventbrite.com/e/opendev-hardware-automation-registration-104569991660 OpenDev: Hardware Automation 15:03:19 dtantsur, exactly 15:03:36 this ^^ event is coming up next week. I'm not sure if there is a schedule already. 15:03:45 ah 15:03:50 #link https://www.openstack.org/events/opendev-2020/opendev-schedule-2 The schedule 15:04:30 who's arranging/presenting this? dtantsur 15:04:54 uzumaki: this is a Foundation event, it's not really about presentations, more about discussions 15:05:16 uzumaki: it is more like a forum discussion 15:05:19 so not one person talking, but rather one moderator, a few experts and a bunch of random people who care 15:05:22 oh! I see, must be cool, I might attend this one! 15:05:36 uzumaki: I highly recommend, if it plays nicely with your timezone 15:05:45 bunch of random people who care? THAT'S ME! 15:05:45 so some central topics/questions and the hope is discussion results 15:05:47 Sounds interesting. Has it been in the works for a while? 15:06:09 rpioso: it has, yes. we've already had one such opendev event centered around large-scale deployments 15:06:30 TheJulia: you back and with stashes full of yummies? 15:07:11 dtantsur: putting stuff away now 15:07:20 anything else to announce or remind us of? (except for staying safe, washing hands and wearing masks?) 15:07:53 Just for everyone to please take a little time to review this week. If we need to do ad-hoc review jams, I'm happy to host 15:08:24 did someone say jams? 15:08:32 :D 15:08:50 it's a good idea, actually 15:08:58 sounds good to me 15:08:58 as long as there's jam 15:09:17 let's get back to it in open discussions 15:09:20 #topic Review subteam status reports (capped at ten minutes) 15:09:35 #link https://etherpad.opendev.org/p/IronicWhiteBoard starting around like 299 15:09:53 Thanks everyone who participated in the bug triaging, great progress! 15:10:16 I think as the next step we should clean up the RFE list a bit. Maybe propose some of RFE Review on the upcoming meetings. 15:12:09 okay all done with putting things away 15:12:16 248? that's a lot of RFEs :O 15:12:18 dtantsur: ++ 15:12:28 * dtantsur throws TheJulia the remote control 15:12:32 Heh 15:12:47 uzumaki: exactly, there is no way we're going to finish all of them. and we probably shouldn't. 15:12:54 We don't retire RFEs really because they are all valid ideas, but often we get 2-3 of them per major thing 15:12:57 it's just too much =O 15:13:03 or things get resolved as bug fixes and we don't realize it 15:13:09 happens ^^^ 15:13:18 I've closed a bunch of duplicate RFEs already 15:13:35 Yup, anyway! 15:13:38 can I help? 15:14:12 uzumaki: it may be a bit non-trivial without a lot of context. starting with bug triaging may be easier. 15:14:30 okay! 15:14:32 uzumaki: we've got some words written about it: https://docs.openstack.org/ironic/latest/contributor/bugs.html#triaging-guide 15:14:37 tell me where to shoot 15:14:47 got it 15:14:55 uzumaki: but! if you want to ask questions in channel as related to RFEs, we may be able to provide additional context if you don't know off the top of your head. The thing is, it will go slow that way 15:15:14 iurygregory: hey, is ngs + zuulv3 + grenade still problematic? 15:15:23 TheJulia, totally =( 15:15:39 I think people are afraid of grenade hehe XD 15:16:00 iurygregory: should we just establish a time for a few people to jump on a call and try to work through it 15:16:09 and yes, grenade has been the source of great sorrow 15:16:12 TheJulia, I realize that, that's why I was hesitant in asking.. I'll start with bug triage for a few days, let's see where that takes me 15:16:21 TheJulia, sounds good, I can put up a doodle and send on openstack-discuss? 15:16:22 uzumaki: awesome :) 15:16:36 TheJulia, grenades are known to be that way "sources of pain" 15:16:44 heh 15:16:46 indeed 15:16:50 not untrue 15:17:09 arne_wiebalck: re scale is the only thing your aware of just memory consumption right now on the conductors? 15:17:32 TheJulia: yes 15:17:36 I guess standalone auth for bifrost is "Coming Soon" 15:17:45 arne_wiebalck: mind if I update the item to note that? 15:17:57 TheJulia: ofc not :) 15:18:54 * uzumaki wonders why dtantsur always uses the fancy double negatives to make a point xD 15:19:14 uzumaki: double negations are normal in Russian, using them in English adds some spice 15:19:35 dtantsur, if from spice you mean getting people to read it twice, yes, it does the trick 15:19:45 I mean precisely that, yes :) 15:19:54 xD 15:20:12 * iurygregory also uses double negatives =X 15:20:30 * TheJulia unfortunately is not in the habit of double negatives 15:20:35 Ramdisk TLS unchanged? 15:21:11 iurygregory: could you add links to the update as you propose the changes to simplify and reduce job load? 15:21:18 * uzumaki remembers the Martin Luther speech when he says "I'm not unmindful.." that's a really spicy double negative 15:21:44 Any update on compatability profiles? 15:21:47 TheJulia, sure 15:21:58 TheJulia: ramdisk TLS unchanged 15:22:18 got distracted with the power off + agent token issue 15:23:02 I saw that was still a WIP which is why I didn't add that to the items to review this week 15:23:52 I guess I'm good to proceed, just curious if there is an update for redfish compatability profiles since the current update is undated. 15:23:57 arne_wiebalck, rpioso ^^^ 15:23:58 I hope to finish it today-tomorrow 15:24:03 dtantsur: ack 15:24:17 TheJulia, added to the weekly priorities 15:24:31 iurygregory: beyond what is already proposed? 15:24:50 Are we good to proceed for priorities for the week? 15:24:54 TheJulia: re redfish, no, I did not get round to work on this yet 15:25:35 I added to both status and the WP 15:26:28 onward to priorities! 15:26:34 #topic Deciding on priorities for the coming week 15:27:08 #link https://etherpad.opendev.org/p/IronicWhiteBoard 15:27:11 Starting at line 129 15:27:17 arne_wiebalck, TheJulia: We're continuing to work on the Redfish Interoperability profile for sushy. Reviewed the progress with the team late last week. Initially focusing on the ServiceRoot and ComputerSystem resources. Once those are satisfactory-ish, we would like to demo. ETA ~1 week. 15:27:19 * TheJulia removes merged items 15:27:51 * rpioso will update the white board to reflect ^^^ 15:27:58 rpioso: thanks 15:28:04 TheJulia: :-) 15:29:16 So I have a huge list of proposed items stariting at line 197 15:29:23 any questions/concerns/items missing? 15:30:40 so many CI failures X( 15:30:56 TheJulia: For the RAM patch, did you manage to test this with a real node? 15:31:33 TheJulia: The code looks good to, I would just like to see what happens IRL :) 15:33:16 arne_wiebalck: I haven't had time to 15:33:51 I'm fairly sure on the result that I've noted being the case though, but yeah, would be good to get it loaded up and run the machine out of ram 15:35:01 Is everyone good with the list? 15:35:13 I'm 15:35:16 * TheJulia starts brewing coffee for everyone 15:35:38 the list looks good to me 15:36:29 a lot of stuff is just CI failures or are almost there, so a recheck or quick review may be all that is needed on some of the patches 15:36:42 Anyway! Shall we move on? 15:37:01 ++ 15:37:04 We don't seem to have any discussion topics, so I guess we would jump directly to the Baremetal SIG 15:37:09 #topic Baremetal SIG 15:37:23 arne_wiebalck: Anything to discuss or to let people know about? 15:37:50 TheJulia: no 15:37:54 okay then! 15:38:00 Onward to RFE Review! 15:38:10 #topic RFE Review 15:38:29 dtantsur wanted us to quickly revisit his RFE from our last meeting 15:38:36 #link https://storyboard.openstack.org/#!/story/1618014 15:38:47 I've updated it with a somewhat nicer format and more words 15:39:28 Sounds good to me 15:39:43 Well, reads is more appropriate 15:39:56 Does anyone have any questions regarding this item? 15:40:50 * TheJulia gets out the automated crickets 15:41:08 none on my side 15:42:17 dtantsur: I think lazy consensus grants you rfe-approved 15:42:22 \o/ 15:42:27 Aija Jaunteva proposed openstack/ironic-specs master: [RFE] Operationally efficient and fast-track bare metal hardware provisioning https://review.opendev.org/740721 15:42:46 btw, this work item is not too complex, so if anybody wants to take it to practice - be my guest 15:42:53 dtantsur: feel free to add rfe-approved to the item 15:42:55 seems like it'd be better to have one or two people indicating that they approve. can i suggest julia and iurygregory? 15:43:24 I will add 15:43:34 thx iurygregory! 15:43:47 iurygregory: thanks 15:43:54 Well then, onward to open discussion! 15:44:07 #topic Open Discussion 15:44:32 Does anyone have anything to bring up/discuss? 15:44:35 yay it worked \o/ 15:44:44 wrt the steps override, could we have this on the driver fields? 15:45:34 configuration options not always handy 15:46:12 kaifeng: I feel like that is likely a logical next step 15:46:13 TheJulia: We have updated the RFE https://storyboard.openstack.org/#!/story/2003594. 15:46:43 I see. 15:46:52 TheJulia: A spec has been posted for review: https://review.opendev.org/#/c/740721/ 15:46:53 patch 740721 - ironic-specs - [RFE] Operationally efficient and fast-track bare ... - 1 patch set 15:48:12 rpioso: We saw, that I think is going to require some time to digest since it seems to be mixing terms from other areas under a generic umbrella, so we may need to wrap our heads around what is each specific area it touches upon 15:48:50 yep, the very first request: formulate everything in driver-specific terms 15:49:00 I initially assumed you were about to rewrite half of ironic :) 15:49:03 TheJulia: I think you'll find it doesn't touch much and is optional :-) 15:49:39 TheJulia: LOL. We don't have that much ambition ;-) 15:49:45 rpioso: I mean in terms of word selection to describe the feature. I had the same reaction as dtantsur and that is going to take some time to grok 15:50:15 I think the old feature name was rather succinct, personally 15:51:02 I feel like we should add the spec to the list of items to review 15:51:05 Any objections? 15:51:27 TheJulia: We feel it was too vendor specific. The change makes it available to other drivers and addresses a couple of operator pain points. 15:52:20 rpioso: It would be good for more vendors to have similar behavior. Anyway, as I noted, it is going to take a little time to digest 15:53:13 TheJulia: And they will be able to if they'd like. It's generic. Implementation of the low-level interactions are vendor-specific. 15:53:24 rpioso: indeed 15:54:56 TheJulia: We've focused on the parts that we believe are of most general interest. Few words are spent on iDRAC-specific stuffs. We're trying to be considerate of the reviewers' time. 15:55:38 rpioso: I'm a little worried that it will have the reverse effect. Anyway, since I didn't have any objections I'll add it to the list 15:56:03 Anyone else have anything to bring up before we wrap up the meeting? 15:56:05 TheJulia: Thank you so much! 15:57:44 * TheJulia hears the autocricket 4000 make cricketing sounds 15:58:13 CRICKKKKKKet 15:58:19 Thanks everyone! 15:58:21 rloo: ++ 15:58:33 :D 15:58:43 #endmeeting