解决了

Horizo​​n View Instant Clone＆Nutanix固件更新....理智检查..

  • 2019年5月24日
  • 4个答复
  • 1806年的观点
v
徽章
我们已经在Nutanix上运行了Horizo​​n View环境，待了6个月多一点，我准备进行第一轮磁盘/BIOS等固件更新。我的主要关心是，由于我们正在使用Horizo​​n View Instant Clones，因此每个主机上的“父映像”上有一个功能...我们正在运行View 7.5，并且我知道在以前的版本中，有一个称为“ Instant Clone”的属性维护“您将值更改为1，它将关闭并删除该父映像，从而将任何台式机放在该主机上的配置中，从而使您可以将其放置在维护模式下并进行业务。我需要一些清晰度（和理智检查！），如何允许（或者我不使用LCM）执行这些必要的固件更新而不将我的视图环境放下...使用了24x7的环境并且无法承受中断..请给我看你的轮子，所以我无需重新发明！谢谢社区！
图标

最好的答案实际上2019年9月30日，18:48

\n
    \n
  1. Edit the value for \"InstantClone.Maintenance\" to 1 \n
  2. After a few minutes, vCenter and Horizon View will see that value, and shut down\/delete the cp-parent VMs on that host, and the value will change to 3 \n
  3. Once you see the cp-parent VMs are gone, you can go into Prism and go to LCM, once you have performed an inventory, you should be able to put a check next to the host you want to upgrade (ONLY CHECK THE HOST YOU WISH TO UPGRADE!). \n<\/ol>LCM will take care of the rest. It will invoke DRS (make sure HA Admission control is disabled or Nutanix will fail the process). It will migrate all workloads off the host, shut down the CVM, place the host into maintenance mode and begin the firmware upgrades. WHen the host comes back online, all your health checks are good, just change the value back to 0, and move some workloads back. When new VMs are needed in your instant clone pool, the cp-parent images will be spawned again. I would generally wait until the cp-parent images were re-spawned before moving to the second host. I only have 4 nodes in my instant clone cluster currently, so depending on how many firmware are needed bank on at least an hour per node I am on AOS 5.10.5 LTS, as there were some much needed improvements in LCM in the 5.10.x line up, so be sure you are on that build or higher.
    \n
    \nNOTE: if you have ANY nodes that require SATADOM upgrades, you HAVE to apply them on every node before any other firmware shows as available.
    \n Let me know, i'm happy to answer any other questions!","className":"post__content__best_answer"}">
查看原件
该主题已关闭以供评论

4个答复

m
徽章
@virtallysteve，，，，
您是否找到了这个答案？我们使用即时克隆站立一个新的集群并遇到了同一件事。我想知道我是否只需要一次手动执行每个节点，而不是我更喜欢的滚动升级方法。希望您找到一个更好的解决方案 - 我很想听听。
@VirtuallySteve<\/user-mention>,
\nDid you ever find an answer to this? We're standing up a new cluster using instant clones and running into the same thing. I'm wonder if I just have to manually do each node one at a time instead of the rolling upgrade method that I'd far prefer. Hopefully you found a better solution - I'd love to hear it.","quoteUsername":"mjg","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
v
徽章
MJG，目前，执行运行即时克隆的节点的最佳方法是单独的。VMware使它变得更加容易，因为您会注意到每个节点（在VSPhere Web客户端中）具有自定义属性“ instantclone.saintclone.maintenance”，并且当前值应为0。我的步骤要升级固件或任何您的步骤需要将主机置于维护模式下：
  1. 编辑“ instantclone.maintenance”的值为1
  2. 几分钟后，vCenter和Horizo​​n视图将看到该值，并关闭/删除该主机上的CP-Parent VM，该值将更改为3
  3. 一旦看到CP-Parent VM消失了，您就可以进入Prism并转到LCM，一旦您执行了库存，就应该能够将支票放在主机旁边您想要升级的支票（只检查您的主机希望升级！）。
LCM将照顾其余的。它将调用DRS（确保禁用HA入院控制或Nutanix将失败该过程）。它将从主机上迁移所有工作负载，关闭CVM，将主机置于维护模式并开始固件升级。当主机返回在线时，您的所有健康检查都很好，只需将值更改回0，然后将一些工作负载移回。当您的即时克隆池中需要新的VM时，将再次产生CP-Parent图像。我通常会等到重新产生CP父母图像后才移至第二个主机。目前，我的即时克隆群集中只有4个节点，因此，根据每个节点至少需要多少个固件，我在AOS 5.10.5 LTS上，因为5.10中的LCM需要有所改善。X排队，因此请确保您使用该构建或更高。

