In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","id":41482,"featuredImage":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f38aec9c-1b9f-472b-8bc4-5177f93527b7_thumb.png","label":"Blog","replyCount":0,"views":150,"post":{"id":63100,"author":{"id":7898,"url":"\/members\/aluciani-7898","name":"aluciani","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/77accf89-4f79-48be-81e6-c2ac5507e29b.png","userTitle":"Chevalier","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Chevalier","color":"#660099"},"userLevel":7},"content":"

In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","url":"\/community-blog-154\/nutanix-community-podcast-2022-year-in-review-41482?postid=63100#post63100","creationDate":"2023-01-03T14:40:38+0000","relativeCreationDate":"10 days ago"},"contentType":"article","type":3,"likes":3,"hasCurrentUserLiked":false},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

解决了

如何重命名CVM容器？

  • 2017年4月18日
  • 4个答复
  • 2493次观点
Hatchda
徽章 +5
有没有一种方法可以在不重建容器的情况下重命名CVM容器？最近重新安装了Nutanix块的供应商没有遵循指示，并错误地命名了该集装箱。



该容器上有4个虚拟服务器，我想保留这些系统，而无需重建它们。



由于可用的50GB大于每个VM，因此我可以将每个VM放在本地NTNX-Local-DS（SSD）Datestore中吗？



然后销毁容器并重新创建它？



谢谢大卫
图标

最好的答案Patrbng2017年4月18日，15:52

\n
\nI 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.","className":"post__content__best_answer"}">
查看原件

    \n

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

    \n

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

    \n

    \nThen Destroy the Container and Recreate it?

    \n

    \nThanks,David","quoteUsername":"hatchda","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    4个答复

    Patrbng
    UserLevel 2
    徽章 +19
    您可以用正确的命名构建第二个容器，将其安装到主机上，然后对第二个容器进行存储VMotion。所有VM都移动后，您将其卸载后删除原始容器。绝对远离本地数据存储。



    我会在下班时间进行存储VMotion。我们在数据存储之间进行存储VMOTION的早期经验是，它导致了群集中所有VM的延迟。

    \n

    \nI 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.","quoteUsername":"patrbng","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Hatchda
    徽章 +5
    帕特尔恩，



    感谢您的想法..甚至没有想到创建另一个容器。它像魅力一样摇摆。该系统不在生产中，VM的存储VMotion很快就进行了。



    谢谢大卫

    \n

    \nThanks 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.

    \n

    \nThanks,David","quoteUsername":"hatchda","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Patrbng
    UserLevel 2
    徽章 +19
    好消息。希望您的Nutanix解决方案将取得巨大的成功！
    b
    UserLevel 4
    徽章 +17
    Hatchda为了重命名容器而不创建新的容器，您可以按照以下方式进行操作

    1.关闭容器上所有VM的电源

    2.从vSphere客户端从vSphere库存中删除VM

    3.通过棱镜卸下容器

    4.通过NCLI重命名容器

    ncli>容器LS

    ID：000546C7-A035-6C35-0000-00000000E316 :: 13361

    ncli>容器编辑ID = 13361 new-name = new-container-name

    5.刷新棱镜

    6.通过棱镜将容器安装到所有ESXI主机上

    7.通过VSPHERE客户端验证重命名的容器

    8.右键单击VMX文件，并添加到所有VM受影响的库存中
    hatchda<\/a> in order to rename container without creating new one you can do as follows

    \n1. power off all VM's on the container

    \n2. remove VM's from vsphere inventory via vsphere client

    \n3. unmount the container via Prism

    \n4. rename the container via ncli

    \n ncli> container ls

    \n Id : 000546c7-a035-6c35-0000-00000000e316::13361

    \n ncli> container edit id=13361 new-name=new-container-name

    \n5. refresh the prism

    \n6. mount the container to all ESXi hosts via Prism

    \n7. verify renamed container via vsphere client

    \n8. right click on vmx file and add to inventory for all VM's affected","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu