[rdo-dev] Building and shipping RPMs from Ansible collections

[Javier Pena]

> 
> On Tue, Feb 25, 2020 at 14:25 Alfredo Moralejo Alonso wrote:
> > On Tue, Feb 25, 2020 at 12:23 PM Sagi Shnaidman <sshnaidm at redhat.com>
> > wrote:
> >> We need to test what we ship to customers, so we need to figure that
> >>> out first for Ansible, together with the Ansible team.
> >>> Has shipping on Red Hat CDN for Collections been defined by the
> >>> Ansible organization?
> >>>
> >>
> >> TBH, I don't think Ansible team is a part to consult with. Openstack
> >> modules are moved to Openstack repository and Ansible team has no any
> >> relation to it now.
> >> As well as Podman modules that will be moved soon (hopefully when I find
> >> the time) to CRIO namespace (https://github.com/containers)
> >> The whole point of Ansible 2.10 is to remove all community modules from
> >> core and takeover of responsibilities for them to interested parties.
> >> So I think nothing should block us to build/ship the RPMs
> >>
> >>
> > My understanding is that 2.10 sill move some supported modules also to
> > collections and they have defined the way to deliver it using both galaxy
> > for upstream and automation hub for downstream [1][2]. We could confirm
> > with Ansible team if they plan to deliver it *only* via automation-hub or
> > also using packages, but I guess we will rely on what they provide for all
> > supported content. I think it'd be good to have a clear picture of what
> > they will support and how they will deliver it.
> >
> > For the collections maintained in OPenStack, it may make sense to build
> > RPMs for it to keep our rpm-based workflow.
> >
> 
> Could we investigate and/or design an `ansible-galaxy-rpm` tool to
> produce and maintain the spec files?
> If that doesn't exist, it could be a very useful thing to have. As an
> example, the haskell packages in fedora are produced using a `cabal-rpm`
> tool and it seems like a viable solution to use for maintaining the
> ansible collection as rpm.
> 

I felt curiosity for this, and had a look at the Ansible Galaxy API.

It seems to be quite straightforward, so I have created https://github.com/javierpena/galaxy-collection-to-rpm with a simple script to create the spec file for a collection.

If we wanted to build some collections using DLRN, we could add some code to provide better support, similar to what was done in the past for Ruby gems [3].

Regards,

Javier

[3] - https://github.com/softwarefactory-project/DLRN/commit/cd64b6b172362dbadae25c3a93e7e00c9e5acaaf

> -Tristan
> 
> >
> > [1] https://www.ansible.com/products/automation-hub
> > [2] https://www.ansible.com/blog/getting-started-with-automation-hub
> >
> >
> >
> >> Thanks
> >> --
> >> Best regards
> >> Sagi Shnaidman
> >> _______________________________________________
> >> dev mailing list
> >> dev at lists.rdoproject.org
> >> http://lists.rdoproject.org/mailman/listinfo/dev
> >>
> >> To unsubscribe: dev-unsubscribe at lists.rdoproject.org
> >>
> > _______________________________________________
> > dev mailing list
> > dev at lists.rdoproject.org
> > http://lists.rdoproject.org/mailman/listinfo/dev
> >
> > To unsubscribe: dev-unsubscribe at lists.rdoproject.org
> 
> _______________________________________________
> dev mailing list
> dev at lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
> 
> To unsubscribe: dev-unsubscribe at lists.rdoproject.org
>