Originally, I was containing my vars within the roles, but after realizing
that those vars override everything else, instead, I only populate the
default/main.yml with vars inside the roles, just so things don't error,
and define everything else in my main group_vars.
So, in my setup, when I have vars that are global, I put them in
group_vars/all/*, then label them if there is more than one option.
e.g.
#file: group_vars/all/nfs_servers
---
nfs_exports:
git:
server: 1.1.1.1
export: /data/git
mount_point: /mnt/git
options: defaults,_netdev
media:
server: 1.1.1.1
export: /data/media
mount_point: /var/lib/media
options: defaults,_netdev
home_dirs:
server: 2.2.2.2
export: /data/home_dirs
mount_point: /home
options: defaults,_netdev
#file: group_vars/git_servers
---
nfs_mounts:
- git
#file: group_vars/desktops
---
nfs_mounts:
- home_dirs
- media
On Wednesday, December 2, 2015 at 4:20:21 PM UTC-5, Jason Morgan wrote:
>
> I am currently developing a Playbook consisting of a number of roles via
> include statements as show below:
>
> hosts: testing
> sudo: yes
> roles:
> - timezone
> - ntp
> - mariadb
> - nfs-server
>
> I would appreciate some advice of where to put all the varables for the
> server eg Database , NFS exports, Timezone etc Would they be added as vars:
> in the main playbook ? As vars under a host_vars directory ?
>
> Thanks Jason
>
--
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/e12e4106-285c-4d76-98d1-ddd7a3596850%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
