自动在云中自动化的nutanix群集的选项

  • 2021年11月22日
  • 0答复
  • 285意见
dlink7
UserLevel 4
徽章 +19
  • dlink7
  • 主持人
  • 87个答复

我使用新的Nutanix Playbooks在AWS中制作了一个简短的视频。剧本提供了一种视觉方式，可以在混合云中自动化动作。由于制作视频简而言之，我没有花很多时间谈论您可以设定的选项。

Prism Central有很多警报，您可以用来触发您要采取的动作。如果您看不到正确的“警报”，则可以自定义现有的“警报”以满足您的需求，并将成为用户定义的警报。在我的示例中，我在添加节点时使用了超过80％的容量的关键记忆容量。如果您的群集通常高于10个节点，则可能尝试根据一个节点使用较高百分比，将是整体内存的较低百分比。同样，选择较低的内存百分比可能会更具侵略性。您还需要设置的一件事是“如果条件持续存在”。我没有设置它，以便我可以轻松录制演示。这将为您提供短暂的爆发。

用户定义的警报

当您进行配置时，如果其他语句触发了警报是否关键，或者是从自定义定义的警报中触发警告，则可以执行此操作。

如果/其他剧本

值得注意的是，警告或关键的拼写需要小写才能使其起作用。

一旦触发了关键工作流程，它将开始向群集添加一个节点。而不是在群集中添加节点并解决一个警报，而是使用AutoPilot来跟踪内存使用情况，以防我们需要添加更多节点。除非解决警报，否则剧本不会在同一警报上再次触发。使用自动驾驶仪，我们可以让它继续检查我们的状态。今天，使用剧本，您只能在每个剧本中拥有一套自动驾驶仪。我们正在根据警告批判性删除节点。通过删除，我们确实在Python脚本制作API之后确实解决了警报。完成一次后，我们将能够再次提醒触发器，从而导致更多节点被删除。

我在下面添加了脚本。还有其他一些博客文章使用类似的脚本可以帮助您浏览这些脚本。删除节点脚本基本上与添加脚本相同，但还检查集群中至少有3个节点。

如果您还有其他问题，请开火！还有更多的编码示例https://www.nutanix.dev/

1个附件
I had made a short video on auto scaling Nutanix cluster in AWS using new Nutanix Playbooks. Playbooks offer a visual way to start automating actions in your hybrid cloud. Due to making the video <\/a>short, I didn't spend a lot of time talking about options that you could set.\u00a0<\/p>

Prism central has a lot of alerts that you can use to trigger the action that you want to take. If you don't see the right \u201cAlert\u201d you can customize one of the existing ones to meet your needs and will be a user defined alert. In my example I was using a critical memory capacity over 80% capacity on adding nodes. If your clusters are typically higher than 10 nodes you might try using a higher percentage based on one node is going to be a lower percentage of memory overall. Likewise you could be more aggressive with picking a lower memory percentage. One thing that you'll want to set as well is the \u201ctrigger alert if condition persists for\". I didn't have it set so I could easily record the demo but I think it would be quite reasonable to 10 \u2013 15 minute range. This will give you some protection on short lived bursts.<\/p>

\u00a0<\/p>

\"//www.jhbzcj.com/next/hybrid-cloud-with-clusters-149/\"
user defined alerts<\/figcaption><\/figure>

When you go to configure your playbook you can do if else statements triggering on whether the alert was critical or if it was a warning from the custom defined alert.<\/p>

\u00a0<\/p>

\"//www.jhbzcj.com/next/hybrid-cloud-with-clusters-149/\"
If\/Else Playbooks<\/figcaption><\/figure>

\u00a0<\/p>

One thing to note, the spelling of warning or critical needs to be lowercase for it to work.<\/p>

Once the critical workflow is triggered it will start to add a node to the cluster. Instead of adding a node to the cluster and resolving an alert we are using autopilot to keep tracking memory usage in case we need to add more nodes. The playbooks won't get triggered again on the same alert unless the alert is resolved. Using autopilot we can let it keep checking the status for us. Today with playbooks you can only have one autopilot set per playbook. We are removing nodes based on the warning criticality. With removal, we do resolve the alert after the API is made by the python script. After it's done once, we would be able to alert the trigger again causing more nodes to be removed.<\/p>

\u00a0<\/p>

I have added my scripts below. There are some other blog posts that use similar scripts that can help you walk through those. The remove node script is basically the same as the add but is also checking if there are at least 3 nodes in the cluster.<\/p>

If you have any other questions, fire away!\u00a0 Also more coding examples on\u00a0https:\/\/www.nutanix.dev\/<\/a><\/p>

\u00a0<\/p>

\u00a0<\/p>","quoteUsername":"dlink7","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