为什么只有一个集装箱?

  • 2016年3月28日
  • 4回复
  • 1295的浏览量
年代
徽章 ＋２
我没有看到关于为什么单一容器是最佳实践的解释。使用多个容器是否会导致更多的开销(内存使用除外)?

一个显而易见的选择是将几乎相同的OS VM放在重复数据删除容器中，以最大限度地节省空间。然后将任何用户数据vDisks放在一个压缩容器中。

我只是想听听为什么这不是一个好主意。
    \n
    \nIt seems like an obvious choice would be to put your OS VM's that are virtually identical in a deduped container to maximize space savings. Then put any user data vDisks in a compressed container.
    \n
    \nJust looking for some input on why this is not a good idea.","quoteUsername":"stever3901","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    4回复

    B
    Userlevel 4
    徽章 + 17
    它应该是一个单一的存储池，而不是容器

    您应该有多个容器，这取决于您的需求
    每个容器级别都部署重复数据删除和压缩功能

    容器类似于向Hypervisor提供数据存储的文件夹
    \n
    \nYou should have multiple container depend on your requirements
    \nDedupe and Compression fetures are deployed per Container level
    \n
    \nContainer is like a folder providing datastore to your Hypervisor","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    嗨史蒂夫,
    如果你愿意，我很乐意在本地或webex上同步，但这是我目前的两点意见。

    如果您愿意，您可以拥有大量的容器，但就像过去的LUN /卷一样，它往往会使事情变得更加模糊和复杂。

    特别是在AHV的世界里，有一个容器只是让生活变得简单。此外，在4.5++中，你可以同时运行所有的存储特性，系统只是“找出它”(即重复数据删除、压缩、Erasure Coding等)

    至少，我在这里的KISS原则(也是咨询机构普遍建议的)至少是开启在线压缩。它很神奇，坦白地说，非常有效。
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    \nHappy to sync up locally or on webex if you'd like, but here's my 2 cents for now.
    \n
    \nYou can have a ton of containers if you'd like, but like the LUN's\/volumes of yesteryear, it tends to make things more obfuscated and complicated.
    \n
    \nEspecially in the AHV world, having one container just makes life easy. Also, in 4.5++, you can run all storage feature simultaneously, and the system just \"figures it out\" (i.e Dedupe, Compression, Erasure Coding, etc)
    \n
    \nAt minimum, my KISS principle here (and what consulting recommends across the board) is at least turn on in-line compression. It's magic, and quite frankly, works darn great.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    年代
    徽章 ＋２
    为什么一个集装箱更好“特别是在AHV的世界”?
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    在AHV世界中，从管理程序的角度来看，它所看到的都是带有直接附加到每个VM的卷的VM(有点像VMW的vVol)。

    管理程序不会看到一个公共数据存储上的文件，而是VM和它们各自的磁盘。


    老实说，在AHV中，容器只是一个“策略对象”，而不是传统的卷或数据存储。这适用于压缩/重复数据删除等数据策略，以及AHV图像服务。

    在我所见过的真实世界中，AHV的部署很少有超过一个容器，因为所有这些。
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    \n
    \nThe hypervisor doesn't see one common datastore with files on it, just the VM's and their respective disks.
    \n
    \n
    \nHonestly, in AHV, the container is just a \"policy object\", rather than a traditional volume or datastore. This goes for data policies like compression\/dedupe, as well as things like the AHV Image Service.
    \n
    \nIn the real world AHV deployment's I've seen, its pretty rare to have more than one container because of all of this..","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    回复


    Baidu