This has been discussed among the SIGs. the idea is to have only ansible available through config-mgmt SIG where the other SIGs consume the package from there. At least, I can tell that from the PaaS SIG perspective and I understand this is how we are moving with the issue of having ansible in our repos. On Fri, Aug 24, 2018 at 7:13 AM Matthias Runge mrunge@matthias-runge.de wrote:
On Thu, Aug 23, 2018 at 11:58:32AM +0200, Sandro Bonazzola wrote:
2018-08-23 11:24 GMT+02:00 Ricardo Martinelli Oliveira < ricardo.martinelli.oliveira@gmail.com>:
Unfortunately, we started facing the problem of not shipping Ansible in the PaaS SIG repo because there are other SIGs doing the same. However, we are working to solve this dependency issue.
For now I'd recommend that you install Ansible 2.6 from the ovirt repos:
Feel free to cross-tag to PaaS SIG while we reach a decision on creating an ansible repo common to everyone.
We have the config-mgmt SIG[1].
Ideally, we'd have ansible there. I see there is a tag to include Ansible 2.0, but nothing more recent: configmanagement7-ansible-20-el7: Ansible 2.0.y
Maybe a member of the Config-Management SIG would be able to comment?
I know, the Cloud SIG and also the Opstools SIG are using Ansible in a more recent version as well, like the virt sig.
Having it only in config management would avoid cross-tagging and stuff.
Matthias
-- Matthias Runge mrunge@matthias-runge.de _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel