The --restricted-migration option was added to allow evacuating nodes in the middle of a hypervisor upgrade, where the only migrations you were sure to be save were those off the evacuated node. In the mean time, migration tags have been added for precisely the purpose of hypervisor upgrades. So mention in the man pages that those usually are the better option.
Signed-off-by: Klaus Aehlig <aeh...@google.com> --- man/hbal.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/man/hbal.rst b/man/hbal.rst index 0bf50f6..00b1b74 100644 --- a/man/hbal.rst +++ b/man/hbal.rst @@ -341,7 +341,8 @@ The options that can be passed to the program are as follows: option, the only migrations that hbal will do are migrations of instances off a drained node. This can be useful if during a reinstall of the base operating system migration is only possible from the old - OS to the new OS. + OS to the new OS. Note, however, that usually the use of migration + tags is the better choice. \--select-instances=*instances* This parameter marks the given instances (as a comma-separated list) -- 2.2.0.rc0.207.ga3a616c
