shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-10-28 03:27:58 +03:00
Code Releases Activity
c3faa5816d
lvm2/scripts/lvm2_cluster_activation_systemd_red_hat.service.in

18 lines
461 B
SYSTEMD
Raw Normal View History

Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
[Unit]
Description=Clustered LVM volumes activation service
Requires=lvm2-clvmd.service
systemd: rename lvm2-cluster-activation and lvm2-clvmd services to follow existing naming lvm2_cluster_activation_red_hat.service.in -> lvm2_cluster_activation_systemd_red_hat.service.in lvm2_clvmd_red_hat.service.in -> lvm2_clvmd_red_hat.service.in Edit lvm2-cluster-activation reference on cmirror - take new lvm2-cmirrord.service, it was just cmirrord(.service) before as the old initscript was used in compatibility mode. Also, use WantedBy=multi-user.target instead of sysinit.target in lvm2-cluster-activation.service.
2014-02-11 13:03:19 +04:00
After=lvm2-clvmd.service lvm2-cmirrord.service
Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
OnFailure=lvm2-clvmd.service
systemd: do not use default dependencies for clvmd/cmirrord units Do not use default dependencies that systemd adds to the units so we have better control of when the service is started/stopped and we don't end up with unexpected behaviour.
2014-02-14 17:37:19 +04:00
DefaultDependencies=no
Conflicts=shutdown.target
Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
[Service]
Type=simple
RemainAfterExit=yes
EnvironmentFile=-@sysconfdir@/sysconfig/clvmd
ExecStart=@systemdutildir@/lvm2-cluster-activation activate
ExecStop=@systemdutildir@/lvm2-cluster-activation deactivate
[Install]
systemd: rename lvm2-cluster-activation and lvm2-clvmd services to follow existing naming lvm2_cluster_activation_red_hat.service.in -> lvm2_cluster_activation_systemd_red_hat.service.in lvm2_clvmd_red_hat.service.in -> lvm2_clvmd_red_hat.service.in Edit lvm2-cluster-activation reference on cmirror - take new lvm2-cmirrord.service, it was just cmirrord(.service) before as the old initscript was used in compatibility mode. Also, use WantedBy=multi-user.target instead of sysinit.target in lvm2-cluster-activation.service.
2014-02-11 13:03:19 +04:00
WantedBy=multi-user.target
Copy Permalink