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.
I used this to spin up a memsql cluster in AWS.
This requires knife, chef, and all the configuration needed to run it with AWS.
Also, requires you create knife data bags for your memsql license, a private key named memsql (remember to sub newlins in your json uploaded to your chef server, etc), a developer user, and a datacrunch user. If you look in the attributes/default.rb as well as the install.rb you can see where it uses the data bags, and corresponding naming structure. I used an encryption file too...
This will allow you to use the memsql_master_aggregator, memsql_child_aggregator, and memsql_leaf roles to create a functioning cluster. The install.rb will find your master by region, and auto-add them all into the cluster...
Lemme know if you have any more questions. I tested it end-to-end.