andrijapanicsb commented on a change in pull request #139:
URL:
https://github.com/apache/cloudstack-documentation/pull/139#discussion_r440958947
##########
File path: source/adminguide/virtual_machines/unmanage_vms.rst
##########
@@ -0,0 +1,81 @@
+About Unmanaged Virtual Machines
+--------------------------------
+
+As of ACS 4.14, CloudStack has the concept of **unmanaged** virtual machines.
These are virtual machines that are on CloudStack
+managed hosts, but that are not in CloudStack's database and therefore
CloudStack cannot control (manage) then in any way. Previously,
+such VMs could exist, but CloudStack did not 'see' them (their existence
*would* be reported in logs as unrecognised VMs).
+
+From ACS 4.14 onwards, CloudStack is able to list these VMs via the
listUnmanagedInstances API command and then import (also known as ingest)
+those unmanaged VMs via the importUnmanagedInstance API so that they become
CloudStack managed guest instances
+
+From ACS 4.15 onwards, administrators are able to unmanage guest virtual
machines.
+
+.. note:: This is currently only available for **vSphere** clusters.
+
+Unmanaging Virtual Machines via API
+-----------------------------------
+
+Administrators are able to unmanage guest virtual machines from CloudStack.
Once unmanaged, CloudStack can no longer monitor, control or administer the
provisioning and orchestration related operations on a virtual machine.
+
+To unmanage a guest virtual machine, an administrator must invoke the
unmnageVirtualMachine API passing the ID of the virtual machine to unmanage.
The API has the following preconditions:
Review comment:
```suggestion
To unmanage a guest virtual machine, an administrator must invoke the
unmanageVirtualMachine API passing the ID of the virtual machine to unmanage.
The API has the following preconditions:
```
----------------------------------------------------------------
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:
us...@infra.apache.org
