Closed shtripat closed 7 years ago
@Tendrl/tendrl-core @atinmu @samikshan plz review.
Looks good for implementation, but I'd suggest addressing some minor concerns such as linking to gluster issues in this spec before merging it.
The references section does have links to glusterfs github issues.
Does gdeploy also report the up (partial) status? I know it returns up (degraded). I'm asking because if this is a new status that we report, it'll need to be documented to tell the users what it actually means.
up (partial)
and up (degraded)
are two different states reported for volumes based on calculations. The pseudo code has the logic which decides in what situations the state would be up (degraded)
The APIs will soon be required, most likely in the Gluster Monitoring milestone. Though, I suggest that for now, we exclude the API details from this spec and file a separate spec or an issue for API endpoints for all the additional gluster state information we now include as part of this spec.
Will remove the entry from this spec. @anivargi please do the needful from API side.
Would be ideal to link to the gluster issues tracking these changes.
I have gluster github issues in references section. Will move here.
tendrl-bug-id: Tendrl/specifications#167 Signed-off-by: Shubhendu shtripat@redhat.com