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] block-nbd script and example config

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] block-nbd script and example config
From: Arnd Schmitter <arnd_xen@xxxxxxxx>
Date: Thu, 20 Oct 2005 10:15:05 +0200
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Kurt Garloff <garloff@xxxxxxx>, Nicholas Lee <emptysands@xxxxxxxxx>
Delivery-date: Thu, 20 Oct 2005 08:12:24 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=XH2h0rq2pGYBejhoPJVUATIHRPNAAu8U2MkZ6j8ay+tu0f6P+f7JXW2FH8e85q1ZRlylO7a051lbzaMdEq/orwx+s31uVu7N188ex9bk8OjPB5qBh558sUWt1rQP0IfhoO3Y2SmT32++zVB+1FlpcXI33Vm0Xr3+uys1D8ZU08w= ;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43570E19.5070509@xxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D32E4B9@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4356C389.1080804@xxxxxxxxxx> <2b6116b30510191752w41c8f88bq11937c9d1688f454@xxxxxxxxxxxxxx> <43570E19.5070509@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.4.1 (Windows/20051006)
Anthony Liguori wrote:
Nicholas Lee wrote:

The only thing to think about is how do handle file devices with spaces
in the filename.  This is going to be common I think.

Since it's a python variable can't you just run a validator on config
import and throw an exception if the devive block doesn't exist. Noting that device paths including special characters need to be
enclosured in "...".

ie. export=phy:"/dev/vgname/bob your uncle; mate! device", ...
Double quotes are actually valid characters in a filename although rarely used.

A more bold way of approaching this would be to adopt a more qemu like syntax of:

hda1="/dev/vgname/bob you uncle; mate1"
hda2="/root/rockhopper.img"

We could use stat to figure out whether something was a file or a device and use the appropriate script (file or phy). For everything else, we could use explicit urls such as:

hda3="nbd://rockhopper.austin.ibm.com:1025"

I like the syntax a lot but I'm not sure that marking a device read-only works nicely anymore. We could have a single readonly attribute like:

readonly=['hda1', 'hda2']
For readonly i would suggest a kind of following syntax:

hda1:r="/dev/..."
hda2:w="/dev/.."

Arnd


        

        
                
___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de


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