Pacemaker 2.0 changed the Pacemaker daemons as follows. == New names == The Pacemaker daemons have been renamed more intuitively, to help make the logs easier to follow. <table> <tr><th>Previous name</th><th>Current name</th><th>Purpose</th></tr> <tr><td>attrd</td><td>pacemaker-attrd</td><td>node attribute manager</td></tr> <tr><td>cib</td><td>pacemaker-based</td><td>Cluster Information Base manager</td></tr> <tr><td>crmd</td><td>pacemaker-controld</td><td>cluster controller</td></tr> <tr><td>lrmd</td><td>pacemaker-execd</td><td>local resource agent executor</td></tr> <tr><td>stonithd</td><td>pacemaker-fenced</td><td>node fencer</td></tr> <tr><td>pacemaker_remoted</td><td>pacemaker-remoted</td><td>remote resource agent executor</td></tr> <tr><td>pengine</td><td>pacemaker-schedulerd</td><td>action scheduler</td></tr> </table> The master process that spawns all the others, pacemakerd, keeps its same name. The systemd unit files and init scripts that start pacemaker and pacemaker_remote keep their same names. The daemon source code subdirectories have all been moved to a new daemons subdirectory of the code base, and the source code files have been renamed for uniqueness, to help make the detail log easier to follow. == Regression tests == (Regression tests are mainly for Pacemaker developers, so most users can ignore this.) The various regression tests have been made more unified. The most noticeable difference is in the command names: <table> <tr><th>Previous name</th><th>Current name</th></tr> <tr><td>BasicSanity.sh</td><td>cts-regression</td></tr> <tr><td>coverage.sh</td><td>cts-coverage</td></tr> <tr><td>cli/regression.sh</td><td>cts-cli</td></tr> <tr><td>lrmd/regression.py</td><td>cts-exec</td></tr> <tr><td>pengine/regression.sh</td><td>cts-scheduler</td></tr> <tr><td>fencing/regression.py</td><td>cts-fencing</td></tr> <tr><td>lrmd_test</td><td>cts-exec-helper</td></tr> <tr><td>stonith-test</td><td>cts-fence-helper</td></tr> </table> The regression tests are now directly in /usr/share/pacemaker/tests instead of subdirectories, and the code has been moved into the cts directory of the source code tree. There were some minor tweaks to command-line arguments here and there; run the test command with --help to see the current options. The -i/--interval option to cts-exec-helper now takes a generic interval specification instead of an integer number of milliseconds.

Pacemaker 2.0 changed the Pacemaker daemons as follows. == New names == The Pacemaker daemons have been renamed more intuitively, to help make the logs easier to follow. <table> <tr><th>Previous name</th><th>Current name</th><th>Purpose</th></tr> <tr><td>attrd</td><td>pacemaker-attrd</td><td>node attribute manager</td></tr> <tr><td>cib</td><td>pacemaker-based</td><td>Cluster Information Base manager</td></tr> <tr><td>crmd</td><td>pacemaker-controld</td><td>cluster controller</td></tr> <tr><td>lrmd</td><td>pacemaker-execd</td><td>local resource agent executor</td></tr> <tr><td>stonithd</td><td>pacemaker-fenced</td><td>node fencer</td></tr> <tr><td>pacemaker_remoted</td><td>pacemaker-remoted</td><td>remote resource agent executor</td></tr> <tr><td>pengine</td><td>pacemaker-schedulerd</td><td>action scheduler</td></tr> </table> The initial process that spawns all the others, pacemakerd, keeps its same name. The systemd unit files and init scripts that start pacemaker and pacemaker_remote keep their same names. The daemon source code subdirectories have all been moved to a new daemons subdirectory of the code base, and the source code files have been renamed for uniqueness, to help make the detail log easier to follow. == Regression tests == (Regression tests are mainly for Pacemaker developers, so most users can ignore this.) The various regression tests have been made more unified. The most noticeable difference is in the command names: <table> <tr><th>Previous name</th><th>Current name</th></tr> <tr><td>BasicSanity.sh</td><td>cts-regression</td></tr> <tr><td>coverage.sh</td><td>cts-coverage</td></tr> <tr><td>cli/regression.sh</td><td>cts-cli</td></tr> <tr><td>lrmd/regression.py</td><td>cts-exec</td></tr> <tr><td>pengine/regression.sh</td><td>cts-scheduler</td></tr> <tr><td>fencing/regression.py</td><td>cts-fencing</td></tr> <tr><td>lrmd_test</td><td>cts-exec-helper</td></tr> <tr><td>stonith-test</td><td>cts-fence-helper</td></tr> </table> The regression tests are now directly in /usr/share/pacemaker/tests instead of subdirectories, and the code has been moved into the cts directory of the source code tree. There were some minor tweaks to command-line arguments here and there; run the test command with --help to see the current options. The -i/--interval option to cts-exec-helper now takes a generic interval specification instead of an integer number of milliseconds.

Pacemaker 2.0 changed the Pacemaker daemons as follows. == New names == The Pacemaker daemons have been renamed more intuitively, to help make the logs easier to follow. <table> <tr><th>Previous name</th><th>Current name</th><th>Purpose</th></tr> <tr><td>attrd</td><td>pacemaker-attrd</td><td>node attribute manager</td></tr> <tr><td>cib</td><td>pacemaker-based</td><td>Cluster Information Base manager</td></tr> <tr><td>crmd</td><td>pacemaker-controld</td><td>cluster controller</td></tr> <tr><td>lrmd</td><td>pacemaker-execd</td><td>local resource agent executor</td></tr> <tr><td>stonithd</td><td>pacemaker-fenced</td><td>node fencer</td></tr> <tr><td>pacemaker_remoted</td><td>pacemaker-remoted</td><td>remote resource agent executor</td></tr> <tr><td>pengine</td><td>pacemaker-schedulerd</td><td>action scheduler</td></tr> </table> The masterinitial process that spawns all the others, pacemakerd, keeps its same name. The systemd unit files and init scripts that start pacemaker and pacemaker_remote keep their same names. The daemon source code subdirectories have all been moved to a new daemons subdirectory of the code base, and the source code files have been renamed for uniqueness, to help make the detail log easier to follow. == Regression tests == (Regression tests are mainly for Pacemaker developers, so most users can ignore this.) The various regression tests have been made more unified. The most noticeable difference is in the command names: <table> <tr><th>Previous name</th><th>Current name</th></tr> <tr><td>BasicSanity.sh</td><td>cts-regression</td></tr> <tr><td>coverage.sh</td><td>cts-coverage</td></tr> <tr><td>cli/regression.sh</td><td>cts-cli</td></tr> <tr><td>lrmd/regression.py</td><td>cts-exec</td></tr> <tr><td>pengine/regression.sh</td><td>cts-scheduler</td></tr> <tr><td>fencing/regression.py</td><td>cts-fencing</td></tr> <tr><td>lrmd_test</td><td>cts-exec-helper</td></tr> <tr><td>stonith-test</td><td>cts-fence-helper</td></tr> </table> The regression tests are now directly in /usr/share/pacemaker/tests instead of subdirectories, and the code has been moved into the cts directory of the source code tree. There were some minor tweaks to command-line arguments here and there; run the test command with --help to see the current options. The -i/--interval option to cts-exec-helper now takes a generic interval specification instead of an integer number of milliseconds.