[chef] Re: Re: aws and chef do not play nice


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: Re: aws and chef do not play nice
  • Date: Wed, 20 Nov 2013 20:30:58 -0800


On Wednesday, November 20, 2013 at 8:24 PM, Morgan Blackthorne wrote:

Speaking of this, I noticed that private VPC nodes don't seem to have node['cloud'] or node['ec2'] defined. Is there a good workaround for this, to always force these attributes to get loaded on those nodes? I bake my own AMIs so if that helps, I'm fine with it.
The hints file Julian describes below takes care of this


On Wednesday, November 20, 2013, Julian C. Dunn wrote:
Part of the issue is that we have not yet found a reliable way in Ohai
to detect whether a machine is running in EC2. Hence the hints file.
However, creating the hints file in recipe code is not sufficient to
populate node['ec2'] because by that point, Ohai has already run.

You can create the hints file *before* you run Chef in a number of
ways, one of which is that "knife ec2 server create" will take a
--hint parameter.

- Julian



-- 
Daniel DeLeo
 




Archive powered by MHonArc 2.6.16.

§