[chef] Re: Re: Calling for Advice

[Jamie Winsor < >]

Mark,

Ranjib gave you an excellent response, IMO. I'd like to elaborate a bit to hopefully illustrate the concept a bit better.

You can create an encrypted data bag on each Chef server. Let's call this data bag "chef_site_credentials". In it you would have an entry for each remote Chef server. It would look like this:

{

"north_america": {

"client_name": "jamie",

"client_key": "SOME_PRIVATE_KEY",

"server_url": "https://na.riotgames.com/organizations/riot" <---- IMPORTANT: make sure this is SSL

},

"china": {

"client_name": "jamie",

"client_key": "SOME_PRIVATE_KEY",

"server_url": "https://na.riotgames.com/organizations/riot" <---- IMPORTANT: make sure this is SSL

}

}

You could then use an API client, like Ridley, to query the remote Chef server for the data that you want. You should hide all of this logic in an LWRP or a Library.

-- 

Jamie Winsor

@resetexistence

https://github.com/reset

On Thursday, May 16, 2013 at 4:48 PM, Ranjib Dey wrote:

you can create a common read only chefclient across all your chef servers and use it as part of the chef run (wrapped in an lwrp or library) to gather this information.

On Thu, May 16, 2013 at 4:12 PM, Mark Pimentel < " target="_blank"> > wrote:

We have a situation where we have multiple datacenters with OSS Chef Servers in each.

If anyone is in a similar situation, I am curious to know how would you get information about nodes in opposite sites?

Say I have a cookbook that needs to reference servers in their configurations that are in the opposite site?  Besides the very obvious of storing the info in some file local to the cookbook is there a more dynamic way to do this? 

--
Thanks,

Mark