>
> On Tue, Feb 25, 2020 at 14:25 Alfredo Moralejo Alonso wrote:
> > On Tue, Feb 25, 2020 at 12:23 PM Sagi Shnaidman
> > 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 CD
On Tue, Feb 25, 2020 at 14:25 Alfredo Moralejo Alonso wrote:
> On Tue, Feb 25, 2020 at 12:23 PM Sagi Shnaidman 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
On Tue, Feb 25, 2020 at 12:23 PM Sagi Shnaidman 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 d
Regarding "TripleO is not tested with Ubuntu" statement, let me give one random
example:
Look at: https://review.opendev.org/#/c/709188/
All "tox" jobs (linters, unittests, molecule) are running on Ubuntu upstream
and they so test bits of tripleo code, on Ubuntu.
Also upstream molecule jobs ar
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
> Even worse: upstream testing is done using Ubuntu, does this mean that we
> start building debs too?
TripleO is not tested with Ubuntu and we don't ship anything in OSP
for Ubuntu, so no, we're not going to start building debs.
> Ansible 2.9 introduced a way to install modules, via 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)
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 Opensta
