You can subscribe to this list here.
2002 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(5) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Gruher, J. R <jos...@in...> - 2014-08-29 01:45:08
|
All- I am running tgt and isns on Ubuntu 14.04 x64 on an Intel Xeon server. When I connect isnsc and try to dump a list of targets (input 12, enter, enter) I frequently see isns crash on the target server: Aug 28 18:39:30 hswceph02 kernel: [104044.551800] isnsd[21762]: segfault at 30 ip 00007f143f5fea8c sp 00007fff256bf880 error 4 in libgdbm.so.3.0.0[7f143f5fb000+5000] Can anyone provide guidance on how to fix, workaround, or further debug? Happy to provide more information and try additional steps to characterize and correct. -Joe |
From: Gruher, J. R <jos...@in...> - 2014-08-19 00:36:03
|
Hi all- I am running Ubuntu 14.04 Server and have TGT and iSNS running. If I connect the isnsc client from a second Ubuntu 14.04 system I can use option "12" to dump a list of iSCSI targets. So far so good. However, if I set up too many targets, option 12 instead fails with a "Connection closed by isns server" message, and then I see iSNS is no longer running on the iSCSI target server. I have restarted many times and tried different numbers of targets. It seems like it is crashing when too many targets are present with the limit being about 24. Works reliably for 24 or less, crashes reliably for 30 or more, didn't try every value in between. Is this a known issue, and is so, any fixes or workarounds available? If not, can I provide any debug information? Thanks, Joe |
From: Xiang, Y. <Yang.Xiang@Teradata.com> - 2013-09-04 21:02:21
|
---Newbie Question--- I am running SLES11 on all nodes. On node A, I installed and configured isns server. And isns is started. On node B, I installed open-iscsi and configured it as a target connected to storage array through SAS connectors on board. "open-iscsi" service is started. On node C, I installed open-iscsi and configured it as an initiator which will use the storage array as file systems. Now what do I need to do in order for node B and node C to be listed on node A as iSCSI nodes. Which commands do I need to run on each of the nodes? The open-iscsi readme is very vague in describing its configuration with iSNS and iSNS doc for SuSE does not have sections on utilizing open-iscsi utilities. Any hint would be highly appreciated. Many thanks, Yang |
From: <kir...@gm...> - 2008-04-16 09:17:31
|
<p>Hi ,</p> <p>I've just written to Ratan Tata asking him to not to go ahead with building a port in Dhamra, Orissa, dangerously close to one of the world's largest sea turtle nesting grounds for the Olive Ridley Sea Turtle. I think its a good idea for Mr. Tata to move the port to another location rather than endanger the turtles.</p> <p>By living up to the Tatas' environmental legacy, Ratan won't just save the highly-endangered Olive Ridley Turtles, he will also end up making Tata a better company.</p> <p>The only problem is that I can't bring about that change alone. I need help from lots of people, especially you.</p> <p>Please do what I've done. Write directly to Ratan <a href='http://www.greenpeace.org/india/turtles/write-to-tata'>by clicking here</a></p> <p>Thanks a million,<br/> kir...@gm...</p> |
From: Nicholas A. B. <na...@ke...> - 2007-09-18 20:39:41
|
Greetings all, I have posted the initial iSNS and iSNS server howto entry on linux-iscsi.org: http://www.linux-iscsi.org/index.php/ISNS http://www.linux-iscsi.org/index.php/Linux_iSNS_Server_Howto Please have a look at the pages for futher information on the status of features within the iSNS server stack. Also, Robert @ Novell had mentioned previously that there has been much work done recently on the iSNS server side. We had agreed earlier to merge our efforts for the iSNS server side, and I am offering this howto as a first step for Linux/iSCSI folks to get an iSNS server up and running as quickly as possible with existing code. There is also an effort for OpenSolaris folks for an iSNS server. Olaf, please feel free to add information to the howto about how to get this setup on a Linux machine. I encourage everyone to add to these entries and howto. Espically on the iSNS server code that is being shipped from distribution vendors, please add this information at your earliest convience so visitors to Linux-iSCSI.org can determine where to go for builds and futher distribution specific information. While there are currently 3 RFC ready iSNS implementations publically available, making this as least confusing as possible to actually get an iSNS server up and running is the goal. Any comments are welcomed. Thanks! --nab |
From: <sun...@wi...> - 2007-03-06 08:31:17
|
What is the scope of developing a generic library for iSNS client support?=20 =20 The main goal of this ISNSC library is to facilitate any target or initiator to use the iSNS client support. This abstracts the iSNS client functionality to the initiator/target and only gives the initiator/target what they want. For example, the initiator can call an API in the proposed library, and get the details of the target. Similarly, the target also can call an API, and can impose the Login control method of RFC. =20 =20 The library takes care of talking to ISNS server, and responding to ESI/SCN messages. Callback function support in the library helps the initiator/target to handle these asynchronous messages like ESI/SCN. This way, iSNS client code would be generic irrespective of the vendor for initiator or target. =20 =20 Mostly this proposed library would be reusing the published iSNS client code. But, This helps in making an initiator/target to support iSNS with much simpler effort by using the library. =20 =20 Any review comments on this? |
From: Ming Z. <mi...@el...> - 2006-10-30 19:40:29
|
FYI, https://lists.sourceforge.net/lists/listinfo/linuxisns-commit was created and cvs commit notification was added. next time u commit, we will find out if it works. Ming On Thu, 2006-10-26 at 12:01 -0600, Robert Whitehead wrote: > The code updates have been placed in cvs. We could create a commit notification list. > There will be more improvements coming forth shortly. > -Robert > > >>> Ming Zhang <mi...@el...> 10/26/2006 11:32 AM >>> > good to know. the code is updated in cvs? shall we create a cvs/svn > commit notification mailing list? > > ming > > > > On Thu, 2006-10-26 at 11:14 -0600, Robert Whitehead wrote: > > I have recently taken on the task to update the iSNS code. > > > > The first task was to get the iSNS server working with the lastest version of the iscsitarget (IET) target on Linux. > > The second task was to get it working with the Microsoft Initiator since it has support for iSNS. > > The code posted recently reflects the changes made to accomplish these two tasks. The testing has been limited so far but it > > was important to get these changes posted out. > > > > Support for the open-iscsi initiator is next. This requires more iSNS support to be built into this initiator. > > > > There is also work to do to bring this iSNS implementation up to the lastest specification and to turn this initial iSNS code into > > a working/completed product. I plan on doing much work in this area. I have reviewed the previous suggestions. There are > > some very good thoughts in these posts. > > > > > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Linuxisns-discussion mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion |
From: Ming Z. <mi...@el...> - 2006-10-27 01:06:53
|
i created the email list but have problem to send related info to u email address. Ming On Thu, 2006-10-26 at 12:01 -0600, Robert Whitehead wrote: > The code updates have been placed in cvs. We could create a commit notification list. > There will be more improvements coming forth shortly. > -Robert > > >>> Ming Zhang <mi...@el...> 10/26/2006 11:32 AM >>> > good to know. the code is updated in cvs? shall we create a cvs/svn > commit notification mailing list? > > ming > > > > On Thu, 2006-10-26 at 11:14 -0600, Robert Whitehead wrote: > > I have recently taken on the task to update the iSNS code. > > > > The first task was to get the iSNS server working with the lastest version of the iscsitarget (IET) target on Linux. > > The second task was to get it working with the Microsoft Initiator since it has support for iSNS. > > The code posted recently reflects the changes made to accomplish these two tasks. The testing has been limited so far but it > > was important to get these changes posted out. > > > > Support for the open-iscsi initiator is next. This requires more iSNS support to be built into this initiator. > > > > There is also work to do to bring this iSNS implementation up to the lastest specification and to turn this initial iSNS code into > > a working/completed product. I plan on doing much work in this area. I have reviewed the previous suggestions. There are > > some very good thoughts in these posts. > > > > > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Linuxisns-discussion mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion |
From: Robert W. <WRW...@no...> - 2006-10-26 18:01:58
|
The code updates have been placed in cvs. We could create a commit notification list. There will be more improvements coming forth shortly. -Robert >>> Ming Zhang <mi...@el...> 10/26/2006 11:32 AM >>> good to know. the code is updated in cvs? shall we create a cvs/svn commit notification mailing list? ming On Thu, 2006-10-26 at 11:14 -0600, Robert Whitehead wrote: > I have recently taken on the task to update the iSNS code. > > The first task was to get the iSNS server working with the lastest version of the iscsitarget (IET) target on Linux. > The second task was to get it working with the Microsoft Initiator since it has support for iSNS. > The code posted recently reflects the changes made to accomplish these two tasks. The testing has been limited so far but it > was important to get these changes posted out. > > Support for the open-iscsi initiator is next. This requires more iSNS support to be built into this initiator. > > There is also work to do to bring this iSNS implementation up to the lastest specification and to turn this initial iSNS code into > a working/completed product. I plan on doing much work in this area. I have reviewed the previous suggestions. There are > some very good thoughts in these posts. > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Linuxisns-discussion mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion |
From: Ming Z. <mi...@el...> - 2006-10-26 17:32:34
|
good to know. the code is updated in cvs? shall we create a cvs/svn commit notification mailing list? ming On Thu, 2006-10-26 at 11:14 -0600, Robert Whitehead wrote: > I have recently taken on the task to update the iSNS code. > > The first task was to get the iSNS server working with the lastest version of the iscsitarget (IET) target on Linux. > The second task was to get it working with the Microsoft Initiator since it has support for iSNS. > The code posted recently reflects the changes made to accomplish these two tasks. The testing has been limited so far but it > was important to get these changes posted out. > > Support for the open-iscsi initiator is next. This requires more iSNS support to be built into this initiator. > > There is also work to do to bring this iSNS implementation up to the lastest specification and to turn this initial iSNS code into > a working/completed product. I plan on doing much work in this area. I have reviewed the previous suggestions. There are > some very good thoughts in these posts. > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion |
From: Robert W. <WRW...@no...> - 2006-10-26 17:15:07
|
I have recently taken on the task to update the iSNS code. The first task was to get the iSNS server working with the lastest version of the iscsitarget (IET) target on Linux. The second task was to get it working with the Microsoft Initiator since it has support for iSNS. The code posted recently reflects the changes made to accomplish these two tasks. The testing has been limited so far but it was important to get these changes posted out. Support for the open-iscsi initiator is next. This requires more iSNS support to be built into this initiator. There is also work to do to bring this iSNS implementation up to the lastest specification and to turn this initial iSNS code into a working/completed product. I plan on doing much work in this area. I have reviewed the previous suggestions. There are some very good thoughts in these posts. |
From: Ming Z. <mi...@el...> - 2006-09-14 15:58:55
|
it is a ugly patch. compile and no further test. could be elegant while i have no more time. the code quality is soso. this is one reason i have no further interest to make the patch better. ;) i assumed we need a isnsd and isnsadm here. ming On Thu, 2006-09-14 at 08:54 -0700, Albert Pauw wrote: > > though not 100% sure, but it should not be difficult to make it > > compilable on linux. i have a quick check, just some header issues. > > Keep me posted on your progress. > > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups "open-iscsi" group. > To post to this group, send email to ope...@go... > To unsubscribe from this group, send email to ope...@go... > For more options, visit this group at http://groups.google.com/group/open-iscsi > -~----------~----~----~----~------~----~------~--~--- > |
From: Ming Z. <min...@gm...> - 2006-09-14 15:46:28
|
though not 100% sure, but it should not be difficult to make it compilable on linux. i have a quick check, just some header issues. On Thu, 2006-09-14 at 08:19 -0700, Albert Pauw wrote: > It's very premature, but here's a link to the files: > > http://www.opensolaris.org/os/project/isns/files/ > > It won't compile on Linux at the moment. > > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups "open-iscsi" group. > To post to this group, send email to ope...@go... > To unsubscribe from this group, send email to ope...@go... > For more options, visit this group at http://groups.google.com/group/open-iscsi > -~----------~----~----~----~------~----~------~--~--- > |
From: Ming Z. <min...@gm...> - 2006-09-14 14:38:38
|
yes, it is very old and we thought to rewrite it. but now if opensolaris has prototype released, maybe we should work on that code base and make sure it is Linux compatible? Ming On Thu, 2006-09-14 at 00:24 -0700, Albert Pauw wrote: > Yes, that's the only one we know of for Linux. > > Unfortunately, it's old (release date 2001) it doesn't compile, at > least on Linux (the client does but I couldn't get it to work, the > server doesn't), the client is menu driven, and it adheres to a very > old draft version of the isns document. So it is not too useful. > > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups "open-iscsi" group. > To post to this group, send email to ope...@go... > To unsubscribe from this group, send email to ope...@go... > For more options, visit this group at http://groups.google.com/group/open-iscsi > -~----------~----~----~----~------~----~------~--~--- > |
From: Kiran P. <kir...@gm...> - 2006-09-12 01:45:11
|
Hi Ming, >There is a discussion going on in open-iscsi list. IET already has a >workable iSNS client and open-iscsi tries to integrate it. So you might >want to involve the discuss as well. Yes i will involve in the discuss. >I think this project should focus on providing a workable iSNS server. >What is your opinion? I agree with you. -Kiran On 9/12/06, Ming Zhang <mi...@el...> wrote: > > Hi Kiran > > Sounds cool. > > There is a discussion going on in open-iscsi list. IET already has a > workable iSNS client and open-iscsi tries to integrate it. So you might > want to involve the discuss as well. > > I think this project should focus on providing a workable iSNS server. > What is your opinion? > > Ming > > On Mon, 2006-09-11 at 21:56 +0530, Kiran Patil wrote: > > Hi All, > > > > I have been working for iSCSI from past one year. > > > > I am ready for time and effort. > > > > -Kiran > > > > On 9/11/06, Ming Zhang <mi...@el...> wrote: > > Hi Kiran > > > > Sorry but I think I did not know you? Could you introduce > > yourself a > > bit? > > > > So you have interest on getting this iSNS work, this need a > > lot of time > > involved. Are you ready for this? > > > > Ming > > > > On Sun, 2006-09-10 at 22:53 +0530, Kiran Patil wrote: > > > Hi Ming, > > > > > > Shall we start the fresh iSNS development. > > > > > > Please guide me and I am ready to work. > > > > > > Thanks, > > > Kiran. > > > > > > ------------------------------------------------------------------------- > > > Using Tomcat but need to do more? Need to support web > > services, security? > > > Get stuff done quickly with pre-integrated technology to > > make your job easier > > > Download IBM WebSphere Application Server v.1.0.1 based on > > Apache Geronimo > > > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > _______________________________________________ > > Linuxisns-discussion mailing list > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > > > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, > security? > > Get stuff done quickly with pre-integrated technology to make your job > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ Linuxisns-discussion > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > |
From: Ming Z. <mi...@el...> - 2006-09-11 21:28:37
|
Hi Kiran Sounds cool. There is a discussion going on in open-iscsi list. IET already has a workable iSNS client and open-iscsi tries to integrate it. So you might want to involve the discuss as well. I think this project should focus on providing a workable iSNS server. What is your opinion? Ming On Mon, 2006-09-11 at 21:56 +0530, Kiran Patil wrote: > Hi All, > > I have been working for iSCSI from past one year. > > I am ready for time and effort. > > -Kiran > > On 9/11/06, Ming Zhang <mi...@el...> wrote: > Hi Kiran > > Sorry but I think I did not know you? Could you introduce > yourself a > bit? > > So you have interest on getting this iSNS work, this need a > lot of time > involved. Are you ready for this? > > Ming > > On Sun, 2006-09-10 at 22:53 +0530, Kiran Patil wrote: > > Hi Ming, > > > > Shall we start the fresh iSNS development. > > > > Please guide me and I am ready to work. > > > > Thanks, > > Kiran. > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web > services, security? > > Get stuff done quickly with pre-integrated technology to > make your job easier > > Download IBM WebSphere Application Server v.1.0.1 based on > Apache Geronimo > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > Linuxisns-discussion mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ Linuxisns-discussion mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion |
From: Kiran P. <kir...@gm...> - 2006-09-11 16:27:00
|
Hi All, I have been working for iSCSI from past one year. I am ready for time and effort. -Kiran On 9/11/06, Ming Zhang <mi...@el...> wrote: > > Hi Kiran > > Sorry but I think I did not know you? Could you introduce yourself a > bit? > > So you have interest on getting this iSNS work, this need a lot of time > involved. Are you ready for this? > > Ming > > On Sun, 2006-09-10 at 22:53 +0530, Kiran Patil wrote: > > Hi Ming, > > > > Shall we start the fresh iSNS development. > > > > Please guide me and I am ready to work. > > > > Thanks, > > Kiran. > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, > security? > > Get stuff done quickly with pre-integrated technology to make your job > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ Linuxisns-discussion > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion > > |
From: Ming Z. <mi...@el...> - 2006-09-11 13:57:06
|
Hi Kiran Sorry but I think I did not know you? Could you introduce yourself a bit? So you have interest on getting this iSNS work, this need a lot of time involved. Are you ready for this? Ming On Sun, 2006-09-10 at 22:53 +0530, Kiran Patil wrote: > Hi Ming, > > Shall we start the fresh iSNS development. > > Please guide me and I am ready to work. > > Thanks, > Kiran. > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ Linuxisns-discussion mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxisns-discussion |
From: Kiran P. <kir...@gm...> - 2006-09-10 17:23:49
|
Hi Ming, Shall we start the fresh iSNS development. Please guide me and I am ready to work. Thanks, Kiran. |
From: Ming Z. <mi...@el...> - 2005-04-09 01:46:21
|
On Fri, 2005-04-08 at 18:27 -0700, Nicholas A. Bellinger wrote: > On Fri, 2005-04-08 at 20:28 -0400, Ming Zhang wrote: > > On Fri, 2005-04-08 at 16:13 -0700, Nicholas A. Bellinger wrote: > > > On Fri, 2005-04-08 at 15:38 -0400, Ming Zhang wrote: > > > > Suggest to divide the development into at least 3 stages. > > > > > > > > 1) implement core function, have a workable solution. a release 1.0 > > > > 2) implement secondary functionalities. > > > > 3) some > > > > > > > > Some stage 1 tasks are > > > > > > > > * Code cleanup: > > > > Support Linux 32bit/64bit. > > > > * Support TCP for transport > > > > > > > > > > Also includes: > > > > > > A) iSNS client taking command line arguements for various discovery > > > domain operations > > yes, we need this. > > > > > > > B) iSNS client calling other userspace programs based upon what mode the > > > iSNS client is running in (initiator/target/both) (initiator-ctl in > > > iscsi-initiator-core.org's case) to perform actions based upon the > > > response, or asynchronous messages from the iSNS server. > > > > > is this a good way or we should call isns action from ini or target? > > > > Depends on the action. The example of initial initiator node > registration with the iSNS server is an iSNS client action. The iSNS > server contacting target nodes that a new initiator node is available is > an iSNS server action. My point is that both ways are needed: > > A) iSNS client action == from the iSNS client command line > B) iSNS server action == from the iSNS daemon to an external program for > initiator/target node [re]configuration > ic. so u mean a 2-way communications. yes, the scn need this and we definitely need to support it. > > > > > > Also, I need to read up on the iSNS RFC again, I don't think we need to > > > go above what the draft says (its UDP with application layer checksums > > > right?) > > > > > yes, i need to read it again as well. today i did a quick read and get > > refreshed. > > > > > > Some stage 2 tasks are > > > > * SCN > > > > * for iSNS service discovery, 2.5.1, 2.5.3 > > > > * snmp support by net-snmp > > > > > > > > > > As mentioned above, I need to read up on all of this. > > > > > > > Some stage 3 tasks are > > > > * 2.7 iSNS server fail over and synchronization. > > > > > > > > > > > > Some extra thoughts. > > > > > > > > > > > > * Must provide a persistence-neutral way to store the iSNS database. It > > > > can be a Berkley DB or a complete openlDAP solution. so a wrapper is > > > > needed to isolate the main code from it. > > > > > > > > > > Berkley DB is what we want in this case. OpenLDAP would be used for > > > storing the authentication information in a single locate. The OpenLDAP > > > clients would be running on each Initiator node. > > > > > fine. > > > > This was just based on my knowledge of LDAP. I always understand that > the primary use of LDAP is as a single repository for authentication > information, and not for storing large amounts of generic data in a > database style format..? > hehe. i might know a little more than you. it is ok for ldap to hold data like isns info, anyway it is K of records not M of records. see page 8, 2.1.4 isns database. ming |
From: Nicholas A. B. <na...@ke...> - 2005-04-09 01:35:05
|
On Fri, 2005-04-08 at 20:28 -0400, Ming Zhang wrote: > On Fri, 2005-04-08 at 16:13 -0700, Nicholas A. Bellinger wrote: > > On Fri, 2005-04-08 at 15:38 -0400, Ming Zhang wrote: > > > Suggest to divide the development into at least 3 stages. > > > > > > 1) implement core function, have a workable solution. a release 1.0 > > > 2) implement secondary functionalities. > > > 3) some > > > > > > Some stage 1 tasks are > > > > > > * Code cleanup: > > > Support Linux 32bit/64bit. > > > * Support TCP for transport > > > > > > > Also includes: > > > > A) iSNS client taking command line arguements for various discovery > > domain operations > yes, we need this. > > > > B) iSNS client calling other userspace programs based upon what mode the > > iSNS client is running in (initiator/target/both) (initiator-ctl in > > iscsi-initiator-core.org's case) to perform actions based upon the > > response, or asynchronous messages from the iSNS server. > > > is this a good way or we should call isns action from ini or target? > Depends on the action. The example of initial initiator node registration with the iSNS server is an iSNS client action. The iSNS server contacting target nodes that a new initiator node is available is an iSNS server action. My point is that both ways are needed: A) iSNS client action == from the iSNS client command line B) iSNS server action == from the iSNS daemon to an external program for initiator/target node [re]configuration > > > Also, I need to read up on the iSNS RFC again, I don't think we need to > > go above what the draft says (its UDP with application layer checksums > > right?) > > > yes, i need to read it again as well. today i did a quick read and get > refreshed. > > > > Some stage 2 tasks are > > > * SCN > > > * for iSNS service discovery, 2.5.1, 2.5.3 > > > * snmp support by net-snmp > > > > > > > As mentioned above, I need to read up on all of this. > > > > > Some stage 3 tasks are > > > * 2.7 iSNS server fail over and synchronization. > > > > > > > > > Some extra thoughts. > > > > > > > > > * Must provide a persistence-neutral way to store the iSNS database. It > > > can be a Berkley DB or a complete openlDAP solution. so a wrapper is > > > needed to isolate the main code from it. > > > > > > > Berkley DB is what we want in this case. OpenLDAP would be used for > > storing the authentication information in a single locate. The OpenLDAP > > clients would be running on each Initiator node. > > > fine. > This was just based on my knowledge of LDAP. I always understand that the primary use of LDAP is as a single repository for authentication information, and not for storing large amounts of generic data in a database style format..? -- Nicholas A. Bellinger <na...@ke...> |
From: Ming Z. <mi...@el...> - 2005-04-09 00:43:46
|
i do a quick read on the code and i feel that 1) the code structure is not reasonable. i believe there can be a lot of defines and functions that can be shared by client and server. so a reasonable code structure should be linux-isns/src/ client/ common/ server/ 2) all code are indent in a way i feel uncomfortable. i prefer the linux kernel way. :P 3) i want to remove the whole windows stuff since i do not think we have extra energy to maintain that. and that make the code unclear with those #ifdef stuff. i hate those too much when working on iometer. so i suggest one of us do such a cleanup and then we decide the stuff in common/. then we can work on it. i suggest u do the whole client stuff and i do the server stuff. then we have a clear divider and make this development easier. u can integrate it with you ini and we can do some tests right way from u ini. svn is fine for me, can u setup a svn server? i am now work at home and no extra box i can use. |
From: Ming Z. <mi...@el...> - 2005-04-09 00:28:26
|
On Fri, 2005-04-08 at 16:13 -0700, Nicholas A. Bellinger wrote: > On Fri, 2005-04-08 at 15:38 -0400, Ming Zhang wrote: > > Suggest to divide the development into at least 3 stages. > > > > 1) implement core function, have a workable solution. a release 1.0 > > 2) implement secondary functionalities. > > 3) some > > > > Some stage 1 tasks are > > > > * Code cleanup: > > Support Linux 32bit/64bit. > > * Support TCP for transport > > > > Also includes: > > A) iSNS client taking command line arguements for various discovery > domain operations yes, we need this. > B) iSNS client calling other userspace programs based upon what mode the > iSNS client is running in (initiator/target/both) (initiator-ctl in > iscsi-initiator-core.org's case) to perform actions based upon the > response, or asynchronous messages from the iSNS server. > is this a good way or we should call isns action from ini or target? > Also, I need to read up on the iSNS RFC again, I don't think we need to > go above what the draft says (its UDP with application layer checksums > right?) > yes, i need to read it again as well. today i did a quick read and get refreshed. > > Some stage 2 tasks are > > * SCN > > * for iSNS service discovery, 2.5.1, 2.5.3 > > * snmp support by net-snmp > > > > As mentioned above, I need to read up on all of this. > > > Some stage 3 tasks are > > * 2.7 iSNS server fail over and synchronization. > > > > > > Some extra thoughts. > > > > > > * Must provide a persistence-neutral way to store the iSNS database. It > > can be a Berkley DB or a complete openlDAP solution. so a wrapper is > > needed to isolate the main code from it. > > > > Berkley DB is what we want in this case. OpenLDAP would be used for > storing the authentication information in a single locate. The OpenLDAP > clients would be running on each Initiator node. > fine. > > > > |
From: Ming Z. <mi...@el...> - 2005-04-09 00:26:58
|
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. > |
From: Nicholas A. B. <na...@ke...> - 2005-04-08 23:21:24
|
On Fri, 2005-04-08 at 15:38 -0400, Ming Zhang wrote: > Suggest to divide the development into at least 3 stages. > > 1) implement core function, have a workable solution. a release 1.0 > 2) implement secondary functionalities. > 3) some > > Some stage 1 tasks are > > * Code cleanup: > Support Linux 32bit/64bit. > * Support TCP for transport > Also includes: A) iSNS client taking command line arguements for various discovery domain operations B) iSNS client calling other userspace programs based upon what mode the iSNS client is running in (initiator/target/both) (initiator-ctl in iscsi-initiator-core.org's case) to perform actions based upon the response, or asynchronous messages from the iSNS server. Also, I need to read up on the iSNS RFC again, I don't think we need to go above what the draft says (its UDP with application layer checksums right?) > Some stage 2 tasks are > * SCN > * for iSNS service discovery, 2.5.1, 2.5.3 > * snmp support by net-snmp > As mentioned above, I need to read up on all of this. > Some stage 3 tasks are > * 2.7 iSNS server fail over and synchronization. > > > Some extra thoughts. > > > * Must provide a persistence-neutral way to store the iSNS database. It > can be a Berkley DB or a complete openlDAP solution. so a wrapper is > needed to isolate the main code from it. > Berkley DB is what we want in this case. OpenLDAP would be used for storing the authentication information in a single locate. The OpenLDAP clients would be running on each Initiator node. > |