Idea #6884
Updated by Brett Smith over 8 years ago
This is a planning story. The expected outcome is more well-specified stories. Background: Right now our install docs usually suggest you use runit to supervise daemon processes. This has several downsides: * It repeatedly complicates the install instructions with infrastructure that could be added to the packages directly. * runit is unfamiliar to many users, which adds to the difficulty of system deployment and maintenance. * runit is not readily available on CentOS 6, and possibly other versions. Questions the planning process should answer: * What inits do we need to support? I assume sysvinit and systemd. Any others? Ubuntu 12.04 has Upstart, but apparently with some level of sysvinit compatibility. * Should our packages try to support multiple inits simultaneously, or should each package support the init that ships with the distribution? * Is there some fpm-like tool we can/should use to generate different init scripts for us? (I think Nico was investigating something along these lines.) * [Others? See the discussion starting at "6663 note 30":https://arvados.org/issues/6663#note-30 for some deployment background and desired functionality.] [Others?] It would be cleanest to have a separate story for every daemon package, although hopefully once we have one or two under our belts, the rest will go much more quickly.