From owner-freebsd-cluster@FreeBSD.ORG Mon Jun 23 05:36:59 2003 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EF3737B401 for ; Mon, 23 Jun 2003 05:36:59 -0700 (PDT) Received: from mail024.syd.optusnet.com.au (mail024.syd.optusnet.com.au [210.49.20.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62E1743F85 for ; Mon, 23 Jun 2003 05:36:57 -0700 (PDT) (envelope-from Peter.Ross@alumni.tu-berlin.de) Received: from guckloch.zuhause (melax4-142.dialup.optusnet.com.au [210.49.66.142])h5NCaeA17973; Mon, 23 Jun 2003 22:36:41 +1000 Received: from guckloch.zuhause (localhost.zuhause [127.0.0.1]) by guckloch.zuhause (8.12.9/8.12.9) with ESMTP id h5NCYs0i000809; Mon, 23 Jun 2003 22:34:54 +1000 (EST) (envelope-from Peter.Ross@alumni.tu-berlin.de) Received: from localhost (petros@localhost)h5NCYpeZ000806; Mon, 23 Jun 2003 22:34:52 +1000 (EST) X-Authentication-Warning: guckloch.zuhause: petros owned process doing -bs Date: Mon, 23 Jun 2003 22:34:51 +1000 (EST) From: Peter Ross X-X-Sender: petros@guckloch.zuhause To: Gabriel Ambuehl In-Reply-To: <1711841578.20030618104618@buz.ch> Message-ID: <20030623214253.O520@guckloch.zuhause> References: <1711841578.20030618104618@buz.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-cluster@freebsd.org Subject: Re[2]: iSCSI and clustering with FreeBSD X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 12:36:59 -0000 On Wed, 18 Jun 2003, Gabriel Ambuehl wrote: > > BTW: I wrote two weeks ago that I like to start writing an iSCSI > > initiator. I spent the last days reading documents and sources and > > installing my programming and test environment. > > So I didn't start writing yet but I'm on the way.. > > You maybe want some help with that? Yes:-) It starts with basic design questions. Sorry, I am always late.. I want to implement the iSCSI initiator as a CAM SIM driver. I was pointed to the umass driver which is a "translator" between SCSI and USB commands. The developers handbook gives me a good introduction how to write a SIM driver. But how to establish the connection, especially the authorization? I am not sure how to handle this. I think it shouldn't be part of the kernel driver. Maybe similiar to NFS asking for Kerberos tickets? But the developers of nfssvc don't seem to be lucky about this.. I don't feel I have the experience to decide this so I would appreciate answers. BTW: You can see there are ways to share the task.. Thank you Peter From owner-freebsd-cluster@FreeBSD.ORG Mon Jun 23 12:17:16 2003 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A318137B401 for ; Mon, 23 Jun 2003 12:17:16 -0700 (PDT) Received: from walnut.he.net (walnut.he.net [64.71.137.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BD1343FEC for ; Mon, 23 Jun 2003 12:17:16 -0700 (PDT) (envelope-from kmacy@fsmware.com) Received: from localhost (kmacy@localhost) by walnut.he.net (8.8.6p2003-03-31/8.8.2) with ESMTP id MAA09446; Mon, 23 Jun 2003 12:17:05 -0700 Date: Mon, 23 Jun 2003 12:17:05 -0700 (PDT) From: Kip Macy X-Sender: kmacy@walnut.he.net To: Peter Ross In-Reply-To: <20030623214253.O520@guckloch.zuhause> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-cluster@freebsd.org Subject: Re: Re[2]: iSCSI and clustering with FreeBSD X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 19:17:16 -0000 > It starts with basic design questions. Sorry, I am always late.. > > I want to implement the iSCSI initiator as a CAM SIM driver. I was pointed > to the umass driver which is a "translator" between SCSI and USB commands. > The developers handbook gives me a good introduction how to write a SIM > driver. A good place to start is to write something strictly in userland that logs in and generates traffic to the target. When I wrote my target it was initially all in userland. After, the protocol handling had proven to be robust I moved it into the kernel. If you try to familiarize yourself with too many things at once, it may take you a long time to get started. -Kip