> On Apr 13, 2026, at 8:32 AM, Alexander Schreiber via ceph-users > <[email protected]> wrote: > > On Mon, Apr 13, 2026 at 09:34:39AM +0000, Ernesto Puerta via ceph-users wrote: >> Hey Eugen, >> >> AFAIK the Ceph NVMe-oF Gateway superseded the iSCSI one: it's actively >> maintained, more performant, scalable, secure and better integrated with >> the Ceph management & observability framework.
The iscsi-gw has lacked a maintainer for quite a while. If someone really really needs to run iSCSI, they might check out https://github.com/frednass/ceph_petasan >> I'm curious: what's the target platform/use case for iSCSI that NVMe/TCP >> cannot fulfill? Clients that can't talk NVMe/TCP? E.g. some BIOS implementations? Certain VMware releases? > > As someone who is running pure spinning rust Ceph clusters, I assume the > NVMe-oF gateway requires actual NVMe devices to be used for backing, given > that the docs mention sending NMVe commands to targets, correct? I don't *think* that's the case, though I'd be curious re the use-case for the protocol backed by slow media. > > Handing out iSCSI devices sounds useful as backing storage for VMs > (and some can even boot off it). RBD through libvirt is an all-around better solution for that. Fewer moving parts, less overhead, lower resource utilization on the Ceph side. > > Kind regards, > Alex. > -- > "Opportunity is missed by most people because it is dressed in overalls and > looks like work." -- Thomas A. Edison > _______________________________________________ > ceph-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
