Re: [rdo-dev] Building and shipping RPMs from Ansible collections
I would go for the least problematic approach: starting to build collections ASAP.
Collections can be used starting with Ansible 2.9.
My gut feeling is that RPM approach would cause more problems than fixing.
Remember that we test our code on lots of platforms, with virtualenvs (usually tox) and
which in most cases are isolated.
This means that even if we have the RPM-with-module today, we may not be able to use it.
Even worse: upstream testing is done using Ubuntu, does this mean that we start building
debs too?
Ansible 2.9 introduced a way to install modules, via collections, which is not platform
dependent.
I would personally try to avoid reinventing the wheel and use official way.
Cheers
Sorin
On 19 Feb 2020, at 10:12, Sagi Shnaidman <sshnaidm(a)redhat.com>
wrote:
Hi, all
with ongoing process of removing code from Ansible core into collections [1] I'd like
to raise a question - how can we build and provide RPMs from Ansible collection?
We currently use more and more Ansible community modules in TripleO:
- Openstack modules has already moved to be in Openstack repo and won't be present in
Ansible 2.10.
- Podman modules will move to a different collection and won't be present in Ansible
2.10
Both of them are used now and won't be provided by Ansible anymore.
I think it's worth to set up this the sooner the better to prevent unnecessary delays
in the future.
Thanks
[1] https://www.ansible.com/blog/thoughts-on-restructuring-the-ansible-project
--
Best regards
Sagi Shnaidman
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org