You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably blocked on #3526, which I believe is adding physical disk policies described in RFD 457. Once we have this, the blueprint planner will need to make sure that:
it doesn't try to put the dataset for any other kind of Omicron zone (like CockroachDB or Clickhouse or DNS) onto a zpool whose disk has a policy other than "in-service" (will be resolved by [nexus] Remove zones on expunged disks #5599)
once we add the zone's (transient) root filesystem to the zone's config ([nexus] Make nexus aware of zone filesystems #5050), the planner will also need to identify zones whose root filesystem is on one of these disks and replace it (i.e., write a new config with a root filesystem that's elsewhere) and we'll need to make sure that sled agent does the right thing with that
The text was updated successfully, but these errors were encountered:
…5601)
Previously, the planner placed Crucible zones on zpools unconditionally.
Now, we respect the policy and state of disks to
limit which disks are targets to receive these zones.
Partial fix of #5372
Expunges zones for which the corresponding physical disk, holding
durable data, has been removed.
A follow-up PR will be necessary to expunge zones which have had their
transient zone filesystems removed,
but Nexus is not yet aware of where zone placement decisions are made.
Partial fix of #5372
This is probably blocked on #3526, which I believe is adding physical disk policies described in RFD 457. Once we have this, the blueprint planner will need to make sure that:
The text was updated successfully, but these errors were encountered: