Hi, I don't have a solution for you, I just wanted to make you aware of this note in the docs:
Warning The iSCSI gateway is in maintenance as of November 2022. This means that it is no longer in active development and will not be updated to add new features.
Here's some more information [2]:
The planned replacement is based on the newer NVMe-oF protocol and SPDK. See this presentation for the purported performance benefits: https://ci.spdk.io/download/2022-virtual-forum-prc/D2_4_Yue_A_Performance_S…
The git repository is here: https://github.com/ceph/ceph-nvmeof. However, this is not yet something recommended for a production-grade setup. At the very least, wait until this subproject makes it into Ceph documentation and becomes available as RPMs and DEBs. For now, you can still use ceph-iscsi - assuming that you need it, i.e. that raw RBD is not an option.
It will probably still work but you might encounter issues which won't be resolved anymore. Regards, Eugen [1] https://docs.ceph.com/en/quincy/rbd/iscsi-overview/#ceph-iscsi [2] https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/message/GDJJL7VSDUJ... Zitat von Ramon Orrù <ramon.orru@lnf.infn.it>:
Hi, I’m configuring the iSCSI GW services on a quincy 17.2.3 cluster.
I brought almost everything up and running (using cephadm), but I’m stuck in a configuration detail:
if I check the gateway status in the Block -> iSCSI -> Overview section of the dashboard, they’re showing “Down” status, while the gateways are actually running. It makes me think the mgr is not able to talk with iSCSI APIs in order to collect info on the gateways, despite I correctly added my mgr hosts IPs to the trusted_ip_list parameter in my iscsi service definition yaml.
While further checking the gateway logs I found some messages like:
debug ::ffff:172.17.17.22 - - [15/Nov/2023 10:54:05] "GET /api/config?decrypt_passwords=True HTTP/1.1" 200 - debug ::ffff:172.17.17.22 - - [15/Nov/2023 10:54:05] "GET /api/_ping HTTP/1.1" 200 - debug ::ffff:172.17.17.22 - - [15/Nov/2023 10:54:05] "GET /api/gatewayinfo HTTP/1.1" 200 -
Just after I reload the dashboard page. So I tried to add the 172.17.17.22 IP address to trusted_ip_list and it worked: iSCSI gateways status went green and Up on the dashboard. It sounds to me like it's some container private network address, but I can’t find any evidence of it when inspecting the containers cephadm spawned.
My question is: how can I identify the IPs I need to make the iSCSI gateways properly reachable? I tried to add the whole 172.16.0.0/24 private class but no luck , the iscsi container starts but is not allowing 172.17.17.22 to access the APIs.
Thanks in advance
regards
Ramon
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io