Hi,
so for people who do not know me, my name is Michael Scherer, I work as a sysadmin on the open source and standard (OSAS) team at Red Hat, focusing on infrastructure issues for community my employer want to support (in the limit of 26h per day). In practice, that mean doing system administration for projects like manageiq, ovirt, gluster and others.
My team want to push for community owned infrastructure (kinda like what Fedora and Mageia do, leveraging the config as code pattern and solution like puppet and ansible), so we are publishing as much as possible our configuration under free software license and so we have started to develop a set of ansible roles that can be reused accross community, trying to provides best practices[1]. They are partially on gitlab.com and partially on github.com.
We standardized on ansible for various reasons, mostly due to a perceived higher ease of use by beginners and a slightly less painful deployment model (no need to keep agent and server in sync, which was a pain point for me for puppet, despites loving puppet itself).
And we reached the conclusion that we could make this work useful to others, and a logical conclusion was to join the config management sig.
So what we had in mind is the following: - we could use the roles to test them on various centos platforms with Centos CI and thus providing easy to use roles for centos users. We are mostly using Centos for infastructure. - the roles could also be used to test against the git head version of ansible to make sure that regression in role and/or ansible are detected early - this could show as best practices for roles developpers, with testing, etc
So, what does members of the SIG think of the idea ?
[1] who are highly opinionated and subjective, as I said, I am sysadmin, which is a polite way to say I am professionally stubborn.