>
> 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
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
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
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
> 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
