15:00:49 #startmeeting ironic 15:00:49 Meeting started Mon Jun 14 15:00:49 2021 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:49 The meeting name has been set to 'ironic' 15:00:50 o/ 15:00:52 o/ 15:00:57 o/ 15:00:57 o/ 15:01:03 \o 15:01:08 o/ 15:01:17 Greetings everyone, and welcome to our weekly meeting! 15:01:27 o/ 15:01:32 Our agenda can be found on the wiki 15:01:34 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:02:16 #topic Announcements / Reminders 15:02:38 I don't believe we have anything to announce or remind ourselves of this week. Does anyone have anything to raise this week? 15:03:20 * TheJulia hears the crickets appear and gives it a few more moments 15:03:53 Looks like we have no action items from last week 15:04:13 I guess we can proceed to subteam status reports then 15:04:55 yep 15:05:00 #topic Review subteam status reports 15:05:05 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:06:52 arne_wiebalck: By chance have you discussed node error history with kaifeng or are we basically at no update this week? 15:07:03 sorry, no update 15:07:22 I will try to pick this up 15:07:26 ack 15:07:37 iurygregory_, rpittau: any update on privsep? 15:07:52 I'll note it's not technically a subteam, but zer0c00l put up a PR for Anaconda driver docs. I added a couple of folks as reviewers and marked it as a review prio. 15:07:52 * TheJulia senses iurygregory_ is out today 15:08:05 no updates 15:08:11 JayF: line 75 :) 15:08:23 not sure we want to have the discussion today since iury's not here 15:08:27 * JayF is multitasking in a downstream meeting and may not have checked the whiteboard 15:08:30 rpittau: ack 15:08:34 JayF: ack 15:08:38 yeah, I think Iury took a day off 15:08:57 TL;DR I was concerned about launching a subprocess in IPA 15:09:06 given the "fun" around eventlet 15:09:19 but yeah, we can wait for him to come back (although I won't be here next Monday.. so ironic) 15:09:40 dtantsur: ack, okay 15:09:47 hmm 15:10:58 Well, Onward to priorities for the coming week? 15:11:19 yep 15:11:35 #topic Deciding on priorites for the coming week 15:11:37 #link https://review.opendev.org/q/hashtag:ironic-week-prio+status:open 15:12:04 I have two driver_info clean-ups to add: https://review.opendev.org/c/openstack/ironic/+/796287 https://review.opendev.org/c/openstack/ironic/+/796289 cc stendulker 15:12:06 I went through about an hour ago and I didn't see much that could be added to the list at present. Does anyone have anything they would like to see on the list? 15:12:23 dtantsur: Will have a look 15:12:33 thanks! I'm asking you because they touch iLO 15:12:48 dtantsur: np. Thank you 15:13:01 any objections to adding these 2 patches? 15:13:13 none, they have been added 15:13:19 Does anyone have anything else this week? 15:13:20 cool thx 15:13:22 TheJulia: I guess your -1 on https://review.opendev.org/c/openstack/ironic/+/768009 can be removed, no? This may prevent further reviews. 15:13:56 arne_wiebalck: likely needs to be rebased, fwiw 15:13:56 can I add baremetal-operator PRs? :D (jk) 15:14:07 lol 15:14:12 oh my 15:14:25 so onward to the baremetal sig? 15:14:32 ++ 15:14:47 let's 15:15:08 #topic Baremetal SIG 15:15:17 dtantsur's presentation on the IPAB is uploaded to the usual youtube channel 15:15:24 Awesome! 15:15:30 #link https://www.youtube.com/watch?v=1L1Ld7skgDw IPA-builder introduction 15:15:33 thanks again, dtantsur ! 15:15:35 has a blog entry been posted to ironicbaremetal.org ? 15:15:37 nice 15:15:41 I haven't posted anything 15:16:09 TheJulia: should we make this the routine for new presentations? 15:16:16 Okay, If I get a few minutes I'll try to do that 15:16:22 ty 15:16:33 I don't think there is anything else for the SIG. 15:16:57 arne_wiebalck: I think it would be good, but we need to make it a community habit to update the blog with $new stuff that is not just the videos from the SIG 15:17:14 TheJulia: ++ 15:17:15 Well, in that case, time for Open Discussion 15:17:18 #topic Open Discussion 15:17:24 arne_wiebalck: looks like you had a topic :) 15:17:48 yes, it is about network burn-in 15:17:59 cpu, mem, disk are merged 15:18:13 network is slightly more complicated as we need two nodes 15:18:24 at CERN, we use dynamic pairing for this 15:18:30 Interesting 15:18:42 initially with a message queue, atm with a shared file 15:18:55 for upstream I was thinking to use tooz/zookeeper 15:19:00 for the match making 15:19:12 I know, for a while I had a semi-dedicated iperf target for such things, But pairing can make sense from a "can two nodes talk really fast to each other" 15:19:20 the first iteration may use static pairs in driver_info 15:19:40 just wanted to check if the overall plan sounds ok 15:19:55 why not use another fixed server? 15:20:10 you mean like the controller? 15:20:16 bandwidth mostly 15:20:29 imagine 100 servers trying to connect 15:20:33 you also want to check cross-node bandwidth between the racks potentially 15:20:36 oh, and yeah 15:20:44 if your doing 100 at a time your going to have saturation issues 15:20:53 dtantsur: it is an option which the static approach would cover as well 15:21:18 I think the idea makes sense and the approach of simple static and then evolve it makes sense as long as we don't explicitly add requirements for new services as a hard operating requirement 15:21:26 dtantsur: but it is not only connectivity, but also if we can go full steam 15:21:57 TheJulia: this is why I thought tooz as we (can) use this already 15:22:19 It's going to be tough to get creds for something like that down into the agent, isn't it? 15:22:23 TheJulia: for leader election in inspector, for instance 15:22:37 Last time I used iperf, it had no concept of credentials 15:22:47 I'm saying if tooz is going to be used 15:22:53 ahh 15:23:02 there's not any cleaning steps, afaik, which coordinate between ironic and ipa for the step 15:23:05 well, it could be determied conductor side and fed to the agent 15:23:15 so if you're locking for access to the network server, you're going to need creds to do that locking in IPA 15:23:26 or come up with a new method for IPA clean steps to coordinate with conductor 15:23:38 which is probably a lot more complexity than desired for this problem? 15:23:43 I don't think tooz is necessarilly for locking 15:23:53 at least, that is not my perception, at least directly 15:23:59 Heh. Clean steps [lock network server] [ network burn in ] [unlock network server] 15:24:00 but getting creds in, is indeed a problem 15:24:00 TheJulia: it can be, I think 15:24:04 and then communication flows 15:24:06 where 2 of them are in the conductor and one is in IPA 15:24:13 and you'd only need to ensure the priorities lined up 15:24:19 * JayF not sure he loves that but it would likely work 15:24:30 it seems like you're enabling someone with IPA access to lock IPA on another server? 15:24:42 (not sure if it's a concern or not) 15:25:02 Lets take this path, simple start, see where that leaves us, and then iterate from there? 15:25:06 I'm concerned about this feature in general which is why I'm trying to hash it out :) see if it's less complex than I thought itw as at first glance 15:25:10 sounds good to 15:25:12 me 15:25:12 so static operator supplied info, and then see if we can do automagic 15:25:17 static works as well 15:25:31 it is just not so nice if you have broken servers 15:25:42 ok, thanks everyone! 15:26:01 Does anyone else have anything for Open Discussion? 15:27:21 not me 15:27:49 Id just like to remind everybody about our work on the security interface spec: https://review.opendev.org/c/openstack/ironic-specs/+/576718/27/specs/approved/security-interface.rst 15:27:55 In that case, the last step of our meeting is next 15:28:27 lmcgann: perhaps a few words to express why it is important to those in attendance of today's meeting? 15:31:09 I know I'm kind of putting you on the spot, but it helps people relate and understand why 15:32:41 Anyway, I guess we can proceed with our agenda 15:32:47 #topic Who is going to run the next meeting? 15:32:56 Any volunteers ? 15:33:02 I cannot - will be out for a language exam (doh) 15:33:10 eek 15:33:17 German ... should be fun! 15:33:18 should we switch IRC to German for the week? 15:33:34 Granted, it will mostly be machine translated for many of us 15:33:39 only for dtantsur maybe 15:33:44 hehe 15:34:14 Well, I can do it next week, I guess 15:34:16 I think I can run the next meeting 15:34:28 rpittau: you sure? 15:34:31 sorry for the delay TheJulia, Im trying to think of a good way to describe the spec 15:34:33 yeah :) 15:34:34 dtantsur: Wie werde ich all diese Server bereitstellen? 15:34:46 :D 15:34:49 but it will be in Italian :P 15:35:03 molto bene! 15:35:07 lol 15:35:12 lmcgann: simplest phrases or expressions generally help, or even the desired end result 15:35:37 rpittau: in Italian, ugh. 15:35:50 Good Morning Ironic Folks, Happy Monday! 15:35:56 * TheJulia should actually like... learn some about Italian explicitly given Latin experience 15:36:35 I will use morse alphabet. using the word "pizza" or absence of it. 15:36:37 rpittau: Okay, I guess your running the meeting next week if nothing comes up 15:36:48 cool :) 15:37:07 dtantsur: that's a way :D 15:37:23 dtantsur: so do we convey everything with pizzapizza or pizza and translate that to dots and dashed and then that to words?! 15:37:35 dtantsur: or Norse alphabet? 15:38:01 for Norse alphabet we may need hjensas to run the meeting 15:38:11 dtantsur: this is true... 15:38:26 Anyway, Thanks everyone, have a wonderful week! 15:38:54 Thanks TheJulia ! 15:38:59 thanks! 15:39:04 #endmeeting