[ClusterLabs] pacemaker resources under systemd

[Ulrich Windl]

Hi!

Systemd think he's the boss, doing what he wants: Today I noticed that all
resources are run inside control group "pacemaker.service" like this:
  ├─pacemaker.service
  │ ├─ 26582 isredir-ML1: listening on 172.20.17.238/12503 (2/1)
  │ ├─ 26601 /usr/bin/perl -w /usr/sbin/ldirectord /etc/ldirectord/mail.conf
start
  │ ├─ 26628 ldirectord tcp:172.20.17.238:25
  │ ├─ 28963 isredir-DS1: handling 172.20.16.33/10475 -- 172.20.17.200/389
  │ ├─ 40548 /usr/sbin/pacemakerd -f
  │ ├─ 40550 /usr/lib/pacemaker/cib
  │ ├─ 40551 /usr/lib/pacemaker/stonithd
  │ ├─ 40552 /usr/lib/pacemaker/lrmd
  │ ├─ 40553 /usr/lib/pacemaker/attrd
  │ ├─ 40554 /usr/lib/pacemaker/pengine
  │ ├─ 40555 /usr/lib/pacemaker/crmd
  │ ├─ 53948 isredir-DS2: handling 172.20.16.33/10570 -- 172.20.17.201/389
  │ ├─ 92472 isredir-DS1: listening on 172.20.17.204/12511 (13049/3)
...

(that "isredir" stuff is my own resource that forks processes and creates
threads on demand, thus modifying process (and thread) titles to help
understanding what's going on...)

My resources are started via OCF RA (shell script), not a systemd unit.

Wouldn't it make much more sense if each resource would run in its own control
group? I mean: If systemd thinks everything MUST run in some control group, why
not pick the "correct " one? Having the pacemaker infrastructure in the same
control group as all the resources seems to be a bad idea IMHO.

The other "discussable feature" are "high PIDs" like "92472". While port
numbers are still 16 bit (in IPv4 at least), I see little sense in having
millions of processes or threads.

Regards,
Ulrich