You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose implementation of the VOLUME_CONDITION capability in the node server of TopoLVM in order to leverage this feature, but propose it as alpha grade.
What is use case behind this feature:
I think we could add VolumeCondition monitoring into TopoLVM in order to allow reporting abnormal volume statuses of the underlying logical volumes and volume groups via Events. to make transparent to the user whats wrong.
E.g. after a node reboot, if the LV activation fails, the volume event for an inactive logical volume could indicate to the user that remediation is necessary.
The text was updated successfully, but these errors were encountered:
It looks good to output the activation state of the volume corresponding to the PV as shown in your example. As discussed in the related issue, I guess it is difficult to use SMART.
This issue has been automatically marked as stale because it has not had any activity for 30 days. It will be closed in a week if no further activity occurs. Thank you for your contributions.
What should the feature do:
The CSI Specification has added an alpha feature for VolumeCondition monitoring. This has been adopted in kubernetes into alpha grade as of 1.21 https://kubernetes.io/docs/concepts/storage/volume-health-monitoring/
I would like to propose implementation of the VOLUME_CONDITION capability in the node server of TopoLVM in order to leverage this feature, but propose it as alpha grade.
What is use case behind this feature:
I think we could add VolumeCondition monitoring into TopoLVM in order to allow reporting abnormal volume statuses of the underlying logical volumes and volume groups via Events. to make transparent to the user whats wrong.
E.g. after a node reboot, if the LV activation fails, the volume event for an inactive logical volume could indicate to the user that remediation is necessary.
The text was updated successfully, but these errors were encountered: