We support it as part of the cinderlib integration (Managed Block Storage), each rbd device is represented as single ovirt disk when used. The integration is still in tech preview and still has a long way to go, but any early feedback is highly appreciated
On Mon, Oct 7, 2019 at 2:20 PM Strahil <hunter86...@yahoo.com> wrote: > > Hi Dan, > > As CEPH support is quite new, we need DEV clarification. > > Hi Sandro, > > Who can help to clarify if Ovirt supports direct RBD LUNs presented on the > VMs? > Are there any limitations in the current solution ? > > Best Regards, > Strahil NikolovOn Oct 7, 2019 13:54, Dan Poltawski <dan.poltaw...@tnp.net.uk> > wrote: > > > > On Mon, 2019-10-07 at 01:56 +0300, Strahil Nikolov wrote: > > > I'm not very sure that you are supposed to use the CEPH by giving > > > each VM direct access. > > > > > > Have you considered using an iSCSI gateway as an entry point for your > > > storage domain ? This way oVirt will have no issues dealing with the > > > rbd locks. > > > > > > Of course, oVirt might be able to deal with RBD locks , but that can > > > be confirmed/denied by the devs. > > > > Thanks for your response - regarding the locks point, I realised later > > that this was my own incorrect permissions given to the client. The > > ceph client was detecting the broken locks when mounting the rbd device > > and unable to blacklist it. I addressed this by swithcign to the > > permissions 'profile rbd'. > > > > Regarding iSCSI, we are using this for the hosted engine. However, I am > > attracted to the idea of managing block devices with individual rbd > > devices to facilate individual block device level snapshotting and I > > assume performance will be better. > > > > thanks, > > > > Dan > > > > ________________________________ > > > > The Networking People (TNP) Limited. Registered office: Network House, > > Caton Rd, Lancaster, LA1 3PE. Registered in England & Wales with company > > number: 07667393 > > > > This email and any files transmitted with it are confidential and intended > > solely for the use of the individual or entity to whom they are addressed. > > If you have received this email in error please notify the system manager. > > This message contains confidential information and is intended only for the > > individual named. If you are not the named addressee you should not > > disseminate, distribute or copy this e-mail. Please notify the sender > > immediately by e-mail if you have received this e-mail by mistake and > > delete this e-mail from your system. If you are not the intended recipient > > you are notified that disclosing, copying, distributing or taking any > > action in reliance on the contents of this information is strictly > > prohibited. > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/DLM6FRTGVDG232PQFHUA3IDOS5PT6WQ2/ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AXXQ2KIW23Q62MYZYSXE4POVYS3JXX72/
