Emilien Macchi 5e88de63f5 Add --cpuset-cpus support for both Docker and Podman ... Limit the specific CPUs or cores a container can use. If cpuset-cpus is configured in the container layout, then the value will be used when running the container cli with --cpuset-cpus. If 'all' is used as a value, we'll then take all available cpus, computed by: "0-" + str(psutil.cpu_count()-1) If unset (default), the cpuset-cpus value is computed by using psutil with a new function which returns a comma-separated list range of CPUs that a container can use. This parameter is particulary useful for NFV: https://bugzilla.redhat.com/show_bug.cgi?id=1750781 Indeed, for NFV workloads, in order to achieve 0 packet loss, linux processes, ovs-dpdk (if applicable) and VMs are isolated thanks to kernel args (isolcpus) and tuned profiles (cpu-partitioning). Change-Id: I9443ad60affe9c7823b17daa259efee542c6fe22		2019-09-24 03:48:54 +00:00
..
__init__.py	Initial Cookiecutter Commit.	2017-01-25 11:24:31 +13:00
base.py	Initial Cookiecutter Commit.	2017-01-25 11:24:31 +13:00
test_builder_base.py	Add --cpuset-cpus support for both Docker and Podman	2019-09-24 03:48:54 +00:00
test_builder_compose1.py	Add --cpuset-cpus support for both Docker and Podman	2019-09-24 03:48:54 +00:00
test_builder_podman.py	Add --cpuset-cpus support for both Docker and Podman	2019-09-24 03:48:54 +00:00
test_paunch.py	Introduce paunch apply --healthcheck-disabled	2019-04-15 16:17:04 +00:00
test_runner.py	Merge "Fix discovering container names"	2019-09-24 01:00:01 +00:00
test_utils_common.py	Add --cpuset-cpus support for both Docker and Podman	2019-09-24 03:48:54 +00:00
test_utils_systemctl.py	Check if container is running before doing an exec	2019-08-27 23:19:05 +00:00
test_utils_systemd.py	Ensure we don't have any trailing "requires" for paunch units	2019-05-29 12:33:08 +02:00