| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2026-06-22 | |||
| 10:11:48 | chandankumar | nope rest of them I have address | |
| 10:11:59 | chandankumar | I will try to get it updated by eod or tomorrow morning | |
| 10:12:15 | sean-k-mooney | cool ill plan to take a look tomorow or wednesday so | |
| 10:12:36 | sean-k-mooney | assuming there are no other issues and we are mostly aligned we will probly merge it end ro week or early next week | |
| 10:18:22 | chandankumar | sounds good | |
| 10:26:45 | sean-k-mooney | so thinking about this i wonder if cypto erase need to be configurable. the block erase version of sanitize and format is actully more secure then cypto erase alone | |
| 10:26:58 | sean-k-mooney | so we could consider 2 tuneable | |
| 10:27:30 | sean-k-mooney | clear_mode=block|crypto clear_method=sanatize|zero | |
| 10:28:04 | sean-k-mooney | clear_mode=block|crypto|auto clear_method=sanatize|zero|auto | |
| 10:28:41 | sean-k-mooney | chandankumar: it really is 2 seperate question so i think that might be a better way to model it | |
| 10:29:12 | sean-k-mooney | chandankumar: apprenly there is also a nvme write-zeroes command | |
| 10:29:38 | sean-k-mooney | chandankumar: so we can use that instead of dd or shred for the zero fallback if supproted | |
| 10:30:49 | chandankumar | yes, The Write Zeroes command is used to set a range of logical blocks to zero. | |
| 10:31:31 | sean-k-mooney | yep but it can zeor the entire device and its doe by the cornoler rather then the cpu | |
| 10:32:04 | sean-k-mooney | so in zero mode waht we could do is delete all namespace, create 1 namespace that cover the entire device and then zero it with write-zeors | |
| 10:32:17 | sean-k-mooney | i also think we need to do that namespace reset in general | |
| 10:32:42 | sean-k-mooney | so as part of cleaning we will need to ensure we have restored teh defivce to havign 1 namespace that uses the entire device | |
| 10:33:10 | sean-k-mooney | in case the tenatn had reconfigured it to soemthing else | |
| 10:34:40 | chandankumar | sudo nvme id-ctrl /dev/nvme0n1 -H | grep -A 10 "oncs" | |
| 10:34:42 | chandankumar | oncs : 0xdf | |
| 10:34:44 | chandankumar | [12:12] : 0 Namespace Zeroes Not Supported | |
| 10:34:46 | chandankumar | [11:11] : 0 Maximum Write Zeroes with Deallocate Not Supported | |
| 10:34:48 | chandankumar | [10:10] : 0 All Fast Copy Not Supported | |
| 10:34:50 | chandankumar | [9:9] : 0 Copy Single Atomicity Not Supported | |
| 10:34:52 | chandankumar | [8:8] : 0 Copy Not Supported | |
| 10:34:54 | chandankumar | [7:7] : 0x1 Verify Supported | |
| 10:34:56 | chandankumar | [6:6] : 0x1 Timestamp Supported | |
| 10:34:58 | chandankumar | [5:5] : 0 Reservations Not Supported | |
| 10:35:00 | chandankumar | [4:4] : 0x1 Save and Select Supported | |
| 10:35:02 | chandankumar | [3:3] : 0x1 Write Zeroes Supported | |
| 10:36:24 | chandankumar | Let me read about this one | |
| 10:42:14 | chandankumar | current spec does not focus on namespace. | |
| 10:43:37 | sean-k-mooney | right that a gap we need to adress | |
| 10:43:42 | chandankumar | we need retrive all the namespace from the contoller, then delete all of them and create single namespace then perform nvme write zero | |
| 10:43:55 | chandankumar | Do we need to do it in the same one? Do a follow up on that? | |
| 10:44:58 | chandankumar | or just make a note, follow up during implementation | |
| 10:47:47 | sean-k-mooney | this need to be done in this spec | |
| 10:47:50 | sean-k-mooney | not as a followup | |
| 10:48:18 | chandankumar | ok | |
| 10:48:39 | sean-k-mooney | we need to ensure we provide the deivce in a standarized repoducabel state | |
| 10:48:46 | sean-k-mooney | regardless of what the previous user did to it | |
| 10:49:48 | sean-k-mooney | so 1 namespace for the entire device, cleared or previosu content and we shoudl likely also ensure that there are no encyption keys present but that might be somethign we can defer to the implemeation | |
| 10:53:39 | chandankumar | for sanitize, we donot need to worry about namespace, for write zeros, we can pull the namespace, delete all ns and create one, perform write zero | |
| 10:53:45 | chandankumar | one more question | |
| 10:55:17 | chandankumar | regarding config option, clear_mode=block, clear_method=sanitize, you have used pipe to specify all the option here just for example | |
| 10:55:49 | sean-k-mooney | yep that just me showitn the options of the enum | |
| 10:55:55 | chandankumar | ok, got it | |
| 10:56:11 | sean-k-mooney | so this is a summary of what iw was tahttign to you about with ai https://paste.opendev.org/show/bDKh5ZaFcfOv7lDGlLer/ | |
| 10:58:33 | chandankumar | ah good, I did not thought about passing via device_spec | |
| 10:58:45 | sean-k-mooney | i gave it your latest spec draft and asked it to codify the options we were discusion into a new section that you could include | |
| 10:59:01 | sean-k-mooney | well we need to set this per device | |
| 10:59:06 | sean-k-mooney | so that the simpler way to do that | |
| 10:59:16 | chandankumar | yup, it is much simpler | |
| 10:59:31 | sean-k-mooney | we may consider allowign this as a atibute via the api in the future | |
| 10:59:37 | sean-k-mooney | but for now lets keep it simple | |
| 11:00:42 | sean-k-mooney | https://paste.opendev.org/show/bDKh5ZaFcfOv7lDGlLer/ is not entirly correct in that cyborg wont do any driver binding | |
| 11:01:04 | sean-k-mooney | that shoudl happen when the qemu isntance is stopped/deleted by libvirt automaticlly | |
| 11:01:31 | sean-k-mooney | this is assuming managed=yes semantics | |
| 11:02:12 | sean-k-mooney | so cyborg will assume that we can just use nvmcli witht hedefivce and we cna declare all device driver binding out of scope | |
| 11:02:30 | sean-k-mooney | otherwise that sumamry is close to what i woudl write in the spec | |
| #openstack-cyborg - 2026-06-23 | |||
| 13:17:07 | opendevreview | sean mooney proposed openstack/cyborg-specs master: Add consistent and secure RBAC spec for Cyborg https://review.opendev.org/c/openstack/cyborg-specs/+/991932 | |
| 13:37:04 | opendevreview | Merged openstack/cyborg-specs master: Add consistent and secure RBAC spec for Cyborg https://review.opendev.org/c/openstack/cyborg-specs/+/991932 | |
| 13:53:08 | sean-k-mooney | fyi we will start the meeting at the top of the hour | |
| 14:01:28 | sean-k-mooney | #Start-Meeting | |
| 14:01:37 | sean-k-mooney | #start-meeting | |
| 14:01:51 | sean-k-mooney | ah no - | |
| 14:01:57 | opendevmeet | sean-k-mooney: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | |
| 14:01:57 | sean-k-mooney | #startmeeting | |
| 14:01:57 | raukadah | it should startmeeting cyborg with # | |
| 14:02:12 | sean-k-mooney | ping list sean-k-mooney amoralej bogdando jgilaber rlandy chandankumar | |
| 14:02:26 | sean-k-mooney | we will give everyone a minitue to join | |
| 14:02:28 | rlandy | o/ | |
| 14:02:31 | jgilaber | o/ | |
| 14:02:34 | chandankumar | o/ | |
| 14:02:49 | skovili | o/ | |
| 14:03:00 | sean-k-mooney | as alwasys if you have topic feel free to add them to the adgenda | |
| 14:03:04 | sean-k-mooney | #link https://etherpad.opendev.org/p/openstack-cyborg-irc-meeting | |
| 14:03:06 | chandankumar | sean-k-mooney: we need to re-run the command for start the meeting `#startmeeting cyborg` | |
| 14:03:06 | melwitt | I don't think the meetbot started it (have to give meeting name when starting) | |
| 14:03:27 | sean-k-mooney | oh right | |
| 14:03:35 | opendevmeet | The meeting name has been set to 'cyborg' | |
| 14:03:35 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 14:03:35 | opendevmeet | Meeting started Tue Jun 23 14:03:35 2026 UTC and is due to finish in 60 minutes. The chair is sean-k-mooney. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 14:03:35 | sean-k-mooney | #startmeeting cyborg | |
| 14:03:43 | sean-k-mooney | #link https://etherpad.opendev.org/p/openstack-cyborg-irc-meeting | |
| 14:04:22 | sean-k-mooney | i think we are all here now | |
| 14:04:29 | sean-k-mooney | so first topic | |
| 14:04:35 | sean-k-mooney | #topic abandoned specs | |
| 14:04:53 | amoralej | o/ | |
| 14:04:57 | sean-k-mooney | so i did a clean up of olad specs a while ago and i decied to continue that today | |
| 14:05:08 | sean-k-mooney | 3 specs of note | |
| 14:05:11 | sean-k-mooney | Refactor API Structure Proposal | |
| 14:05:19 | sean-k-mooney | #link https://review.opendev.org/c/openstack/cyborg-specs/+/841077/3/specs/zed/approved/refactor-api-structure.rst | |
| 14:05:27 | sean-k-mooney | Add NVIDIA MIG management spec | |
| 14:05:40 | sean-k-mooney | #link https://review.opendev.org/c/openstack/cyborg-specs/+/885778 | |
| 14:05:47 | sean-k-mooney | Add api to support change device vgpu_type | |
| 14:05:55 | sean-k-mooney | #link https://review.opendev.org/c/openstack/cyborg-specs/+/885439 | |
| 14:06:14 | sean-k-mooney | these are all 2-3 years old and while some of the fucntionaltiy or refactor may be desireable | |
| 14:06:38 | sean-k-mooney | i closed thse as i think we will need to aproch them form first principals | |
| 14:07:01 | sean-k-mooney | the nvidia mig management is actully kind fo superceaded | |