Ansible work and organization

[Marc Dequènes (Duck)]

Hello folks,

Since I started working on MM3 migration using Ansible, I received
absolutely no feedback on the Ansible side of my work (and I asked
several time, specifically on this aspect). At first I was new in the
project, this was an attempt, I did not have much access, so it was
created as an external git repository. Now very quickly an
'infra-ansible' repo was created and is already filling with review
requests, but it seems to me we missed a few steps to coordinate.

I'm not very familiar with the Gerrit workflow, but I'm learning, that's
why I asked how I could integrate my work into the new repo but got no
reply. It seemed to me my work could be a proper startup point, but now
I'm faced with splitting and reintegrating my work with what is already
coming in. It feels really useless a work, frustrating, and I also see
no reason to loose all the history.

Also I talked (ML, JIRA) about the roles we (in OSAS) were working on in
order to share the load of the maintenance across several projects. Our
experience is we often need almost the same classic features, so no
reason to recreate the wheel and maintain different versions. We cannot
trust any role on the Internet, but we can trust people in Red Hat or
well known contributors. Nobody seemed to have an objection on this;
nobody adked any question either. Nevertheless now the incoming reviews
shows all of this is ignored and we're doing exactly it: a new
postgresql role just popped-up in one review for example¸ but we already
have one which is used by the MM3 work.

I really tried to not be pushy, to ask for your opinions and reviews,
but not much happened. I thought people were busy and it would come in
time. Now I really don't know how I can catch up.

So, we need to discuss:
  - how OSAS is going to work with the infra team:
    I'm new, so it's ok to feel a bit off, but I'd like better coordination.
    I should not have to do extra work for integrating what I did on
MM3, so clearly it's a failure I would like to avoid in the future.
  - how the config management will be organized/managed:
    there's many ways to organize, to call the roles, to test the rules.
    I've based my work on Misc's good work and added a few things myself.
    I've also started working on testing using Vagrant: it works but has
limitations. There's other attempts on the Internet but they also have
drawbacks, maybe others we did not find yet. So there's room for
discussion too, and integration with your CI. The current setup is in my
repo.
  - how some resources (Ansible roles…) are to be shared or not:
    the OSAS team is very small, shares its time and energy among
several projects, you have several people with a good Puppet background
but less so on Ansible, so I would advise sharing workload. The OSAS
team can act as a neutral third party and insure all needed features are
taken into account, reviews are done in a timely manner, for example. It
was just a logical move from us to allow us spending less time on these
tasks¸ but this is open to discussion (as stated on my previous messages)

As we say here: yoroshiku onegai shimasu.
\_o<

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20160829/ae85fb69/attachment.sig>