From ba3c6bf55525e79fa62a29fb1de80136c33dc5b4 Mon Sep 17 00:00:00 2001 From: chenxing Date: Fri, 20 Dec 2019 16:59:03 +0800 Subject: [PATCH] Add description of live_migration_timeout_action option Change-Id: I1e661751e62ecfa6ce9e3800cd5c3a285c0cca11 Closes-Bug: #1857013 --- doc/source/admin/configuring-migrations.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/source/admin/configuring-migrations.rst b/doc/source/admin/configuring-migrations.rst index 471d8ba66772..b2d76b131b6c 100644 --- a/doc/source/admin/configuring-migrations.rst +++ b/doc/source/admin/configuring-migrations.rst @@ -234,10 +234,12 @@ memory-intensive instances succeed. #. **Live migration completion timeout** - The Compute service aborts a migration when it has been running for too - long. The timeout is calculated based on the instance size, which is the - instance's memory size in GiB. In the case of block migration, the size of - ephemeral storage in GiB is added. + The Compute service will either abort or force complete a migration + when it has been running too long. This behavior is configurable + using the :oslo.config:option:`libvirt.live_migration_timeout_action` + config option. The timeout is calculated based on the instance size, which + is the instance's memory size in GiB. In the case of block migration, the + size of ephemeral storage in GiB is added. The timeout in seconds is the instance size multiplied by the configurable parameter :oslo.config:option:`libvirt.live_migration_completion_timeout`,