Re: [Rdo-list] Configuration publishing, organisation of the repo

- rdobase make sense, but I still like to have stuff more split. See https://github.com/gluster/gluster.org_ansible_configuration/tree/master/... for what i use (I should also place one for ssh keys) and https://github.com/gluster/gluster.org_ansible_configuration/blob/master/...

- I would also like to discuss if we can pin dependencies (all or just part of them), either by tagging version, or using branch. I am not sure ansible-galaxy do support it now (or at least fully support what I want), but I am quite sure this is planned (as it was discussed during a meeting last month in London). So we should maybe investigate that model.

From looking at the documentation [2], it looks like it is possible to

Also, for various work reasons, I was also looking at transitioning my duty and part of the project (better now than later) to a new member of my team, as I do have some more urgent stuff to finish, and need to scale myself (so i figured that it would be better to do that in a project where he wouldn't be alone). I will give details later, and let Rich help for that. Of course, people can still ping me anyway but the idea is to have more than just me from the OSAS/sysadmin side.