Hyperconverge setup on xenserver

[buzzzo]

Hi

I'm planning to test startwind san on a couple of xenserver hypervisor.
My doubts are realted on the number of phsyical iscsi nic (target) to give both to vm and to hypervisor.

Supposing i'm using two iscsi net (192.168.1.x,192.168.2.x) do i need to reserve two physical nic to vm and two to hypervisor ?.
I know i could use just two nics and then let hypervisor just use them to talk with the iscsi virtual nic on the starwind vm, but
based on your expierence is it possible to introduce a bottleneck with this setup ?

Thx in advance

[darklight]

Since it's working on VMWare through virtualized NICs, I believe it should also work on XEN.
I've been using Starwind with XEN a while ago as a dedicated storage since Starwind guys told me hyper-converged is not tested/supported. But such kind of test you are doing is very interesting to me, so please keep us updated

[Tarass (Staff)]

Sure thing, darklight, would very interesting for me either.

Buzzzo, please, keep us informed. Thanks!

[buzzzo]

Just a quick update

I'm testing the hyperconverged setup on just one r710 node with the latest beta version of xenserver 6.6.x.
Up to now i'm testing the setup with just one node (aka: no replication in place)

I've 7 disk in raid5.

Just a few facts:

1) on the perc 6i i've setup stripe size to 64k (as per best practice suggestion)
2) I've format the ntfs starwind's storage pool volume (on vsan vm) with 64k block size
3) the starwind flat file image block device is setted to 512byte

Are these 3 values good enough or are totally wrong ?

Thx in adavance

[darklight]

Hi mate,

1) It's OK.
2) Sounds strange to me. I would leave it by default (4k).
3) 512 is a must for Xen, i assume, so it's OK.

Thanks for update!

[Tarass (Staff)]

Thanks all for awesome contributions. Keep it rocking!