We also create debs for storm, and it works great for us. (We bundle all of the services for our system into one unified deb package, otherwise I’d post the deb setup.)
-Jeff On Apr 30, 2014, at 3:20 PM, Cody A. Ray <[email protected]> wrote: > We created debs and hosted on our own apt servers for our production deploys. > > I just tried helping someone get setup by using storm-deploy for the first > time. Ran into this issue: > https://github.com/nathanmarz/storm-deploy/issues/62. Tried the > 'update-clojure-jclouds' branch and it continued moving forward but hit a > brick wall with an "Unexpected Server Error" from AWS (via jclouds). Not sure > where to go next with storm-deploy other than downgrading java. > > Looked briefly at Wirbelsturm; long enough to find the book-long AWS > instructions: https://github.com/miguno/wirbelsturm/blob/master/docs/AWS.md. > Having to setup Route 53 and IAM users just for deploying a storm cluster > seemed like overkill, so didn't pursue further. > > -Cody > > > On Mon, Apr 14, 2014 at 9:10 AM, Rahul Patil at Amazon > <[email protected]> wrote: > Hello folks, > I see at least 3 tools that can be used to deploy a Storm cluster on EC2. > > 1. Storm deploy : https://github.com/nathanmarz/storm-deploy > 2. Wirbelsturm : https://github.com/miguno/wirbelsturm > 3. Storm deploy alternative : > https://github.com/KasperMadsen/storm-deploy-alternative > > If you have used any of the above tools, can you share your experiences? Are > there other tools you would recommend? Any gotchas with deploying Storm > applications that also use AWS SDK? > > Thanks in advance! > Rahul > > > > > > > > > > -- > Cody A. Ray, LEED AP > [email protected] > 215.501.7891
