osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[tripleo] Deprecating paunch CLI?


wrt podman_container module,
I have submitted podman_container module to ansible [1] that was reverted
later, the main reason of revert was lack of idempotency. I planned to add
it later, but ansible cores refused to wait.
Maybe we can submit it to tripleo-ansible, finish idempotency and polish
it, and then to submit to ansible upstream again.
That way we'll have well tested with tripleo podman_container module.
Meanwhile we can use paunch module, as it's easier to move from one ansible
module to another.

[1]
https://github.com/ansible/ansible/commit/f01468a9d97f5af4ff61b3b7cac6e3f09015f791

On Mon, Sep 16, 2019 at 7:11 PM Emilien Macchi <emilien at redhat.com> wrote:

> On Mon, Sep 16, 2019 at 11:47 AM Rabi Mishra <ramishra at redhat.com> wrote:
>
>> I'm not sure if podman as container tool would move in that direction, as
>> it's meant to be a command line tool. If we really want to reduce the
>> overhead of so many layers in TripleO and podman is the container tool for
>> us (I'll ignore the k8s related discussions for the time being), I would
>> think the  logic of translating the JSON configs to podman calls should be
>> be in ansible (we can even write a TripleO specific podman module).
>>
>
> I think we're both in strong agreement and say "let's convert paunch into
> ansible module".
> And make the module robust enough for our needs. Then we could replace
> paunch by calling the podman module directly.
> --
> Emilien Macchi
>


-- 
Best regards
Sagi Shnaidman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190916/09b22027/attachment.html>