Hi,
Good news, my colleague Stefan fixed the namespace inconsistencies that
I was mentioning: https://github.com/ceph/ceph/pull/48367#event-7561106877
Thanks a lot Ilya for reviewing the PR btw!
Regards,
Lucian
On 20.09.2022 16:56, Lucian Petrut wrote:
Hi,
rbd namespaces are supported. It's just that "rbd device (un)map"
seems to ignore the "--namespace" argument (unmap has the same issue
on Linux, we'll have to look into it).
The good news is that the namespace can be specified as part of the
image identifier, e.g:
rbd device map ${rbdPool}/${rbdNamespace}/${rbdImage}
rbd device unmap ${rbdPool}/${rbdNamespace}/${rbdImage}
messenger v2 is supported as well, for example you can enforce it like
so:
mon host = v2:${monAddress}
Just one minor implementation detail, the wnbd driver is completely
unaware of Ceph, it's just forwarding IO requests to userspace daemons
(rbd-wnbd in this case).
Regards,
Lucian
On 20.09.2022 15:20, Stefan Kooman wrote:
On 9/20/22 11:23, Lucian Petrut wrote:
Hi,
We've just published new Pacific and Quincy MSIs, including the ipv6
fix as well as a few others that haven't landed upstream yet. Please
let us know how it works.
It works \o/. Just successfully created, mapped, and written to an
rbd image in Windows. The driver seems to be using messenger v1
(communicating on port 6789). Is there support for messenger v2?
The "rbd device list" commands shows a "namespace" column. Are rbd
namespaces supported (would be awesome)?
Gr. Stefan
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
