diff options
| author | Zhang Chen <chen.zhang@intel.com> | 2019-03-22 18:13:33 +0800 |
|---|---|---|
| committer | Juan Quintela <quintela@redhat.com> | 2019-03-25 18:45:46 +0100 |
| commit | 5ed0deca41b201a66d858d7296fe6b780d757404 (patch) | |
| tree | 1e25eb91f6770f99c589a82a623b6d9eadecd8b0 /qapi/migration.json | |
| parent | 82cd368ccd0a962f1f141e0e529abc54d5ab504e (diff) | |
Migration/colo.c: Make user obtain the last COLO mode info after failover
Add the last_colo_mode to save the status after failover.
This patch can solve the issue that user want to get last colo mode
use query_colo_status after failover.
Signed-off-by: Zhang Chen <chen.zhang@intel.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'qapi/migration.json')
| -rw-r--r-- | qapi/migration.json | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/qapi/migration.json b/qapi/migration.json index e383951765..cfde29acf8 100644 --- a/qapi/migration.json +++ b/qapi/migration.json @@ -1380,12 +1380,17 @@ # @mode: COLO running mode. If COLO is running, this field will return # 'primary' or 'secondary'. # +# @last_mode: COLO last running mode. If COLO is running, this field +# will return same like mode field, after failover we can +# use this field to get last colo mode. (since 4.1) +# # @reason: describes the reason for the COLO exit. # # Since: 3.1 ## { 'struct': 'COLOStatus', - 'data': { 'mode': 'COLOMode', 'reason': 'COLOExitReason' } } + 'data': { 'mode': 'COLOMode', 'last_mode': 'COLOMode', + 'reason': 'COLOExitReason' } } ## # @query-colo-status: |