[chef] Re: Triggering remote actions based on new nodes

[Bryan Baugher < >]

There isn't really a way in chef to have one node notify another (i.e. update something on that node or run chef-client), or have one node notify another node's resource.

The typical plan is to use chef's search feature to retrieve the information needed (i.e. get the ip addresses of nodes with the 'rails' role) to update firewall rules and have each node run on a regular interval (cron or daemon). So once you have bootstrapped your node it will be added within the interval to the firewall rules, SQL queries...

On Wed, Jun 27, 2012 at 3:55 PM, H. Wade Minter < " target="_blank"> > wrote:

Hi folks,

I've looked around to find answers on this, but haven't been successful, so apologies if it's a FAQ.

We're automating the buildout of a Rails application with Chef, migrating from a partially-implemented Puppet installation.  Things are going well, but we're reaching the endgame and would like to remove a few last manual steps.

We have tools in place to build and configure a node.  However, when a new node comes online, we have a few things that need to happen on other systems.  We need firewall rules updated on database and memcache servers, and we also need MySQL GRANT statements run to allow the node to connect to the database.

Is there a way to have that happen - to notify the memcache servers to update their firewall rules, run statements on the MySQL server, etc?  It seems like this problem would be solved in terms of helping automate scale out, but we haven't found the answer yet.

--Wade

____________________________________________________________
H. Wade Minter  |  Director of Engineering
TeamSnap: The smartest, easiest way to manage your team online
phone: 720.496.1053  |  fax: 815.550.2938
" target="_blank">   

--
-Bryan