Skip to content

Clarify live migration limitation #3103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rsmontero merged 1 commit into from
Nov 11, 2024
Merged

Clarify live migration limitation #3103

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions source/management_and_operations/vm_management/vm_instances.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -854,10 +854,10 @@ To explain that, we are gonna use an example:
leases:
terminate:
edit: false
execute_after_weeks: 3
execute_after_weeks: 3
poweroff:
edit: true
execute_after_minutes: 5
execute_after_minutes: 5

The previous example will create two schedule actions:

Expand Down Expand Up @@ -1017,7 +1017,7 @@ There are some ``onevm`` commands operations meant for the cloud administrators:
**Deployment:**

- ``deploy``: Starts an existing VM in a specific Host.
- ``migrate --live``: The Virtual Machine is transferred between Hosts with no noticeable downtime.
- ``migrate --live``: The Virtual Machine is transferred between Hosts with no noticeable downtime. The VM storage cannot be migrated to other system datastores.
- ``migrate``: The VM gets stopped and resumed in the target host. In an infrastructure with :ref:`multiple system datastores <sched_ds>`, the VM storage can be also migrated (the datastore id can be specified).

Note: By default, the above operations do not check the target host capacity. You can use the ``--enforce`` option to be sure that the host capacity is not overcommitted.
Expand Down Expand Up @@ -1186,10 +1186,10 @@ After that you can access the VM and configure the SSH service:
.. |sunstone_guac_rdp| image:: /images/sunstone_guac_rdp.png
.. |sunstone_guac_rdp_interface| image:: /images/sunstone_guac_rdp_interface.png
.. |sunstone_guac_nic_1| image:: /images/sunstone_guac_nic_1.png
.. |sunstone_guac_nic_2| image:: /images/sunstone_guac_nic_2.png
.. |sunstone_guac_nic_2| image:: /images/sunstone_guac_nic_2.png
.. |sunstone_sg_main_view| image:: /images/sunstone_sg_main_view.png
.. |sunstone_sg_attach| image:: /images/sunstone_sg_attach.png
.. |fireedge_sunstone_ssh_list| image:: /images/fireedge_sunstone_ssh_list.png
:width: 45%
.. |fireedge_sunstone_ssh_console| image:: /images/fireedge_sunstone_ssh_console.png
:width: 45%
:width: 45%