These can be separated into individual tasks when ready to be worked on

• Unfencing: use a copy of fence_dummy as device, test automatic unfencing and topology-based unfencing
• Live migration tests: already have migrator resource, but no tests check for migration
• Generated CIB should use as many Pacemaker features as possible (templates, id-refs, resource sets, etc.)
• Fencing tests currently all use stonith_admin to fence a node, but should also test killing corosync or pacemaker-remoted to trigger fencing (maybe randomly pick between the two methods whenever fencing, or add specific tests for each)