Hi Lee,
On 06/09/2017 07:02 PM, The Lee-Man wrote:
> I am seriously interested in both adding an API like this (if done
> right) and in adding more/better locking so that iscsid could support
> more parallelism.
While I maintain open-iscsi for Debian, I must confess that I haven't
looked too
On Wednesday, April 26, 2017 at 9:15:50 AM UTC-7, Christian Seiler wrote:
>
> On 04/26/2017 01:03 PM, Gris Ge wrote:
> > On Wed, Apr 26, 2017 at 09:14:35AM +0200, Christian Seiler wrote:
> >> On 04/26/2017 01:11 AM, Gris Ge wrote:
> >>> B) Expand iscsid to listen on a socket for IPC with
On 04/26/2017 01:03 PM, Gris Ge wrote:
> On Wed, Apr 26, 2017 at 09:14:35AM +0200, Christian Seiler wrote:
>> On 04/26/2017 01:11 AM, Gris Ge wrote:
>>> B) Expand iscsid to listen on a socket for IPC with JSON output.
>>> Pro:
>>> * Easy to create language bindings via JSON
On 04/26/2017 09:29 AM, Ulrich Windl wrote:
Christian Seiler schrieb am 26.04.2017 um
09:14 in
> Nachricht :
>> On 04/26/2017 01:11 AM, Gris Ge wrote:
>>> B) Expand iscsid to listen on a socket for IPC with
On Wed, Apr 26, 2017 at 09:14:35AM +0200, Christian Seiler wrote:
> On 04/26/2017 01:11 AM, Gris Ge wrote:
> > B) Expand iscsid to listen on a socket for IPC with JSON output.
> > Pro:
> > * Easy to create language bindings via JSON + IPC.
> > Con:
> > *
>>> Christian Seiler schrieb am 26.04.2017 um 09:14
>>> in
Nachricht :
> On 04/26/2017 01:11 AM, Gris Ge wrote:
>> B) Expand iscsid to listen on a socket for IPC with JSON output.
>> Pro:
>> * Easy
On 04/26/2017 01:11 AM, Gris Ge wrote:
> 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
>
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:
*