You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/01/04 15:45:05 UTC

[GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #170: systemvm: vmware migration changes

andrijapanicsb commented on a change in pull request #170:
URL: https://github.com/apache/cloudstack-documentation/pull/170#discussion_r551395376



##########
File path: source/adminguide/systemvm.rst
##########
@@ -812,6 +812,13 @@ The administrator can log in to the secondary storage VM if needed.
 .. |vr-upgrade.png| image:: /_static/images/vr-upgrade.png
    :alt: Button to upgrade VR to use the new template.
 
+Migrating System VMs
+--------------------
+
+System VMs (any of the Console Proxy VM, Secondary Storage VM, Virtual Router or Load Balancer) can be migrated across hosts using migrateSysteVm API or migrate action in the UI. These VMs can be migrated between hosts of the same cluster only.
+
+Since 4.16, for VMware, migration of System VMs can also be done a destination host in a different cluster belonging to the same pod. Storage migration of the stopped System VMs is also supported.

Review comment:
       ```suggestion
   Since CloudStack 4.16, for VMware, migration of System VMs can also be done to a destination host in a different cluster belonging to the same pod (in case of cluster-wide primary storage pools, this will cause the Root volume of the system VM to be migrated to the appropriate datastore in the new cluster). Storage migration of stopped System VMs is also supported.
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org