-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for 'disabling' physical disks to prevent future allocations #3526
Conversation
@@ -312,6 +326,9 @@ CREATE TABLE IF NOT EXISTS omicron.public.physical_disk ( | |||
-- FK into the Sled table | |||
sled_id UUID NOT NULL, | |||
|
|||
-- Describes how the control plane manages this disk | |||
state omicron.public.physical_disk_state NOT NULL, | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO(me): add an index to look up all "draining" disks".
Also maybe update the terminology here to match #4719
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: I should use the term "deactivating" here, rather than "draining", because "draining" can refer to cooperative removal (e.g. in the context of draining instances from a sled)
During the update sync, we had an interesting discussion where we floated the following idea: Instead of storing the "State" in the disk itself, what if state was implied by presence in a blueprint? In this world:
I'm going to explore this space a bit more, since I think it would fundamentally change how the "disk state" is stored in the DB. |
Closing in favor of #5335 |
Part of #3480
Fixes #5153