Easy Multi-Node Configuration with Chef and Consul
One of the questions Chef users often ask is "How can I orchestrate Chef runs across multiple nodes, where node A depends on something that happens on node B." The standard solution has been to store the data temporarily on the Chef server where the dependent nodes can reach it.
Instead of a kludgy workaround that passes state data between machines, what if you had an always on, always up-to-date service catalog showing the IP address, port and health of every service on your network. You can even store arbitrary data in Consul for Chef to consume during runs.
Take the hassle out of multi-node configuration management with Consul and Chef.