| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2026-03-30 | |||
| 19:14:50 | sean-k-mooney | 2024.1 is alreay unmaintaiend and we dont test upgrades form unmaineted branches | |
| 19:15:07 | sean-k-mooney | ya that | |
| 19:15:29 | sean-k-mooney | 2024.2 will be eol soon too | |
| 19:15:38 | gmaan | but greande job can be backported till 2025.1 (though 2024.2 is going to EOL soon) | |
| 19:15:55 | gmaan | yeah, I will say if it is more work then doing till 2025.2 is worth | |
| 19:16:05 | sean-k-mooney | ya so 2026.1 is my main focus and im ont againt 2025.2 or 2025.1 if it works | |
| 19:16:15 | gmaan | ++ indeed | |
| 19:17:07 | sean-k-mooney | gmaan: did the nodeset change merged for grenade by the way? | |
| 19:17:38 | gmaan | sean-k-mooney: I think not yet, let me ping dan also once he will be back | |
| 19:17:54 | sean-k-mooney | ack | |
| #openstack-cyborg - 2026-03-31 | |||
| 10:57:24 | opendevreview | Takashi Kajinami proposed openstack/cyborg-tempest-plugin master: Add stable/2026.1 job https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/982768 | |
| 13:38:36 | opendevreview | chandan kumar proposed openstack/cyborg master: Add NVMe DevStack development guide and local.conf template https://review.opendev.org/c/openstack/cyborg/+/982711 | |
| 13:39:08 | chandankumar | Hello all, Cyborg team meeting starts in 22 mins, Please add your here: https://etherpad.opendev.org/p/openstack-cyborg-irc-meeting#L45 | |
| 14:00:35 | chandankumar | Hello, who all are around for cyborg meeting? | |
| 14:00:46 | sean-k-mooney | o/ | |
| 14:00:53 | chandankumar | #startmeeting cyborg | |
| 14:00:53 | opendevmeet | Meeting started Tue Mar 31 14:00:53 2026 UTC and is due to finish in 60 minutes. The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 14:00:53 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 14:00:53 | opendevmeet | The meeting name has been set to 'cyborg' | |
| 14:01:14 | chandankumar | #courtesy ping rlandy bogdando[m] | |
| 14:01:33 | chandankumar | Feel free to add your topics to the agenda | |
| 14:01:42 | chandankumar | #link https://etherpad.opendev.org/p/openstack-cyborg-irc-meeting#L45 | |
| 14:03:19 | chandankumar | we have few topics today and less attendence due to holidays | |
| 14:03:24 | chandankumar | Let me start with first one | |
| 14:03:55 | chandankumar | #topic Dropping devstack_setup.rst in favor of devstack_nvme rst: Needs suggestion | |
| 14:04:05 | chandankumar | #link https://opendev.org/openstack/cyborg/src/branch/master/doc/source/contributor/devstack_setup.rst | |
| 14:04:26 | chandankumar | I am working on adding a fresh guide for cyborg nvme devstack setup https://review.opendev.org/c/openstack/cyborg/+/982711/2/doc/source/contributor/devstack_nvme.rst | |
| 14:04:30 | chandankumar | #link https://review.opendev.org/c/openstack/cyborg/+/982711/2/doc/source/contributor/devstack_nvme.rst | |
| 14:04:55 | chandankumar | Since devstack_setup.rst is quite old and we have similar content kind of in devstack_nvme.rst | |
| 14:05:13 | chandankumar | Do we want to drop the devstack_setup.rst in favor of devstack_nvme.rst? | |
| 14:05:20 | sean-k-mooney | in my opion no | |
| 14:05:32 | sean-k-mooney | i just started reviewing https://review.opendev.org/c/openstack/cyborg/+/982711/2/doc/source/contributor/devstack_nvme.rst | |
| 14:05:36 | sean-k-mooney | before the meeting | |
| 14:05:48 | chandankumar | https://review.opendev.org/c/openstack/cyborg/+/982711 provides https://review.opendev.org/c/openstack/cyborg/+/982711/2/devstack/local-conf | |
| 14:05:48 | sean-k-mooney | and there are a number of things i woudl perfer to change before proceedign with it | |
| 14:06:20 | sean-k-mooney | yep im ok with providing sample local.confs | |
| 14:06:43 | chandankumar | In that case, I will wait for the review comments. | |
| 14:06:47 | sean-k-mooney | the main devstack document shoud ljust descibe the basics fo deploying cyborg | |
| 14:07:17 | sean-k-mooney | then we shoudl have driver specific docs that explain how to use emulated or real hardware with devstack for each dirver | |
| 14:07:35 | sean-k-mooney | so to me they fufill diffent usecase | |
| 14:08:02 | sean-k-mooney | what i dont want to have to do is try and figureou out what parts to remove if im just working on the nvidia driver or pci driver | |
| 14:08:14 | sean-k-mooney | form the devstack_nvme doc | |
| 14:08:39 | sean-k-mooney | does that make sense | |
| 14:08:54 | chandankumar | yes, sounds good. | |
| 14:09:08 | sean-k-mooney | the other thing i woudl personally change is remove the use of virt-install and instead provide an example domain exml and use virsh define | |
| 14:09:28 | sean-k-mooney | the current mix of virsh install + virsh edit is a littel confusing and messy | |
| 14:09:42 | sean-k-mooney | as in something are done on the cli then we have to add the iommu eleemtns | |
| 14:10:18 | sean-k-mooney | idealy i woudl have a seperate doc for creating a development vm tahat we can cross refence and have the nvme guide focus on the compliation and cybrog configureation | |
| 14:11:14 | sean-k-mooney | so baiscly 3 docs 1 for optional vm creation, 1 for the geneeric devstack usage to deploy cyborg and a final one that docuemtn how to configure the nvme driver with real or fake nvme devices | |
| 14:12:11 | chandankumar | ok, these are good suggestions, it will make the docs experience cleaner. | |
| 14:12:16 | sean-k-mooney | https://review.opendev.org/c/openstack/cyborg/+/982711/2/doc/source/contributor/devstack_nvme.rst is currently covering 4 related but difernet topics | |
| 14:12:53 | sean-k-mooney | host config/vm creation, emulated deivce creation, devstack install. and finally using the nvme driver | |
| 14:12:57 | chandankumar | I will break the patch into 2 patches one for devstack with fresh instructions and another for nvme or fake driver with vs creation | |
| 14:12:59 | sean-k-mooney | well or pci driver currently | |
| 14:13:11 | sean-k-mooney | the lattter part probaly shoudl be in the user docs for the driver | |
| 14:13:49 | chandankumar | ok | |
| 14:14:02 | sean-k-mooney | ack hte tempest plugin and verifcaion part including the creation fo the device profile ectra proably shoudl be its own doc too | |
| 14:14:17 | sean-k-mooney | since that will be pretty commen for all drivers | |
| 14:14:28 | sean-k-mooney | and we shoudl avoid duplciating it | |
| 14:14:58 | sean-k-mooney | i can leave some of these comemnts in the review later but that the majority fo my feed back | |
| 14:15:18 | chandankumar | Ok, I will work on breaking it into different docs | |
| 14:15:29 | sean-k-mooney | content looks reasonable over all but the doc is covering to many topic today | |
| 14:15:41 | sean-k-mooney | cool ill re reivew when you revise it | |
| 14:15:51 | chandankumar | sure, thank you! | |
| 14:16:16 | chandankumar | Now moving to reviews since there is no other topic | |
| 14:16:20 | chandankumar | #topic reviews | |
| 14:16:31 | chandankumar | I was working on cleaning up python-cyborgclient | |
| 14:16:44 | chandankumar | proposed these two simple reviews | |
| 14:16:47 | chandankumar | #link 982246: Drop dead code common/http.py | https://review.opendev.org/c/openstack/python-cyborgclient/+/982246 | |
| 14:17:15 | chandankumar | common/http.py is dead code, not used anywhere in cyborgclient. | |
| 14:17:44 | chandankumar | and second on cleaning up unused deps | |
| 14:17:47 | chandankumar | # 982244: Cleanup requirements.txt unused packages | https://review.opendev.org/c/openstack/python-cyborgclient/+/982244 | |
| 14:17:47 | sean-k-mooney | i was going to ask have you cofnirmed its not used in horizon but we dont have a plugin | |
| 14:18:43 | chandankumar | https://github.com/openstack/python-cyborgclient/blob/master/cyborgclient/common/httpclient.py is used in the cyborgclient not http.py | |
| 14:19:22 | sean-k-mooney | https://minio-api.teim.app/zuul-logs/8bf/main/8bf05a369b744132ab643a1fdf5d17c3/code-review/review-report.html yep the ai review agrees | |
| 14:19:39 | sean-k-mooney | i think the removal shoudl be safe but ill verify that later | |
| 14:19:45 | sean-k-mooney | i think directionaly this is good | |
| 14:20:00 | sean-k-mooney | we will need a release note | |
| 14:20:29 | sean-k-mooney | otherwise i think the patch is fine. the cyborg client may be used by thirdparty external tools | |
| 14:20:48 | chandankumar | ah ok, will add a release note, good point about external tools | |
| 14:20:50 | sean-k-mooney | so we will need to do a major version bump when we release it | |
| 14:21:00 | sean-k-mooney | but i think that is fine | |
| 14:21:27 | sean-k-mooney | as for the requireme clean up i agree that also looks reasonabe. | |
| 14:21:45 | chandankumar | https://review.opendev.org/c/openstack/python-cyborgclient/+/982244/2/requirements.txt it drops cryptography | |
| 14:21:51 | sean-k-mooney | oslo.log we may revisit but in general the client "logs" via print statmetnt | |
| 14:22:20 | chandankumar | as we were discussing earlier, other deps might bring down cryptography, Do we still want to keep it? | |
| 14:22:34 | sean-k-mooney | if we are currently using python loging in teh cleint the correct fix woudl be to keep oslo.log and port the code to use it | |
| 14:22:46 | sean-k-mooney | chandankumar: no we only ist direct deps | |
| 14:23:03 | sean-k-mooney | so if our indirect deps pull it in (openstacksdk likely will) | |
| 14:23:09 | sean-k-mooney | then thats ok | |
| 14:23:28 | chandankumar | for oslo.log, I will keep it and port the code to use it in a seperate patch. | |
| 14:24:26 | chandankumar | that's it on review | |
| 14:24:30 | chandankumar | Moving to bugs now | |
| 14:24:39 | chandankumar | #topic bugs | |
| 14:24:52 | chandankumar | #link Remove deprecated HTTPClient and VerifiedHTTPSConnection: https://bugs.launchpad.net/python-cyborgclient/+bug/2146351 | |
| 14:25:35 | chandankumar | VerifiedHTTPSConnection is used only at https://github.com/openstack/python-cyborgclient/blob/dcab1011666bcb9fc0e0a6062db3b6badb843ce9/cyborgclient/common/httpclient.py#L91 | |
| 14:25:41 | sean-k-mooney | we should be using the httpclint form the sdk exlusively | |
| 14:25:52 | sean-k-mooney | pror to that we woudl have used the keystoneauth one directly | |
| 14:26:38 | chandankumar | Do you have the link to httpclient from the sdk? | |
| 14:26:58 | sean-k-mooney | we shoudl not be using it directly in most case we shoudl be using the sdk functionaltiy | |