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
Many a times a pool needs to be drained to be decomissioned. Typically the replicas need to go to the same pool group this pool belongs to. Currently you have to explicitly specify:
... -target=pgroup PoolGroupName
It would be nice just drop this extra parameters and by default
migration copy
would copy replicas to pool group(s) the pool belongs to.
NB: pool may belong to multiple pool groups. Mabe alpha version of this functionality should refuse migration (fail) if pool belongs to multiple pool groups with clear message.
The text was updated successfully, but these errors were encountered:
The behavior has to be backward compatible in the folllowing way:
migration copy ..... foo
Assumes, as before, that foo is destination pool
Whereas :
migration copy ... -target=pgroup
without specifying pool group name triggers this migration into the same pool group
invoked w/o -target and without pool name arguments
migration copy ...
has to fail just like it does now (this is somethig I have changed my mind about since Tuesday). I think this is safer as provides exact same behavior as before.
Many a times a pool needs to be drained to be decomissioned. Typically the replicas need to go to the same pool group this pool belongs to. Currently you have to explicitly specify:
It would be nice just drop this extra parameters and by default
would copy replicas to pool group(s) the pool belongs to.
NB: pool may belong to multiple pool groups. Mabe alpha version of this functionality should refuse migration (fail) if pool belongs to multiple pool groups with clear message.
The text was updated successfully, but these errors were encountered: