#6 Enables hostmonitor to work on pacemaker-remote. #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Masakari-hostmonitor can check other host's status with pacemaker-remote. Previous hostmonitor only check a host which runs on the full cluster stack of corosync. This hits the upper limit of the cluster, 16 hosts, and we have to set up multi pacemaker cluster when the number of host is >16. Pacemaker-remote resolves the problem, so to enable hostmonitor to check a cluster status by pacemaker-remote we can set up a number of hosts in one cluster more than 16.
|
looks good to me. |
|
Thank you for the Fix. Looks good. |
sampathP
added a commit
that referenced
this pull request
Feb 4, 2016
#6 Enables hostmonitor to work on pacemaker-remote.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Masakari-hostmonitor can check other host's status with pacemaker-remote.
Previous hostmonitor only check a host which runs on the full cluster stack
of corosync. This hits the upper limit of the cluster, 16 hosts, and we
have to set up multi pacemaker cluster when the number of host is >16.
Pacemaker-remote resolves the problem, so to enable hostmonitor to check
a cluster status by pacemaker-remote we can set up a number of hosts in
one cluster more than 16.