Using NFS (facts in json files in a directory) would be convenient but we need the variables available before we run ansible (when NFS is not available) so we'd need to run another service (like redis) on the install node with a persistent store of the facts. There are also some notes in the docs about
redis client in EPEL being too old (also true for EL7?)
beta-status
can't use password while connecting to redis
After this is implemented we could probably give removing pull_variables.yml another shot ( #182 )
Another way would be to have a central store of the facts that the nodes can query when they run ansible-pull. This would remove some of the hacks we have, like discussed in https://github.com/CSC-IT-Center-for-Science/fgci-ansible/issues/182
I haven't looked into this or tested it but seems cleaner and could perhaps also provide some performance boost:
http://docs.ansible.com/ansible/playbooks_variables.html#fact-caching
Using NFS (facts in json files in a directory) would be convenient but we need the variables available before we run ansible (when NFS is not available) so we'd need to run another service (like redis) on the install node with a persistent store of the facts. There are also some notes in the docs about
After this is implemented we could probably give removing pull_variables.yml another shot ( #182 )