fence: add GET_CLIENTS_TO_FENCE caps

added a GET_CLIENTS_TO_FENCE so that
the plugins can register with this caps
to advertise that they support publishing
the metadata like identifier and the cluster
IP addresses of the clone cline for the fence
operations.

Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>

identity/README.md

@@ -234,6 +234,13 @@ message Capability {
       // plugin can invoke RPCs that require access to the storage system,
       // similar to the CSI Controller (provisioner).
       NETWORK_FENCE = 1;
+
+      // GET_CLIENTS_TO_FENCE indicates that the CSI-driver provides RPCs for a
+      // GET_CLIENTS_TO_FENCE operation to fet the clients to fence.
+      // The presence of this capability determines whether the CSI-Addons CO
+      // plugin can invoke RPCs that require access to the storage system,
+      // similar to the CSI Controller (provisioner).
+      GET_CLIENTS_TO_FENCE = 2;
     }
     // type contains the Type of CSI Service that the CSI-driver supports.
     Type type = 1;

identity/identity.proto

@@ -134,6 +134,13 @@ message Capability {
       // plugin can invoke RPCs that require access to the storage system,
       // similar to the CSI Controller (provisioner).
       NETWORK_FENCE = 1;
+
+      // GET_CLIENTS_TO_FENCE indicates that the CSI-driver provides RPCs for a
+      // GET_CLIENTS_TO_FENCE operation to fet the clients to fence.
+      // The presence of this capability determines whether the CSI-Addons CO
+      // plugin can invoke RPCs that require access to the storage system,
+      // similar to the CSI Controller (provisioner).
+      GET_CLIENTS_TO_FENCE = 2;
     }
     // type contains the Type of CSI Service that the CSI-driver supports.
     Type type = 1;