womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add nova-manage ironic-compute-node-move

Browse Source 
When people transition from three ironic nova-compute processes down
to one process, we need a way to move the ironic nodes, and any
associcated instances, between nova-compute processes.

For saftey, a nova-compute process must first be forced_down via
the API, similar to when using evacaute, before moving the associated
ironic nodes to another nova-compute process. The destination
nova-compute process should ideally not be running, but not forced
down.

blueprint ironic-shards

Change-Id: I33034ec77b033752797bd679c6e61cef5af0a18f
This commit is contained in:
John Garbutt
2023-06-26 17:32:38 +01:00
committed by Jay Faulkner
parent f1a4857d61
commit 08d7be1726
4 changed files with 141 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
releasenotes/notes/ironic-shards-5641e4b1ab5bb7aa.yaml
+5
View File
@@ -10,3 +10,8 @@ features:
which ironic nodes are managed by each nova-compute service.
Note that when you use ``[ironic]shard`` the ``[ironic]peer_list``
is hard coded to a single nova-compute service.
There is a new nova-manage command ``db ironic_compute_node_move`` that
can be used to move ironic nodes, and the associated instances, between
nova-compute services. This is useful when migrating from the legacy
hash ring based HA towards the new sharding approach.