There are several situations when we do not want new VM instances to be placed on a certain sled:

1. when the operator or update/migrate program needs to drain a sled prior to SW/HW maintenance
2. when the migrate program wants to reserve the sled so that it has the expected capacity for VMs it's trying to migrate over
3. when the operator wants to reserve the sled to migrate in it a "noisy neighbor" from another sled

Tasks

• Backend implementation and API: [nexus] add sled provision state #4520
• Do we need to expose a read-only view of the provision state on the console?
  • We've decided that we'd like to wait to flesh out our fault management a bit before tackling this.
• Do we need to add support for setting provision state to the Oxide CLI?
  • This is handled automatically.