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: Nicholas Lee <emptysands@xxxxxxxxx>
Date: Thu, 20 Oct 2005 13:52:46 +1300
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Kurt Garloff <garloff@xxxxxxx>
Delivery-date: Thu, 20 Oct 2005 00:50:01 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bu0HDUG9oDXochaJHXuB6xL88BQkXuyyrR9hsp7bYcED4o19rLeQii+weyRXNkthd8lM3ibsoYk7D73+Dtwsb8wcI4LTLAL9lmcrMYwgF+NjDZ7UFLohULvqMO1tY8hx4TYsGhTK0usya/m+Q0iyQk9DapKqzPtP/YYHYWqZY9E=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4356C389.1080804@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 10/20/05, Anthony Liguori <aliguori@xxxxxxxxxx> wrote:
> >disks = [ 'export=phy:/dev/sda1, target=/dev/sda1, options=rw',
> >          'export=phy:/dev/vg/my_usr, target=/dev/sdb1, options=ro' ]

> 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", ...


--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

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