> We are using Ceph with oVirt (via standalone Cinder) extensively in a
> production environment.
> I tested oVirt cinderlib integration in our dev environment, gave some
> feedback here on the list and am currently waiting for the future
> development. IMHO cinderlib in oVirt is currently not fit for production
> use, I think this matches your assessment.

> What can we do to help advance Ceph integration in oVirt?
> What are the plans for oVirt 4.4?
> Will standalone Cinder storage domains still be supported in oVirt 4.4?
> Will there be a migration scenario from standalone Cinder to cinderlib?
TBH, to help, bug reports are probably the most useful. Having
feedback from users with "real world" setups
and usage will help us improve. As stated before, our biggest issue at
the moment is packaging, once it's handled
it will be significantly easier to test and develop.
Standalone cinder domains were never actually supported (never left
tech preview), we do not have immediate plans
for an upgrade path, but you can definitely submit an RFE for this

> Accidentally just yesterday I had an incident in our test environment
> where migration of a VM with MANAGED_BLOCK_STORAGE (=cinderlib) disks
> failed (causes are known and unrelated to cinderlib). Restarting the VM
> failed because of leftover rbdmapped devices. This is similar to the
> case I reported in https://bugzilla.redhat.com/show_bug.cgi?id=1697496.
> I don't clearly see if this fixed or not. Shall I report my recent problem?
We added better cleanup for migration cleanup to handle the bug.
There is another issue which was not known at the time with multipath
preventing unmapping rbd devices[1], and it might be what you
This can be fixed manually by blacklisting rbd devices in multipath
conf, but once the bug is fixed vdsm will handle configuring it.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1755801
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: 
List Archives: 

Reply via email to