exposing more of systemd to snappy packages

Kapil Thangavelu kapil.thangavelu at canonical.com
Thu Dec 18 14:56:37 UTC 2014

On Wed, Dec 10, 2014 at 10:46 AM, Sergio Schvezov <
sergio.schvezov at canonical.com> wrote:
> On Wed, Dec 10, 2014 at 5:39 PM, Kapil Thangavelu <
> kapil.thangavelu at canonical.com> wrote:
>> at the moment we're generating systemd from package metadata.yaml (we
>> used to just include unit files in the package). i assume that's so we
>> could embed/generate the right invocations for app armor and paths. But
>> there's quite a lot of functionality that packages are giving up as a
>> result, cron/timer and one off scripts come to mind. is there any chance we
>> can expose more of this back to packages either via additional yaml
>> translation or direct systemd conf sections for merge.
> I think we don't want to expose component technology in the packaging
> yaml. Your case certainly needs to be thought of though (and maybe make a
> comeback in a descriptive form).

atm interesting systemd features are cron and the ability to do onetime
scripts post snap package install but prior to job start.  its unclear from
the extant docs if there others way to achieve the later. there's some
notion of using the sysd cgroup features for limiting utilization but thats
an admin install time concern not a packaging one per se.

re abstract syntaxes here's a strawman

   - period: crontab_syntax
     exec: path_in_snap/abc

  - exec: path_in_snap/xyz

copied this into asana

re timers capability this seems to cover it best
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20141218/5a9dcc57/attachment.html>

More information about the snappy-devel mailing list