@scottalanmiller Right and they leap at that without a full picture, that's all I was admittedly trying to say.

@obsolesce said in Linux-based StarWind VSAN: hardware-agnostic, minimalistic, and FREE SDS:

@travisdh1 said in Linux-based StarWind VSAN: hardware-agnostic, minimalistic, and FREE SDS:

@obsolesce said in Linux-based StarWind VSAN: hardware-agnostic, minimalistic, and FREE SDS:

Is this tied together with VMWare? I thought this was going to be usable on Fedora, for example.

If the Starwind software is running on Linux, the hypervisor shouldn't matter. You'll be able to mount the share Starwind it's exporting on XenServer or KVM just as well, but well all the experts just in case. @KOOLER @Oksana

I'm asking because Linux and SW vSAN are worded everywhere as if it's 100% tied to VMWare, with no other use case. I can't imagine that being the case, but am asking to make sure... perhaps it's worded like that because it's written by a VMWare Architect trying to boast and sell VMWare. Just wondering, because I was under the impression you can use it how you want, not just with VMWare.

I agree with you, seems like bad marketing. I’ll be interestes in using it with KVM, for example. I thing it will just export iSCSI.

Also we could achieve hyperconvergence "the other way" (unlike having a global shared filesystem like Gluster or Ceph) but use fine grained replication (per VM/VM disk). That's really interesting (data locality, tiering, thin pro etc.). Obviously, we'll collaborate to see how to integrate this in our stack 🙂