Feature #7331

[Deployment] Add systemd unit definition to the keepproxy package

Added by Brett Smith over 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
OPS - Kanban
Start date:
09/14/2015
Due date:
% Done:

0%

Estimated time:
Story points:
2.0

Description

Functional requirements:

  • The definition should always be installed somewhere under /usr/share/doc/keepproxy.
  • On distros we support that ship with systemd (currently just Debian 8), the package installs the unit definition on the system.
  • Users should not need to edit this file to make configuration changes. Instead they should make changes to a file in /etc/default (on Debian) or /etc/sysconfig (on Red Hat) which are respected by the unit definition.
  • We want this to be as close as possible functionally to what we currently do under runit—whether that's thanks to runit features, or stuff we arrange in our runit script.
  • We want Restart= to automatically restart the daemon in most cases. See systemd.service documentation
  • We want StandardOutput= to move output to syslog or similar. See systemd.exec documentation

(some other background: http://www.kibinlabs.com/systemd-logging-tricks/)


Related issues

Related to Arvados - Feature #6034: [Deployment] Add sysvinit script to the keepproxy packageRejected2015-10-14

History

#1 Updated by Brett Smith over 3 years ago

  • Description updated (diff)

#2 Updated by Ward Vandewege over 3 years ago

  • Description updated (diff)

#3 Updated by Brett Smith over 3 years ago

  • Description updated (diff)

#4 Updated by Brett Smith about 3 years ago

  • Target version changed from Arvados Future Sprints to Kanban

#5 Updated by Tom Clegg over 1 year ago

  • Status changed from New to Resolved

Also available in: Atom PDF