Sorry, I had meant to reply earlier. We (PAAS Sig) need ansible for our OpenShift installer. We already have it packaged in CentOS, and as it's pointed out, many other groups are using that package. I would like to transition to using the ansible from the Config Management SIG, as long as it is compatible/comparable to the ansible released by RHEL and EPEL. I wasn't part of the conversation at CentOS Interlock, but I sure hope that is one of the goals. The problem is, we can't wait until January. Our product is already out and needs an ansible update to 2.2.0, so that is going to be coming out soon. We plan on doing our ansible 2.2.0 release, and then start a transition to using the Config Management ansible. That's my plan. If someone has better ideas, I won't mind hearing them. Troy On Mon, Nov 14, 2016 at 4:58 PM, David Moreau Simard <dms at redhat.com> wrote: > I just learned that Ansible is already packaged in SIGs [1]. > > Can we straigthen that out so that there's not multiple individuals > working towards the same goals ? > > [1]: http://cbs.centos.org/koji/buildinfo?buildID=11347 > > David Moreau Simard > Senior Software Engineer | Openstack RDO > > dmsimard = [irc, github, twitter] > > > On Sat, Nov 12, 2016 at 12:12 PM, François Cami <fcami at fedoraproject.org> wrote: >> On Sat, Nov 12, 2016 at 6:02 PM, David Moreau Simard <dms at redhat.com> wrote: >>> On Sat, Nov 12, 2016 at 11:37 AM, François Cami <fcami at fedoraproject.org> wrote: >>>> 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. >>> >>> Does upstream Ansible even support as far back as 1.9.x and 2.0.x ? >> >> The answer is quite probably "no". >> >>> Are you going to be shipping what are basically EOL and >>> unsupported/unmaintained versions ? >> >> Yes. >> There will be a note in the wiki making that clear. >> Tbh I have no other choice as ceph upstream repeatedly told me the >> ceph-ansible playbook is only validated against ansible-1.9 for now. >> >> One of the goals of the ansible effort is to test that particular >> playbook against different ansible versions and fix the bugs in the >> playbook. >> I'd rather start from a known-working environment than from a broken >> one to do so. >> >> François >> >> >>> Looking at releases [1], the last 2.0.x and 1.9.x versions were both >>> in April 2016 -- not /that/ old by any stretch but still old enough to >>> question upstream about their supportability. >>> >>> [1]: https://github.com/ansible/ansible/releases >>> >>> David Moreau Simard >>> Senior Software Engineer | Openstack RDO >>> >>> dmsimard = [irc, github, twitter] >>> _______________________________________________ >>> CentOS-devel mailing list >>> CentOS-devel at centos.org >>> https://lists.centos.org/mailman/listinfo/centos-devel >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel at centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel