On 15.01.2020 16:42, Emilien Macchi wrote:
On Wed, Jan 15, 2020 at 10:31 AM Carter, Kevin <kevin@cloudnull.com <mailto:kevin@cloudnull.com>> wrote:
Nicely done Emilien!
On Wed, Jan 15, 2020 at 8:38 AM Emilien Macchi <emilien@redhat.com <mailto:emilien@redhat.com>> wrote:
[...]
The most popular question that has been asked about $topic so far is: how can I run paunch debug to print the podman commands. Answer: https://docs.openstack.org/tripleo-ansible/latest/roles/role-tripleo-contain...
I just thought about it but I thought we could have a tripleo command like :
$ openstack tripleo container deploy --name keystone --host overcloud-controller1 $ openstack tripleo container deploy --name keystone --host overcloud-controller1 --dry-run
It would use the new Ansible-runner to execute something like: https://docs.openstack.org/tripleo-ansible/latest/roles/role-tripleo-contain... Dry-run would basically run the same thing with Ansible in check mode.
In overall, we would still have a CLI (in tripleoclient instead of Paunch); and most of the container logic resides in podman_container which aims to be shared outside of TripleO which has been the main goal driving this effort. What do you think?
Yes please, "shared outside of TripleO" is great aim to accomplish. I think a simple standalone pomdan+systemd+tripleo-container-manage might lead us much further than only Tripleo, and only OpenStack cases.
-- Emilien Macchi
-- Best regards, Bogdan Dobrelya, Irc #bogdando