- From: Hector Castro <
>
- To:
- Subject: [chef] Re: Re: Auto scaling with chef questions
- Date: Sun, 9 Dec 2012 16:05:17 -0500
Right now, we are using customized user data via the AS launch
configuration to insert instance IDs (collected from EC2's internal
metadata service) into the Chef node name.
--
Hector
On Fri, Dec 7, 2012 at 7:00 PM, Jeffrey Hulten
<
>
wrote:
>
In autoscaling groups you set a launch config which can contain a
>
first-run.json that you can include to the chef-client.
>
>
{ "run_list" : "role[my_service]" }
>
>
chef-client -j /etc/chef/first-run.json
>
>
--
>
Jeffrey Hulten
>
Principal Consultant at Automated Labs, LLC
>
>
206-853-5216
>
Skype: jeffhulten
>
>
On Dec 7, 2012, at 3:50 PM, Cassiano Leal wrote:
>
>
> I had been thinking about the very same thing for a while, but haven't had
>
> the time to run some tests.
>
>
>
> My guess so far is that every new machine that spins up will run
>
> chef-client, create a node and a client using the validator key and using
>
> the ec2-****** FQDN as client/node name. Have you tried running 'hostname
>
> -f' on an EC2 server?
>
>
>
> --
>
> Cassiano Leal
>
>
>
> On Friday, December 7, 2012 at 21:43, Bridger Larson wrote:
>
>
>
>> The company I am working for is moving to AWS. I want to be able to have
>
>> Chef pre-installed on our application server AMI’s so when they start up
>
>> they will be configured correctly.
>
>>
>
>> If one AMI can create many servers, how does the Chef client give them
>
>> different client names?
>
>> How does Chef know to remove them when the server is deleted?
>
>>
>
>> Thanks!
>
>> Bridger Larson
>
>
>
Archive powered by MHonArc 2.6.16.