1:26 p.m.
So I tentatively made an attempt to push stuff through to see what it
would look like.
Here's what I came up with:
- ansible-role-rdobase [1]
-- Sets up basic things like packages we'd expect to be installed
everywhere, sets up SSH config, users, MOTD
- ansible-role-rdomonitoring [2]
-- Sets up sensu master server and client servers for monitoring
- ansible-role-rdobot [3]
-- Sets up rdobot [4], a bot to broadcast relevant monitoring alerts to channels
- rdo-monitoring [5]
-- The playbooks that consume the above roles (retrieved through
ansible-galaxy install -r requirements.yml) and a static host
inventory
-- Has a config.yml stripped of _sensitive_ information, still need to
figure out where we want to put that
Does this layout make sense ? I feel it's simple enough and galaxy
makes it easy to collect dependencies.
[1]: https://github.com/rdo-infra/ansible-role-rdobase
[2]: https://github.com/rdo-infra/ansible-role-rdomonitoring
[3]: https://github.com/rdo-infra/ansible-role-rdobot
[4]: https://github.com/rdo-infra/rdobot
[5]: https://github.com/rdo-infra/rdo-monitoring
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Mon, Mar 14, 2016 at 10:43 AM, David Moreau Simard <dms(a)redhat.com> wrote:
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