Re: [Rdo-list] Configuration publishing, organisation of the repo
I think we all agree that it makes sense to split Ansible roles in
different repositories.
What else do we have ? A good first step would be to try and do an inventory.
I've started throwing together an etherpad [1] since the ML is
probably not a good medium for this.
It's not complete, I have to run for now but once we know what we
have, perhaps it can give us a good perspective of how things should
be organized.
[1]: https://etherpad.openstack.org/p/rdo-inventory
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Sat, Mar 12, 2016 at 8:32 AM, Michael Scherer <mscherer(a)redhat.com> wrote:
Hi,
so we were planning to discuss the topic since a long time, but didn't
found the time until last week (after last cloud outage).
So we made a meeting on how would it be the best to open the
infrastructure and decided to first start by a github org.
( see https://github.com/rdo-infra )
Now, the hard question is "how do we organize it", which requires to
know what we have to organise.
From my side, we have the ansible playbook I use to deploy
rdoproject.org. I do have a set of external role I reuse for others
projects (and would like to keep that way, since this make my job easier
for others projects)
I know that David also use ansible for others stuff, and I am not sure
what else is missing (jenkins job builder file, more ?)
Any opinions ?
(next question will be "how much repo and how do we split them")
--
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com