We have just had a new cluster installed and its running AHV, I have used Nutanix for about 6 years but always with ESX so its all a bit new to me!
I’m sure I’ll have a few questions but currnetly I have this annoying issue! I have uploaded a few images to PC, qcow2 files, but when I deploy a VM using the images it always creates the VMs in the selfservicecontainer storage container, which is a tad annoying as I then have to move it manually using acli vm.update_container vm-name container=container name wait=false In PC the storage container drop down box for the VM is grayed out so I can’t change it in the PC web GUI. the cli works but I would like to create the VM in what ever storage container I want without having to move it after the event! Is this possible?
Page 1 / 1
Hi, Apart from doing it from prism element I don't know. I'm also interested to know if anyone has the answer/tips.
you can’t from PE either, if you select clone from image service there is no option to choose where the disk gets created
No exactly I meant you must to select the storage container when you upload the qcow2 through PrismElement.
Same concern. It seems no way to have a simple solution. What we could do is either using CLI command or using PC to update disk container after VM created.
Same concern. It seems no way to have a simple solution. What we could do is either using CLI command or using PC to update disk container after VM created.
the option to do it in PC for a VM deployed via image is grayed out, so you have to use the acli
That is how it works. Images uploaded via PC will come in the selfservicecontainer for all clusters that the image is uploaded to.
Images uploaded via prism element you can choice a storagecontainer (during upload), not afterwards.
All machines created from the image are placed in the storage container where the image resides.
Now the fun part, try to switch over to use storage policies. So all vm's can stay in the selfservicestorage container. With storage policies you can change the compression/rf/encryption/etc when needed for that vm. So you never have to "storagemigrate” the vdisks again. (which needs to be done via cli and is not possible via PE/PC)
so you can change the compression\dedupe per VM rather than at the storagecontainer level?
@Khoskin correct. But not dedupe I've updated my post ;)
ok we don’t use depupe or erasure coding anyway. Are there any docs for best practice for what workloads benefit from offline\inline compression, dedupe and erasure coding? We have a mixed workload of general purpose VM’s but a few fileservers and SQL boxes.
I've updated my post ;)