This repository has been archived by the owner on Mar 22, 2021. It is now read-only.
Add support for cluster provisioning #15
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We break out the provisioning part into its own script so that we can more easily provision multiple hosts simultaneously. We also make sure that SSH is all set up so that users can just directly start SSH'ing between nodes.
|
It's probably worth looking at https://github.com/CentOS-PaaS-SIG/linch-pin at some point. I scanned the code, without knowing it well, but it seems OK to me. |
|
Yeah, good point on linch-pin. We'll probably have to do this when we want to add support for other provisioners. I opened #16 for this. Thanks for the lookover! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modify the spec to accomodate cluster provisioning. Add support for the new syntax in the parser and the testrunner. Test scripts can communicate with the nodes directly by hostname (the value specified in the
namekey), or by IP (e.g.RHCI_myhostname_IP).Closes: #12