[CentOS-devel] [Config Management SIG] delivering Ansible

François Cami fcami at fedoraproject.org
Sat Nov 12 16:37:09 UTC 2016


As explained during the CentOS Interlock, I'd like to take over
Ansible maintenance within the Config Management SIG.
I need at least Julien's and Fabian's official approval by email on
centos-devel to do so.

The goal of this particular effort will be to:
* ship "ansible" (S)RPMs and their dependencies not in CentOS itself
* write documentation on how to do this rebuild again if needed
* write documentation on how to install Ansible as shipped by the SIG

Version-wise, I plan to deliver 1.9/2.0/2.1/2.2 in separate
repositories managed by separate centos-release-ansible-{19,20,21,22}
RPMs. Any issue during the build and test phases will be reported here
or on IRC. Persistent issues will be posted to the wiki.

Current status:
* build targets and tags for Ansible 1.9 and 2.0 are already in CBS
 ( https://bugs.centos.org/view.php?id=10850 )
* these are multiarch (x86_64 + aarch74) - ansible is noarch which is
OK on paper, yet due to
https://bugzilla.redhat.com/show_bug.cgi?id=1392918 it could be
problematic (Fabian, thanks for the heads-up)
* ansible 1.9, 2.1, 2.2 have all been built in CBS by different SIGs
* ansible 1.9 to 2.2 have all been built in Fedora's koji for EPEL

* access to cbs (I'm good)
* request the missing build targets & tags (2.1 & 2.2) via bugs.centos.org
* enough github access rights to
https://github.com/centos-sig-configmanagement to create and manage
repositories there
* commit access to
- note that I /will/ replace that repository by a new one, with a git
branch per ansible version

I aim to ship ansible 1.9 to 2.2 by early January.
It is expected that some versions might ship much earlier than others.
Testing is expected to be minimal for the first iteration of the project.

Comments welcome of course.

Best regards,

More information about the CentOS-devel mailing list