Tuesday, 2022-09-20

opendevreviewMerged openstack/ironic master: Correct Image properties lookup for paths  https://review.opendev.org/c/openstack/ironic/+/85269401:07
opendevreviewMerged openstack/ironic master: CI: Changes to support Anaconda CI jobs  https://review.opendev.org/c/openstack/ironic/+/84958701:07
opendevreviewJay Faulkner proposed openstack/ironic bugfix/21.0: Correct Image properties lookup for paths  https://review.opendev.org/c/openstack/ironic/+/85845902:26
opendevreviewMerged openstack/ironic-inspector master: Ignore connection errors when getting ironic ports  https://review.opendev.org/c/openstack/ironic-inspector/+/83684702:32
JayFshould https://review.opendev.org/c/openstack/ironic-inspector/+/791251 and https://review.opendev.org/c/openstack/ironic-inspector/+/836847 be backported? Does anyone even use inspector on stable (has to be a yes, right?)02:32
lecris[m]TheJulia: dtantsur: Unfortunately the newer bios and ipmi does not fix the issue03:55
TheJuliaWhat about network cards?03:56
lecris[m]TheJulia: Don't have external cards to test and I don't see how to update the firmware for that04:12
lecris[m]One thing worth checking is, is it possible to combine dhcpopts and regular conf file?04:17
lecris[m]Oh, but I see the tags for pxe are added to each individual port04:19
opendevreviewSONG SHUKUN proposed openstack/ironic master: Add support auth protocols for iRMC  https://review.opendev.org/c/openstack/ironic/+/85703504:45
lecris[m]Is there an issue open for migrating from grub2-install to grub2-mkconfig?04:55
lecris[m]This issue is popping up: https://bugs.launchpad.net/diskimage-builder/+bug/193087804:55
TheJuliaWe place the assets and set the Nvram entry now. I think we even have a patch out there or did to flat out ignore grub2-install05:02
TheJulialecris[m]: w/r/t combining, not really. The issue is ultimately for some reason the card explicitly doesn’t read/care about field length, and leans on the null value as a terminator… something I’ve personally never seen before05:03
TheJuliaJayF: many… I would backport them to wallaby05:05
* TheJulia goes to bed… because of hours of calls tomorrow05:07
lecris[m]<TheJulia> "We place the assets and set..." <- Is this for nova deployed images built from disk-image-builder. So why am I getting grub2 issues?05:07
lecris[m]Kay, thnx for the help TheJulia: 05:08
TheJuliaWholedisk or partition images?05:08
lecris[m]Not sure, I've built with baremetal and added kernel and ramdisk05:09
TheJuliaAnd are their contents already valid?  Dib images should be fine, but we have made numerous updates as grub maintainers have been pushing things such as grub2-install behavior changes as they break signing for assets thus breaking secure boot05:10
lecris[m]I'll take another look at the docs to see if I'm doing all the steps correctly05:11
TheJulialecris[m]: heading down the wholedisk image path is highly recommended. If your setting a kernel/RAM disk then it is a partition image05:11
lecris[m]Thnx for the hint05:12
TheJuliaAnd EFI booting looks for a partition. Ironic’s agent code does try to preserve/place efi booting assets if they are in the image, but some cloud image bases don’t include those binary assets, fwiw05:13
TheJuliaAnyway, sleep()05:14
adam-rozmanGood day Ironic !06:03
arne_wiebalckGood morning adam-rozman and Ironic!06:07
opendevreviewEbbex proposed openstack/bifrost master: Use a more traditional ansible approach to include_vars  https://review.opendev.org/c/openstack/bifrost/+/85580606:22
opendevreviewEbbex proposed openstack/bifrost master: Refactor use of include_vars  https://review.opendev.org/c/openstack/bifrost/+/85580706:22
rpittaugood morning ironic! o/07:51
lecris[m]Trying to boot an ironic instance from volume but my cinder backend is ceph and the deploy complains that it is not iscsi08:20
lecris[m]I've seen that there is rdb_iscsi but not sure what that enables08:20
lecris[m]So how is openstack supposed to be configured here?08:21
opendevreviewKOBAYASHI DAISUKE proposed openstack/ironic stable/wallaby: Check Fujitsu backport CI  https://review.opendev.org/c/openstack/ironic/+/85835209:41
dtantsurfolks, https://review.opendev.org/c/openstack/bifrost/+/858391 is a bit of a mess, but it's needed to fix stable/yoga09:42
ajyaTheJulia: it should be updated. What is is used for? Should distribution list that we manage internally would be better than one individual?10:16
opendevreviewJakub Jelinek proposed openstack/ironic-inspector master: Introduce skip list to inspector  https://review.opendev.org/c/openstack/ironic-inspector/+/85330410:23
iurygregorygood morning Ironic11:05
iurygregorylecris[m], I never used the boot from volume, but there is some docs around it https://docs.openstack.org/ironic/latest/admin/boot-from-volume.html 11:10
dtantsurlecris[m]: yeah, you'll need to use the iSCSI feature (whatever it's called - I'm also not strong in this area). Which, I'm afraid, Ceph is slowly deprecating :( TheJulia is again the best person to talk to.11:16
lecris[m]I guess it's a long way till we could mount ceph volumes in ironic?11:18
dtantsurlecris[m]: well... I don't think iPXE understands rdb, which leaves us without many options.11:18
dtantsurThe idea was for Ceph to offer iSCSI support, which iPXE understands and can boot from.11:19
dtantsurIt has been developed, but then they apparently backed away from this idea. I don't know why.11:19
lecris[m]Wouldn't it be possible to boot a lightweight agent to mount and configure from there?11:20
dtantsurlecris[m]: and then kexec into the actual OS? possible, but really error-prone and difficult to debug.11:21
dtantsuralso no idea of an rbd mount survives kexec11:21
lecris[m]True, I've had my fair share when using warewulf11:21
dtantsurlecris[m]: the good news is: if you know how to do it in your environment, you can probably emulate it with https://docs.openstack.org/ironic/latest/admin/ramdisk-boot.html11:22
dtantsurso, the idea is not unheard of, based on quick googling: https://www.mail-archive.com/ceph-users@ceph.io/msg10371.html11:24
lecris[m]Hmm looks promising11:25
lecris[m]Isn't it already possible to have controller node translate ceph volumes to iscsi?11:28
dtantsurI cannot answer this unfortunately11:32
lecris[m]Well at least I've managed to get the whole stack running minus some features I can work around for now11:36
lecris[m]Still puzzled by the dnsmasq dhcp issue though11:37
*** tosky is now known as Guest101212:14
*** tosky__ is now known as tosky12:14
zigoHi there ! Building Ironic 21.0.0 is no problem under Debian Unstable, but building the backport fails with these unit tests:12:28
zigohttps://paste.opendev.org/show/blI3zZWCpsHL5VqnhKr7/12:28
zigoDoes anyone have a clue which python lib needs updating ?12:28
zigodtantsur: ^12:28
zigoTheJulia: ^12:29
iurygregoryzigo, I remember we have to fix some problems for jsonschema 12:29
zigoOh, jsonschema 4 ?12:29
zigoNo, got the same version (backported the one from Unstable too...).12:30
*** tosky is now known as Guest101312:30
*** tosky__ is now known as tosky12:30
iurygregoryyeah 4 something had some problems and we fixed12:30
iurygregorythere is also the problem with oslo.db oslo.db==12.1.012:31
iurygregory=)12:31
iurygregorywe merged a workaround for this already12:31
zigoThe pip freeze is this: https://paste.opendev.org/show/bi8jHmEHq6JXeHNQR2fu/12:32
zigoiurygregory: Oh, it was broken with latest oslo.db ?12:33
zigoI need the patch then!12:33
zigoThat could be it ...12:33
iurygregoryzigo, a lot of things were broken with this oslo.db version :D12:33
zigoThis ? https://github.com/openstack/ironic/commit/74795abf2ff972b2b848eee98426bcdfee2a9c2012:34
dtantsurzigo: oslo.db is a likely candidate12:34
dtantsurthat's the workaround for now12:34
zigoLet me try to force oslo.db 12.1.0 in the Debian Experimental build and see if it fails.12:34
zigoThanks for the clues.12:35
iurygregoryzigo, correct =)12:35
iurygregorygood luck!12:35
zigoBINGO !12:42
zigoForcing oslo.db 12.1.0 fails the build, now trying the patch ... :)12:42
zigoThanks again.12:42
iurygregoryzigo, nice \o/12:48
kubajjGood afternoon ironic!12:52
kubajjI just looked at Zuul and it says Post Failure, has anybody seen that before? https://zuul.opendev.org/t/openstack/build/5e35cd8742b24f38adde8fadde1dbb0712:53
iurygregorykubajj, sometimes it can happen, you can comment "recheck post failure jobs"12:54
iurygregorywithout the "" =)12:54
kubajjiurygregory: thanks, will do12:54
TheJulia yay for putting meeting on the wrong day12:59
TheJuliaAlso... good morning everyone!12:59
kubajjgood morning TheJulia13:00
iurygregoryTheJulia, the PTG one?13:04
iurygregorywe can move for tomorrow lol13:04
TheJuliahuh?!13:04
TheJuliaI don't have that on my calendar13:04
TheJuliaeeek13:04
iurygregoryyou accepted yesterday O.o13:04
iurygregorycompany email .-.13:04
TheJuliaWait, is that the meeting in 2+ hours?13:04
iurygregory2h 55min13:05
iurygregory16 UTC13:05
TheJuliaokay, I have that one13:07
TheJuliaI thought I had a 4 hour block of meetings starting at 6am local time this morning13:07
TheJuliaturns out it is only 3 hours starting at 7 am13:07
iurygregoryO.O13:07
iurygregory"only"13:07
zigoIMO, it'd be nice to release new versions for ironic + ironic-inspector to fix this oslo.db compat 12.1.0 thing...13:11
iurygregoryzigo, it will be released this week13:14
zigogr813:14
iurygregory+ zed stable/branch13:14
dtantsuriurygregory: I might have a free evening in the end, could you add me to the invite?13:19
iurygregorydtantsur, sure13:20
iurygregorydone13:20
opendevreviewUemit Seren proposed openstack/sushy master: Implement allowed values for BootSourceOverrideEnabled  https://review.opendev.org/c/openstack/sushy/+/85046113:22
opendevreviewUemit Seren proposed openstack/sushy master: Implement allowed values for BootSourceOverrideEnabled  https://review.opendev.org/c/openstack/sushy/+/85046113:23
opendevreviewJulia Kreger proposed openstack/ironic master: Concurrent Distructive/Intensive ops limits  https://review.opendev.org/c/openstack/ironic/+/84000613:47
TheJuliaiurygregory: might just be easier to edit https://review.opendev.org/c/openstack/ironic/+/85761513:53
TheJuliaas opposed ot waiting13:54
rpittauiurygregory: I guess there's no way to move the PTG meeting?13:58
iurygregoryrpittau, well it would depend ... only 3 ppl voted so it makes a bit complicated, but I'm all for more ppl participating =)14:31
iurygregoryTheJulia, ok, moved to +214:32
iurygregoryJayF, TheJulia thoughts on what rpittau asked about moving the PTG meeting?14:32
JayFI'm mostly open during working hours today14:33
iurygregorytomorrow 15 UTC would work for both of you checking the doodle (not sure if still applies)14:33
JayFI have a meeting at 8am (in 27 minutes)14:33
JayFthat's 8am my time, I am clear14:33
* TheJulia is soooo confused14:33
JayFTheJulia: AIUI: rpittau wants us to move the ptg meeting so he can attend. Does tomorrow @1500UTC aka 8am PT work?14:34
TheJuliabut my calendar is open tomorrow morning :)14:34
TheJulia++14:34
TheJulia\o/14:34
iurygregoryok, updating the invitation14:34
rpittauiurygregory: it's ok, I see also dtantsurgave his availability for today, don't want to reschedule for all of you just for me, and it would mean also thursday, not even tomorrow14:34
* TheJulia does the one less meeting today dance14:34
iurygregoryrpittau, oh .-. tomorrow 15 UTC you can't?14:35
rpittauiurygregory: unfortunately not :/14:35
dtantsurtomorrow is probably out of question for me as well (unless I'm still too sick to go to the driving school)14:36
dtantsuralthough.. 15 UTC is doable, if not for long14:36
dtantsur(same for Thu)14:36
JayFI can go backwards from that too, 14UTC works14:37
iurygregoryfor Thursday TheJulia doesn't have any free time it seems14:37
iurygregoryat least for 15/16 UTC14:37
TheJuliaI may have marked myself out on Thursday14:39
TheJuliaCan look in a moment14:39
TheJuliaI have a friend coming into town this weeeknd and going to hang out with them on Friday now that we’ve figured things out14:39
iurygregorynice =)14:40
iurygregoryif 15 UTC on Thursday works for you I can update the invitation for everyone, otherwise we keep today's time14:41
JayFI'm clear all thursday14:41
JayFbut will not be here Friday (it's my birthday and I'm taking it off)14:41
iurygregoryno meetings on Friday lol14:42
iurygregorytime off on birthday ++14:43
TheJuliaiurygregory: what your seeing is all of hte meetings I'm invited to but have not accepted14:43
TheJuliaiurygregory: I'm free during my morning on Thursday14:43
iurygregoryTheJulia, I'm only looking at the doodle XD14:43
dtantsur15:00 Thu is fine14:44
TheJuliaoh, I likely didn't answer that then14:44
iurygregoryyeah =)14:44
iurygregoryok, updating to Thu 15 UTC14:44
* iurygregory also sends email to openstack-discuss now14:45
rpittauthanks all :)14:45
TheJuliaspeaking of PTG... it seems the operators have expressed interest in their being operator centric discussions hosted by project teams, so if we can carve an hour out of the schedule for operators that hopefully doesn't conflict with other teams, I think it would be good14:45
iurygregoryyes14:46
iurygregoryI was planning to discuss this during this session 14:47
opendevreviewUemit Seren proposed openstack/sushy master: Implement allowed values for BootSourceOverrideEnabled  https://review.opendev.org/c/openstack/sushy/+/85046114:53
iurygregoryCongratulations to JayF \o/ he will be the PTL for the Antelope cycle =D15:04
JayFI feel like the dog that caught the car, what do I do now ;) 15:04
JayFseriously, I'll be leaning heavily on iurygregory, Julia, and anyone else who is willing to listen :D I've got a lot to learn over the next few months15:05
iurygregoryJayF, we will help you =)15:05
iurygregorythe release part is very well documented (I never had any problems :D)15:06
rpittaucongrats JayF :)15:09
JayFI have a handful of stable reviews that should be quick and easy if folks want to help with some quick wins so I can get them another level down: https://review.opendev.org/c/openstack/ironic/+/858459 https://review.opendev.org/c/openstack/ironic/+/857771  https://review.opendev.org/c/openstack/ironic/+/85620515:21
JayFhttps://review.opendev.org/c/openstack/ironic-python-agent/+/85777215:21
dtantsurJayF: congrats/condolences, we're here to help! :)15:23
arne_wiebalckThanks iurygregory for all your PTL work during the last cycle!15:24
dtantsuryep, iurygregory++15:24
arne_wiebalckAnd congratulations JayF for both your new roles!15:24
iurygregoryThanks arne_wiebalck dtantsur =)15:35
rpittaubye everyone, see you tomorrow o/15:39
TheJuliaJayF: noticed I missed one thing on https://review.opendev.org/c/openstack/ironic/+/840006, fixed it this morning15:57
JayF:eyes:15:57
TheJuliawow that was some giant eyes15:58
JayFoh yeah, I reviewed this on mobile but didn't login and vote15:58
TheJuliaahh, yeah15:58
JayFTheJulia: it worked on your client? lol15:58
TheJuliayeah, irccloud15:58
JayFTheJulia: and also, giant bitmap emoji not being downsized is a buf in your font configuration15:58
JayFassuming you're on linux, yeah15:58
TheJulia👓15:58
JayFI do not want to admit how many hours I spent troubleshooting emoji on my gentoo install lol15:59
JayFit still doesn't do compound emoji (e.g. color modifiers for emoji, where the unicode is like brown-smile)15:59
TheJuliaheh16:10
* TheJulia makes fresh coffee before trying to actually be productive now16:10
opendevreviewMerged openstack/ironic master: tests: Add a WarningsFixture  https://review.opendev.org/c/openstack/ironic/+/85634516:11
kubajjiurygregory: fixed https://review.opendev.org/c/openstack/ironic-inspector/+/85330416:13
arne_wiebalckWe just instantiated the first ARM node with Ironic at CERN \o/16:19
TheJulia\o/16:20
kubajjarne_wiebalck: \o/16:20
iurygregorykubajj, ack I will take a look16:21
iurygregoryarne_wiebalck, congrats!16:21
TheJuliaAny objection if I rev https://review.opendev.org/c/openstack/ironic/+/857615 to include a release note?16:21
iurygregoryTheJulia, none on my side, happy to +2 again16:23
iurygregoryand is such a small thing I'm also happy to +W =)16:24
opendevreviewJulia Kreger proposed openstack/ironic master: Fix nodes stuck at cleaning on Network Service issues  https://review.opendev.org/c/openstack/ironic/+/85761516:32
TheJuliaposted and +2'ed16:32
opendevreviewJulia Kreger proposed openstack/ironic-python-agent stable/wallaby: Fix software raid output poisoning  https://review.opendev.org/c/openstack/ironic-python-agent/+/85846416:39
TheJuliaJayF: w/r/t https://review.opendev.org/c/openstack/ironic/+/857984 I think we have a terminology issue, happy to take a shot at fixing it real quick16:47
opendevreviewJay Faulkner proposed openstack/ironic-python-agent bugfix/8.1: Fix software raid output poisoning  https://review.opendev.org/c/openstack/ironic-python-agent/+/85846516:48
JayFTheJulia: ^^ that one needs landing before wallaby16:48
JayFTheJulia: either fix it or leave a comment and I can circle back16:48
TheJuliaworkflowed16:50
JayFTheJulia: I had a feeling something around that was wrong, ty16:51
TheJuliaJayF: happy to revise in a few 16:53
JayFI already have it open16:53
TheJuliaok16:53
JayFthen looks like that ipa fix has conflicts going further back than wallaby :( 16:53
TheJuliaJayF: raid wasn't completely sorted until wallaby16:54
JayFaha, so probably just needs to stop at wallaby then, good stuff16:54
TheJuliayeah16:54
TheJuliaso... w/r/t bugfix branches, did we ever actually abandon the old ones, because i thought we had a list to abandon16:55
JayFHonestly, that was something I was generally going to inquire about16:55
JayFincluding if we know if there are folks consuming them16:55
JayFbecause it does add quite a bit of overhead16:55
TheJuliaRH consumes some of them, but generally it should only be the last few. We've got a couple years of them on IPA16:56
JayFMaybe this should be a PTG topic?16:57
TheJulia++16:57
JayFOnly maintaining bugfix branches until the named-version of them is released would be one route to potentially go16:57
JayFso e.g. once zed is released, any bugfix branches would go away until we decided to cut the first pre-antelope bugfix branch?16:57
JayFidk16:57
JayFI have no insight into how folks consume these, and frankly am surprised given how painful upgrading openstack can be operationally that folks would do it more than twice a year lol16:58
TheJuliaso, we actually wrote this down16:58
TheJuliaand it summed up to the last 2 bugfix branches, but in practice... that has not panned out since use has lagged more than anticipated16:58
JayFCan you be more explicit about what you mean by "use has lagged"16:59
opendevreviewMerged openstack/sushy master: Fix misuse of assertTrue  https://review.opendev.org/c/openstack/sushy/+/85690716:59
TheJulialike being bugfix-3 and not moving forward16:59
JayFokay, so we haven't done a good job of following up and actually retiring bugfix branches beyond the 2 we support?17:00
TheJuliaThat is my understanding as well17:02
TheJuliaiurygregory: ^^17:02
JayFack; I can add that to my list as long as we confirm that's what we want.17:02
JayFactually, I'll add an item for Monday's meeting17:02
TheJuliasounds good to me17:02
opendevreviewJay Faulkner proposed openstack/ironic master: Document existence of non-production "fake" driver  https://review.opendev.org/c/openstack/ironic/+/85798417:06
JayFTheJulia: ^ is that better?17:06
TheJuliaJayF: much17:08
TheJuliaJayF: a minor nit/suggestion17:09
JayFack, will fix that pluralization after finishing this rebase17:10
JayFprobably 15m17:10
TheJuliak17:10
TheJuliano worries, still trying to fix my router17:10
* TheJulia glaers at the big white 5G cube of doom not playing nicely with the load balancer17:10
* TheJulia attempts the age old reboot17:14
JayFTheJulia: when you fix your router, if you have 5 minutes I could use a second pair of eyes17:33
JayFtrying to get https://review.opendev.org/c/openstack/ironic/+/858459 back to bugfix/20.2, it needed a rebase, and now unit tests are failing17:33
* TheJulia raises an eyebrow17:37
TheJuliaI8791623be95e7e47739ee051753de97eb0e5e2a3 needs to merge first17:41
opendevreviewMerged openstack/ironic stable/xena: Do not reboot into nowhere after BIOS settings with fast-track  https://review.opendev.org/c/openstack/ironic/+/85620518:01
JayFOH18:06
JayFI was thinking it might be something like that, but didn't see anything in bugfix21.018:06
JayFI guess thi slanded before 21.0 was cut18:06
JayFgood stuff ty18:06
JayFTheJulia: backported that, literally the exact same two tests are filing :| 18:11
opendevreviewMerged openstack/ironic-inspector master: Introduce skip list to inspector  https://review.opendev.org/c/openstack/ironic-inspector/+/85330418:12
opendevreviewMerged openstack/ironic bugfix/21.0: Correct Image properties lookup for paths  https://review.opendev.org/c/openstack/ironic/+/85845918:12
JayFooh bad rebase, I love it when it's my fault18:12
TheJuliawoot :(18:30
TheJuliaokay, router fixed18:30
TheJuliahopefully this will work better now18:30
JayFTheJulia: is it possible there's yet-another-prereq for that backport?18:31
* JayF is about to go digging down git logs18:31
TheJuliaquite18:31
TheJuliaI'd git blame the conflicting area18:31
JayFthe conflicts are all in tests18:31
JayFbut when they are fixed; the tests fail18:31
TheJuliahmm :\18:31
JayFaha18:32
JayFhttps://github.com/openstack/ironic/commit/33bb2c248a20d6a2a0af570655124cbc86d58b6a18:32
JayFit's that, almost certainly18:32
JayFyeah, and I need to rebase out the test that is needed for that, maybe18:33
JayFokay this makes sense18:33
JayFunit tests failing because the branch doesn't have the feature, who woulda thought :| 18:34
opendevreviewJay Faulkner proposed openstack/ironic bugfix/20.2: Fix pxe image lookups  https://review.opendev.org/c/openstack/ironic/+/85857218:38
JayFthat also means that https://review.opendev.org/c/openstack/ironic/+/858459 shouldn't be backported beyond 21.0, since https://github.com/openstack/ironic/commit/33bb2c248a20d6a2a0af570655124cbc86d58b6a didn't exist in 20.218:39
opendevreviewJulia Kreger proposed openstack/ironic stable/ussuri: CI: fix ussuri branch  https://review.opendev.org/c/openstack/ironic/+/84351518:40
opendevreviewJay Faulkner proposed openstack/ironic master: Document existence of non-production "fake" driver  https://review.opendev.org/c/openstack/ironic/+/85798418:43
opendevreviewJay Faulkner proposed openstack/ironic bugfix/18.1: Do not reboot into nowhere after BIOS settings with fast-track  https://review.opendev.org/c/openstack/ironic/+/85846818:44
TheJuliaJayF: https://github.com/openstack/ironic-specs/blob/master/specs/approved/new-release-model.rst <-- background18:54
TheJuliahttps://review.opendev.org/c/openstack/ironic/+/838592/2/ironic/conf/deploy.py <-- easy win?!19:01
TheJuliaerr19:01
TheJuliahttps://review.opendev.org/c/openstack/ironic/+/83859219:01
TheJuliaNobodyCam: can you chime in on https://review.opendev.org/c/openstack/ironic-python-agent/+/566544 w/r/t step name19:20
JayFTheJulia: sounds like my interpretation: bugfix/[] branches should die when it's named-release comes out seems right?19:20
TheJuliaI believe that was the original intent/hope19:21
JayFack; in that case I'll still say something in meeting and we should probably cut final releases for those bugfix branches when zed is cut19:21
opendevreviewMerged openstack/ironic master: Document existence of non-production "fake" driver  https://review.opendev.org/c/openstack/ironic/+/85798419:32
iurygregoryTheJulia, sorry for some reason I missed your ping looking at other things, for bugfix branches we added to the etherpad the ones that are in use cc JayF 20:00
JayFYeah; it looks like the written policy says we should be retiring them once the letter-release they relate to is out20:01
iurygregoryyeah20:01
JayFright now we violate that in a couple of places ... I'm just trying to ensure the extra churn we pay for stable branch maintenance is worth it20:01
JayFafaict, for ironic, we need to retire 19.0 and 18.0, and for IPA, 8.3 and 8.1  -- I haven't looked at the other repos yet20:02
JayFI'm happy to do this, but was going to wait until we said it at a meeting20:02
JayF(and hopefully there won't be objection to retiring the zed-related bugfix branches fairly quickly after zed is cut)20:03
JayFhonestly, I don't care how many of these we have as long as we actually think people are using them and that people *should* use them20:03
iurygregorybugfix/19.0 we do use 20:03
JayFfor that second one -- I don't see any reason someone would run 19.0 instead of yoga20:03
JayFlol curious why not yoga in that case :D 20:03
JayFI'm glad you are the counterexample, I wanna understand the motivation20:04
iurygregoryyeah, basically is to avoid shipping new features20:05
JayFLike, let me put it this way: if you don't want new features; why not xena? If you do, why yoga?20:06
JayFin fact, afaict, our release doc as written specifically discourages people from running a bugfix release when the named one exists20:06
iurygregoryin this case we landed a feature after xena that we claim we support downstream20:07
JayFbut you can't put people on that release into yoga b/c it's not a "safe" upgrade per-se20:07
JayFhonestly this written policy doesn't reflect reality at all20:08
JayFand we should fix it20:08
NobodyCamWill look in a bit20:09
JayFwe support named branches **much** longer than 12 months, and we support bugfix releases for much longer than that oo20:09
iurygregorythey are not really aware of "what version of Ironic" is in use20:09
JayF**too20:09
JayFI mean sure, but I have an upstream hat on, I don't have a red one to wear :D 20:09
JayFso I'm trying to find a way to make this ... understandable without including RH shipped software in the explanation20:09
TheJuliaNobodyCam: thanks20:09
JayF(and I'm very OK with making that explanation "work" for what RH ships, you all are the gateway to a huge amount of Ironic users; I just want our written things to make sense :D)20:10
JayFand bluntly, I've maintained downstream forks before; it's no fun and no good for anyone upstream or down20:11
TheJuliado metal3 folks, public folks that is, make use of our bugfix branches?20:12
iurygregoryyeah we need to update https://github.com/openstack/ironic-specs/blob/2f4edc8320a0594402c41d44ebe4368ec43a5f16/specs/approved/new-release-model.rst20:13
JayFHonestly this conversation is me fishing for input so I can go update that :D 20:14
iurygregoryTheJulia, afaik nope 20:14
JayFSo bugfix/* branches are for: 1) standalone ironic users and 2) occassionaly they map directly to a downstream RH release, so you all want to keep it supported20:14
TheJuliaiurygregory: not update/amend, but draft new perhaps?20:15
JayFthat's reasonable in terms of, how the world actually works; I just wonder if 1 and 2 are the same set (e.g. do we have any users, not on rh, using bugfix releases?)20:15
iurygregoryTheJulia, agree20:15
* JayF realizes these answers are probably impossibleish to get20:16
TheJuliaJayF: yup :(20:16
TheJuliawe *have* had issues in the past where we were blocked on getting a x.y version that was intermediate to a branch released because infra wouldn't let us create new intermediate tags/branches to fix it20:17
TheJuliaand those were largely driven by folks who looked at our versions and went "I'll use that"20:17
TheJuliaI *suspect* active bugfix branch maintenance has largely made those sorts of complaints disappear20:17
TheJuliabecause now they are not really orpahned like they were20:17
TheJuliaand we actually are able to backport some fixes....20:18
JayFhonestly, I'm tempted to suggest we say bugfix releases go away when the named-version of those are out (e.g. 21.0/20.2 would go away when zed is released)20:18
JayFEXCEPTING if someone in the community has adopted it20:18
* TheJulia wonders if we're just over-thinking and should just trim out the old bugfix branches20:18
JayFor something along those lines20:18
JayFthen we can sorta pick and choose but still have a policy that's reasonably consistent20:18
TheJuliaJayF: ++20:18
TheJuliaI think that is a good way to put it20:18
TheJuliaa short update that would be, fwiw20:18
JayFI mean, hell, when I worked places that didn't track master Ironic, I usually told them to use the stable/* release that RDO was using20:18
JayFbecause you were nearly-guaranteed to be on the long-end-border of support20:19
JayFI'm going to leave that as a meeting agenda item, and reword it a little, but as long as we're all on the same page in the meeting I'll push a new spec20:20
JayF> TheJulia wonders if we're just over-thinking and should just trim out the old bugfix branches20:21
JayFfwiw, I don't like this approach because as a project, we should like kinda consider ourselves an API?20:21
iurygregoryI think rpittau dtantsur and I would live in paradise if we could move things to stable/zed XD20:21
JayFand not having policies, and following them, that other people can read means we have a bad api lol20:21
* iurygregory brb coffee20:21
JayFthese are things I think about, even though they might not matter quite so much 20:21
TheJuliaJayF: I was more trying to convey that maybe what we are doing now does the needful and solves a lot of the problems, the issue by in large part is we've created a lot more backporting work which may not be needful20:22
TheJuliaand going back/fixing some of these things when someone discovers a really bad bug is sometimes impossible without the pre-existing branchpoint20:23
JayFTheJulia: that's mainly why I brought it up as a topic, tbh. I feel like I do useful stuff when I backport to stable/[abc] but I feel like I'm throwing things into a black hole when they go into bugfix/[0-9]20:23
TheJuliai agree, it is nebulous until someone complains :(20:23
JayFI'm going to post to the mailing list and ask. More information never hurt anyone :D 20:24
TheJuliagood plan20:25
TheJulianow where did my brain go20:25
iurygregoryI think we asked already if there were people using it20:29
iurygregory[ironic] Thoughts on closing some branches20:30
iurygregory27 de jun20:30
JayFah, and that's how we got to the currently-pruned list20:32
iurygregoryyeah20:33
opendevreviewJay Faulkner proposed openstack/ironic bugfix/20.2: Fix pxe image lookups  https://review.opendev.org/c/openstack/ironic/+/85857220:37
opendevreviewJulia Kreger proposed openstack/ironic-tempest-plugin master: Tempest test for anaconda deploy  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/85403120:56
opendevreviewMerged openstack/ironic master: Fix nodes stuck at cleaning on Network Service issues  https://review.opendev.org/c/openstack/ironic/+/85761520:56
opendevreviewMerged openstack/ironic master: increase disk_erasure_coconcurrency  https://review.opendev.org/c/openstack/ironic/+/83859220:56
JayFiurygregory: TheJulia: rpittau: dtantsur: lolsob. First TC meeting? Thursday, right when our PTG topics meeting is20:58
JayFI could probably do both given it's an IRC meeting, but that's not ideal 20:58
iurygregoryJayF, ops XD21:00
NobodyCamoh I've never seen a comment post like that... wonder what I did21:00
iurygregoryyeah, totally not ideal (you would need to switch context a lot I think)21:00
JayFI mean, it is what it is. I think I can swing it, and don't want us to have to move it (again)21:01
opendevreviewMerged openstack/ironic-python-agent master: add openstack-python3-zed-jobs-arm64 job  https://review.opendev.org/c/openstack/ironic-python-agent/+/85493721:05
iurygregoryWHAT? :eyes:21:16
iurygregoryoh ok, zed-jobs-arm6421:17
iurygregoryjesus I was like "we didn't cut the release why we have this merged" LOL21:17
opendevreviewJulia Kreger proposed openstack/ironic stable/ussuri: CI: fix ussuri branch  https://review.opendev.org/c/openstack/ironic/+/84351521:29
TheJuliaheh, better to have the jobs now than later :)21:29
TheJuliaJayF: is the tc meeting going to be a call or a irc chat?21:31
JayFTheJulia: ... I assumed it's IRC??21:34
JayFis that a bad assumption?21:34
JayF>  Location: IRC OFTC network in the #openstack-tc channel21:34
JayFso yeah, it's IRC21:34
TheJuliahave we written a prelude for Zed?!22:07
TheJuliano, we have no prelude22:07
opendevreviewJulia Kreger proposed openstack/ironic master: add default conductor group capability  https://review.opendev.org/c/openstack/ironic/+/85570522:13
* TheJulia gets out the words and a text editor22:19
JayFTheJulia: "Now that we have re-leased Z, next time will be A you see" :P 22:20
* TheJulia groans22:20
JayF(to the tune of the ending of the alphabet song, appropriately)22:20
JayFTheJulia: I think you should add a task for the 2nd thing to 2010267 so if/when that merges, it won't close yet 22:21
JayF(re: your recently posted patch)22:21
JayFalso might wanna put it up for RFE-approval next meeting, although I'm fine with it and it's obvious22:22
TheJuliaI was like "surely we've done this" and nope22:22
TheJuliaso "that was easy"22:22
JayFassuming current behaior is if you create a new node w/o specifying group but with groups configured, it goes kaboom? (API error/bad req)22:23
TheJuliaJayF: current behavior is it gets created with none, and you need a conductor in the none group to change the node after the fact.22:28
JayFThat smells like there's a validation bug in there too -- e.g. should I be able to add nodes to *any* conductor group that doesn't have conductors from that group registered in it?22:28
JayFlike I would've hoped creating a "None" group'd node would be impossible if there were no "None" group'd conductors22:28
JayFcan I create a "banana" conductor group node w/o having a "banana" conductor?22:29
TheJuliawe don't keep a central list of them, and they can be changed22:29
TheJuliaits a hash ring division key, really22:29
JayFooh22:29
JayFthat is ... unfortunate22:29
TheJuliayeah22:29
JayFthere's no good way to fix it if that's the design22:30
TheJuliabut... powerful too22:30
JayFOh, believe me, I was already thinking of ways that you could (ab)use that22:30
JayFTBH I'm just thinking of the poor operator "oh hell, I added these to the producktion group by accident" and having no way to fix but touching DB or adjusting conductor config22:31
TheJuliaI think arne hit that once22:31
TheJuliaI *think* we likely need to have a fallback/retry on node_update because of that22:31
TheJuliaand drivers22:31
TheJuliaanything that is a hashring key should trigger a fallback imho22:32
TheJulia"oh! you wan todo x and that would have changed the conductor, lets fallback if not locked, try to lock and update it"22:32
opendevreviewJulia Kreger proposed openstack/ironic master: Zed: Add a prelude for the release notes  https://review.opendev.org/c/openstack/ironic/+/85858222:33
JayFI was thikning that too, but couldn't wrap my brain around how22:33
JayFI am ... less optimistic about that type of change after the work I did for heartbeat-only agent downstream at yahoo22:33
TheJuliaahh22:33
TheJuliaI can see how it works mechanics wise in my mind, but I'm approaching the end of my day after getting started so early22:33
JayFof course, we don't have to solve anything now22:34
JayFjust food for thought22:34
JayFgo have an eod, see you tomorrow o/22:34
TheJuliatomorrow we likely need to update the release mappings22:34
TheJuliaand check release note content22:35
JayFbtw, if I haven't said it "Zed" is like, my favorite Ironic release name so far22:36
JayFI have a thing for three-letter-words-pronounced-like-a-letter22:36
TheJuliaI dislike it because the "zed is dead" joking that immediately started22:36
TheJuliabut that is just me22:37
JayFI've not heard that except just now, from you22:37
JayFyou have proliferated your hated meme! oh no :( 22:37
TheJulianooooooooooooooooooo22:37
JayFhonestly, outside of openstack folks, the releases are all letters22:38
JayFyou start throwing wallaby and victoria and all that around, people get confused, letters are understandable22:38
JayFI actually am looking very forward to the 2023.x naming convention starting up22:38
* TheJulia wonders if the board is *actually* aware of that22:40
JayFTheJulia: the new versioning stuff? The TC rez said we keep names for marketing (e.g. Antelope = 2023.1) 22:42
JayFso like, does things change from a foundation standpoint?22:42
* JayF probably would've referred us just use actual version numbers, but that's less fun anyway22:42
JayFactually, I wonder how that impacts our bugfix releases22:42
TheJuliaunlikely, since the name is the marketing unifier/delineator22:43
JayFif policy says releases should be versioned 2023.1 22:43
JayFthen how do we make a bugfix off that?22:43
TheJuliawe don't22:43
TheJuliaoh wait22:43
JayFhttps://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html it's unclear22:43
TheJuliaare they mandating everyone tanks their versioning22:44
TheJulia?22:44
JayFI'm saying it's unclear.22:44
JayFAnd we need to proactively be aware of how things are lining up w/release team for A22:44
JayFso that's not implemented as an implied requirement when it's not required by the resolution22:44
TheJuliait is the unified release22:44
TheJuliaeach project together, not each individual project22:45
JayFSo I'm saying, right now, yoga Ironic is uploaded to pypi as like, probably 20.0 or something /me didn't look it up22:45
TheJuliaand it should continue to be so22:45
JayFI'm wondering if this implies -- or if releaqse team will try to require us -- to publish antelope as 2023.122:45
TheJuliaand if they try to change that, they are going to really screw up pypi22:45
JayFwell, not really, as long as versions go up22:45
JayFwhich they would, moving to year-first in the release name22:45
TheJuliabut it breaks versioning logic22:45
JayFthe only thing that would break in a technical sense is our workflow (and other projects that might use it, if they exist)22:45
TheJuliawe had to nuke the cirica 2014 versions for similar reasons22:46
JayFHm. I don't think it'd be a break in this case (because existing versions are all going to be <2023)22:46
JayFbut hopefully that experience will be in folks' mind if they consider doing that22:46
JayFand I'll keep an eye on it22:46
TheJuliaOpenStack Release (as in called openstcak) != nova 23.0, ironic 22.0, etc22:47
TheJuliaafaik, there is no longer a single OpenStack package on things like pypi...22:47
TheJulia(... there was once... it was addressed if memory serves)22:47
JayFYour comments all match my understanding. It's just weird to have a numerical name that is not the same as the numerical version22:49
JayFand I had a concern; possibly unfounded, that folks would try to unify them22:49
TheJuliaThis is... a worry22:49
TheJuliaanyhow, time will tlel22:49
JayFjust something to keep an eye on :)22:49
TheJuliaI'm going to plugin the work lappy and start thinking about dinner22:49
JayFObligitory "go make pizza for Summer" :D 22:50
JayFo/ 22:50
TheJulianot tonight, but I should make some dough22:50
JayFVanessa has been making some pizza dough out of sourdough disard22:51
JayF*discard22:51
JayFI stretched one out real thin and made myself a bad NY-style pizza lol22:51
TheJulianice22:52

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