Definitively something the charm should handle. I think we would need to implement two entry points to cluster member removal:
one opportunistic one running on the departing unit in its stop hook (a member departing sending a leave message is the preferred approach according to ovsdb-server documentation)
an action which can be issued by the operator on the remaining units in the event a unit is abruptly removed from the cluster without removing itself
Definitively something the charm should handle. I think we would need to implement two entry points to cluster member removal:
one opportunistic one running on the departing unit in its stop hook (a member departing sending a leave message is the preferred approach according to ovsdb-server documentation)
an action which can be issued by the operator on the remaining units in the event a unit is abruptly removed from the cluster without removing itself