Monday, 2023-08-07

rpittaugood morning ironic! o/06:58
kubajjGood morning Ironic 08:26
opendevreviewAdam Rozman proposed openstack/ironic master: implement basic-auth support for user image download process  https://review.opendev.org/c/openstack/ironic/+/89041110:15
iurygregorygood morning Ironic11:17
adam-metal3Hi Ironic, just a kind advertisement I have pushed basic auth support related changes, if you are interested please take a look: https://review.opendev.org/c/openstack/ironic/+/890411 , https://review.opendev.org/c/openstack/ironic-python-agent/+/890272 and thanks for the comments JayF12:13
* dtantsur puts on his queue12:22
* iurygregory tags both patches with the hashtag12:22
rpittauthanks adam-metal3 have them in my queue :)12:27
kubajjdtantsur: hi, do I understand this https://specs.openstack.org/openstack/ironic-specs/priorities/2023-2-workitems.html#improving-deploy-kernel-ramdisk-config correctly, that we would like to have something like a flag in the config - let's say arch_separate - that would signal ironic that instead of ironic/ironic/conf/agent.py the ironic/ironic/conf/agent_arm.py parameters would be used for ARM?12:36
dtantsurkubajj: I personally didn't envision it to go so far as to duplicate all options12:41
dtantsurkubajj: we have prior art that looks like this https://opendev.org/openstack/ironic/src/branch/master/ironic/conf/pxe.py#L74-L8012:42
dtantsurI thought we just introduce deploy_kernel_by_arch and deploy_ramdisk_by_arch (and bootloader_by_arch?)12:42
dtantsuractually, having overrides in something like [pxe:aarch64] would be cool, but I'm not sure it can be expressed in oslo.config12:42
kubajjdtantsur: oh, so we want just those config parameters that would say: we are using our own custom ramdisk for arm12:45
dtantsurkubajj: yeah. Currently you can set deploy ramdisks globally or per node. The former does not really work for the multi-arch case, the latter is annoying.12:48
kubajjdtantsur: ok, thanks12:48
TheJuliagood morning13:51
iurygregorygood morning TheJulia 14:58
JayFGood morning, meeting time :)14:59
iurygregoryo/15:00
masgharo/15:00
kubajjo/15:00
* iurygregory was too fast15:00
rpittauo/15:01
* TheJulia wonders if the meeting needs coffee15:01
iurygregoryJayF, are you going to start? :D15:01
rpittau\o/15:01
JayF#startmeeting ironic15:01
opendevmeetMeeting started Mon Aug  7 15:01:24 2023 UTC and is due to finish in 60 minutes.  The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'ironic'15:01
rpittauo/15:01
TheJuliao/15:01
JayFTheJulia: I was actually starting a pot :)15:01
iurygregoryo/15:01
kubajjo/15:01
masgharo/15:01
rpittauthat was fun :)15:01
TheJuliaJayF: hopefully enough to share with the channel! :)15:01
JayFI'm more thinking lets all be on top of it15:01
JayFso when it's done I can have a cup without rushing away ;) 15:02
JayF#topic Announcements/Reminder15:02
JayFStanding reminder: tag your patches #ironic-week-prio, review things using the priority dashboard15:02
JayFbonus add for today: the reverse is true; if your patch is no longer ready for review, just drop the tag until it is again15:02
JayFso that our dashboard is a clean way to know what things need attn15:02
JayFNext event on our schedule in the agenda is the Bobcat Non-client library freeze coming up 8/2415:03
JayFplease ensure your sushy changes and other library code is landed well before then for Bobcat release15:03
JayFMoving on 15:03
JayFThere were no action items last meeting; skipping agenda item.15:03
JayF#topic Review Ironic CI Status15:03
JayFSo I know rpittau had an item here; bifrost is broken by centos stream, it seems?15:04
rpittauyep15:04
rpittauthe BZ to fix that is ON_QA hence the question15:04
JayFI don't know what that means15:04
rpittauthe package is ready, just need to be approved15:04
rpittauand it will be published15:04
rpittauonce it's published there's no need for the workaround15:05
JayFThis only impacts bifrost CI, yeah?15:05
rpittaucorrect15:05
JayFMy $.02 is to keep the workaround in your pocket, but AFAICT we don't have much pressing bifrost stuff15:05
JayFso I'd lean slightly towards waiting for the fix15:05
JayFbut that's a mild preference15:05
TheJuliaIs it blocking the ironic gate at all, or has this apparent workaround kept us moving forward?15:06
rpittauthe workaround is on hold15:06
JayFTheJulia: I think we only test CentOS Stream in Bifrost gate; that's what I was trying to ask earlier15:06
rpittauTheJulia: bifrost ci is broken up to zed at the moment15:06
rpittauthe other projects look good so far15:06
rpittauit's because we only have cs9 nodes in bifrost15:07
JayFI'15:07
JayF**I'll note that I think the virt side of the stack had to land a similar workaround15:07
JayFat a devstack level15:07
TheJulialooks like all the bifrost jobs on the ironic gate are non-voting, 2 of 3 work15:07
rpittauwell yeah, technically the issue is on devstack15:07
TheJuliaregardless, seems like we're good to move on then?15:08
rpittauI haven't seen any impact in other projects besides bifrost15:08
JayFyeah I'd say fix it if we get something pressing on bifrost15:08
JayFotherwise let it sit15:08
rpittauyep, agred15:09
JayFIs there any other notable things going on with CI? Aside from bifrost; I think we're as happy as we've been in a while15:09
rpittaunothing else AFAICS15:09
JayFMoving on15:10
JayF#topic Review Ongoing 2023.2 Workstreams15:10
JayFI'll note, generally, we're reaching the homestretch of the release; things we want to land need to get up for review quickly so we can make sure they hit15:10
JayFwe've already had a super productive cycle though15:10
JayF#link https://etherpad.opendev.org/p/IronicWorkstreams2023.215:11
JayFGiving another minute for comments on in-progress items15:12
kubajjshould I include the improving of config if I don't know if I'll complete it before the freeze?15:12
JayFkubajj: first of all, lets try to get it in this cycle :) the freeze you have to worry about for that is 8/31-ish15:13
JayFso you have weeks to complete that15:13
kubajjoh, okay15:13
JayFsomewhere between 8/31 and 10/4 we have to have our final release cut15:13
JayF8/31 is when the other projects will stop taking major changes15:13
JayF#topic OpenStack User Survey Updates15:14
JayFI added this item to the agenda because here15:14
JayF#link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034589.html15:14
JayFProjects were asked to come up with any project-specific questions for the survey15:15
JayFIronic has none, currentyl15:15
JayFWe probably should? But I'm not sure what exactly, so I made this item to 1) increase awareness and see if anyone was interested in drafting questions and 2) give folks a chance to have input before I just go add something if nobody else has interest15:15
TheJuliadoes anyone remember our ideas from last year15:16
iurygregoryI thought we had questions in the survey lol15:16
TheJuliathe ones that came up after we would have had to send them in?15:16
JayFI don't even recall this at all last cycle tbh15:16
JayFand if we have questions in the survey, they are missing from the google doc linked there15:17
JayFor, always possible; I just missed it :D 15:17
TheJuliawell, it would have been last june/july15:17
JayFI created15:19
JayF#link https://etherpad.opendev.org/p/ironic-user-survey-questions-202315:19
JayFWe can use that to coordinate; I'll make sure to get something to them by EOW either way15:19
iurygregory++15:19
JayF#topic Open Discussion15:19
JayFfloor is open for any other items15:19
opendevreviewJulia Kreger proposed openstack/ironic master: Support sha256/sha512 with the ilo firmware upgrade logic  https://review.opendev.org/c/openstack/ironic/+/88216415:20
JayFLast call?15:21
TheJuliaregarding service steps15:22
TheJuliaI've not had time recently to work on it too much, but I'm wondering if it would be one of those "lets just merge it with imperfect testing" and sort it out next cycle sort of things15:23
JayFI think we should make sure it lands this cycle; but can we be explicit about what further testing we want to make on it?15:23
TheJuliasome unit testing + tempest, but the through unit tests work just fine15:24
JayFI'm not terribly worried about it not getting a temptest test, frankly15:24
TheJuliaso decent confidence, just there may be a obvious missing piece somewhere hwich we could just treat as a bug later15:24
JayFwith that context, I wouldn't hold it up15:24
TheJuliaokay, cool15:24
JayFas long as it works when manually tested15:24
TheJuliaI'll try to polish it and get a client patch up this week15:25
JayFawesome15:26
JayFThat's exciting, if you need specific help please ask15:26
JayFI'm invested in being sure that lands in bobcat15:26
JayFAnything else for open discussion?15:27
TheJuliaJayF: a client patch would always be appreciated :)15:27
JayFlets land the API side then :D 15:27
TheJuliaokay then!15:28
TheJulia:)15:28
TheJuliaI have two things to follow-up on and I can shift gears to taht15:28
JayFthe other item that one or both of us owe15:29
JayFis I think johnthetubaguy wanted us to test sharding15:29
JayFand we know Nova will be strict about that B-3 deadline15:29
JayFand if client for service steps is a fast follow that's not that bad15:29
JayFso I think I might focus on getting my nova-set-lessee patch tested, and then sharding tested, so that can get in15:29
* JayF finally wrangled a devstack late last week15:30
TheJuliaI'm not sure we have anything there that would be needed/blocking for that on our side15:30
TheJuliaat least, that I'm conciously aware of, if we do, we should put it on the etherpad15:31
TheJuliaotherwise it will just get lost in my short term recall15:31
JayFI'm saying I think John-the-person wanted us to sanity check the changes15:31
JayFand test in devstack15:31
TheJuliaahh, ok15:31
TheJuliareasonable15:32
JayFnot that there's some pending technical action so much as one or both of us expressing confidence in the changes15:32
JayFI have a devstack up and plans this week to use it to test that and my nova-set-lessee change15:32
JayFEither way, lots of stuff to do :) hopefully can keep pointed in a direction and doing good stuff15:32
JayFfor now I think the meeting is mostly petered out though, I'm going to close it?15:33
TheJuliasounds good to me15:33
JayF#endmeeting15:33
opendevmeetMeeting ended Mon Aug  7 15:33:55 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:33
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-08-07-15.01.html15:33
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-08-07-15.01.txt15:33
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-08-07-15.01.log.html15:33
rpittaugood night! o/15:35
dtantsurTheJulia: we have implemented the automatic checksum algo detection, haven't we?16:20
TheJuliaI believe so16:20
TheJuliahttps://docs.openstack.org/releasenotes/ironic-python-agent/unreleased.html#relnotes-9-5-016:21
dtantsur\o/16:21
dtantsurthx16:21
TheJulianp16:34
opendevreviewJulia Kreger proposed openstack/ironic-python-agent master: minor: fix release notes file path  https://review.opendev.org/c/openstack/ironic-python-agent/+/89069419:57
*** dking is now known as Guest820920:13
opendevreviewMerged openstack/ironic-python-agent master: minor: fix release notes file path  https://review.opendev.org/c/openstack/ironic-python-agent/+/89069420:25
*** Guest8209 is now known as dking20:25
opendevreviewJulia Kreger proposed openstack/ironic-python-agent stable/2023.1: Log the number of bytes downloaded  https://review.opendev.org/c/openstack/ironic-python-agent/+/89069620:43
opendevreviewJay Faulkner proposed openstack/ironic master: DNM: Testing sharding against Ironic  https://review.opendev.org/c/openstack/ironic/+/88827721:31
* TheJulia closes the text editor for service steps tests and takes migraine meds because a front has moved in and brought a migraine23:05

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!