-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Documentation/design: add launch design #51
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
Documentation/design: add launch design #51
Conversation
78cc555 to
9d58683
Compare
Documentation/design/launchphase.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason why? As today the tectonic installer is idempotent right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
today
installer/installer/pkg/workflow/install.go
Lines 129 to 134 in ae41b0a
| func installTNCCNAMEStep(m *metadata) error { | |
| if !clusterIsBootstrapped(m.clusterDir) { | |
| return createTNCCNAME(m) | |
| } | |
| return nil | |
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not a requirement as we discussed previously. If the launch errors on re-run, it is acceptable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As today the tectonic installer is idempotent right?
It is most definitely not idempotent. Running the installer a second time is one of the best ways to screw up your cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did it couple times when I came back to my terminal from interruption, didn't remember seeing errors. Anyway whatever is easier is fine to me.
Documentation/design/launchphase.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Th" -> "The". And you can probably drop the /.
9d58683 to
b111829
Compare
yifan-gu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
The ".ign" suffix is sufficient to identify these as ignition filenames. The old filenames were from 461ff5f (cli: add support for user ignition files, 2018-03-23, coreos/tectonic-installer#3120), which does not motivate the "ingition-" prefix. This gets us closer to the filenames discussed in bf830cc (Documentation/design: add prepare design, 2018-07-11, openshift#50) and b111829 (Documentation/design: add launch design, 2018-07-11, openshift#51).
add current profile annotations to CVO manifests
This should add support for a list of env vars for the API key, and can be used for other variables in the future. Signed-off-by: wolf <[email protected]> Co-authored-by: wolf <[email protected]>
This should add support for a list of env vars for the API key, and can be used for other variables in the future. Signed-off-by: wolf <[email protected]> Co-authored-by: wolf <[email protected]>
Add design doc for launch step.
Also includes detail on bootstrap cluster flow decided in Option B