I'm currently playing with chef to evaluate whether or not such a configuration tool might help us in our *nix-based environment.
For the last few days I'm struggling with one problem I can't find a solution for. Basically, I have 2 private network ranges 192.168.1.0/24 and 192.168.2.0/24. There is a Server (Ubuntu 14.04.4 LTS) having access to both networks (192.168.1.1/24 on em1 and 192.168.2.1/24 on em2) which is running the chef-server.
As far as I understand, chef will listen on the interface which has the default route configured for (here 192.168.1.1 on em1). However, I want chef to watch over the servers on both networks.
When I bootstrap to Servers on 192.168.2.0/24, the client gets installed but there is no response from the client because the server calls itself 192.168.1.1 which is not visible to 192.168.2.0/24 (after all it's just a common subnet).
Is there a way to let chef listen on both interfaces (e.g. something like 'listen on 0.0.0.0/0')? I've searched the whole net but only found solutions for the underlying services like bookshelf. Do you have any advice on how to realize the configuration management in such an environment?