Hi，I don't not know what API provides. about ceph-iscsi-cli HOT 7 CLOSED

There is no API document because there is no supported API yet.

from ceph-iscsi-cli.

Oh, thank you for your answer

from ceph-iscsi-cli.

As Mike said, no 'supported/stable' API yet. But the api is used by the cli, so if you want a list of what is currently available you can just hit the /api endpoint once you have rbd-target-api daemon started. eg. curl --insecure --user admin:admin -X GET http://192.168.122.69:5000/api or use your favourite rest api interface......

from ceph-iscsi-cli.

@pcuzner，thinks，Your answer is very helpful to me , I just want to try to control the gateway through Web UI，

from ceph-iscsi-cli.

Hi I verified all the API in the list（ from curl --insecure --user admin:admin -X GET http://192.168.122.69:5000/api ），I find that most of them are available and all gateways are synchronized with api change.But when I used "curl --insecure --user admin:admin -X PUT http://192.168.122.69:5000/api/target/iqn.2003-01.com.redhat.iscsi-gw0", I made a mistake, It is found that local and other gateways are not effective through gwcli ，the targetcli finds that only the local is effective， so, Is that why Mike says not support API ？

from ceph-iscsi-cli.

I think that specific issue was just fixed the other day in this commit:

8f5066c

The general reason we said we do not have a supported API yet, is because the only tool using it is gwcli, and we might have made some mistakes in the design and we also do not want to make the API gwcli specific.

We are open to making a supported API though.

from ceph-iscsi-cli.

Yes, I can successfully create target after updating the code and I'm not confused anymore. Thank you for your help.

from ceph-iscsi-cli.