Hi, We use Puppet when I work and we've done a bit of orchestration with both Mcollective and Fabric. I'm very interested in using Ansible instead of Fabric since I've learned it can use Facter facts.
We have a mix of Solaris and Linux nodes, and for the Solaris nodes it looks like I need to set the path to sudo specifically for that to work with sudo_exe. This wasn't surprising as I had to do it with Fabric too. So my question is basically, what's the best way to do that globally for all the Solaris hosts? It seems like I could leverage a fact to do that, both Facter and Ansible itself have facts I could use with a conditional somehow. But where would I put that? Or would it be better to just have a separate inventory file for them and do it there? Another example is determining which environment (Dev/UAT/Prod) a host is in. That's a custom Facter fact we already set through Puppet, and seems like it would make sense to leverage that somehow. But the docs on the web site seem to indicate that it would be better to split my inventory into different files per environment. I like the idea of using the same facts to make decisions in Puppet and Asible, so we know we're working off the same data with both tools. Thanks, Rich -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/c1ad0e29-e1b0-4a31-957d-64d1458b22a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
