[Debian-ha-maintainers] Bug#813008: Bug#813008: pacemaker-remote: The dummy RA belongs to the pacemaker package

[Ferenc Wágner]

In short, these files should be moved from pacemaker-remote to pacemaker
(and the agent description filled out eventually to generate a sensible
man page):

/usr/share/man/man7/ocf_pacemaker_remote.7.gz
/usr/lib/ocf/resource.d/pacemaker/remote

Additionally, the pacemaker-remote RPM contains logrotate and sysconfig.
Pacemaker-remote uses the same logging configuration as pacemaker, and
there is a separate sysconfig section for pacemaker-remote used by both.

The pacemaker and pacemaker-remote packages should Break/Conflict each
other (their daemons listen on the same socket, but pacemaker-remote
does not depend on the cluster stack), require some common files (DTDs?,
RNG schemas?, XSL transforms?, default config?) and recommend the CLI
utilities.  Or is it the utilities requiring the XML stuff?  The
/var/lib/pacemaker/* directories should be provided at least, but they
don't warrant a new package.

For some reason these are in the pacemaker RPM, not in pacemaker-cli:
crm_attribute
crm_master
crm_node
(with their man pages).

Should we move all other binaries except daemons into pacemaker-cli-utils?
/usr/sbin/attrd_updater
/usr/sbin/fence_pcmk
/usr/sbin/stonith_admin
and their man pages.

The above two groups are excluded from the pacemaker-cli RPM, probably
they use direct interfaces to the various sub-daemons and don't work over
pacemaker-remote.  But 4.3.5. of the Remote book states otherwise:

    The pacemaker_remote daemon allows nearly all the pacemaker tools
    (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on
    guest nodes natively.

/usr/lib/x86_64-linux-gnu/pacemaker/lrmd_test is shipped in the
pacemaker-cts RPM, which means we can simply drop it (we don't ship the
test framework now).

Beyond the above, inexplicably missing from the pacemaker RPM:
/usr/lib/ocf/resource.d/pacemaker/o2cb - but its man page is present
/usr/sbin/fence_legacy - though explicitly mentioned in the spec file

Extra in the pacemaker RPM:
/usr/share/pacemaker/nagios/plugins-metadata
  NAGIOS_METADATA_DIR defaults to /usr/share/nagios/plugins-metadata for
  us, and somebody should package
  https://github.com/ClusterLabs/nagios-agents-metadata to 
  provide the contents.  Our Nagios plugin dir is also defaulted to
  /usr/lib/x86_64-linux-gnu/nagios/plugins, which does not match the
  nagios-plugins-* packages, need to fix that, too.
/var/lib/pacemaker/cores
  Something seems to create it actually...  Better ship it, also for
  pacemaker-remote.

These are now in pacemaker, but probably dysfunctional on Debian, and
found in the pacemaker-cli RPM:
/usr/share/pacemaker/report.collector
/usr/share/pacemaker/report.common