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

PUT /omicron-zone -- stop provisioning datasets! #6991

Open
smklein opened this issue Nov 5, 2024 · 1 comment · May be fixed by #7006
Open

PUT /omicron-zone -- stop provisioning datasets! #6991

smklein opened this issue Nov 5, 2024 · 1 comment · May be fixed by #7006
Assignees

Comments

@smklein
Copy link
Collaborator

smklein commented Nov 5, 2024

This is a historical artifact -- we used to provision datasets in the PUT /omicron-zone API, but should now be able to rely on reconfigurator's executor to provision necessary datasets. This issue tracks removing the logic in:

// TODO(https://github.com/oxidecomputer/omicron/issues/6043):
// - If these are the set of filesystems, we should also consider
// removing the ones which are not listed here.
// - It's probably worth sending a bulk request to the storage system,
// rather than requesting individual datasets.
for zone in &requested_zones.zones {
let Some(dataset_name) = zone.dataset_name() else {
continue;
};
// First, ensure the dataset exists
let dataset_id = zone.id.into_untyped_uuid();
self.inner
.storage
.upsert_filesystem(dataset_id, dataset_name)
.await?;
}

(Or, at least, replacing it with a check that these datasets exist)

@smklein smklein self-assigned this Nov 5, 2024
@smklein
Copy link
Collaborator Author

smklein commented Nov 5, 2024

Blocked by #6989 , otherwise RSS will presumably break if these lines are changed. RSS will need to request the datasets itself (this is fixed in #7000 )

@smklein smklein linked a pull request Nov 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant