ec2 attributes

Jose_Guilherme_Vanz · April 16, 2015, 11:09am

Hi

I’m configuring an AWS auto scaling group in my infrastructure. Now, I am
writing a script to install and configure chef-client in the ec2 instances
launched automatically.

When I run the chef-client first time, it find my recipes and try to run
them. Some of the recipes uses attributes from ec2 (e.g.
node[‘ec2’][‘instance_id’] ). But this attribute does not exist in the
instance. Some guy s in the irc channel told me to rerun ohai to reload the
attributes. For this, I added the following code in the recipe:

gist.github.com

https://gist.github.com/jvanz/d8b73de8a0d4457e11e7

gistfile1.rb

ohai "reload" do                                                                                 
    action :nothing 
    plugin 'ec2'
end.run_action(:reload)

But the problem persists. Is This what I should do?

Peter_Burkholder3 · April 16, 2015, 12:27pm

The node needs a 'hint' that it's in EC2. Namely this:

mkdir -p /etc/chef/ohai/hints
touch /etc/chef/ohai/hints/ec2.json

then run chef-client and ohai will find all ec2 facts.

--Peter

On Thu, Apr 16, 2015 at 7:09 AM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

Hi

I'm configuring an AWS auto scaling group in my infrastructure. Now, I am
writing a script to install and configure chef-client in the ec2 instances
launched automatically.

When I run the chef-client first time, it find my recipes and try to run
them. Some of the recipes uses attributes from ec2 (e.g.
node['ec2']['instance_id'] ). But this attribute does not exist in the
instance. Some guy s in the irc channel told me to rerun ohai to reload the
attributes. For this, I added the following code in the recipe:

ohai reload · GitHub

But the problem persists. Is This what I should do?

--

Peter Burkholder — Customer Success Engineer

Unavailability: No travel/PTO in April

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

Yoshi_Spendiff · April 16, 2015, 3:15pm

It's worth knowing that if you use knife ec2 to create instances then it
makes the hint file for you, which is possibly why you never knew about it.

On Thu, Apr 16, 2015 at 5:27 AM, Peter Burkholder pburkholder@chef.io
wrote:

The node needs a 'hint' that it's in EC2. Namely this:

mkdir -p /etc/chef/ohai/hints
touch /etc/chef/ohai/hints/ec2.json

then run chef-client and ohai will find all ec2 facts.

--Peter

On Thu, Apr 16, 2015 at 7:09 AM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

Hi

I'm configuring an AWS auto scaling group in my infrastructure. Now, I am
writing a script to install and configure chef-client in the ec2 instances
launched automatically.

When I run the chef-client first time, it find my recipes and try to run
them. Some of the recipes uses attributes from ec2 (e.g.
node['ec2']['instance_id'] ). But this attribute does not exist in the
instance. Some guy s in the irc channel told me to rerun ohai to reload the
attributes. For this, I added the following code in the recipe:

ohai reload · GitHub

But the problem persists. Is This what I should do?

--

Peter Burkholder — Customer Success Engineer

Unavailability: No travel/PTO in April

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

--
Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.com

Jose_Guilherme_Vanz · April 16, 2015, 7:23pm

I cannot use knife ec2. The instance is started by my auto scaling group.
Anyway, the instructions sent by Peter solved my problem

Thank you

On Thu, Apr 16, 2015 at 12:16 PM Yoshi Spendiff <
yoshi.spendiff@indochino.com> wrote:

It's worth knowing that if you use knife ec2 to create instances then it
makes the hint file for you, which is possibly why you never knew about it.

On Thu, Apr 16, 2015 at 5:27 AM, Peter Burkholder pburkholder@chef.io
wrote:

The node needs a 'hint' that it's in EC2. Namely this:

mkdir -p /etc/chef/ohai/hints
touch /etc/chef/ohai/hints/ec2.json

then run chef-client and ohai will find all ec2 facts.

--Peter

On Thu, Apr 16, 2015 at 7:09 AM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

Hi

I'm configuring an AWS auto scaling group in my infrastructure. Now, I
am writing a script to install and configure chef-client in the ec2
instances launched automatically.

When I run the chef-client first time, it find my recipes and try to run
them. Some of the recipes uses attributes from ec2 (e.g.
node['ec2']['instance_id'] ). But this attribute does not exist in the
instance. Some guy s in the irc channel told me to rerun ohai to reload the
attributes. For this, I added the following code in the recipe:

ohai reload · GitHub

But the problem persists. Is This what I should do?

--

