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
Probably this is low priority. Not likely many user use this interface.
crm cluster remove tw3 works nicely so far.
Well, I expect the following alternative will do the same job. crm node delete tw3
Do you mean crm cluster remove <node> and crm node delete share the same code functions and execute the the process? Then we need another PR to do this
If the code can be reused directly, that will be great. From the behavior wise, crm node delete <node> should adjust_pcmk_delay_max here. Maybe, most of other behavior should be the same too.
Or, create it as an alias of "crm cluster remove"
Or, deprecate crm node delete, and eventually drop it?
It will also adjust the related cluster configurations and clean up the
leftover (eg. stopping the cluster services) on the removed node.
CloseClusterLabs#891.
It will also adjust the related cluster configurations and clean up the
leftover (eg. stopping the cluster services) on the removed node.
CloseClusterLabs#891.
Probably this is low priority. Not likely many user use this interface.
If the code can be reused directly, that will be great. From the behavior wise,
crm node delete <node>
should adjust_pcmk_delay_max here. Maybe, most of other behavior should be the same too.Or, create it as an alias of "crm cluster remove"
Or, deprecate
crm node delete
, and eventually drop it?Originally posted by @zzhou1 in #890 (comment)
The text was updated successfully, but these errors were encountered: