Some of this has been mentioned before, but to collect it all in one location, here is information of particular interest to distribution packagers and users who build Pacemaker themselves:
* Should you stay on the 1.1 series or move to 2.0? See the following list of factors to consider, primarily whether you need any of the deprecated support that was removed, or you want a release that includes deprecation warnings before removing support: https://wiki.clusterlabs.org/wiki/Choosing_Between_Pacemaker_1.1_and_2. 0 * The daemons have been renamed. The configure script has a new option, --enable-legacy-links. If enabled (the default), symlinks will be installed at the old daemon names pointing at the new ones. This has two purposes: to allow older versions of tools (such as crm shell and pcs) that directly invoke the old names for metadata etc. to continue working; and to allow Pacemaker 1.1.17+ cluster nodes to host bundles using a container image containing Pacemaker 2.0.0+. If you do not need this support (most likely in the future when versions of the tools that support the new names are available), you can specify -- disable-legacy-links. * The default location of the detail log is now /var/log/pacemaker/pacemaker.log (not directly in /var/log or sharing a log with corosync). * Compare the Pacemaker-1.1.18 pacemaker.spec.in file with the new one to look for any changes you might want to reproduce. There have been improvements in Python 3 support, etc. -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org