WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] NetApp vfiler example scripts

To: "Stefan de Konink" <skinkie@xxxxxxxxx>
Subject: Re: [Xen-devel] NetApp vfiler example scripts
From: "Mark Johnson" <johnson.nh@xxxxxxxxx>
Date: Tue, 20 May 2008 07:34:49 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Delivery-date: Tue, 20 May 2008 04:35:11 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=80XQHIOiUjtdvpc6moKbVjs1B406GVMz1FWJ8Q6Dwkk=; b=QRwzHTGA2E1kcnc2GRbSQ/MGch68ARyz5mS+FiqD0wRAndEnCFWnTwijA//UIjTDqFCKgAqk7e1M2ulrgGYKmuBk7EFFnNd9526AKB48hCf7aRXPFN5wbhctkCM5ghO2nTUPlu8vC/6adfVBQNIbLEk85Xai+C42Vt7hAIQzCKk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VpSdmy9XdAgO1d46oYMeajvBYWNgbv0JGHr1VT42PfeScxULAUjhu166z2CKs5nueB949SnGYQYPfSG1466f/lYD3Oo2V962bMWgnwutJUK6u3b+AelHrNrm82zNqiQsrxzJ7eekV7JVQmMvGr9sY1yRdQZEfOMZvnf/IVTyY1o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4831E29F.3020003@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080428225234.P11125-100000@xxxxxxxxxxxxx> <200805191729.16752.mark.williamson@xxxxxxxxxxxx> <4831ACBD.3010405@xxxxxxxxx> <200805191926.09930.mark.williamson@xxxxxxxxxxxx> <4831E29F.3020003@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, May 19, 2008 at 4:27 PM, Stefan de Konink <skinkie@xxxxxxxxx> wrote:
> Mark Williamson schreef:
> Mark Johnson schreef:
>> I've been playing with adding extensions to phy: to handle dynamic
>> block devices. For iscsi, it's something like.
>>    phy:iscsi:[static]/<targetid>/<lun>/[serverIpAddr]
>>
>> e.g.
>>   disk = ['phy:/dev/zvol/dsk/tank/guests/snv89,0,w',
>>
>> 'phy:iscsi:static/iqn.1986-03.com.sun:02:17f34578-00a9-ef69-f3e9-b8a2896a4915/0/192.168.0.70,1,w']
>>
>> when the block hotplug script see's the phy:<ext>: it
>> looks for something like a block-<ext> script and runs
>> it if it can find it, else, defaults down normal path.
>
> Isn't that what normally happens? Just type blabla: and it will go to
> block-blabla?

Not for Solaris.


>> The iscsi hotplug script verifies/sets up the disk, then adds
>> a params-dynamic (equivalent to Stefan's node?) entry in
>> xenstore.  A small change to the disk backend looks for a
>> dynamic entry first, then defaults back to param if it can't find it.
>
> I have based all my code on the shoulders of giants, the final code was one
> big mash up.

I assume you aren't using pygrub to boot off of a iscsi disk?



Thanks,

MRJ

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel