BR; I've built my own iSCSI targets (using Fedora and CentOS), and use them in production. I've also built 2 different Ceph clusters. They are completely different. Set aside everything you know about iSCSI, it doesn't apply. Ceph is a clustered object store, it can dynamically expand (nearly) without limit, and is (mostly) self-healing. There are overlay technologies that allow Ceph clusters to pretend to be Amazon S3 or OpenStack Swift (RadosGW), block devices, similar to OpenStack Cinder or Amazon EBS (RBD), and file systems usable directly by Linux clients (CephFS). You might look at the architecture documentation: https://docs.ceph.com/docs/master/architecture/ The only point of overlap is that Ceph can be coerced to provide iSCSI targets. Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International, Inc. DHilsbos@xxxxxxxxxxxxxx www.PerformAir.com -----Original Message----- From: Bobby [mailto:italienisch1987@xxxxxxxxx] Sent: Tuesday, January 7, 2020 7:49 AM To: ceph-users@xxxxxxx Subject: Ceph and iSCSI Hi all, I am new to Ceph. But I have a some good understanding of iSCSI protocol. I will dive into Ceph because it looks promising. I am particularly interested in Ceph-RBD. I have a request. Can you please tell me, if any, what are the common similarities between iSCSI and Ceph. If someone has to work on a common model for iSCSI and Ceph, what would be those significant points you would suggest to someone who has some understanding of iSCSI? Looking forward to answers. Thanks in advance :-) BR _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |