| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2026-06-16 | |||
| 15:48:07 | opendevreview | Merged openstack/cyborg master: Remove broken image signature verification https://review.opendev.org/c/openstack/cyborg/+/991027 | |
| #openstack-cyborg - 2026-06-17 | |||
| 04:45:31 | rlandy | doodle created | |
| 12:37:38 | chandankumar | sean-k-mooney: Hello, feel free to merge https://review.opendev.org/q/topic:%22pci-sim%22, it looks from my end. | |
| 12:39:28 | sean-k-mooney | i was just posting a repsoce and basiclly asking if we were ok to investiage the things you noted once the inital patch was merged | |
| 12:40:01 | sean-k-mooney | so ok im not imitdaly seeign the reason the second pf didnt have vfs in your env | |
| 12:40:18 | sean-k-mooney | but its someitng ill do more testing with when i starte trying to use this in tempest | |
| 12:41:58 | sean-k-mooney | i have not really done baremental testing with this yet so there may be quirks that need to be worked out such as investiatign if we can supprot a mix of fake and realy device passhtough at the same time | |
| 12:41:59 | chandankumar | sounds good to investigate further on that | |
| 12:42:50 | chandankumar | But let;s get this series merge, it is too big to carry | |
| 12:43:26 | sean-k-mooney | the other thing that im condierign is addign a few debuging script to the devstack jobs, basically running lspci or virsh nodedev list as a post run playbook to collect soem extra host info for debugging later | |
| 12:43:47 | chandankumar | good idea, I will give a try with mix and see how it looks | |
| 12:43:51 | chandankumar | +1 | |
| 12:44:30 | sean-k-mooney | so with intel_iommu=off sriov and normal pci passhtough wont work | |
| 12:44:49 | sean-k-mooney | but if you set it to intel_iommu=on and iommu=pt | |
| 12:44:51 | sean-k-mooney | it might | |
| 12:45:25 | sean-k-mooney | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-parameters.txt#L2533 | |
| 12:46:05 | sean-k-mooney | ther is also noforce or soft we could explre fore the mixed case | |
| 12:47:08 | chandankumar | ah thank you for the link, it has so many options | |
| 12:47:31 | sean-k-mooney | ya, iommu=pt is what we use for dpdk and sriov on the same host | |
| 12:47:41 | sean-k-mooney | so i dont knwo if that woudl make it work | |
| 12:47:51 | sean-k-mooney | its somethign we can investigate in any case | |
| 12:48:11 | sean-k-mooney | for first party ci we wont have the mixed case so this is more for local dev | |
| 12:49:31 | sean-k-mooney | oh looks like intremap defualt ot on if the intel_iommu=on | |
| 12:50:12 | sean-k-mooney | if we figure out a combinaiton that works we can docuement it | |
| 12:52:31 | chandankumar | sure | |
| 12:54:48 | sean-k-mooney | https://paste.opendev.org/show/bYiLthWNUfK7OclB7HqW/ | |
| 12:54:55 | sean-k-mooney | that what nova is seing in ci by the way | |
| 12:55:11 | sean-k-mooney | so it is seeing the VFs on boht pfs | |
| 12:55:40 | sean-k-mooney | so im wonderinf if the is a short widnwos where tha tcan race or if it was somehtign local on your system form a prior run | |
| 12:55:55 | sean-k-mooney | one thin i tmay be is that i have not test with only cyborg enabeld and multiple pfs | |
| 12:56:07 | sean-k-mooney | so that the first time im goign to investigate | |
| 12:56:20 | sean-k-mooney | i have been testign with the pfs split between nova and cyborg | |
| 12:56:45 | sean-k-mooney | were you only allcoating them to cybrog locally. | |
| 12:57:37 | chandankumar | ENABLE_PCI_SIM=True | |
| 12:57:39 | chandankumar | # pci-sim topology: 2 fake PFs, 4 VFs each. | |
| 12:57:42 | chandankumar | # With both integrations enabled, PF0 VFs go to Nova and PF1 VFs to Cyborg. | |
| 12:57:43 | chandankumar | PCI_SIM_NUM_PFS=2 | |
| 12:57:45 | chandankumar | PCI_SIM_NUM_VFS=4 | |
| 12:57:47 | chandankumar | PCI_SIM_CONFIGURE_NOVA_PCI=True | |
| 12:57:49 | chandankumar | PCI_SIM_CONFIGURE_CYBORG_PCI=True | |
| 12:57:51 | chandankumar | PCI_SIM_ALLOW_UNSAFE_INTERRUPTS=True | |
| 12:58:04 | sean-k-mooney | ok that what i ws testing with as well | |
| 12:58:27 | sean-k-mooney | still i can build out some test cases for the diffent option adn see what breaks | |
| 12:59:04 | chandankumar | The error I hit earier while enabling cyborg then I hit while enabling both nova and cyborg | |
| 13:05:22 | sean-k-mooney | chandankumar: so my current todo list for that moduel was add the ablity to create mdevs, add the ablity to emulate an e1000 nic adn then possibel add the ablity to emulate an nvme device | |
| 13:05:52 | sean-k-mooney | the secodn two are more asperationall but i think ti woudl be possibel to do by reusing some of the nvmevirt work | |
| 13:06:26 | sean-k-mooney | but im not currently willing to commit to the latter in a short itme frame becasue that is very non tirival | |
| 13:07:03 | sean-k-mooney | addign the ablity for the PFs to supprot mdpy mdevs shoudl be realitivly simple | |
| 13:07:28 | sean-k-mooney | emulating a nic that works enough for neturon sriov testing is somewhere in between | |
| 13:07:44 | sean-k-mooney | we dont stricly need that but it is simpler then pretending to be a nvme device | |
| 13:31:29 | chandankumar | nmvevirt has no iommu group support On which I am kind of blocked to see nvme with in the guest . From pci-sim work, I think i can reuse some of your work to add the support there | |
| 13:32:23 | chandankumar | or I can do opposite, take some of the work from nvmevirt and add it into pci-sim | |
| 13:32:29 | chandankumar | But I need to think on that | |
| 13:33:02 | chandankumar | on another note, I was writting some tests to validate cyborg placemnt workflow with pci scenario test https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/992210 it might be useful | |
| 13:33:23 | chandankumar | I will update my above review with pci-sim work for the tempest tests | |
| 13:33:26 | chandankumar | brb | |
| 13:46:51 | sean-k-mooney | oh cool | |
| 13:47:35 | sean-k-mooney | ya i was plannign to focus on scenairo test to validate the vm lifecycle | |
| 13:47:50 | sean-k-mooney | so the placmeent reporting tests will complement that | |
| 14:02:44 | opendevreview | Merged openstack/cyborg master: devstack: add pci-sim fake SR-IOV PCI passthrough test fixture https://review.opendev.org/c/openstack/cyborg/+/989470 | |
| 14:02:46 | opendevreview | Merged openstack/cyborg master: Add pci-sim developer guide https://review.opendev.org/c/openstack/cyborg/+/991177 | |
| 14:55:44 | opendevreview | chandan kumar proposed openstack/cyborg master: Rename devstack CYBORG_CONF_FILE to CYBORG_CONF for consistency https://review.opendev.org/c/openstack/cyborg/+/979805 | |
| 14:55:45 | opendevreview | chandan kumar proposed openstack/cyborg master: Add NVMeVirt emulated NVMe device support for devstack https://review.opendev.org/c/openstack/cyborg/+/977083 | |
| 14:57:40 | opendevreview | chandan kumar proposed openstack/cyborg master: Add NVMeVirt emulated NVMe device support for devstack https://review.opendev.org/c/openstack/cyborg/+/977083 | |
| 15:30:27 | opendevreview | chandan kumar proposed openstack/cyborg master: Rename devstack CYBORG_CONF_FILE to CYBORG_CONF for consistency https://review.opendev.org/c/openstack/cyborg/+/979805 | |
| 15:30:28 | opendevreview | chandan kumar proposed openstack/cyborg master: Add NVMeVirt emulated NVMe device support for devstack https://review.opendev.org/c/openstack/cyborg/+/977083 | |
| #openstack-cyborg - 2026-06-18 | |||
| 05:26:39 | opendevreview | chandan kumar proposed openstack/cyborg master: Add NVMeVirt emulated NVMe device support for devstack https://review.opendev.org/c/openstack/cyborg/+/977083 | |
| 06:29:36 | opendevreview | chandan kumar proposed openstack/cyborg master: Add NVMeVirt emulated NVMe device support for devstack https://review.opendev.org/c/openstack/cyborg/+/977083 | |
| 07:13:56 | chandankumar | sean-k-mooney: https://123b844dd0bc940cd071-d2975a8f065f970ca29e743c021b8a36.ssl.cf1.rackcdn.com/openstack/5f698c9d53e44e52bbd22509f59b8b25/testr_results.html tempest test is working now with nvmevirt and pci-sim | |
| 07:30:58 | opendevreview | chandan kumar proposed openstack/cyborg-tempest-plugin master: [WIP] Add cyborg pci nvme test https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/979847 | |
| 07:32:38 | opendevreview | chandan kumar proposed openstack/cyborg-tempest-plugin master: [WIP] Add cyborg pci nvme test https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/979847 | |
| 07:40:13 | opendevreview | chandan kumar proposed openstack/cyborg-tempest-plugin master: [WIP] Add cyborg pci nvme test https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/979847 | |
| 07:40:47 | chandankumar | revived the old nvmevirt scenario tests, might not be ready for review, but seems to be working | |
| 07:41:08 | chandankumar | for pci-sim | |
| 07:44:13 | opendevreview | chandan kumar proposed openstack/cyborg-tempest-plugin master: [WIP] Add cyborg pci nvme test https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/979847 | |
| 10:02:03 | opendevreview | chandan kumar proposed openstack/cyborg-tempest-plugin master: [WIP] Add cyborg pci nvme test https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/979847 | |
| #openstack-cyborg - 2026-06-19 | |||
| 04:56:28 | opendevreview | chandan kumar proposed openstack/cyborg-specs master: Add generic NVMe driver spec with secure cleanup https://review.opendev.org/c/openstack/cyborg-specs/+/985349 | |
| 05:22:33 | opendevreview | chandan kumar proposed openstack/cyborg-specs master: Add generic NVMe driver spec with secure cleanup https://review.opendev.org/c/openstack/cyborg-specs/+/985349 | |
| #openstack-cyborg - 2026-06-22 | |||
| 06:09:32 | opendevreview | chandan kumar proposed openstack/cyborg-specs master: Add generic NVMe driver spec with secure cleanup https://review.opendev.org/c/openstack/cyborg-specs/+/985349 | |
| 09:44:19 | chandankumar | sean-k-mooney: Hello | |
| 09:44:29 | sean-k-mooney | o/ | |
| 09:44:32 | chandankumar | I wanted to discuss about nvme cleanup fallback strategy. | |
| 09:44:41 | chandankumar | In previous draft spec, we were checking whether the driver supports which of the cleaning strategy: nvme sanitize (CES, BES, OWS) or nvme format(SES2, SES1). If not then we can move it shred or dd. But shred or dd is not gurantee secure erase. | |
| 09:44:51 | chandankumar | Since In libvirt emuluted nvme, it supports SES2 and SES1. SES2 performs cypto erase | |
| 09:44:59 | chandankumar | It is the last cleaning strategy available for testing right now in our emulated env. | |
| 09:45:05 | sean-k-mooney | secure erase is not the goal | |
| 09:45:05 | chandankumar | Here is what I was thinking about new cleanup strategy: | |
| 09:45:16 | sean-k-mooney | cleaning is | |
| 09:45:22 | chandankumar | nvme sanitize (CES, BES, OWS) then nvme format(SES2) if not supported then move the device to error state and let' operator decide what to do that. | |
| 09:45:30 | sean-k-mooney | no | |
| 09:45:46 | sean-k-mooney | either we only suprpot device with sanitize | |
| 09:46:06 | sean-k-mooney | or we have a fallback that works for all devices | |
| 09:46:17 | sean-k-mooney | but its not ok for use to provision a device to a vm that we cant clean | |
| 09:46:28 | sean-k-mooney | we coudl use nvme format | |
| 09:46:49 | sean-k-mooney | but if the device will alwasy end up in error then we shoudl not allow ti to be managed by cybrog | |
| 09:47:42 | sean-k-mooney | also while we can have teird cleaning levels we should not fallback at runtime | |
| 09:48:35 | sean-k-mooney | we shoudl discover the clenaing supprot level and or allow specify the cleaning mode via the config but we shoudl only attpemt one method of cleaning in the runtime path | |
| 09:49:01 | sean-k-mooney | shread/dd woudl jusut overrite the entirly block device if we use that path | |
| 09:49:49 | sean-k-mooney | that is what we do for lvm volumes in cidner and nova | |
| 09:50:03 | chandankumar | Not all devices support nvme format also | |