Feature: Turn off auto-respawning of systemd services when the cluster starts them
Fix: Use the official fedora user/group ID for haclient/hacluster
Test: cts: Fix fence_dummy and its usage
Refactor: corosync: Merge three sets of CPG related code
Fix: membership: Simplify crm_peer_init()
Fix: logging: If SIGTRAP is sent before tracing is turned on, turn it on
Fix: cman: Give cman time to start before starting the rest of pacemaker
Log: mcp: Improved startup logging
Build: clean up after try_extract_header_define()
Test: Prevent clock drift when setting up a cluster
Test: cts: Update log patterns
Log: crmd: Downgrade an error message since we can recover
Fix: systemd: Reload systemd after adding/removing override files for cluster services
Refactor: Clean up cluster header
Build: Turn off fortify source when building with profiling support
Build: Suggest good defaults for configure on rpm based systems
Build: Merge systemd detection logic
Build: streamline the spec file
Feature: crm_mon --neg-location drbd-fence-by-handler

Adds a list of negative location constraints to crm_mon output,
optionally filtered by id prefix.

Example output:

===
<normal crm_mon output>
...

Fencing constraints:
 drbd-fence-by-handler-iscsi-vmstore2-rule-ms_drbd_iscsi-vmstore2	prevents ms_drbd_iscsi-vmstore2 from running as master on bk13-2
===

If so configured (DRBD fencing-policy != dont-care, fence-peer handler
set to crm-fence-peer.sh), a DRBD Primary places these constraints when
the replication link is not established.

This is a condition that is otherwise not obvious from crm_mon output,
as to pacemaker, everything looks "normal".