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

[David Moreau Simard]

On Wed, Mar 16, 2016 at 4:58 PM, Michael Scherer <mscherer at redhat.com> wrote:
> - rdobase make sense, but I still like to have stuff more split. See
> https://github.com/gluster/gluster.org_ansible_configuration/tree/master/roles/base/tasks
> for what i use (I should also place one for ssh keys)
> and
> https://github.com/gluster/gluster.org_ansible_configuration/blob/master/playbooks/deploy_base.yml
>

I see where you're going, I personally feel this is a lot of
micro-roles and I guess this boils down to personal preference.

> - 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.

I haven't really tested something other than master [1] but I can tell
that it works.
>From looking at the documentation [2], it looks like it is possible to
use tags as well.

[1]: https://github.com/rdo-infra/rdo-monitoring/blob/master/ansible-role-requirements.yml#L4
[2]: http://docs.ansible.com/ansible/galaxy.html#advanced-control-over-role-requirements-files

>
> 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.

All good, keep us updated !

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]