Paunch: extend systemd unit flags

Bug #1814764 reported by Cédric Jeanneret on 2019-02-05
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cédric Jeanneret

Bug Description


It would be great to allow paunch to extend a bit the content of the systemd unit created for the containers. I especially think the following are of interest:

The path is relative, so if we set RuntimeDirectory=foo, it will mean /run/foo

Since the /var/run is usually emptied upon reboot, and as podman doesn't create host directories for its volumes, injecting those flags would provide a really nice way to avoid issues.

More doc about those flags might be found here:

We might also take the opportunity to allow for CPU/Memory limitation.




Changed in tripleo:
importance: Undecided → Medium
milestone: none → stein-3
status: New → Triaged
tags: added: containers
Changed in tripleo:
assignee: nobody → Cédric Jeanneret (cjeanner)

Fix proposed to branch: master

Changed in tripleo:
status: Triaged → In Progress

Submitter: Zuul
Branch: master

commit b452a33030a19c34fdc3dbf65f39aa5f511de1e3
Author: Cédric Jeanneret <email address hidden>
Date: Wed Feb 6 11:24:07 2019 +0100

    Allow to pass some of systemd.exec flags

    It may happen we have some shared directory mounted within
    the container - if it is located in /run or in some other
    tmpfs location, it won't persist across reboots.

    SystemD provides the capability to create those directories, and
    this patch allows to take advantage of this capacity.

    Basically, we might add as many flag as we want.

    Closes-Bug: #1814764
    Change-Id: I5d2ef49ec205b7a43c488d4ceef0724e5ef2b6cc

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/paunch 4.3.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers