Solved

How to rename CVM Container?

  • 18 April 2017
  • 4 replies
  • 3062 views

Badge +5
Is there a way to rename the CVM Container without rebuilding the container? The vendor who recently re-installed the Nutanix Block didn't follow the directions and named the container incorrectly.

The container has 4 Virtual Servers running on them and I would like to preserve these systems without the need of rebuilding them.

Could I place each VM in the Local NTNX-local-ds (SSD) datestore since the 50GB available is larger than each VM?

Then Destroy the Container and Recreate it?

Thanks,David
icon

Best answer by patrbng 18 April 2017, 15:52

View original

This topic has been closed for comments

4 replies

Userlevel 2
Badge +19
You could build a second container with the correct naming, mount it to the hosts and then do a storage vmotion to the second container. After all the VMs are moved you then delete the original container when its unmounted. Definitely stay away from the local datastore.

I would do the storage vmotion's in the off-hours though. Our early experience with storage vmotions between data storage was that it caused increased latency to all the vm's in the cluster.
Badge +5
patrbng,

Thanks for the idea.. didn't even think of creating another Container. It woked like a charm. The system is not in production and the storage vMotion of the VM's went fairly quickly.

Thanks,David
Userlevel 2
Badge +19
Great news. Hopefully you'll have great success with your Nutanix solution!
Userlevel 3
Badge +17
hatchda in order to rename container without creating new one you can do as follows
1. power off all VM's on the container
2. remove VM's from vsphere inventory via vsphere client
3. unmount the container via Prism
4. rename the container via ncli
ncli> container ls
Id : 000546c7-a035-6c35-0000-00000000e316::13361
ncli> container edit id=13361 new-name=new-container-name
5. refresh the prism
6. mount the container to all ESXi hosts via Prism
7. verify renamed container via vsphere client
8. right click on vmx file and add to inventory for all VM's affected