Hi folks, Now we released Ussuri, we're looking at retiring Paunch from TripleO. We'll do it step by step to avoid any CI issue. First step is to remove it from THT: https://review.opendev.org/#/c/731565 The changes should be fully transparent for our users (deployment, updates, upgrades) except for the day 2 operations like container lifecycle management (paunch CLI is being retired). The new role is documentere here: https://docs.openstack.org/tripleo-ansible/latest/roles/role-tripleo_contain... If you have any concern or need any help on that transition, feel free to ask here, or on #tripleo or even ping me directly. Thanks, On Thu, Apr 23, 2020 at 9:00 AM Emilien Macchi <emilien@redhat.com> wrote:

On Thu, Apr 23, 2020 at 8:59 AM Andreas Jaeger <aj@suse.com> wrote:

...

On 23.04.20 14:33, Emilien Macchi wrote:

...

Hi folks,

In Ussuri we manage to successfully replace Paunch by Ansible (role + modules) to manage the container lifecycle in TripleO. As a reminder, this effort was part of the Simplification work that is being done in TripleO to reduce our number of tools and align it with our deployment framework based on Ansible.

https://docs.openstack.org/tripleo-ansible/latest/roles/role-tripleo_contain...

...

Paunch has been turned off for some time now and isn't tested anymore in upstream CI (master only). I would like to propose its deprecation in Ussuri and a removal in Victoria (or later if any valid pushback).

https://review.opendev.org/#/c/720598/

I propose to do it like django_openstack_auth: Remove all content and just leave a README in there so that nobody commits changes to master,

Yes we will do that in Victoria cycle; if the deprecation is granted. -- Emilien Macchi

-- Emilien Macchi