[chef] Re: Re: Extracting the nodes in an environment that contain a particular cookbook


Chronological Thread 
  • From: Fabien Delpierre < >
  • To: chef < >
  • Subject: [chef] Re: Re: Extracting the nodes in an environment that contain a particular cookbook
  • Date: Tue, 15 Sep 2015 15:41:32 -0400

Since you're using AWS, it might be easier to query the AWS API for those IP addresses and insert them into your Logstash config files using Chef templates. You'd just have to assign an IAM role to your EC2 instances that is allowed to query the API for that stuff.

On Tue, Sep 15, 2015 at 3:24 PM, ANGELA EBIRIM < " target="_blank"> > wrote:
Hi Fabien,

Thanks for all the useful responses!

I'm implementing a standalone logstash that will receive http logs from another logstash install, in the same environment, over tcp.

So from logstash A, the output config will be 
output
 {
tcp {
  port : 9090
  host: <ip address of logstash B>
 }
}

and on logstash B, the input config will be 
input 
 {
   port: 9090
   host: <ip address of logstash A>
   }
}

so the need is to find a way to programmatically deduce the ip addresses of the various nodes on which the logstash installs rest because our aws environments (dev) shut down each night and so the ip addresses will be different each time a new instance comes up.



Sent from iCloud
I don't know if there's an efficient way of searching for a specific cookbook across the run lists of all nodes, as I've never played with Chef's REST API, but there's probably a way. It's all a bit beyond what you'd normally do within a Chef cookbook, though, at least in my opinion. What are you trying to accomplish in the end?

On Tue, Sep 15, 2015 at 2:05 PM, ANGELA EBIRIM < " target="_blank"> > wrote:
Hello,

I'm hoping that someone could assist me.

I've got a situation in that I'm trying to find the nodes in an environment that contain a particular cookbook in it's run list.

How would I do this without using knife? I'm going to put it into a recipe.

Many thanks






Sent from iCloud





Archive powered by MHonArc 2.6.16.

§