新VM的默认保护组

  • 2014年2月17日
  • 8回复
  • 1488次观点
偷窥
UserLevel 4.
徽章 +20
你好，

是否有一种方法（除了休息或脚本/ crontab之外）将在容器中创建的任何新VM放到“默认”保护域中？

基本原理是为群集的所有VM创建一个“标准”策略，如“默认情况下，每2小时复制此群集”，如果需要处理异常，则可以按案例进行处理。

我有一个攻击Nutanix的客户，目标是从NetApp / NFS / IBM刀片解决方案到Nutanix，如果一切顺利。
问题是，它们使用SnapMirror每1小时复制其数据存储（1按群集）。他们确实希望能够只复制VM，但他们不希望将每个新VM单独添加到保护域。

Sylvain。
Sylvain Huguet - 2X Nutanix Technology Champion 2015-2016，法国Nutanix Connect章冠军，法国VMug Leader，6x VMware Vexpert 2011到2016年
    \n
    \nIs there a way (other than REST or scripting\/crontab) to put any new VM created inside a container to a \"default\" protection domain?
    \n
    \nThe rationale is to create a \"standard\" policy for all VMs of a cluster like \"this cluster is replicated every 2h, by default\", then if exceptions need to be handled, they can be treated on a case by case basis.
    \n
    \nI have a customer that is PoCing Nutanix, with the goal to move from a NetApp\/NFS\/IBM Blades solution to Nutanix if everything goes well.
    \nProblem is, they use SnapMirror to replicate their datastore (1 by cluster) every 1h. They do want to be able to replicate just a VM, but they don't want to have to add each new VM individually to a protection domain.
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    8回复

    Dlink7.
    UserLevel 4.
    徽章 +19
    只是通过今天的脚本。虽然问题，您是否需要每个容器或群集级别设置的默认保护域？或者群集是否有默认值，然后容器会过度全局设置？
    偷窥
    UserLevel 4.
    徽章 +20
    最小值应在容器级别。
    我们比我们创建容器更频繁地创建VM。

    如果可以为群集定义默认值，则在容器级别覆盖它，请罚款，但我也可以为群集的每个新容器设置默认保护组...

    无论如何，随着容器需要复制到另一个容器，这并没有很多意义，没有？群集如何能够自动决定现场A上的哪个容器达到哪个容器B？

    Sylvain。
    Sylvain Huguet - 2X Nutanix Technology Champion 2015-2016，法国Nutanix Connect章冠军，法国VMug Leader，6x VMware Vexpert 2011到2016年
    \nWe create VM far more often than we create containers.
    \n
    \nIf it's possible to define a default for a cluster then override it at the container level, fine, but I can also set the default protection group for each new container of the cluster...
    \n
    \nAnyway, as a container needs to replicate to another container, this doesn't make a lot of sense, no? How would the cluster be able to automaticaly decide which container on site A goes to which container on site B?
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Dlink7.
    UserLevel 4.
    徽章 +19
    不需要容器到容器复制，它将全部在生产域级别升级，您可以在一个复制到不同网站的辅送者中拥有VM。
    偷窥
    UserLevel 4.
    徽章 +20
    我不知道我是否理解你的帖子，但如果你的意思是它必须在保护域级别设置，是的。
    我在这种情况下我的想法是将默认保护域分配给群集或容器中创建的所有新VM。
    这样，您可以配置保护域设置一次（如复制频率），然后将所有新VM继承这些设置。
    如果您需要VM的特定设置，则仍然能够将其他保护域分配给此VM并实际上覆盖默认设置。

    在我的情况下，我们将从站点1上的集群A上每小时复制所有VM，以便在站点2上的群集B中，我们将被覆盖。
    在Futur中，如果我们创建不需要复制的VM（如vshield代理VM for Exemple），我们可以为这些VM创建特定容器，或者从保护域中排除它们并达到所需的结果。

    Sylvain。
    Sylvain Huguet - 2X Nutanix Technology Champion 2015-2016，法国Nutanix Connect章冠军，法国VMug Leader，6x VMware Vexpert 2011到2016年
    \nMy idea in this case would be to have a default protection domain assigned to all new VMs created in the cluster or container.
    \nThat way, you can configure the protection domain settings once (like replication frequency) and then have all new VMs inherit these settings.
    \nIf you need specific settings for a VM, you would still have the ability to assign another protection domain to this VM and effectivly override the default settings.
    \n
    \nIn my case, as we are replicating all VMs every hour from cluster A on site 1 to cluster B on site 2, we would be covered.
    \nIn the futur if we create VMs that does not need replication (like vShield agent VM for exemple), we could either create a specific container for these VMs, or exclude them from the protection domain and achieve the desired result.
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Dlink7.
    UserLevel 4.
    徽章 +19
    使用NoS 4.0和PowerShell，您可以自动化此操作

    http://itblooppressure.com/2014/04/17/nos-4-0-powershell-add-all-your-vms-to-a-protection-domain/
    \n
    \nhttp:\/\/itbloodpressure.com\/2014\/04\/17\/nos-4-0-powershell-add-all-your-vms-to-a-protection-domain\/","quoteUsername":"dlink7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    偷窥
    UserLevel 4.
    徽章 +20
    伟大的解决方案！

    我建议了一个应该工作的一衬垫。
    我无法测试它（尚未），但我在升级到NOS4.0时立即计划

    但是，我仍然希望在Nutanix群集水平上进行真正集成的东西，而不是从外部自动化/策划。
    事情是，这个解决方案真的很整洁，但我仍然依赖于一个脚本，必须监视，也许升级。
    另一个移动的件。

    我的客户，这个请求已经管理了更多的4200虚拟机，他们可能会在未来2年内加倍该号码。默认情况下，默认情况下将真正有用。

    Sylvain。
    Sylvain Huguet - 2X Nutanix Technology Champion 2015-2016，法国Nutanix Connect章冠军，法国VMug Leader，6x VMware Vexpert 2011到2016年
    \n
    \nI suggested a one liner that should work, too.
    \nI cannot test it (yet) but I plan to as soon as I upgrade to NOS4.0
    \n
    \nBut still, I would like something realy integrated at the Nutanix Cluster level, rather than automated\/orchestrated from the outside.
    \nThe thing is, this solution is really neat, but I will still depend on a script, that has to be monitored, and maybe upgraded.
    \nAnother moving piece.
    \n
    \nMy client that had this request already manage more that 4200 VMs, and they may double that number in the next 2 years. Having this integrated by default would really be helpful here.
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    T.
    秩
    UserLevel 2.
    徽章 +13
    嗨伙计们对此问题的任何解决方案，我都有客户询问它。

    谢谢，
    托尼
    \n
    \nThanks,
    \nTony","quoteUsername":"tonyholland00","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    C
    徽章 +5
    能够将保护配置/ SLA详细信息直接分配给群集或存储容器是很酷的 - 以额外的方式查看/交互与基础架构

    回复


    Baidu