| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Consider the 'UNKNOWN' status of volumes while calculating the cluster
status. Following will be the cluster state and state information.
Cluster State State Information
UP "OK : None of the Volumes in the cluster are in Critical State"
UP "OK : No Volumes present in the cluster"
UP "WARNING : Some Volumes in the cluster are in Critical State"
UP "WARNING : Some Volumes in the cluster are in Unknown State"
UP "WARNING : Some Volumes in the cluster are in Warning State"
UP "WARNING : All Volumes in the cluster are in Warning State"
DOWN "CRITICAL: All Volumes in the cluster are in Critical State"
DOWN "CRITICAL: All Volumes in the cluster are in Unknown State"
Bug-url: https://bugzilla.redhat.com/1128007
Change-Id: I06fb1697cb4919420ab6d6ea54e9d9ee96820d2a
Signed-off-by: Ramesh Nachimuthu <rnachimu@redhat.com>
Reviewed-on: http://review.gluster.org/9053
Reviewed-by: Shubhendu Tripathi <shtripat@redhat.com>
Reviewed-by: Sahina Bose <sabose@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BZ 1089641, changed the mk-livestatus query so that
it picks the right services
BZ 1089670, introduced a check to set status to OK if
no volumes present in the cluster
Bug-Url:https://bugzilla.redhat.com/show_bug.cgi?id=1089670
Bug:Url:https://bugzilla.redhat.com/show_bug.cgi?id=1089641
Change-Id: I93aed685c75ff3455e1129c0d8f9e485b6c5f2b0
Signed-off-by: Nishanth Thomas <nthomas@redhat.com>
Reviewed-on: http://review.gluster.org/7708
Reviewed-by: Sahina Bose <sabose@redhat.com>
Tested-by: Sahina Bose <sabose@redhat.com>
|
|
|
This plugin use mk-livestatus to retrieve the status of the
all the volumes and provide aggregrate status of the cluster
Addressed review comments
Change-Id: Ia83b41cfdc6dcfc1f379c024ba6ea33f9ccfe598
Signed-off-by: Nishanth Thomas <nthomas@redhat.com>
|
