Feature #11344
closeduse systemd unit files for service management
0%
Description
With systemd becoming more widespread, Ceph's services (MON, OSD, MDS, RGW) should be implemented with proper systemd unit files.
There are already some unit files in the tree, under /systemd/.
We should determine:
1. What are the packaging changes needed to ship these for users?
2. Do these service unit files work as-is, or will they need further tweaking?
3. For Debian-family packages, can we conditionally ship upstart files on older distros, and systemd unit files on newer distros?
4. Services numbers. There was some discussion on ceph-maintainers regarding whether we should have a single "ceph-mon.service" (implying that users should only run one monitor daemon per server) or if we should support multiple "ceph-mon@" services (implying that users will need to specify additional information when starting the service(s)). The version in our tree is "ceph-mon@". James' work for Ubuntu Vivid is only "ceph-mon". How can we unify here?
Updated by Mark Kirkwood about 9 years ago
With reference to 2/ above. I stumbled into the need to understand this by upgrading my workstation to Ubuntu 15.04 - hello systemd! The most obvious thing missing from the current unit files is the ceph-create-keys for monitor boot strap, without this, well we are pretty hosed I think.
With reference to 3/ above, we are going to need some code changes to ceph-disk and ceph-deploy so they understand such subtleties too.
Updated by Sage Weil almost 8 years ago
- Status changed from New to Resolved
1) done
2) done
3) we ship sysvinit, upstart, and systemd files. debian users can install wahtever init system they want.
4) we use @name for all daemons. cluster name is set host-wide in /etc/default/ceph.