注意：如果您有任何需要SATADOM升级的节点，则必须在所有其他固件显示之前将它们应用于每个节点。
让我知道，我很高兴回答其他任何问题！
\n
    \n
  1. Edit the value for \"InstantClone.Maintenance\" to 1 \n
  2. After a few minutes, vCenter and Horizon View will see that value, and shut down\/delete the cp-parent VMs on that host, and the value will change to 3 \n
  3. Once you see the cp-parent VMs are gone, you can go into Prism and go to LCM, once you have performed an inventory, you should be able to put a check next to the host you want to upgrade (ONLY CHECK THE HOST YOU WISH TO UPGRADE!). \n<\/ol>LCM will take care of the rest. It will invoke DRS (make sure HA Admission control is disabled or Nutanix will fail the process). It will migrate all workloads off the host, shut down the CVM, place the host into maintenance mode and begin the firmware upgrades. WHen the host comes back online, all your health checks are good, just change the value back to 0, and move some workloads back. When new VMs are needed in your instant clone pool, the cp-parent images will be spawned again. I would generally wait until the cp-parent images were re-spawned before moving to the second host. I only have 4 nodes in my instant clone cluster currently, so depending on how many firmware are needed bank on at least an hour per node I am on AOS 5.10.5 LTS, as there were some much needed improvements in LCM in the 5.10.x line up, so be sure you are on that build or higher.
    \n
    \nNOTE: if you have ANY nodes that require SATADOM upgrades, you HAVE to apply them on every node before any other firmware shows as available.
    \n Let me know, i'm happy to answer any other questions!","quoteUsername":"VirtuallySteve","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
m
徽章
@virtallysteve
感谢您的快速回复！昨天，我能够使用这种方法在几个节点上获得固件，并且进行得很顺利。

不要为主题提出太多内容，但是您是否介意我问您如何处理AOS升级？我只使用了滚动升级方法，这似乎会破裂。是否可以一次执行AOS一个节点/让过程等待您切换下一个节点instantclone.maintenance至1？
@VirtuallySteve<\/user-mention>
\nThanks for the quick reply! I was able to get firmware on a couple of nodes using this method yesterday and it went smoothly.
\n
\nNot to fork the topic too much, but do you mind if I ask how you're handling the AOS upgrades? I've only ever used the rolling upgrade method which this would seem to break. Is it possible to do AOS one node at a time\/have the process wait for you to switch the next node InstantClone.Maintenance to 1?","quoteUsername":"mjg","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
v
徽章

MJG，不用担心，我真的很高兴能提供帮助！

很高兴您的固件更新进展顺利！绝对要慢一点，以确保节点升级之间的一切都健康。AOS对主机完全无破坏。无需将主机安装在每个CVM上安装AO，并以舞台/安全的方式重新启动它们，因此无需将主机置于维护模式。让Nutanix群集为CVM做事。

我强烈建议您从事的第一批固件/AOS升级工作，请与Nutanix打开主动票。让他们进行预付健康检查，他们将在您的工作期间保持门票打开（如果您有问题，您将获得下一个在已经打开的机票的情况下获得的支持）。我曾经在下一个工作日回电，让他们进行升级后的健康检查。我很乐意分享自己的命令等，我现在自己运行，以确保事情健康。

mjg, no worries, I am really glad to help!<\/p>

Glad your firmware updates are going well! Definitely take it slow to ensure everything is healthy between node upgrades. AOS is completely non-disruptive to the hosts. No need to place the hosts in maintenance mode, as it installs AOS on each CVM, and reboots them in a staged\/safe fashion. Let the Nutanix cluster do its thing for the CVMs.<\/p>

I highly recommend the first couple types of firmware\/AOS upgrade work you do, open a proactive ticket with Nutanix. Have them do a pre-work health check, they'll keep the ticket open during your work (in the event you have an issue, you'll get next in line support with a ticket already opened). I used to then call back in the next working day and have them do post-upgrade health checks. I'm more than happy to share my commands etc that I run on my own now to ensure things are healthy.<\/p>","quoteUsername":"VirtuallySteve","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