[chef] How to set override attributes with "knife node edit"?


Chronological Thread 
  • From: Michael Stillwell < >
  • To:
  • Subject: [chef] How to set override attributes with "knife node edit"?
  • Date: Sun, 6 Mar 2011 20:08:10 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=BltRuhSlbaSFMZzfHdK8xh/NDOwG5qTAoIQIQ6SYQ9NkWYQnhNQqauxf9+8sLT7EeP ClK8Lg9ictWMzntvlrF7gTeMI5C3W/a+uTJh3OimyXKDtBpaVnphzDHeO8XHnohG82lI mmR8kL8z0hi58erGykeKPtEewf4vAgbdbuuD4=

I'm having trouble getting "knife node edit" to behave as expected.
I'm setting attributes on the key { "override": ... } within the JSON
data structure however my changes aren't picked up during chef-client
runs--indeed after running chef-client the attributes disappear from
the data structure.

That is, if I change, say, "override.foo.servers" and save the file
the change is persisted to opscode in some way (if I immediately
re-edit, I can see the change I made) however if I run chef-client on
the node, it ignores the change I made, and somehow arranges for it to
be deleted.

How do the precedence "namespaces" within the "knife node edit" JSON
data structure work? How do they correspond to attributes in the
opscode web interface? (These have no precedence setting I can see--if
I change something in the opscode interface, I am changing its
"normal", "override" or "default" value?)

I've read through

http://wiki.opscode.com/display/chef/Attributes

several times, but it doesn't explain what the "knife node edit" data
structure represents, and what will happen if you edit different
areas. (e.g. I assume editing the "automatic" section does nothing.)




Thanks,
Michael



Archive powered by MHonArc 2.6.16.

§