From 17ebad53979ff590ef70c67366d4ea3ab71d0896 Mon Sep 17 00:00:00 2001
From: suzhengwei <suzhengwei@inspur.com>
Date: Tue, 7 Mar 2023 18:09:22 +0800
Subject: [PATCH] releasenote for Masakari VMove

Change-Id: I640ea99f680b5ff4a773a58282a6d4e1c16366da
---
 .../notes/blueprint-add-vmoves-348fd430aa936721.yaml   | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 releasenotes/notes/blueprint-add-vmoves-348fd430aa936721.yaml

diff --git a/releasenotes/notes/blueprint-add-vmoves-348fd430aa936721.yaml b/releasenotes/notes/blueprint-add-vmoves-348fd430aa936721.yaml
new file mode 100644
index 00000000..eab9fe31
--- /dev/null
+++ b/releasenotes/notes/blueprint-add-vmoves-348fd430aa936721.yaml
@@ -0,0 +1,10 @@
+---
+features:
+  - |
+    It persists vm moves information for one host failure notification
+    into the database, which could help users to insight the process
+    or result of the host recovery workflow, such as which vms evacuated
+    succeed or failed, and which ones are still evacuating.
+
+    Added VMove API in microversion 1.3, please refer to ..  _`VMoves`:
+    https://docs.openstack.org/api-ref/instance-ha/#vmoves-vmoves