We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be nice if we could rely on inventory for "datasets we observe", and the blueprint for "datasets we want to have".
There exists a dataset table that's kinda redundant with the blueprint information, but exists for historical reasons:
omicron/schema/crdb/dbinit.sql
Lines 559 to 604 in 15b4c45
We used to have a similar table for services, but got rid of it in favor of blueprints. It would be nice if we could do the same for datasets!
omicron.public.dataset
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be nice if we could rely on inventory for "datasets we observe", and the blueprint for "datasets we want to have".
There exists a dataset table that's kinda redundant with the blueprint information, but exists for historical reasons:
omicron/schema/crdb/dbinit.sql
Lines 559 to 604 in 15b4c45
We used to have a similar table for services, but got rid of it in favor of blueprints.
It would be nice if we could do the same for datasets!
omicron.public.dataset
records to look up Crucible socket addressesomicron.public.dataset
records to track Crucible space usageThe text was updated successfully, but these errors were encountered: