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
Do we have the option to remove a nsm cluster from the abm?
You can mark a nsm cluster as lost but what if we want to remove the cluster?
The current installation with framework doesn't support already registered nsm clusters.
If we could remove the nsm clusters from the abm this should also help.
ticket: openvstorage/framework#1632
The text was updated successfully, but these errors were encountered:
We could implement that an unused nsm cluster could be removed, and I think it should be relatively easy.
(The command would give an error in case the nsm host is already in use.)
But first: is this actually needed? It seems to me that ops should fix their setup/registration flow?
Fixing the setup/registration flow should be priority numero uno indeed.
But since mistakes can always occur, i think such a call could come in
handy. Instead of having to re-deploy the entire cluster, they can easily
remove the registered NSM
On Mon, May 29, 2017 at 4:22 PM, Jan Doms ***@***.***> wrote:
We could implement that an unused nsm cluster could be removed, and I
think it should be relatively easy.
(The command would give an error in case the nsm host is already in use.)
But first: is this actually needed? It seems to me that ops should fix
their setup/registration flow?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#713 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AM6JZizoiFU4otDObxBSPExARj8T8Owwks5r-tSzgaJpZM4NVHBU>
.
Do we have the option to remove a nsm cluster from the abm?
You can mark a nsm cluster as lost but what if we want to remove the cluster?
The current installation with framework doesn't support already registered nsm clusters.
If we could remove the nsm clusters from the abm this should also help.
ticket: openvstorage/framework#1632
The text was updated successfully, but these errors were encountered: