Hello, all!
  Thank you very much for your helpful responses. Regarding Wirbelsturm,
even it looks quite appealing at the first glance, in my opinion it is a
little bit complex (
https://github.com/miguno/wirbelsturm/blob/master/docs/AWS.md) than the
initial storm-deploy. It is still in beta version and there are too many
steps that should be performed for configuring. Also you have to to install
ec2 cli utilities.
   Since I would like something to deploy my application fast, I will go
firstly with storm-deploy but I'll take into the consideration the
Wirbelsturm.
If you have successfully used  Wirbelsturm on Windows environment , please
let me know how complex was for you.
Thank you.
  Best regards,
  Florin




On Fri, Mar 28, 2014 at 12:46 AM, Sasi Panja <[email protected]> wrote:

> Hi Florin,
> The cluster consisted of 1 master, 1 zookeeper, and 5 workers (test env)
> and it took about 10 minutes for everything to be up and view  the UI
> console. The storm-deploy script was run from another ec2 machine running
> in the same zone.
> I was then able to run my topology in less than 2 minutes.
>
> As Marc mentioned, it might be worth to try Michael's Wirbelsturm script,
> which seems quite elegant and powerful from the github/blog documentation.
> -Sasi
>
>
> On Thu, Mar 27, 2014 at 4:15 AM, Marc Vaillant <[email protected]>wrote:
>
>> Hi Florin,
>>
>> I just wanted to suggest that you also look at Wirbelsturm by Michael
>> Noll as an alternative to storm-deploy
>> https://github.com/miguno/wirbelsturm.  I think that you will find it
>> more complete, better documented, and more mainstream because it uses
>> vagrant and puppet instead of pallet and jclouds.  I highly recommend
>> reading Michael's blog post about it:
>>
>> http://www.michael-noll.com/blog/2014/03/17/wirbelsturm-one-click-deploy-storm-kafka-clusters-with-vagrant-puppet
>>
>> Best,
>> Marc
>>
>> On Thu, Mar 27, 2014 at 10:19:24AM +0200, Spico Florin wrote:
>> > Hello, Sasi!
>> >   Thank your very much for your response.Due to the fact that I would
>> like to
>> > deploy also a Storm application on Amazon, it really helps to spare
>> time . If
>> > it possible, just as an information, do you have some measurement on
>> how much
>> > time did take the cluster to be up and running?
>> >
>> > Best regards,
>> >  Florin
>> >
>> >
>> > On Wed, Mar 26, 2014 at 8:36 PM, Sasi Panja <[email protected]>
>> wrote:
>> >
>> >
>> >     I was able to deploy and run 0.9.0-rc2  on EC2  using
>> https://github.com/
>> >     nathanmarz/storm-deploy
>> >
>> >     After following the instructions from the wiki and updating the
>> >     configuration files, the following command worked for me  :
>> >
>> >      lein deploy-storm --start --name yourclustername  --branch master
>> --commit
>> >     0.9.0-rc2
>> >
>> >     I am using   Leiningen 2.3.4
>> >
>> >     All the workers, master and zookkeeper servers were up and running
>> in the
>> >     cluster
>> >
>> >
>> ###########################################################################
>> >     #####
>> >
>> >     # CLUSTERS CONFIG FILE under storm-deploy/conf
>> >
>> >
>> ###########################################################################
>> >     #####
>> >
>> >     nimbus.image: "us-west-2/ami-ca2ca4fa"         #64-bit ubuntu
>> >     nimbus.hardware: "m1.xlarge"
>> >
>> >     supervisor.count: 5
>> >     supervisor.image: "us-west-2/ami-ca2ca4fa"         #64-bit ubuntu on
>> >     us-west-2
>> >     supervisor.hardware: "m1.xlarge"
>> >
>> >     zookeeper.count: 1
>> >     zookeeper.image: "us-west-2/ami-ca2ca4fa"         #64-bit ubuntu
>> >     zookeeper.hardware: "m1.large"
>> >
>> >
>> ###########################################################################
>> >     #####
>> >
>> >     config.clj under   ~/.pallet
>> >
>> >
>> ###########################################################################
>> >     #####
>> >
>> >     (defpallet
>> >
>> >       :services
>> >
>> >       {
>> >
>> >        :default {
>> >
>> >                  :blobstore-provider "aws-s3"
>> >
>> >                  :provider "aws-ec2"
>> >
>> >                  :environment {:user {:username "storm"  ; this must be
>> "storm"
>> >
>> >                                       :private-key-path
>> "/home/ubuntu/.ssh/
>> >     id_rsa"
>> >
>> >                                       :public-key-path
>> "/home/ubuntu/.ssh/
>> >     id_rsa.pub"}
>> >
>> >                                :aws-user-id "XXXXXXXX}
>> >
>> >                  :identity "XXXX"
>> >
>> >                  :credential "XXXXXX"
>> >
>> >                  :jclouds.regions "us-west-2"
>> >
>> >                  }
>> >
>> >         })
>> >
>> >     ----------------------------------------------------------------
>> >
>> >
>> >     -Sasi
>> >
>> >
>> >     On Wed, Mar 26, 2014 at 3:01 AM, Spico Florin <
>> [email protected]>
>> >     wrote:
>> >
>> >         Hello!
>> >           I would like to know what changes should be applied to the
>> >         storm-deploy script (https://github.com/nathanmarz/storm-deploy)
>> in
>> >         order to install it on Amazon?
>> >           Thank you in advance.
>> >           Regards,
>> >           Florin
>> >
>> >
>> >
>> >
>>
>
>

Reply via email to