Wednesday, 2022-09-21

*** matt__ is now known as matfechner03:06
opendevreviewAdam Rozman proposed openstack/ironic-python-agent master: prioritize lsblk as a source of device serials  https://review.opendev.org/c/openstack/ironic-python-agent/+/85586605:22
opendevreviewAdam Rozman proposed openstack/ironic-python-agent master: prioritize lsblk as a source of device serials  https://review.opendev.org/c/openstack/ironic-python-agent/+/85586605:48
kamleshChauvhanGood Morning Ironic!06:52
rpittaugood morning ironic! o/07:32
jm1dtantsur: hello :) looks like your register_machine patches for openstacksdk have been merged https://review.opendev.org/q/project:openstack/openstacksdk+owner:dtantsur%2540protonmail.com09:40
jm1dtantsur: thanks for that! :)09:40
jm1dtantsur: somehow this code is timing out in wait_for_provision_state https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_d6c/854113/13/check/bifrost-collections-src/d6cf784/job-output.txt09:41
jm1dtantsur: in the old code the provisioning took a minute, now its timing out after 3 minutes. so i guess there is an issue with the code. maybe i am calling register_machine wrong? https://review.opendev.org/c/openstack/ansible-collections-openstack/+/854113/14/plugins/modules/baremetal_node.py#66509:45
kubajjdtantsur: just a thought, how do we deal with the software RAID skip list - inspector problem?10:05
iurygregorygood morning ironic11:09
kamleshChauvhaniurygregory, Is it ok to add priority tag for https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/855710 11:28
iurygregorykamleshChauvhan, it's ok11:29
iurygregoryironic-cores, double checking ipa patches https://review.opendev.org/c/openstack/ironic-python-agent/+/855866 https://review.opendev.org/c/openstack/ironic-python-agent/+/566544 do you think we should try to include in zed ?12:33
rpittauiurygregory: not sure we have time this week?12:47
iurygregoryrpittau, yeah, one had a +2 but they updated the patch (would also be good a releasenote on it...)12:48
iurygregoryXD12:48
TheJuliaI think it would be good to get the nvidia/mellenox thing in, not really a fan of the step name though12:52
TheJuliaAlso, good morning!12:52
iurygregorygood morning TheJulia 12:57
iurygregoryyeah, I was reading the comments now 12:58
iurygregoryI'm checking releasenotes for inspector, no open patches \o/13:00
rpittauTheJulia: I agree on the step name, at least adding a reno to explain that13:11
TheJuliayeah, I suspect this would be an argument to support name aliases13:11
kamleshChauvhanTheJulia, Hi.13:19
TheJuliaHi, I'm on a board meeting right now, whats up13:19
kamleshChauvhanI think you missed to vote post review on patch  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/848709.13:19
kamleshChauvhanCan you please help to share vote on this patch once free..13:19
iurygregoryI was planing in ping Julia about this one (was reviewing the patch)13:41
TheJuliayou guys realize the plugin is independently released right?13:43
TheJuliaMy plate is overflowing, fwiw.13:44
iurygregoryyeah, I know =)13:45
TheJuliafwiw, I've been sporatically seeing gerrit not saving some things, I think it async http calls which don't complete from the browser13:48
TheJuliaHad the same issue with a conference review tool as well :( Going too fast == stuff not getting saved13:51
iurygregorygerrit was a bit slow for me this days, and I had to re-login almost everyday 14:02
opendevreviewRiccardo Pittau proposed openstack/bifrost master: Move bifrost integration tests to Ubuntu Jammy  https://review.opendev.org/c/openstack/bifrost/+/84882814:09
opendevreviewRiccardo Pittau proposed openstack/bifrost master: Move bifrost integration tests to Ubuntu Jammy  https://review.opendev.org/c/openstack/bifrost/+/84882814:12
rpittauthis ^ should be ready now14:13
TheJuliaI've also had internet connectivity blips where things cut out for a couple seconds or I get a spike of packet loss14:18
iurygregoryrpittau, this would also mean we have Jammy as supported right?14:18
rpittauiurygregory: well, partially14:19
iurygregorywe would need to update docs I think + releasenote14:19
rpittauneed to convert the other jobs, but if that goes well should be quick14:19
rpittauyeah14:19
iurygregorylet's hold a bit get some open patches merged and see if we can get this by eod today if goes green =)14:19
rpittauI would put the reno in the final patch though14:20
iurygregoryyeah, but CI jobs we can change after release etc 14:20
rpittaummm not this one, bifrost is all on us14:21
rpittauah nvm, read that wrong14:21
TheJulia"perfection is the enemy of good"14:21
rpittaulooks like jammy will be officially proposed to replace focal in CI/CD during Antelope, so we're right in time14:42
* dtantsur remembers to open IRC14:45
dtantsurjm1: looking..14:45
dtantsurjm1: I sense a bad timeout value somewhere, 3 minutes may not be enough14:46
dtantsurjm1: https://opendev.org/openstack/ansible-collections-openstack/src/branch/master/plugins/module_utils/openstack.py#L98 somehow takes priority over the value in module?14:52
jm1dtantsur: reversed it to previous timeout of 30 minutes and indeed it passed after 5 minutes. now it fails in the next step, which is expected because we changed the return values https://f8bf2d4a845608449589-8f1f171af5507b30533733754e7f1ad8.ssl.cf5.rackcdn.com/854113/15/check/bifrost-collections-src/7187f5a/job-output.txt14:52
dtantsurjm1: yeah, 5 minutes is more realistic for cleaning on VMs (even more for bare metal)14:53
jm1dtantsur: so your sense was good ;)14:53
dtantsur:)14:53
jm1dtantsur: maybe you could change the role to check for both the old and the new return value name?14:54
jm1dtantsur: then it should work with both the old and new aoc/sdk versions14:54
dtantsurjm1: what was the reason for rename?14:55
dtantsurthis is not coming from the SDK, is it?14:55
dtantsuris there any sort of a convention? I'd expect baremetal_node_info to return baremetal_nodes?14:57
jm1dtantsur: we are trying to enforce a consistent name scheme across all modules. in most modules this means dropping the prefixes, so that we are left with "nodes" or "servers" or whatever. a side effect is that users will get errors which will notify them about changed return values. which is good because module results of nearly all modules have changed in one or another way due to the sdk's cloud layer rewiring15:00
jm1dtantsur: the idea is better warn users about changes than to let their code silently fail15:01
dtantsurI guess I'm a bit uneasy about result names not matching module names..15:01
dtantsurfrom the bifrost's perspective, we'll need to change a dozen of occurrences. possible, but not ideal.15:02
opendevreviewMerged openstack/ironic-tempest-plugin master: Swap maintenance fix to cleanup step  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/85052415:04
jm1dtantsur: module names is another thing we have to think about, but just had no time for. some modules have short names like server, others have longer names such as baremetal_node, then again others have the projectname inside their names such as keystone_* and then we have completely crazy names.15:04
dtantsurjm1: I'd keep baremetal_ prefix, at least because we have a conflict about ports15:04
dtantsurI'd definitely drop the usage of project codenames15:05
TheJuliaIs anyone doing a blog post for Zed?15:05
* TheJulia has word writing cap on thanks to board meeting15:05
jm1dtantsur: actually i agree with your approach of using longer names everywhere. for now i will rename the return value back to your previous name and we can rethink the module names (and its return value names) later15:06
dtantsurjm1: yeah, let's start with a formal consensus first15:06
jm1dtantsur: you might have to fix bifrost anyway and without the name change you will have to discover the locations your self ;)15:08
dtantsurgrep to the rescue \o/15:08
TheJuliagrep is always to the rescue15:11
TheJuliaunfortunately it lacks an AI to self determine what needs to be found in *all* cases without input15:11
* TheJulia assumes this statement launches the AI which eliminates humanity15:12
opendevreviewVerification of a change to openstack/ironic-tempest-plugin master failed: Add iDRAC Redfish sync boot mode test  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/84870915:13
opendevreviewMerged openstack/bifrost master: Rename include_dhcp_server -> enable_dhcp for consistency  https://review.opendev.org/c/openstack/bifrost/+/85809015:24
rpittaubye everyone, see you tomorrow! o/15:25
JayFdtantsur: ty for the detailed information on use of bugfix/* branches on the list; it's nice to know the work backporting to them isn't going into a vacuum :D 15:27
dtantsursure thing :)15:31
JayFdtantsur: I will likely (in the next week or two) propose a small spec to cleanup our docs on our supported releases -- basically trying to make our docs line up with reality15:34
JayFI bet there are a ton of Ironic users who assume, wrongly, that we don't regularly backport stuff to ussuri and even at some points train15:34
dtantsurI'm one of them :D15:36
JayFBasically these days, if there's a backportable patch, I take it back to ussuri minimum unless the rebase starts getting too hairy15:37
JayFI got all our nova driver fixes from the last 2-3 years backported thru to train in nova as well15:37
JayF(FWIW this also means if I miss one, lmk and I'll put it in my queue)15:37
JayFThis is why I wanted to make sure we actually use the stuff -- if we support it, I wanna do an A++ job of it, if we don't, I don't wanna do the job at all lol15:38
TheJuliaSo I just realized I forgot to mention I won't really be around Friday15:47
TheJulia. o O (not that most open source contributors *really* are most Fridays...)15:47
JayFSame here; it's my birthday so I took the day off. But as usual will probably have IRC open anyway :P15:48
TheJuliaheh15:49
* TheJulia is going to go meet up with some NC friends in LA on Friday15:50
dtantsurJayF: note that we (= OpenShift) are not typical OpenStack consumers. We tend to consume newer releases than average.15:50
JayFdtantsur: good :D15:50
TheJuliadtantsur: fwiw, this is a pattern we hope to consume on my side of the house in the future (yay for strong compatibility contracts!)15:50
dtantsur\o/15:51
JayFI was about to say, we've worked so hard on upgrade compatability15:51
JayFupgrades shouldn't be so scary anymore15:51
TheJuliano, yet there is still a huge stigma15:51
TheJuliaand I think everyone who has been bitten over the past few years just flat out ignored release notes15:51
TheJuliaat least, for those that I've talked to15:51
* dtantsur -> driving school, see you tomorrow15:52
TheJuliadtantsur: good luck!15:53
* TheJulia needs to learn to drive the 45' mobile command center soon15:53
JayFTheJulia: I told our downstream deployers here that I'm nearly 100% sure you could take an openstack installation of nearly any modern release, cut everything off, run migrations, upgrade code, cut everything on, and it would work *as long as* you didn't miss anything in the release/deprecation notes15:54
JayFTheJulia: (then told them not to do that because the statement after the "as long as" is impossible)15:54
TheJuliahonestly, I think the vast majority of time I spend on release to release stuff is either things break in CI because a branch is x age, or folks have y code downstream with conditionals and weird logic which interacts with things in a way they want to have that we wouldn't advise15:55
JayFThe upgrade pain at places I've worked have always been 1) business-process related (e.g. they won't eat the downtime or accept the risk) or 2) patches making upgrading be a bunch of rebase hell and refactoring workflows to "fit" new upstream features that replaced downstream patches15:57
TheJuliaor features which people have created downstream and never bothered to upstream :(15:58
TheJuliaI'm *really* surprised how much that happens15:58
TheJuliabut... not eveyrone groks how to navigate Open Source15:58
JayFTheJulia: ...I have personally helped upstream downstream features that I'm nearly 100000% sure when they were written would've been rejected due to overly-strict project scoping or not-enough-review-time16:00
TheJuliaAnd sometimes they are, and sometimes we would have been "cool" or "cool, but maybe not at this moment"16:01
TheJuliaall a dialog which is needed16:01
TheJuliawhich relates to the current thing I'm writing actually16:01
opendevreviewMerged openstack/python-ironicclient master: Fix wrong assertion methods  https://review.opendev.org/c/openstack/python-ironicclient/+/85824016:19
opendevreviewMerged openstack/ironic master: Concurrent Distructive/Intensive ops limits  https://review.opendev.org/c/openstack/ironic/+/84000616:38
* TheJulia dances16:39
JayFnice16:40
TheJuliaI'm really surprised how many of my "eh, I'll do this because it makes a lot of sense to just do since I'm in that area for other reasons" stuff landed this cycle16:55
TheJulia*sigh* https://github.com/OpenStackweb/ironic-website/pull/5016:57
TheJuliaJayF: what is your gh username? we need to ensure you have rights on that repo16:58
JayFTheJulia: jayofdoom16:59
JayFhttps://github.com/jayofdoom16:59
JayFI need to update my personal readme there (and on my blog) to reflect the last week of news16:59
TheJuliagah, I need to email someone17:03
opendevreviewMerged openstack/ironic-tempest-plugin master: Add iDRAC Redfish sync boot mode test  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/84870918:54
iurygregoryTheJulia, do you mind if push the clean-up for ironic release notes in the same patch you pushed to add the prelude? 19:07
TheJuliaiurygregory: not at all19:08
iurygregoryTheJulia, ack =)19:08
TheJuliale sign, netlify19:47
TheJuliaerr, le sigh19:47
arne_wiebalckJayF: was there any feedback on your bare metal SIG mail? I did not see anything on the list, I think.19:49
JayFarne_wiebalck: zero response whatsoever :( 20:08
arne_wiebalckJayF: not unexpected20:09
JayFEh, you're right but it's still sad 20:09
arne_wiebalckJayF: we videos we did have a couple 100 views each so someone is watching them :)20:09
arne_wiebalck*the videos20:10
JayFgetting folks to actively participate is hard20:10
arne_wiebalckyes20:10
JayFI'm going to start broadcasting some of my work via streams either in twitch or yt20:10
JayFwe can see if ... less interactive ironic-adjacent videos do well20:10
arne_wiebalckok, great20:10
JayFbut I don't know what to do about the recurring sig. I'd suggest maybe keep the time, and do it even if we don't have a talk? 20:10
arne_wiebalckthe talk was the trigger to make people join20:11
JayFYeah, you're likely right.20:11
arne_wiebalckthere was very little else happening, but a talk sometimes triggered a discussion20:11
JayFWe can stoop to bribery, I can give free stickers to attendees lol20:11
arne_wiebalckand the ops feedback sessions were good20:11
arne_wiebalckwe had to add sessions20:11
JayFIt's sorta an inherently difficult concept, right?20:11
arne_wiebalckor metal pins to speakers20:12
JayFoperators are, almost everywhere, going to be overworked and understaffed20:12
arne_wiebalckyep20:12
JayFso getting them to participate is double-hard20:12
JayFI wonder if like, we could pitch it as a live helpdesk20:12
arne_wiebalckI mean it kind of worked to have one talk per month for a year or so20:12
JayFI mean, I'd be happy to spend that hour fielding questions about how to use ironic, how to solve problems, etc20:12
JayFarne_wiebalck: that's almost more talks/year than we have active contributors, it's just hard to sustain20:13
JayFmaybe a quarterly or something? IDK20:13
arne_wiebalckyeah, good idea: "come and bring your question, no matter which level"20:13
* JayF has to bail, he's got a meeting in 2 minutes20:13
JayFexactly20:13
JayFI'd enjoy that as someone on the "helping" side of the fence, too20:13
arne_wiebalckyes ... ok, to be continued :)20:13
JayFI mean, I log IRC and am always watching20:14
JayFfeel free to dump thoughts here or maybe even in a future-of-bm-sig etherpad20:14
arne_wiebalckok!20:14
stevebaker[m]good morning20:41
TheJuliagood morning stevebaker[m] 21:19
TheJuliaJayF: I wrapped the blog post and fixed the images.... so it should be good now. now to just get a volunteer for a zed post... :)21:42
*** scottsol[m] is now known as scottsol21:57
TheJuliaoh my inspector's sqlalchemy stuffs is going to be "fun"22:26
TheJuliaonly 15 unit tests pass right now22:26
TheJuliamostly the query/interaction model, so hopefully not horrible22:27
TheJuliamaybe... this *is* the time to migrate inspector into ironic22:46

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