Skip to content
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

Dataset accounting: VMM zone filesystems should be explicitly requested #6108

Open
smklein opened this issue Jul 17, 2024 · 1 comment
Open
Labels
nexus Related to nexus Sled Agent Related to the Per-Sled Configuration and Management storage Related to storage.

Comments

@smklein
Copy link
Collaborator

smklein commented Jul 17, 2024

Currently, the sled agent picks a random U.2 to hold the zone filesystem for instances:

let latest_disks = self
.storage
.get_latest_disks()
.await
.all_u2_mountpoints(ZONE_DATASET);
let root = latest_disks
.into_iter()
.choose(&mut rng)
.ok_or_else(|| Error::U2NotFound)?;

This, unfortunately, leaves nexus out-of-the-loop regarding space allocation within the zone dataset.

Nexus should be aware of where instances are provisioned to manage accounting explicitly.

@smklein smklein added storage Related to storage. Sled Agent Related to the Per-Sled Configuration and Management nexus Related to nexus labels Jul 17, 2024
@smklein
Copy link
Collaborator Author

smklein commented Jul 17, 2024

See also: #6109

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nexus Related to nexus Sled Agent Related to the Per-Sled Configuration and Management storage Related to storage.
Projects
None yet
Development

No branches or pull requests

1 participant