snapd

improve systemd configuration support

Bug #1643816 reported by Boris Rybalkin on 2016-11-22

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Snapcraft	Fix Released	Wishlist	Sergio Schvezov	Snapcraft 2.25
	snapd	Fix Committed	Undecided	Unassigned

Bug Description

I am porting uwsgi systemd config to snap and having some problem. Snap installs correctly while systemd cannot start the service (some other configuration issue). I think uwsgi will notify systemd that it has started and looks like snap daemon does not support Type=notify.

Original config:
---------------------
[Unit]
Description=uWSGI Internal
After=syslog.target

[Service]
;User=platform
ExecStart={{ app_dir }}/uwsgi/bin/uwsgi --ini {{ config_root }}/config/uwsgi/internal.ini
Restart=always
KillSignal=SIGQUIT
Type=notify
StandardError=syslog
NotifyAccess=all
Environment=LD_LIBRARY_PATH={{ app_dir }}/python/lib

[Install]
WantedBy=multi-user.target
---------------------
Which is almost exact copy of the recommended config by uwsgi developers:
http://uwsgi-docs.readthedocs.io/en/latest/Systemd.html

This is snap version:
---------------------
  uwsgi:
    command: uwsgi/bin/uwsgi --ini ${SNAP_COMMON}/config/uwsgi/public.ini
    daemon: simple
    restart-condition: always
    plugs: [network, network-bind]
---------------------

Snap way of defining systemd services seems very limited, is there a way to provide systemd version of the config in snapd?