| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2026-02-24 | |||
| 14:01:55 | amoralej | o/ | |
| 14:02:19 | jgilaber | I think we can start, feel free to add topics to the agenda | |
| 14:02:20 | jgilaber | #link https://etherpad.opendev.org/p/openstack-cyborg-irc-meeting#L45 | |
| 14:02:42 | jgilaber | first topic is from sean-k-mooney | |
| 14:02:45 | jgilaber | #topic linters | |
| 14:02:55 | sean-k-mooney | we can probly just note the titles | |
| 14:03:13 | sean-k-mooney | so the first topic is the usage and adoption of linters in cybrog | |
| 14:03:51 | sean-k-mooney | it is my intent to review quite alot of the code over the next 2 weeks and focus on impoving the automated linitign and code quality issues | |
| 14:04:10 | sean-k-mooney | first by adding pre-commit and tools we have used like codespell to the repo | |
| 14:04:37 | sean-k-mooney | then i woudl like to add ruff-check to and fix a set of liniting issues and finally adopt ruff for formating | |
| 14:05:12 | sean-k-mooney | my intent is to automat many of the sytel and correctness topics we currently have to review for and modernise the code base | |
| 14:05:25 | sean-k-mooney | i woudl like to know how others feel about this | |
| 14:06:06 | jgilaber | based on the experience of similar work for watcher I think it's worth it | |
| 14:06:26 | amoralej | +1 | |
| 14:06:26 | amoralej | did you try to run linters with current codebase? will it need many changes? | |
| 14:06:39 | sean-k-mooney | not yet and i expect yes | |
| 14:06:54 | sean-k-mooney | the side benifit of this is it will force me to read a large protion of the code base | |
| 14:07:05 | sean-k-mooney | and gain familarity with it by proxy | |
| 14:07:12 | amoralej | anyway, it will be needed, so it's a good time to go for it | |
| 14:07:57 | sean-k-mooney | ya i tought doing this early will reduce the firction for future work as we reviee the project adn start extending it | |
| 14:08:24 | sean-k-mooney | are there any other comments/request on this topic? | |
| 14:08:36 | sean-k-mooney | if not we can move to ci | |
| 14:09:12 | jgilaber | I think we can move on | |
| 14:09:46 | jgilaber | #topic ci jobs | |
| 14:10:08 | sean-k-mooney | so here there is some good news and bad neews | |
| 14:10:21 | sean-k-mooney | the good news is chandan fixed the ipv6 job last week | |
| 14:10:43 | sean-k-mooney | and that is merges so i plan to propes makign that voting again adn adding it to gate in the next few days | |
| 14:11:11 | sean-k-mooney | the bad news is the cherry-pick check is broken on the stable branches | |
| 14:11:43 | sean-k-mooney | so i have a fix on master https://review.opendev.org/c/openstack/cyborg/+/977793 that i need to revise but that will need to be backport before we can fully unblock the tempest plugin repo | |
| 14:12:03 | sean-k-mooney | we can cover that more in the review section | |
| 14:12:36 | sean-k-mooney | the other change i was plannign to make is to combine the bandite tox job into the pep8 one which will become oru single linter job | |
| 14:12:54 | sean-k-mooney | that will bring our jobs closer to how nova/watcher ectra are set up | |
| 14:13:16 | sean-k-mooney | the other gap i noticed is we currently do not have a greade job | |
| 14:13:31 | sean-k-mooney | im not sure we will have time to add one this cycle before RC1 | |
| 14:13:45 | sean-k-mooney | my question is do you think its ok to do that early in the next cycle | |
| 14:13:58 | sean-k-mooney | or shoudl we priorites adding grenade before rc1? | |
| 14:15:56 | jgilaber | I think it's ok to defer it, it's not likely we'll see many big code changes until next cycle | |
| 14:17:05 | sean-k-mooney | ack my current plan was to look at it after we cut rc1 | |
| 14:17:15 | sean-k-mooney | assumign other dont take a look before then | |
| 14:18:53 | sean-k-mooney | if there is no other comment on ci job priorty we could move to the last topic which is more of an annouchment | |
| 14:19:10 | jgilaber | let's move on | |
| 14:19:20 | jgilaber | #topic bugs | |
| 14:19:39 | sean-k-mooney | so as noted in the ether pad | |
| 14:19:42 | sean-k-mooney | i created https://launchpad.net/~cyborg-bug-team as an open team so folks interested in triage can now join that team | |
| 14:20:00 | sean-k-mooney | i have configure it in lauchpad as the bug supervior | |
| 14:20:21 | sean-k-mooney | meaning member of the team can add tag, set imporantce and update teh status of the bugs | |
| 14:20:59 | sean-k-mooney | i have configured it to expire membership after 12 months but you will get a renewal email and you will be auto appoved for joining/renewal | |
| 14:21:21 | sean-k-mooney | so if you plan to help with cyborg but triage please join that when you have time | |
| 14:21:31 | sean-k-mooney | thats all i had | |
| 14:21:58 | jgilaber | thanks sean-k-mooney, I just joined the team | |
| 14:22:18 | jgilaber | if there are no more comments, we can move to the reviews section | |
| 14:22:32 | jgilaber | #topic Reviews | |
| 14:22:49 | jgilaber | #link https://review.opendev.org/c/openstack/cyborg/+/970153/13 | |
| 14:23:46 | sean-k-mooney | so this review fixes a long running issue with cyborg where internally it used CONF.host for both the rpc endpoint and compute node placement resouce provider name | |
| 14:24:17 | sean-k-mooney | in some evns they are the saem such as in our downstream installer where we write the fqdn into /etc/hostname | |
| 14:24:54 | sean-k-mooney | btu in general they value of conf.HOST is the short hostnaem and the resouce provider name is the hypervior_hostname whch tends to be the fqdn | |
| 14:25:33 | sean-k-mooney | this change will try to use both to find the resouce provier, it add config options so you can explcity sepcify it | |
| 14:25:46 | sean-k-mooney | and has an expenital backoff and retry up to 3 times | |
| 14:25:59 | sean-k-mooney | i think this change is ready to merged | |
| 14:26:20 | sean-k-mooney | but wanted to ask if there are any other issue folks woudl liek me to adress before i proceed (after the meeting) | |
| 14:26:56 | jgilaber | +1 from me | |
| 14:26:58 | sean-k-mooney | jgilaber: and bogdando[m] have reviewd eariler versions fo this change. | |
| 14:28:10 | sean-k-mooney | if no ohter comments we can move on to the next review | |
| 14:28:25 | jgilaber | #link https://review.opendev.org/c/openstack/cyborg/+/977177/3 | |
| 14:28:56 | sean-k-mooney | so ^ is me shamelessly stealing the release guide i wrote for watcher adn cleaning it up slightly for cyborg | |
| 14:29:15 | sean-k-mooney | the tl;dr is it calls out the major release milesotnes and the actions we need to do for each of them | |
| 14:30:08 | sean-k-mooney | #link https://e7462b45848db14b956a-a5016a94c30782ba95b6339cf8a222f0.ssl.cf5.rackcdn.com/openstack/c0eb5346b7434ee6a0ec7583d0197a09/docs/contributor/release-guide.html | |
| 14:30:12 | sean-k-mooney | is a render | |
| 14:30:49 | sean-k-mooney | we can refine this more as we go but again if there are no concerns with that i propose to merge that after the meeting as a baseline | |
| 14:31:11 | jgilaber | I've only skimmed the patch but I can vouch for the usefulness of the guide as one of watcher's release liasons this last cycle | |
| 14:31:35 | sean-k-mooney | i can leave it open for a day or two if folks want to review more | |
| 14:31:46 | sean-k-mooney | i woudl like to merge the review after it this week | |
| 14:31:56 | sean-k-mooney | but we are not in a super rush here | |
| 14:32:11 | jgilaber | I'll review it after the meeting | |
| 14:32:36 | sean-k-mooney | ack ill check back then thrusday or friday adn respond to any feedback if there is any | |
| 14:33:21 | jgilaber | thanks, I think we can move to the next one | |
| 14:33:23 | jgilaber | #link https://review.opendev.org/c/openstack/cyborg/+/977020/3 | |
| 14:33:46 | sean-k-mooney | so the next review is the release note prelude | |
| 14:33:50 | sean-k-mooney | #link https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_dfc/openstack/dfcb37a19d884363afaee29efe3c877d/docs/unreleased.html | |
| 14:34:03 | sean-k-mooney | this will become the 2026.1 prelude when we cut the release | |
| 14:34:34 | sean-k-mooney | rlandy: suggested i add a refence to docuemantion so i added it in the last revision | |
| 14:35:03 | sean-k-mooney | im happy to refine it more if there is addtional feedback but i would like to merge this by the end of the week if no outstanding issues are raised | |
| 14:35:15 | rlandy | I'll review again | |
| 14:35:17 | sean-k-mooney | the hard deadlien for merging this is before rc1 | |
| 14:35:26 | sean-k-mooney | so we have 3 weeks | |
| 14:35:36 | sean-k-mooney | rlandy: ack thanks | |
| 14:37:00 | sean-k-mooney | the only ohter comment i have on that is we have the opertunity to add a marketing highlights as part of the release | |
| 14:37:27 | sean-k-mooney | i do not know if there is anythign we woudl ike to do in that regard but now is a good time to start thinking about that | |
| 14:38:08 | sean-k-mooney | i was thinkign fo reuseing the prelude to some degree adn put more of a focus into that for next cycle | |
| 14:38:37 | rlandy | +1 | |
| 14:39:56 | sean-k-mooney | lets keep moving ot get though the adgenda unless there is anything else on this topic. ^ is technially the last change we need for the release | |
| 14:40:53 | jgilaber | ack thanks sean-k-mooney | |
| 14:40:58 | jgilaber | next review | |
| 14:41:00 | jgilaber | #link https://review.opendev.org/c/openstack/cyborg/+/977083 | |
| 14:41:22 | sean-k-mooney | so ^ is a work in progress change that chandan has been working on | |
| 14:41:47 | sean-k-mooney | it is using a project https://github.com/snu-csl/nvmevirt | |
| 14:41:59 | sean-k-mooney | to provide a kernel module to emulate nvme devices | |
| 14:42:23 | sean-k-mooney | this we hope to use to test the pci driver and a future nvme/ssd driver | |
| 14:42:38 | sean-k-mooney | this is making good progress but need more work before it is ready | |
| 14:42:58 | sean-k-mooney | the next review in the list was https://review.opendev.org/c/openstack/project-config/+/977194 | |