Peter Burkholder — Customer Success Engineer

Unavailability: No travel/PTO in April

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

--
Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.com

Morgan_Blackthorne · April 16, 2015, 7:44pm

If you're doing it via autoscaling, you probably want to bake some
automated registration into your AMI. At which point, I would suggest
baking the hint file into said AMI as well.

--
~~ StormeRider ~~

"Every world needs its heroes [...] They inspire us to be better than we
are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Thu, Apr 16, 2015 at 12:23 PM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

I cannot use knife ec2. The instance is started by my auto scaling group.
Anyway, the instructions sent by Peter solved my problem

Thank you

On Thu, Apr 16, 2015 at 12:16 PM Yoshi Spendiff <
yoshi.spendiff@indochino.com> wrote:

It's worth knowing that if you use knife ec2 to create instances then it
makes the hint file for you, which is possibly why you never knew about it.

On Thu, Apr 16, 2015 at 5:27 AM, Peter Burkholder pburkholder@chef.io
wrote:

The node needs a 'hint' that it's in EC2. Namely this:

mkdir -p /etc/chef/ohai/hints
touch /etc/chef/ohai/hints/ec2.json

then run chef-client and ohai will find all ec2 facts.

--Peter

On Thu, Apr 16, 2015 at 7:09 AM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

Hi

I'm configuring an AWS auto scaling group in my infrastructure. Now, I
am writing a script to install and configure chef-client in the ec2
instances launched automatically.

When I run the chef-client first time, it find my recipes and try to
run them. Some of the recipes uses attributes from ec2 (e.g.
node['ec2']['instance_id'] ). But this attribute does not exist in the
instance. Some guy s in the irc channel told me to rerun ohai to reload the
attributes. For this, I added the following code in the recipe:

ohai reload · GitHub

But the problem persists. Is This what I should do?

--

Peter Burkholder — Customer Success Engineer

Unavailability: No travel/PTO in April

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

--
Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.com

Jose_Guilherme_Vanz · April 17, 2015, 1:05am

Yeah, is a good idea.

Thank you

On Thu, Apr 16, 2015 at 4:44 PM Morgan Blackthorne stormerider@gmail.com
wrote:

If you're doing it via autoscaling, you probably want to bake some
automated registration into your AMI. At which point, I would suggest
baking the hint file into said AMI as well.

--
~~ StormeRider ~~

"Every world needs its heroes [...] They inspire us to be better than we
are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Thu, Apr 16, 2015 at 12:23 PM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

I cannot use knife ec2. The instance is started by my auto scaling group.
Anyway, the instructions sent by Peter solved my problem

Thank you

On Thu, Apr 16, 2015 at 12:16 PM Yoshi Spendiff <
yoshi.spendiff@indochino.com> wrote:

It's worth knowing that if you use knife ec2 to create instances then it
makes the hint file for you, which is possibly why you never knew about it.

On Thu, Apr 16, 2015 at 5:27 AM, Peter Burkholder pburkholder@chef.io
wrote:

The node needs a 'hint' that it's in EC2. Namely this:

mkdir -p /etc/chef/ohai/hints
touch /etc/chef/ohai/hints/ec2.json

then run chef-client and ohai will find all ec2 facts.

--Peter

On Thu, Apr 16, 2015 at 7:09 AM, José Guilherme Vanz <
guilherme.sft@gmail.com> wrote:

Hi

I'm configuring an AWS auto scaling group in my infrastructure. Now, I
am writing a script to install and configure chef-client in the ec2
instances launched automatically.

When I run the chef-client first time, it find my recipes and try to
run them. Some of the recipes uses attributes from ec2 (e.g.
node['ec2']['instance_id'] ). But this attribute does not exist in the
instance. Some guy s in the irc channel told me to rerun ohai to reload the
attributes. For this, I added the following code in the recipe:

ohai reload · GitHub

But the problem persists. Is This what I should do?

--

Peter Burkholder — Customer Success Engineer

Unavailability: No travel/PTO in April

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

--
Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.com

Topic		Replies	Views
Ohai attributes in Default attributes Chef Infra (archive)	4	1100	March 18, 2013
Custom Ohai Plugins in attributes/default.rb Chef Infra (archive)	2	329	February 2, 2015
Reload attributes file Chef Infra (archive)	0	491	February 17, 2012
How to set node attributes when creating ec2 instances? Chef Infra (archive)	4	432	May 26, 2012
Chef Client and Attribs Chef Infra (archive)	0	271	October 24, 2014

ec2 attributes

Related Topics