ceph/systemd/ceph-mgr@.service

[Unit]
Description=Ceph cluster manager daemon
After=network-online.target local-fs.target time-sync.target
Wants=network-online.target local-fs.target time-sync.target
PartOf=ceph-mgr.target

[Service]
LimitNOFILE=1048576
LimitNPROC=1048576
EnvironmentFile=-/etc/sysconfig/ceph
Environment=CLUSTER=ceph

ExecStart=/usr/bin/ceph-mgr -f --cluster ${CLUSTER} --id %i --setuser ceph --setgroup ceph
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
StartLimitInterval=30min
StartLimitBurst=3

[Install]
WantedBy=ceph-mgr.target
systemd: add ceph-mgr service and target files Signed-off-by: Tim Serong <tserong@suse.com> 2016-09-07 05:39:58 +00:00			`[Unit]`
			`Description=Ceph cluster manager daemon`
systemd/ceph-mgr: remove automagic mgr creation hack For kraken we auto-created mgr daemons next to mon daemons with some systemd hackery. This is awkward (you can't not get a new mgr daemon when you deploy a mon), systemd-specific (not implemented for upstart on trusty), and mostly unexpected. Since ceph-mgr daemons are now first-class citizens and required for every cluster, make their deployment explicit and transparent to the administrator. Major upgrades are a rare opportunity to have the administrator's full attention so take advantage of it. This effectively reverts 61d779345e9efbe9a2e3f215af1f1dcf6630f04a and 082199f69dd0bd4c18a5f4baea67a88782586657 (and follow-on fixes). Fixes/avoids: http://tracker.ceph.com/issues/19994 Signed-off-by: Sage Weil <sage@redhat.com> 2017-06-29 17:39:28 +00:00			`After=network-online.target local-fs.target time-sync.target`
systemd: add ceph-mgr service and target files Signed-off-by: Tim Serong <tserong@suse.com> 2016-09-07 05:39:58 +00:00			`Wants=network-online.target local-fs.target time-sync.target`
systemd/ceph-mgr: remove automagic mgr creation hack For kraken we auto-created mgr daemons next to mon daemons with some systemd hackery. This is awkward (you can't not get a new mgr daemon when you deploy a mon), systemd-specific (not implemented for upstart on trusty), and mostly unexpected. Since ceph-mgr daemons are now first-class citizens and required for every cluster, make their deployment explicit and transparent to the administrator. Major upgrades are a rare opportunity to have the administrator's full attention so take advantage of it. This effectively reverts 61d779345e9efbe9a2e3f215af1f1dcf6630f04a and 082199f69dd0bd4c18a5f4baea67a88782586657 (and follow-on fixes). Fixes/avoids: http://tracker.ceph.com/issues/19994 Signed-off-by: Sage Weil <sage@redhat.com> 2017-06-29 17:39:28 +00:00			`PartOf=ceph-mgr.target`
systemd: add ceph-mgr service and target files Signed-off-by: Tim Serong <tserong@suse.com> 2016-09-07 05:39:58 +00:00
			`[Service]`
			`LimitNOFILE=1048576`
			`LimitNPROC=1048576`
			`EnvironmentFile=-/etc/sysconfig/ceph`
			`Environment=CLUSTER=ceph`
systemd/ceph-mgr@.service: fix mgr mon cap Signed-off-by: Sage Weil <sage@redhat.com> 2017-03-14 02:37:29 +00:00
systemd: add ceph-mgr service and target files Signed-off-by: Tim Serong <tserong@suse.com> 2016-09-07 05:39:58 +00:00			`ExecStart=/usr/bin/ceph-mgr -f --cluster ${CLUSTER} --id %i --setuser ceph --setgroup ceph`
			`ExecReload=/bin/kill -HUP $MAINPID`
			`Restart=on-failure`
			`StartLimitInterval=30min`
			`StartLimitBurst=3`

			`[Install]`
			`WantedBy=ceph-mgr.target`