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

Automate Omicron Provisioning Flow #1398

Open
smklein opened this issue Jul 12, 2022 · 0 comments
Open

Automate Omicron Provisioning Flow #1398

smklein opened this issue Jul 12, 2022 · 0 comments

Comments

@smklein
Copy link
Collaborator

smklein commented Jul 12, 2022

(Context: 7/12 IAM sync discussed this topic)

We've been adding a bunch of features - IdP integration, image generation, gateways + external IPs, IP pools, etc - which are all great features to have - but which requires some manual intervention to set properly within the context of a rack.

For local development, our advice has been "tweak config files, and re-package", or "remember to hit the right endpoints" on setup to make the rack usable. However, in the context of a "real" rack deployment, this isn't really a feasible option. We'd eventually like to:

  1. Create a set of packages with configurations that are known to be applicable, regardless of which rack it is deployed to
  2. Provide a mechanism - akin to first-time setup via the console - to ensure that all of these known-at-runtime configuration options are set. This could be an interactive program, something which consumes a config file, etc.

This issue tracks providing a program to perform the responsibilities of (2) - either as an interactive part of RSS, as a portion of early boot console setup, or even through a separate config file which we validate, to ensure all these necessary resources have been provided. The end-goal is to make it harder for users to spin up a control plane, and find that some fundamental configuration has not yet been correctly set.

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

No branches or pull requests

1 participant