Hi

I am doing iscsi, but both hypervisor mouting different iscsi target , and
I am not planning to do HA also.  Just mounting a drive to hypervisor to
use.

I sharing the same mount point,  but this seems not works.    It only
first. hypervisor when. But when adding second hypervisor into the cluster
and pre-create the mount point, it does not work.

I am trying to avoid ceph, as there is a lot of machine need to get up ,
in  production environment, at least is 3mon and 3osd , and 1 controller.

Thus trying on iscsi ,  Linbit is not supported yet,  and I do not wish to
use SMB or NFS which CPU usage of storage server could be issue, if trying
to fit a lot VM in hypervisor (for example,  200vm  etc)

Seems not much choice here any more . or others have better solutions ?



On Sun, Sep 13, 2020 at 11:46 AM Hisham Ismail
<hisham.ism...@protonmail.ch.invalid> wrote:

> Hi Hean,
>
> Are you using clustered filesystems such as like GFS2, OCFS or clvm for
> the two hypervisor hosts to share the same mountpoint as mentioned by
> Andrija?
> Im exploring Sheepdoq and Lizardfs to avoid using clustered filesystems
> setup.
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, 11 September 2020 21:54, Hean Seng <heans...@gmail.com> wrote:
>
> > Hi
> >
> > I understand the convenience of NFS, however in NFS, filesystem is at
> > Storage end, and the CPU , RAM performance of Storage become very very
> > important . The Overload may happen on storage rather
> > compute/hybervisor.
> >
> > Where as iscsi based sharedmountpoint might have more efficiency for
> this.
> >
> > I am facing issue is , i create first host with sharemoutpint /vmdisk ,
> > there is no issue of this, After that i add another host the the Cluster,
> > and and I mount the same name of ShareMountPoint (/vmdiak) in the newly
> > added host , since /vmdisk already appear in Primary Storage , and is in
> > "Cluster" , so I did not create it again .
> > I assume this shall work but apparently the /vmdisk in newly added in
> > hypervisor host is not recognizable. .
> >
> > Thank you
> >
> > On Fri, Sep 11, 2020 at 8:45 PM Andrija Panic andrija.pa...@gmail.com
> > wrote:
> >
> > > Hi Hean,
> > > this is a SharedMountPoint option when adding Primary Storage in
> > > CloudStack.
> > > This does require that your 2 hosts (not sure you'll be able to do it
> only
> > > with 2 hosts) have some kind of Clustered Filesystem like clvm, GFS2,
> OCFS
> > > set up on that mount point /LUN - none of those I would recommend
> really
> > > due to long-term stability etc - if you, can avoid it, if you can't
> avoid
> > > it, then... use it.
> > > The /vmdisk folder will be the sharedMountPoint and since more than one
> > > compute hosts are writing to a shared LUN this is why you need a
> clustered
> > > filesystem on top of that LUN.
> > > I would, instead, advise you to explore simple NFS setup or similar.
> > > best,
> > > On Fri, 11 Sep 2020 at 07:12, Hean Seng heans...@gmail.com wrote:
> > >
> > > > Hi
> > > > Is anybody know One Cluster have two KVM host, and each host has same
> > > > ShareMountPoint Name,
> > > > And I to create one Primary Storage with same SharedMountPoint Name,
> for
> > > > example, /vmdisk on both host . (both in same cluster)
> > > > And when create VM, it will automatically create the vm-storage-disk
> > > > inside the Host's Sharemount point .
> > > > --
> > > > Regards,
> > > > Hean Seng
> > >
> > > --
> > > Andrija Panić
> >
> > --
> >
> > Regards,
> > Hean Seng
>
>
>

-- 
Regards,
Hean Seng

Reply via email to