feat(cspi): add provisioned and healthy replica count in CSPI status #99
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.
This PR adds Provisioned and Healthy
replica count present in the pool to CSPI status.
This will be helpful to the users to know no.of
replicas are present in the pool and out of them
Healthy
replica count.kubectl get cspi -n openebs
below will be outputkubectl get cspi -n openebs NAME HOSTNAME ALLOCATED FREE CAPACITY READONLY PROVISIONEDREPLICAS HEALTHYREPLICAS STATUS AGE cstor-stripe-fb4b 127.0.0.1 190k 19200M 19200190k false 2 1 ONLINE 36m
Provisioned Replicas: Count of volume replicas present in the pool.
Healthy Replicas: Count of Healthy volume replicas present in the pool.
Users will able to know provisioned and healthy replica count
without executing extra command
kubectl get cvr -n openebs -l cstorpoolinstance.openebs.io/name=<cspi_name>
Note to reviewers:
Provisioned Replicas
is calculated from the output ofzfs list
after filtering clones and pool name.Healthy Replicas
is calculated from usingzfs stats
which is json output.
ZFS Stats
will give the status information of replicaonly if the dataset has target IP. If we get provisioned
count of replicas from stats then there will be incorrect
output when user is restoring the volumes to mitigate
this we are fetching output from
zfs list
(which will giveall the datasets).
Corresponding API repo PR: openebs-archive/api#54
Signed-off-by: mittachaitu sai.chaithanya@mayadata.io