5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
In summary: So a clone has hooks into the VM it was cloned from, however the clone can be considered a standalone VM as the VM it was cloned from can be Deleted and the clone will be unaffected. As well the clone can be downloaded and uploaded to another cluster (into Image Service) to use as a ~golden image~. It can even be downloaded from its original cluster, and uploaded back into its (original cluster) Image Service, and operate as if it were a standalone VM. Pardon my drawn out thread but I got corn-fused with naming conventions of VM’s and wanted to make sure I understood the process deeply. Thanks again -Sean
How about this method ? 1. create a windows VM and patch it, shutdown. 2.clone it, bring up clone and sysprep it, shutdown 3.Identify the disk (how… name =uuid) and use WINSCP to copy it down to local box which is on a CVM network. 4.copy it back up to image service on same cluster (to roll out new VMs from) 5.copy it to other clusters for same reason/method. Although I dont totally understand the hooks a clone has to a original, I do understand you can DEL the original and the clone should be fine, right ? So once its copied down to local machine is the clone now a standalone with no hooks in the original and could be copied back up as a new box (or Image Service in the case ) ?
When you say “ Deploying a VM from an image, however, does trigger images’ storage blocks being marked as immutable and thus causes storage data of the image and all VMs that are deployed from it to be shared or linked. “ When I deploy a VM from an image I am using the Nutanix AHV Image Service. I have uploaded a disk file into that service. I am not “cloning” a image(VM). Therefore does that apply above ? Thanks this is helpful, I really appreciate your daily attention to this matter ! -SeanG
Manual at the moment -Sean
So how would one make a “copy” that’s independent of the original ? (or can I copy the Clones disk without issues)? I would like to keep the original image to bring up and patch every month, then copy it and sysprep it to distribute the Syspreped Image to the Image Service on all our AHV clusters. Then I have a Syspreped image I can roll out VM’s with.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
