[chef] Re: Re: Re: Re: How to handle the elastic_ip associate recipe to finish up smoothly?


Chronological Thread 
  • From: Sachin Sagar Rai < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: How to handle the elastic_ip associate recipe to finish up smoothly?
  • Date: Sat, 7 Jul 2012 19:01:08 +0545

@JD, thanks for the reply n ur bootstrap gist

I looked at it. But my question about the ssh hanging when elastic_ip is attached is not answered?

Or am I getting it wrong?

-------------------------------------------
@millisami
~ Sachin Sagar Rai
Ruby on Rails Developer
http://tfm.com.np
http://nepalonrails.tumblr.com
Sent with Sparrow

On Saturday, July 7, 2012 at 1:45 AM, JD Harrington wrote:

On Fri, Jul 6, 2012 at 8:27 PM, Sachin Sagar Rai < "> > wrote:
Anybody, any pointers?

I use a custom bootstrap that runs `chef-client --once --daemonize`. I
ended up doing this because my recipe to launch new MySQL slaves
currently requires copying ~150GB of data from a single EBS volume
created from a snapshot onto a newly created EBS RAID set, which can
take a few hours and my SSH connections were timing out. But, this
seems like it would work in this scenario as well.

I call `knife ec2 server create` from a wrapper script which sets
ROLES and ENVIRONMENT which are used in this template. That's a bit
hacky and there's probably a better way to do this, but it's working
for me for now.

The downside to this is that you lose the in-line output from
chef-client, but it's easy to ssh into the machine and tail
/var/log/chef.log to watch it's progress.





Archive powered by MHonArc 2.6.16.

§