Hi Guys, Just start a conversation on how we should do the userspace iscsi initiator C and Python API.
Options:
A) Use exiting functions in 'usr' folder.
Pro:
* Less code work.
* Could leverage existing patch used by RHEL/Fedora[1].
Con:
* The code in 'usr' folder is not thread-safe.
* Need to create a C extension for python module.
B) Expand iscsid to listen on a socket for IPC with JSON output.
Pro:
* Easy to create language bindings via JSON + IPC.
Con:
* More code work on iscsid like lock, ipc listener, json
formatter and etc.
For option A), I created PR[1] for review, and I am OK if upstream
would like to create something new from scratch.
For option B), I may create a demo/POC if we think that fit open-iscsi better.
[1]: https://github.com/open-iscsi/open-iscsi/pull/51
--
Gris Ge
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
