解决了

使用iSCSI进行VDI环境

  • 2017年3月8日
  • 3回复
  • 1199次观看
T.
徽章 +1
你好，

我们正在考虑构建一个单独的VMware Horizo​​ n View群集，并使用于服务器负载的Nutanix群集。
我们有一些创造这一点的情景。并且一个是购买4个新的VMware主机并将它们连接到具有iSCSI的现有Nutanix群集，这只是因为我们已经在现有群集中有足够的存储空间。
我的问题是，它将是使用iSCSI的瓶颈吗？我们将运行大约260名Win7 / Win10任务工作者VDI客户。

问候
托比亚斯
图标

最好的答案j2017年3月10日，04:56

\n
\nI dont work in Sales, but if you'd like to play around with some configuration ideas, drop me an email at jon at nutanix dot com and I'd be happy to put our heads together on the technical bits.
\n
\nRE VAAI
\nWhat I'm talking about is VAAI for block storage, which all VM's use in one fashion or another when you run a VM on a VMFS volume. Specifically a VAAI primative called ATS, we do not support (yet) on ABS. That has to do with array assisted LUN locking in VMFS. Before ATS was introduced, LUN locking was a huge problem in VDI and server virtualization.
\n
\nAlso, if you run VM's on an ABS volume, we lose all ability to control those VM's at a per VM level, so you will see the VM's \"drop out of\" prism reporting.
\n
\nLastly, a single ABS volume uses one oplog volume, whereas each VM virtual disk uses one oplog volume. This has to do with how write caches work within Nutanix. This means that you're going to go from a good amount of write cache per VM, to drastically less write cache shared across many VM's on an ABS volume.
\n
\nNet Net, while ABS technically could do the job, it's really meant for different use cases on bare metal servers, or scale out storage on high end database workloads (VM or physical)","className":"post__content__best_answer"}">
查看原版
\n
\nWe are thinking of building a separate VmWare Horizon view cluster and make the Nutanix-cluster used just for server loads.
\nWe have a few scenarios of creating this. And one is to buy 4 new vmware hosts and connect them to the existing nutanix cluster with iSCSI, this is just because we have enough storage already in the existing cluster.
\nMy question is, will it be a bottleneck to use iSCSI? We will run about 260 Win7\/Win10 task-workers VDI clients.
\n
\nRegards
\nTobias","quoteUsername":"Televinken","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

3回复

j
秩
UserLevel 6.
徽章 +29
请记住，ABS不支持VMFS在iSCSI上的VMFS卷，因此这不是理想的用例。

还要记住，这种思想模式是有很多早期的VDI部署（想想2006-2012时代）的麻烦，因为他们将沉溺于有很多存储容量，但实际上它的IO延迟，IO吞吐量和存储处理器容量使所有差异，而不是实际可用的GB / TB。

这里有很多不同的选择，但其中一个是为VDI购买少量节点，这样你就可以获得Nutanix + VDI的所有比例效益，而且不必担心系统瓶颈本身。

如果你愿意，很高兴聊聊更多。
JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
\n
\nAlso keep in mind that this thought pattern is what got a lot of early VDI deployment (think 2006-2012 era) in trouble, as they would preceive to have lot of storage capacity available, but actually its IO latency, IO throughput, and storage processor capacity that make all of the difference, not actual available GB\/TB.
\n
\nLots of different options here, but one of them would be to purchase a small amount of nodes just for VDI, such that you can get all of the scale out benefits of Nutanix+VDI, and not have to worry about the system bottlenecking itself artificially.
\n
\nHappy to chat more if you'd like.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
T.
徽章 +1
嗨jon，

感谢您的回答。
IO会成为一个问题吗？今天存在260个VDI在现有的Nutanix集群中存在。我只想将它们移动到另一个主机以获得更多CPU / RAM。

vaai可能是一个问题，但我不知道我们是否使用这很多VDI。

问候
托比亚斯
\n
\nThanks for your answer.
\nWill the IO be an issue? The 260 VDI is today present in the existing Nutanix cluster. I would just want to move them to another host to get more CPU\/RAM.
\n
\nVAAI could be an issue, but I don`t know if we use that a lot for VDI.
\n
\nRegards
\nTobias","quoteUsername":"Televinken","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j
秩
UserLevel 6.
徽章 +29
您可以使用非常浅的存储配置获取Nutanix节点，但仍然运行Nutanix进行CPU /内存。这样，它们将为群集添加一些SSD和存储控制器容量，并且一切都将顺利工作，尤其是迁移，因为您可以将主机添加到Nutanix群集，使其成为自己的VMware集群，并仅计算它们新主持人。容易的。

我不在销售中工作，但如果您想和一些配置想法一起游戏，请在Jon在Nutanix Dot Com拍摄电子邮件，我很乐意将我们的头放在技术位上。

vaai.
我所谈论的是vaai for block存储，所有VM在VMFS卷上运行VM时，所有VM都以一种方式使用。特别是一个名为ATS的Vaai引发，我们不支持（尚未）。与VMFS中的阵列辅助LUN锁定有关。在介绍ATS之前，LUN锁定在VDI和服务器虚拟化中是一个巨大的问题。

此外，如果您在ABS卷上运行VM，我们会失去每个VM级别控制这些VM的能力，因此您将看到VM的“丢弃”棱镜报告。

最后，单个ABS卷使用一个Oplog卷，而每个VM虚拟磁盘使用一个Oplog卷。这与如何在Nutanix中写入缓存。这意味着您将从每个VM的良好写缓存中从一定数量的写缓存中逐渐减少在ABS卷上的许多VM上共享的写入缓存。

网网络，而ABS技术上可以做这项工作，它真的适用于裸机服务器上的不同用例，或在高端数据库工作负载（VM或物理）上缩放存储
JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
\n
\nI dont work in Sales, but if you'd like to play around with some configuration ideas, drop me an email at jon at nutanix dot com and I'd be happy to put our heads together on the technical bits.
\n
\nRE VAAI
\nWhat I'm talking about is VAAI for block storage, which all VM's use in one fashion or another when you run a VM on a VMFS volume. Specifically a VAAI primative called ATS, we do not support (yet) on ABS. That has to do with array assisted LUN locking in VMFS. Before ATS was introduced, LUN locking was a huge problem in VDI and server virtualization.
\n
\nAlso, if you run VM's on an ABS volume, we lose all ability to control those VM's at a per VM level, so you will see the VM's \"drop out of\" prism reporting.
\n
\nLastly, a single ABS volume uses one oplog volume, whereas each VM virtual disk uses one oplog volume. This has to do with how write caches work within Nutanix. This means that you're going to go from a good amount of write cache per VM, to drastically less write cache shared across many VM's on an ABS volume.
\n
\nNet Net, while ABS technically could do the job, it's really meant for different use cases on bare metal servers, or scale out storage on high end database workloads (VM or physical)","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu