New user here trying to figure out the best way to convert our current
server provisioning system to Ansible. Our system uses approx. 5 different
attributes to provision each server and we have about 1,000 servers. I'm
wondering whether we could get by by using Ansible's built-in mechanism for
>
> I played around with 'flat file' variables and a dynamic inventory a while
> back;
> group variables seemed to override the inventory level ones.
>
> YMMV, check the precedence levels for vars for the version of Ansible
> you're running.
>
> On 20 J
Our current configuration management system stores hostnames and attributes
for each of our systems, including things like "project" and "site". I'd
like to use these attributes when determining which values to provision a
system with using ansible, just like Puppet does with hiera.
Right now
I posted a rather long post yesterday and it seems to have not yet been
approved. Others have. Is there a reason for this?
I would really hate to have to re-write it again...
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe
