On Wed, May 11, 2016 at 8:13 AM, Julien Pivotto roidelapluie@inuits.eu wrote:
On 05 May 21:40, François Cami wrote:
Hi,
The main Ceph Jewel installer is based on Ansible, so the Ceph part of the Storage SIG would like to be a consumer of the Config Management SIG Ansible bits.
However, Ceph upstream has confirmed:
- 1.9.4 and 2.0.0.1 are 100% compatible
- 2.1 should work (but is quite probably not tested at all)
This raises the following questions:
- would any member of the Config Management SIG be interested in
building and maintaining either 1.9.4 or 2.0.0.1 for the Storage SIG?
- if not, would the Config Management SIG be open to let Storage SIG
members maintain an Ansible 2.0 branch?
Regards, François _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
We are open to cross sig collaboration. We still have to decide which Koji tags we will need for the ansible sig.
Would something like: (build tag) => (destination tag) configmanagement7-ansible-19-el7 => configmanagement7-ansible-19-candidate configmanagement7-ansible-20-el7 => configmanagement7-ansible-20-candidate
with the usual candidate=>testing=>release tags work for you?
Once that is done, we will work on github where any contribution will be welcome.
Noted.
François