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
In the context of the "Support Bundles" project, it is currently difficult for Nexus to answer the question "will a particular U.2 have enough space to store a support bundle of a particular size?".
More generally, Nexus may ask "If I provision a resource to a U.2, and I want it to have some minimum / maximum space, will it fit?
We need the following tools to answer this question:
Nexus needs to keep track of the expected quotas/reservations given to each U.2, and compare the usages of "all datasets on a zpool, so far" when making adjustments to the allocations.
It would also be extremely nice to have commands through omdb that can display these numbers, and give context on what they mean.
It considers the "zpool size usage" to be "the sum of all datasets on that pool". This currently only considers other Crucibles, so it's not a true picture of the world, but an approximate one:
In the context of the "Support Bundles" project, it is currently difficult for Nexus to answer the question "will a particular U.2 have enough space to store a support bundle of a particular size?".
More generally, Nexus may ask "If I provision a resource to a U.2, and I want it to have some minimum / maximum space, will it fit?
We need the following tools to answer this question:
It would also be extremely nice to have commands through omdb that can display these numbers, and give context on what they mean.
As prior art, the "region allocation" query for crucible accounts for some of this information: https://github.com/oxidecomputer/omicron/blob/main/nexus/db-queries/src/db/queries/region_allocation.rs
omicron/nexus/db-queries/src/db/queries/region_allocation.rs
Lines 121 to 125 in 89b998c
omicron/nexus/db-queries/src/db/queries/region_allocation.rs
Lines 175 to 178 in 89b998c
The text was updated successfully, but these errors were encountered: