[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] block-nbd script and example config

  • To: "Kurt Garloff" <garloff@xxxxxxx>, "Xen development list" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 19 Oct 2005 22:57:02 +0100
  • Delivery-date: Wed, 19 Oct 2005 21:54:25 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXUlVpMWKoL+h79R1u43r/KTEd53gAYRgaQ
  • Thread-topic: [Xen-devel] block-nbd script and example config


> Find attached the block-nbd script (in /etc/xen/scripts/) and 
> an example config file. The block-nbd script is based on the 
> -enbd one.
> They have been used successfully in the Xen Tutorial at Linux 
> Kongress.

disk = [ 'nbd: 20004,hda1,w' ]

I think having the space in the export device name is just a little too
nauseating :-)

Could we make the script take ip:port and then turn the ':' into a space
when invoking nbdclient?

On this subject, I think it would be less confusing if we configured
disks using a syntax more akin to that which we use for networking e.g.:

disks = [ 'export=phy:/dev/sda1, target=/dev/sda1, options=rw',
          'export=phy:/dev/vg/my_usr, target=/dev/sdb1, options=ro' ]

I know its late in the day to be making changes like this, but it
doesn't hurt to canvass opinion...

I'd also do away with all the fancy stuff we have to build the command
line and just have a single command line variable that we assemble
everything in to within the config file. The current magic just makes
things more confusing.



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.