Bug 1647057

Summary: Cannot limit memory usage on containers using paunch
Product: Red Hat OpenStack Reporter: Marc Methot <mmethot>
Component: python-paunchAssignee: Steve Baker <sbaker>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: augol, gregraka
Target Milestone: Upstream M3Keywords: Triaged, ZStream
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-paunch-4.2.1-0.20190123122357.fc5aecd.el8ost Doc Type: Enhancement
Doc Text:
With Paunch you can now manage container memory consumption using three new attributes: mem_limit, memswap_limit, and mem_swappiness.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 11:19:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marc Methot 2018-11-06 15:30:30 UTC 
User requires a method to limit the max memory of containers managed by paunch.
Without this, containers can bloat as they wish and also makes memory consumption forecasting unpredictable.

Noting that this is already in the TODO in the builder's code:
https://github.com/openstack/paunch/blob/master/paunch/builder/compose1.py
~~~
  # TODO(sbaker): add missing compose v1 properties:
        # cgroup_parent
        # devices
        # dns, dns_search
        # entrypoint
        # expose
        # extra_hosts
        # labels
        # ports
        # stop_signal
        # volume_driver
        # cpu_quota
        # cpuset
        # domainname
        # hostname
        # mac_address
        # mem_limit
        # memswap_limit
        # mem_swappiness
        # read_only
        # shm_size
        # stdin_open
        # working_dir
~~~

Cheers,
Marc Methot
Comment 7 errata-xmlrpc 2019-09-21 11:19:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811