Understood, and you are right. KVM + iSCSI/shared mount point (requires clustered file system), is, from my POV, a no-go for production (it's different with VMware and XenSeverm whos's support for such thing is excellent/for production use)
On Fri, 5 Mar 2021 at 09:37, Pieter Koorts <pieter.koo...@me.com.invalid> wrote: > Unless CloudStack has a way to automatically attach iSCSI storage to each > virtual machine directly then a clustered filesystem (C-LVM or OCFS2) is > needed to store the VM data as it is the only way to have all compute hosts > to have access to the same data for live migrations and HA when using iSCSI > SANs. At least that's my understanding. > > I was comparing clustered file systems on Hyper-V (CSV) and Linux (C-LVM > or OCFS2) and why Hyper-V has excellent support for it. > > One of the reasons we use Hyper-V Server is this feature but to us a > hypervisor is replaceable, the reliability of the virtual machines within > is not. > > Thank you > > Pieter > > On 4 March 2021 at 20:51, Andrija Panic <andrija.pa...@gmail.com> wrote: > > Struggling to understand why you are mentioning a clustered filesystem on > Linux? (but I do agree all of them are to be avoided, 99% of the time) > > On Tue, 2 Mar 2021 at 17:25, Pieter Koorts <pieter.koo...@me.com.invalid> > wrote: > > We currently use Hyper-V with an iSCSI SAN since Hyper-V does excellent at > > fast shared storage with Windows CSV. The system is reliable but very > > inflexible to changes in strategies when deploying workloads. > > > Moving to Linux as a hypervisor isn't too much of an issue as we do use > > Ubuntu 20.x for many of our workloads just that the only clustered storage > > options for Linux is either Clustered LVM or OCFS2 > > > Never used any "modern" form of OCFS2 deployment so cannot say anything > > regarding it's performance or reliability but past experiences with > > Clustered LVM makes me shudder. Had a few machines silently corrupt with > > Clustered LVM. > > > Thank you > > > Pieter > > > On 2 March 2021 at 15:38, Andrija Panic <andrija.pa...@gmail.com> wrote: > > > It goes without saying that once a big company get's interest in i.e. > > Hyper-V and sponsors the needed development - that is usually a time when > > such a huge feature goes in ACS. > > > Do you need any recommendations from real-life on what to go with, in the > > CloudStack world? > > > Best, > > > On Tue, 2 Mar 2021 at 14:06, Pieter Koorts <pieter.koo...@me.com.invalid> > > wrote: > > > That is a pity. Hyper-V Server 2019 for example is excellent with great > > > enterprise software support like backup facilities, clustered filesystem > > > (iSCSI SAN's, etc). > > > > Suppose unless there is traction like with OpenStack (with Hyper-V > > > support), getting the time and developers to deal with it in CloudStack > > > will be hard. > > > > Will continue my CloudStack research and the options available. > > > > Thank you > > > > Pieter > > > > On 2 March 2021 at 12:49, Andrija Panic <andrija.pa...@gmail.com> wrote: > > > > Unfortunately, I don't thinking CloudStack actually supports (in reality) > > > hyper-v any more - there was the original implementation for Hyper V 2012, > > > but not sure it works any more, at all (and the "VM import" option is > > > available only for VMware, not any other hypervisor, atm) > > > > Best, > > > > On Wed, 24 Feb 2021 at 11:16, Pieter Koorts <pieter.koo...@me.com.invalid> > > > wrote: > > > > Been searching a myriad of places but can't find any concrete information > > > > about this. From what I understand CloudStack can be implemented on top of > > > > an existing vSphere installation and machines imported into CloudStacks > > > > control. > > > > > Is the same thing possible on a Hyper-V cluster by chance? > > > > > Thank you > > > > > Pieter > > > > > > > -- > > > > Andrija Panić > > > > > > -- > > > Andrija Panić > > > > > -- > > Andrija Panić > > -- Andrija Panić
