CaaSP setup #103
Merged
CaaSP setup #103
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
Signed-off-by: Ricardo Dias <rdias@suse.com>
Signed-off-by: Ricardo Dias <rdias@suse.com>
Signed-off-by: Kai Wagner <kwagner@suse.com>
Closed
smithfarm
reviewed
Feb 17, 2020
smithfarm
reviewed
Feb 17, 2020
Signed-off-by: Kai Wagner <kwagner@suse.com>
|
I tested that this does not break either "ses5" or "ses6" deployments. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ricardo and I added the possibility to do a CaaSP deployment with sesdev.
You can now either just spawn a completely configured CaaSP environment for development purposes or you could also directly add rook+ceph on top of it.
Example:
sesdev create caasp4 caasp4(gives you just a CaaSP cluster)sesdev create caasp4 caasp4 --deploy-ses(gives you a CaaSP cluster with already rook+Ceph on top)`If you want to have multiple workers or master you could work with the
--rolesoption as follows:--roles="[master],[worker],[worker],[loadbalancer],[storage]"Signed-off-by: Kai Wagner kwagner@suse.com