新建虚拟机默认保护组

  • 2014年2月17日
  • 8回答说
  • 1488的浏览量
shuguet
Userlevel 4
徽章 + 20
你好,

有没有一种方法(除了REST或脚本/crontab)把任何新创建的虚拟机容器到一个“默认”保护域?

其基本原理是为集群中的所有虚拟机创建一个“标准”策略，比如“默认情况下，该集群每2h复制一次”，然后如果需要处理异常，可以根据情况进行处理。

我有一个客户是PoCing Nutanix，其目标是如果一切顺利的话，从NetApp/NFS/IBM刀片解决方案转移到Nutanix。
问题是，它们使用SnapMirror每隔一小时复制一个数据存储(一个集群一个)。他们确实希望能够复制一个虚拟机，但他们不希望必须将每个新虚拟机单独添加到保护域。

Sylvain。
Sylvain Huguet - 2x Nutanix技术冠军2015-2016，法国Nutanix连接章节冠军，法国VMUG领袖，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
    今天我们就来看看脚本。但问题是，您希望为每个容器设置默认保护域还是在集群级别设置默认保护域?或者集群应该有一个默认设置，然后容器覆盖全局设置?
    shuguet
    Userlevel 4
    徽章 + 20
    最低限度应该在容器级别。
    我们创建VM比创建容器要频繁得多。

    如果可以为集群定义一个默认的保护，那么可以在容器级别覆盖它，但我也可以为集群的每个新容器设置默认的保护组……

    无论如何，当一个容器需要复制到另一个容器时，这没有多大意义，不是吗?集群如何能够自动决定站点A上的哪个容器到站点B上的哪个容器?

    Sylvain。
    Sylvain Huguet - 2x Nutanix技术冠军2015-2016，法国Nutanix连接章节冠军，法国VMUG领袖，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
    容器到容器的复制是不需要的，它必须在生产域级别的站点上进行，你可以将一个容器中的虚拟机复制到不同的站点。
    shuguet
    Userlevel 4
    徽章 + 20
    我不知道我是否理解正确，但如果你的意思是它必须设置在保护域级别，是的。
    在这种情况下，我的想法是为集群或容器中创建的所有新虚拟机分配一个默认保护域。
    这样，您可以配置保护域设置一次(如复制频率)，然后让所有新的虚拟机继承这些设置。
    如果您需要为虚拟机进行特定的设置，您仍然可以为该虚拟机分配另一个保护域，并有效地覆盖默认设置。

    在我的例子中，由于我们每小时从站点1的集群A复制所有虚拟机到站点2的集群B，我们将被覆盖。
    将来如果我们创建不需要复制的虚拟机(如vShield代理虚拟机)，我们可以为这些虚拟机创建一个特定的容器，或者将它们排除在保护范围之外，从而达到预期的效果。

    Sylvain。
    Sylvain Huguet - 2x Nutanix技术冠军2015-2016，法国Nutanix连接章节冠军，法国VMUG领袖，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://itbloodpressure.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"}}}">
    shuguet
    Userlevel 4
    徽章 + 20
    伟大的解决方案!

    我建议用一行也可以。
    我还不能测试它，但我计划一旦我升级到NOS4.0

    但是，我仍然希望能够在Nutanix集群级别上实现真正的集成，而不是从外部进行自动化/协调。
    问题是，这个解决方案确实很整洁，但我仍将依赖于一个脚本，它必须被监视，可能还需要升级。
    另一块移动。

    我的客户有这个请求，已经管理了超过4200个虚拟机，他们可能会在未来2年翻倍这个数字。在这里，将其默认集成将非常有帮助。

    Sylvain。
    Sylvain Huguet - 2x Nutanix技术冠军2015-2016，法国Nutanix连接章节冠军，法国VMUG领袖，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