-
Notifications
You must be signed in to change notification settings - Fork 573
Retrieve AWS metadata for multi-box environment #94
Comments
Seems like you want to setup a Storm cluster. :-) I am currently working on auto-deploying Storm clusters with Vagrant and Puppet -- and I hope I can open source it soon. The tool can already deploy locally (VirtualBox) as well as to AWS. Here are some pointers to get you started:
Note that you do not need the ZK servers to start before the Storm nodes. Storm is clever enough to retry until it works. One less thing to worry about :-) Hope that helps! |
Hi, I just opened sourced my implementation of same. Works on virtual box and aws vpc. We should maybe trade notes and create something even better? Check out my bitbucket account, qanderson. Sent from my iPhone On 04/07/2013, at 6:35, "Michael G. Noll" [email protected] wrote:
|
I'll take a look! I noticed you also used fpm to package Storm & Co. And I found already some similarities (and a few differences -- e.g. I am running a nodeless Puppet setup). More than happy to share/collaborate. |
@miguno I'm looking into your repositories to see how you made multi-machine provisioning at AWS. Can you point me to the right repo? |
@Y4Rvik I think your starting point for multi-machine AWS provisioning would be https://github.com/miguno/wirbelsturm. |
Hi, I have an older vagrant file that I used to setup a small cluster environment. I would like to try get this working on AWS now. Here is a snippet of the previous config:
Now I know the providers doesn't support any of the networking properties, however it would be good if you could extract the host names from the meta data and pass them to the provisioners, this way the provisioning scripts could configure the cluster setup correctly. This also implies some level of ordering. In the case above, zookeeper would need to come first, as its hostname would be important for the remaining nodes.
The text was updated successfully, but these errors were encountered: