This week on the podcast, Dwayne chats with Marc Trouard-Riolle, about Nutanix Cloud Clusters (NC2) on Azure and how to get started. Nutanix Cloud Clusters (NC2) on Microsoft Azure enables your applications to be run where you want them, on-premises or in the public cloud, all operated as a single cloud.<\/p>

<\/oembed><\/p>

考虑的所有因素 - 升级顺序和预先准备指南

阿罗纳
秩
UserLevel 6
徽章 +5

面对现实吧，升级令人生畏，令人困惑，频繁，不可避免，而且痛苦。旨在帮助准备过程，并减轻至少一些担心的Nutanix雅典卫城升级（通过Web控制台升级AOS，Prism Central，Prism Central，Amplevisors和相关软件）。

建议升级订单：

  1. Prism Central（PC）：升级和运行NCC在Prism Central上。
  2. PC：升级Prism Central。
  3. PC：运行NCC。
  4. Prism Element簇（PE）：升级并运行NCC。
  5. PE：升级基础。
  6. PE：运行和升级生命周期经理（LCM）：
    • 执行LCM清单（还更新LCM框架）。在此步骤中，请勿升级除LCM以外的任何其他软件组件。
  7. PE：升级AOS。
  8. PE：运行和升级生命周期经理（LCM）：
    • 执行LCM清单（还更新LCM框架）。
    • 按照LCM的建议，升级SATA DOM固件（用于使用SATA DOMS的硬件）。
    • 按照LCM（BIOS / BMC /其他）建议升级所有其他固件。
  9. PE：升级AHV的AHV群集。
  10. PE：升级集群管理程序托管AHV以外的其他托管。
  11. PE：运行NCC。

数字。Nutanix升级订单1 of 2：棱镜中央和棱镜元素簇

数字。Nutanix升级订单2共2个：管理程序主机

Nutanix建议您在预定的维护窗口或正常工作时间内执行安装和升级。您可以在此期间升级，但是您的用户可能会在升级过程中遇到一些延迟。对于仅使用1GBE网络上行链接的群集，由于可用于此配置的带宽有限，该延迟可能是显而易见的。

来宾VM可能会在主机之间进行直播，这取决于执行的升级，对他们的服务几乎没有影响。用户可以访问其VM，并在升级期间能够正常工作。

在升级无法实现的迁移的VM之前，例如具有VGPU或亲和力规则的VM，您可能需要关闭或调整设置。通常，此建议适用于需要重新启动主机的任何升级（例如管理程序升级）。如果您不这样做，则在撤离访客VM时，升级操作可能会停滞不前。

：感叹：确保阅读在你开始之前，，，，升级清单也参考和资源（列出所有兼容性矩阵的URL）该指南部分作为起点。

愿原力与你同在！：fingers_crossed：

Let\u2019s face it, upgrades are daunting, and confusing, and frequent, and unavoidable, and, well, painful. Aiming to help with the preparation process and alleviate at least some of the worries Nutanix put together Acropolis upgrade (Upgrading AOS, Prism Central, Hypervisors, and Related Software Through The Web Console)<\/a>.<\/p>

Recommended Upgrade Order:<\/a><\/p>

  1. Prism Central (PC): Upgrade and run NCC on Prism Central.<\/li>\t
  2. PC: Upgrade Prism Central.<\/li>\t
  3. PC: Run NCC.<\/li>\t
  4. Prism Element clusters (PE): Upgrade and run NCC.<\/li>\t
  5. PE: Upgrade Foundation.<\/li>\t
  6. PE: Run and upgrade Life Cycle Manager (LCM):\t
该主题已关闭以供评论

2个答复

r
秩

Nutanix何时推荐升级软件？何时可以从“支持下载”页面或何时在1-click中下载？就像官方推荐一样。像是一个测试问题。：眨眼：

When does Nutanix recommend upgrading software? When is is available for download from the support downloads page or when it is in the 1-click? Like officially recommend. Like if it was a test question.\u00a0\":wink:\"<\/p>","quoteUsername":"Rob Thomas","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
阿罗纳
秩
UserLevel 6
徽章 +5

你好 @Rob Thomas

这是一个很好的问题，谢谢。据我所知，您寻求的格式的答案不存在。我将尝试解释为什么我能做到最好。

设置环境有多种方法。有些环境对高可用性没有兴趣（不仅在集群中，而且对环境/场地尺度），有些环境对失败方案进行了次要或中等的视为，并且有些人对它们的影响很低，而失败的容忍度很低，而6秒钟的停电是已经在可接受的区域外面了。有些站点在两个供应商中并行镜像设置，因此，如果/当任何一个供应商的软件中存在错误时，都有一个选项可以隔离问题并在搜索或等待时切换到其他供应商解决方案。

因此，有LTS和STS发布。首先是更稳定，更保守，具有更长的寿命，更新频率较低。后者更加频繁，更具探索性。

因此，总的来说，我认为要考虑的主要因素有两个主要因素：一个是对维护窗口的宽容，另一个是对维护窗口的宽容 - 我们称其为渴望新功能，因为我现在找不到更好的词。这两件事在同一公司内的站点之间可能会有所不同，因此不一定是公司政策。

关于使用1键可用性，这不是一个非常可靠的标记。每当与组件或功能找到问题时，该项目禁用了1-click选项。

我想说的是，要保持安全的一面（假设这是目标），这不仅与Nutanix有关，而且根据我的经验，至少有一个月的供应商在推出之前。如果您有一个额外的安全性，请在测试/开发网站上将其推出，如果您有一个网站，然后在打电话之前持续几周。

Hi @Rob Thomas<\/user-mention>\u00a0<\/p>

That is an excellent question, thank you. To the best of my knowledge, the answer in the format you seek does not exist. I will attempt to explain why it is so the best I can.<\/p>

There is more than one way to set up the environment. Some environments have no interest in high availability (not only within the cluster but on the environment\/site scale), some have considered failure scenarios\u00a0minorly or moderately and accounted for them, some have a very low tolerance for failure where a 6 seconds outage is already outside of the acceptable zone. There are sites that have mirrored setups in two vendors in parallel so that if\/when there is a bug in the software of either of the vendors there is an option to isolate the issue and switch over to the other vendor while searching or waiting for the solution.<\/p>

Hence there are LTS and STS releases. First are more stable, more conservative, have a longer life cycle, less frequent updates. The latter are more frequent, more explorative.<\/p>

So in overall, there are two main factors, I think, to consider: one being the tolerance to maintenance windows and the other \u2013 let\u2019s call it hunger for new features as I can\u2019t find a better word for it right now. Those two things can vary from site to site within the same company drastically so that is not necessarily even the company policy.<\/p>

In regards to using 1-click availability, that is not a very reliable marker to use. Whenever an issue is found with a component or a feature the 1-click option is disabled for that item.<\/p>

I would say, to stay on the safer side (assuming that\u2019s the goal), and that is not only with Nutanix but with any vendor in my experience, give it at least a month before rolling it out. To be extra safe roll it out in the test\/dev site if you have one and let it run for a few weeks before you make the call.<\/p>","quoteUsername":"Alona","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