[chef] RE: Re: Re: Re: Re: Private Chef: registering a client for an existing node


Chronological Thread 
  • From: "Fluke,James" < >
  • To: " " < >
  • Subject: [chef] RE: Re: Re: Re: Re: Private Chef: registering a client for an existing node
  • Date: Thu, 17 Jan 2013 17:30:01 +0000
  • Accept-language: en-US

I am using private Chef and I just found that I can remove the client and not the node, and then recreate the client VM just fine.

 

Jim

 

From: Daniel DeLeo [mailto: On Behalf Of Daniel DeLeo
Sent: Thursday, January 17, 2013 9:10 AM
To:
Subject: [chef] Re: Re: Re: Re: Private Chef: registering a client for an existing node

 

 

On Thursday, January 17, 2013 at 5:23 AM, Gourav Shah wrote:

 

No, that's the whole point :) And it does work with a "regular" open source Chef server, doesn't it?

 

 

Could you double check that?  I have been using the open source version of chef and as long as I remember, you must delete the node before registering with the same name.  

 

Thanks

Gourav

In Hosted Chef and Private Chef, clients get permission to update a node by virtue of creating it; clients otherwise have default permissions. This happens because the RBAC system tracks clients, nodes, etc. by internal unique identifiers and not the external ones (i.e., name). In the open source server, there is a simple check for matching name.

 

-- 

Daniel DeLeo

 




Archive powered by MHonArc 2.6.16.

§