[ClusterLabs] Pacemaker (remote) component relations

[Ferenc Wágner]

Hi,

I'm looking for information about the component interdependencies,
because I'd like to split the Pacemaker packages in Debian properly.
The current idea is to create two daemon packages, pacemaker and
pacemaker-remote, which exclude each other, as they contain daemons
listening on the same sockets.

1. Is the socket names configurable?  Are there reasonable use cases
   requiring both daemons running concurrently?

These two daemon packages would depend on a package providing the common
hacluster user, the haclient group, the sysconfig and logrotate config.

What else should go here?

2. Are the various RNG and XSL files under /usr/share/pacemaker used
   equally by pacemakerd and pacemaker_remoted?  Or by the CLI utils?

3. Maybe the ocf:pacemaker RAs and their man pages?  Or are they better
   in a separate pacemaker-resource-agents package?

4. Is /usr/share/snmp/mibs/PCMK-MIB.txt used by any component, or is it
   only for decyphering SNMP traps at their destination?  I guess it can
   go anywhere, it will be copied by the admin anyway.

There's also a separate package for the various command line utilities,
which would depend on pacemaker OR pacemaker-remote.

5. crm_attribute is in the pacemaker RPM package, unlike the other
   utilites, which are in pacemaker-cli.  What's the reason for this?

6. crm_node connects to corosync directly, so it won't work with
   pacemaker_remote.  crm_master uses crm_node, thus it won't either (at
   least without -N).  But 4.3.5. of the Remote book explicitly mentions
   crm_master amongst the tools usable with pacemaker_remote.  Where's
   the mistake?

7. According to its man page, crm_master should be invoked from an OCF
   resource agent, which could happen under pacemaker_remote.  This is
   again problematic due to the previous point.

8. Do fence_legacy, fence_pcmk and stonith_admin make any sense outside
   the pacemaker package?  Even if they can run on top of
   pacemaker_remote, the cluster would never used them there, right?
   And what about attrd_updater?  To be honest, I don't know what that's
   for anyway...

9. What's the purpose of chgrp haclient /etc/pacemaker if
   pacemaker_remoted is running as root?  What other haclients may need
   access to the authkey file?
-- 
Any input is greatly appreciated, either on the above points, or on
basic misunderstandings of mine.  Thanks for your time,
Feri.