On Fri, 2005-04-08 at 15:16 -0700, Nicholas A. Bellinger wrote:
> On Fri, 2005-04-08 at 14:26 -0400, Ming Zhang wrote:
> > On Thu, 2005-04-07 at 15:19 -0700, Nicholas A. Bellinger wrote:
> > > > 2) what is our plan?
> > >
> > > 1) Fix the bug in the iSNS server that is causing the sefault on
> > > startup.
> > > 2) Get comfortable with using the interactive mode with the client.
> > one question, what u mean interactive mode? and what else modes we would
> > like to provide?
> >
> > * access from a high level library interface
> > * a command line tool to inquiry/reg/dereg/control
> > ...
> >
> >
>
> How the iSNS client currently takes input is what I meant by interactive
> mode. ie: You have to launch the program and then make iSNS calls to
> the server from _inside_ the program. Once the iSNS data is returned
> from the server the client needs to make the approiate initiator-ctl
> or /etc/rc.d/init.d/initiator calls (in the initiator case) to perform
> what actions where requested.
i know what u mean now. i gradually how it works now.
>
> Once this is working, I think its safe to then put the iSNS abractions
> in scripts and make the iSNS client take the actions it currently
> supports in 'interactive mode' and make it take them as command line
> arguements.
so u are talking about a evolution way to do this. i agree. my origina
thought is to use cmd line only.
> An example:
>
> 1) Someone installs iscsi-initiator-core or IET and runs a 'setup'
> script.
>
> 2) The Initiator/Target names are generated in kept in local storage.
>
> 3) The iSNS client is started with a known iSNS server IP.
>
> 4) The iSNS client registers the Initiator/Target Node Name data with
> the iSNS server.
>
|
