| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2026-08-25 | |||
| 14:22:38 | sean-k-mooney | its effectvly only a 2 week delay if we are still happy with the direction | |
| 14:22:53 | chandankumar | great, I will update the status based on real hardware availability. | |
| 14:22:57 | chandankumar | in next meeting | |
| 14:23:32 | chandankumar | thank you, that's it on nvme | |
| 14:23:39 | chandankumar | one last thing on milestone 3 | |
| 14:24:07 | chandankumar | Marking the max microversion for the release | |
| 14:24:32 | sean-k-mooney | unless the manage mode feature lands it will be unchanged at 2.3 | |
| 14:24:43 | sean-k-mooney | so there isnt really much to do | |
| 14:24:59 | sean-k-mooney | https://docs.openstack.org/cyborg/latest/contributor/rest_api_version_history.html | |
| 14:24:59 | chandankumar | ok then we are good here | |
| 14:25:14 | sean-k-mooney | we only need to mark it really if we add on in a cycle | |
| 14:25:51 | chandankumar | ok | |
| 14:25:56 | sean-k-mooney | although we could backfile the markers for 2.2 and 2.3 | |
| 14:26:10 | sean-k-mooney | i suspect that was missed but that is just a docs change | |
| 14:26:17 | sean-k-mooney | so it can merge up until rc1 | |
| 14:26:41 | chandankumar | I will take a look how to add the marker for 2.2 and 2.3 | |
| 14:26:46 | chandankumar | ok | |
| 14:26:58 | sean-k-mooney | nova tend to update the marker even if there istne an api change in a relase | |
| 14:27:10 | sean-k-mooney | we can do that but im not sure if its needed | |
| 14:27:58 | chandankumar | ok | |
| 14:28:06 | sean-k-mooney | at least for a few years nova tended ot have 1 or more api versoin a release | |
| 14:29:07 | chandankumar | sean-k-mooney: can you share the patch from nova which does that after the meeting. | |
| 14:29:17 | sean-k-mooney | sure | |
| 14:29:31 | chandankumar | any more question on milestone 3? | |
| 14:30:01 | chandankumar | if not then moving to reviews section | |
| 14:30:07 | chandankumar | #topic Reviews | |
| 14:30:24 | chandankumar | Here is the link to ongoing reviews | |
| 14:30:28 | chandankumar | #link https://etherpad.opendev.org/p/cyborg-2026.2-status | |
| 14:30:37 | gamio | https://review.opendev.org/c/openstack/cyborg/+/1000240 device_addresses allow-list for the intel nic driver. | |
| 14:30:42 | chandankumar | we have already covered about 2026.2 spec implementations | |
| 14:30:52 | chandankumar | gamio: go ahead | |
| 14:30:55 | gamio | melwitt already gave +1. | |
| 14:31:07 | gamio | case-matching is a separate follow-up, bug 2163799. this patch stays as is. | |
| 14:31:18 | gamio | sean-k-mooney: no rush this week. if you get a chance before FF, that'd be great. | |
| 14:31:50 | sean-k-mooney | chandankumar: its just https://github.com/openstack/nova/commit/73724fef9a66c4df3d018e7368067f883b1ed9e2 but if you have more then 1 or two release where it does nto change it gets too long IMO | |
| 14:31:53 | chandankumar | I will take a look this one | |
| 14:32:06 | chandankumar | thank you sean-k-mooney | |
| 14:32:37 | sean-k-mooney | case-matching you mean case insentivity right | |
| 14:33:24 | gamio | sean-k-mooney: yes, case insensitivity. right now the compare is exact-case | |
| 14:33:31 | sean-k-mooney | the pci adress is actully an int value as are the vendor id and product id adn what we normally see is jut a sting represeation | |
| 14:33:40 | gamio | so a wrong-case or unmatched address is silently skipped instead of warned. | |
| 14:34:16 | sean-k-mooney | ya so eventually we shoudl just normlaise the vlues | |
| 14:34:23 | sean-k-mooney | by lowercasing them before comparing | |
| 14:34:35 | sean-k-mooney | there is no info encoded in teh casing | |
| 14:34:51 | gamio | sean-k-mooney: agreed, that's exactly what i had in mind for the follow-up. | |
| 14:34:58 | sean-k-mooney | ack | |
| 14:35:52 | chandankumar | I also need to check case matching in nvme config | |
| 14:36:13 | chandankumar | thank gamio! | |
| 14:36:25 | chandankumar | There are few open reviews from rlandy around docs | |
| 14:37:15 | chandankumar | let me paste it here | |
| 14:37:29 | chandankumar | #link https://review.opendev.org/c/openstack/cyborg/+/1001774 Improve installation guide index | |
| 14:37:38 | chandankumar | #link https://review.opendev.org/c/openstack/cyborg/+/1001779 Reorganize documentation landing page | |
| 14:37:41 | rlandy | thanks chandankumar | |
| 14:37:46 | chandankumar | #link https://review.opendev.org/c/openstack/cyborg/+/1001755 Move support matrix to admin docs | |
| 14:37:50 | rlandy | these can wait until after FF if needed | |
| 14:37:56 | chandankumar | #link https://review.opendev.org/c/openstack/cyborg/+/1001767 Add agentic scaffolding and contributor docs | |
| 14:37:59 | rlandy | just adding them here for reference | |
| 14:38:36 | chandankumar | ok, I have added them to cyborg-2026.2 status page | |
| 14:38:56 | chandankumar | Thank you rlandy for working on improving the docs. | |
| 14:39:06 | chandankumar | we will go over them. | |
| 14:39:15 | chandankumar | Anything you want to highlight on these patches | |
| 14:39:29 | sean-k-mooney | rlandy: https://review.opendev.org/c/openstack/cyborg/+/1001767 need a rebase | |
| 14:39:43 | rlandy | ok - will take care of that | |
| 14:39:51 | sean-k-mooney | eitehr on top of the latest of the parent or direclty onto master | |
| 14:40:04 | rlandy | ack | |
| 14:40:41 | rlandy | I assume the agentic one needs more work - I will bring that one back after FF for discussion | |
| 14:41:07 | sean-k-mooney | i have not looked at it yet | |
| 14:41:15 | sean-k-mooney | but ill let you know later today | |
| 14:41:43 | sean-k-mooney | skimming it its mostly the right shape | |
| 14:41:52 | sean-k-mooney | so it may be ok but we will see | |
| 14:42:53 | sean-k-mooney | thanks for pickign that up | |
| 14:43:17 | chandankumar | that's it from review, moving to next section | |
| 14:43:39 | chandankumar | #topic Bugs | |
| 14:43:46 | chandankumar | we have one bug from openstack-cyborg | |
| 14:43:58 | chandankumar | #link https://bugs.launchpad.net/openstack-cyborg/+bug/2163799 device_addresses: case-sensitive match silently mishandles wrong-case or absent entries (nic, gpu) | |
| 14:45:37 | chandankumar | I think this bug is related to the follow up improvement coming after https://review.opendev.org/c/openstack/cyborg/+/1000240 | |
| 14:47:22 | sean-k-mooney | yes | |
| 14:47:27 | gamio | plan is a small shared helper in accelerator/common/utils.py (same module as parse_address), used by nic and gpu for now. stacked on top of 1000240. | |
| 14:47:42 | gamio | not touching nvme yet, just keeping the helper generic enough for later. | |
| 14:48:16 | sean-k-mooney | we don tneed it for nvme | |
| 14:48:27 | sean-k-mooney | so this would only be a temproy helper i think | |
| 14:48:43 | sean-k-mooney | becuase the pci bus manager woudl elminat it | |
| 14:49:24 | chandankumar | the bug seems to be valid | |
| 14:49:27 | gamio | sean-k-mooney: right, makes sense given the direction toward device_spec | |
| 14:49:44 | sean-k-mooney | the util fucntion is fine to adress this in the short term | |
| 14:49:49 | sean-k-mooney | and for stable branches | |
| 14:50:03 | sean-k-mooney | but its a mini feature so i woudl triage this as wishlist | |
| 14:50:16 | chandankumar | status? | |
| 14:50:26 | sean-k-mooney | it impvoes the ux but the fact its case sensitive todya is not by itself a bug | |
| 14:50:32 | sean-k-mooney | but this is a ux improvment | |
| 14:50:48 | sean-k-mooney | and its backward compatbale so i think we wuld backprot this | |
| 14:51:13 | sean-k-mooney | chandankumar: triaged and wishlist woudl be my assesment | |
| 14:51:26 | chandankumar | Done, thank you! | |
| 14:51:40 | sean-k-mooney | gamio: i dont think we need to log a warning | |
| 14:51:51 | sean-k-mooney | either we supprot case insentitive or we dont | |
| 14:52:12 | sean-k-mooney | if we supprot it then we shoudl not warn if we dont then the silent ignore is not really a bug | |
| 14:52:38 | sean-k-mooney | we can chat about that on the review | |
| 14:52:42 | chandankumar | ok | |
| 14:52:56 | gamio | sean-k-mooney: got it, no warning either way then. just the case-insensitive compare. that simplifies the follow-up nicely. | |
| 14:53:43 | sean-k-mooney | case inssestive compare and we proably want to normalise the value in the db to lowercase | |