The nbd-clid service will be work in the client side and will handle:
a), all the control cmds from nbd-cli, such as the create/delete/map/delete/list, etc.
b), auto restore the stale connections after the nbd-runner service or the hosted node rebooted.
c), will periodically ping the liveness of the nbd-runner daemon, if it is rebooted some any reason, it will try to tigger the restore stuff again.
d), nbd-clid could work on the same node with nbd-runner service or a separate node.
This will add the nbd-clid service support.
The nbd-clid service will be work in the client side and will handle: a), all the control cmds from nbd-cli, such as the create/delete/map/delete/list, etc. b), auto restore the stale connections after the nbd-runner service or the hosted node rebooted. c), will periodically ping the liveness of the nbd-runner daemon, if it is rebooted some any reason, it will try to tigger the restore stuff again. d), nbd-clid could work on the same node with nbd-runner service or a separate node.