[tripleo] Deprecating paunch CLI? [EXT]

Dave Holland dh3 at sanger.ac.uk
Mon Sep 16 08:21:00 UTC 2019


We've found "paunch debug" useful in tracking down container issues that
we've reported to RH and then fixed, e.g. when diagnosing a too-low file
handle limit:

paunch debug --file /var/lib/tripleo-config/hashed-docker-container-startup-config-step_4.json --overrides '{ "ulimit": ["nofile=9999"] }' --container neutron_l3_agent --action run

Will there be a way to achieve this run-with-overrides functionality
without the CLI?

Thanks,
Dave
-- 
** Dave Holland ** Systems Support -- Informatics Systems Group **
** 01223 496923 **    Wellcome Sanger Institute, Hinxton, UK    **


On Fri, Sep 13, 2019 at 06:00:30PM -0400, Emilien Macchi wrote:
> With our long-term goal to simplify TripleO and focus on what people
> actually deploy and how they operate their clouds, it appears that
> the Paunch CLI hasn't been a critical piece in our project and I
> propose that we deprecate it; create an Ansible module to call Paunch
> as a library only.
> I've been playing with it a little today:
> [1]https://review.opendev.org/#/c/682093/ [review.opendev.org]
> [2]https://review.opendev.org/#/c/682094/ [review.opendev.org]
> Here is how you would call paunch:
>     - name: Start containers for step {{ step }}
>       paunch:
>         config:
> "/var/lib/tripleo-config/hashed-container-startup-config-step_{{ step
> }}.json"
>         config_id: "tripleo_step{{ step }}"
>         action: apply
>         container_cli: "{{ container_cli }}"
>         managed_by: "tripleo-{{ tripleo_role_name }}"
> A few benefits:
> - Deployment tasks in THT would call the new module instead of a
> shell command
> - More Pythonic and clean for Ansible, to interact with the actual
> task during the run
> - Removing some code in Paunch, make it easier to maintain for us
> For now, the Ansible module only covers "paunch apply", we will
> probably cover "delete" and "cleanup" eventually.
> Please let me know if you have any questions or concerns,
> --
> Emilien Macchi
> 
> References
> 
> 1. https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_682093_&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=64bKjxgut4Pa0xs5b84yPg&m=UzaP5_-Gt5C5Oyp0rQnntvqGufCQyDrPINAQB-a9l6g&s=aoB_wM3phD5R4iJA6DqIp1v7NJIV8fxQA41a6OyfIYI&e=
> 2. https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_682094_&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=64bKjxgut4Pa0xs5b84yPg&m=UzaP5_-Gt5C5Oyp0rQnntvqGufCQyDrPINAQB-a9l6g&s=gWOvDz_lchmRc5im_2FHvqqo0s7pLB0DtNl4NZ83vTg&e=



-- 
 The Wellcome Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 



More information about the openstack-discuss mailing list