DaanHoogland commented on code in PR #356: URL: https://github.com/apache/cloudstack-documentation/pull/356#discussion_r1455410276
########## source/adminguide/virtual_machines/importing_unmanaging_vms.rst: ########## @@ -39,37 +49,37 @@ Importing Unmanaged Instances Use Cases and General Usage ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The ability to import Instances allows Cloud operators (both public and private) to onboard new tenants simply and quickly, -with the minimum amount disk IO. But also can be used in disaster recovery scenarios at remote sites (if storage is -replicated) and in the recreation of Instances which have been backed up (part of the code is indeed used in -CloudStack's Backup and Recovery feature). +The ability to import Instances allows Cloud operators to onboard new tenants simply and quickly, +with the minimum amount of disk IO. It can also be used in disaster recovery scenarios at remote sites (if storage is +replicated). -The most complex part of importing Instances is the mapping of an unmanaged Instance's Networks to CloudStack Networks. As an operator -could be importing tens or even hundreds of Instances, a UI for this feature has not been created as yet. +The most complex part of importing Instances is the mapping of an unmanaged Instance's Networks (on the hypervisor level) to CloudStack Networks, as an operator +could be importing tens or even hundreds of Instances. -If the 'destination' Network VLAN(s) and the requested service offerings match the existing Instance, then the Instance can be -imported whilst it is running. If the VLANs or service offerings do not match, then the Instance to be imported must be stopped. -Once the Instance has been added to CloudStack, starting it through CloudStack will alter the Instances settings in line with -those set in the CloudStack DB. +If the 'destination' Network's VLAN(s) and the requested service offerings match the existing VLAN and the CPU/RAM profile of the Instance on the hypervisor level, then the Instance can be +imported while it is running. If the VLANs or service offerings do not match, then the Instance to be imported must be stopped. +Once the Instance has been added to CloudStack, starting it through CloudStack will alter the Instance's settings on the hypervisor in line with +those set in the CloudStack DB (e.g. the Instance might be moved to a different Port Group on vSwitch/dvSwitch, with the corresponding VLAN) To import Instances, it is imagined that a Cloud Provider will: -#. List all of the existing Networks which the Instances to be imported are on. -#. Create corresponding Networks in CloudStack +#. List/get familiar all of the existing Networks on which the Instances to be imported are on. Review Comment: ```suggestion #. List/get familiar with all of the existing Networks on which the Instances to be imported are on. ``` -- 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. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
