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

Re: [Xen-devel] [PATCH 0/3] domUloader

Hi Philip,

On Thu, Jan 26, 2006 at 01:57:35PM -0500, Philip R. Auld wrote:
> Thanks. But I don't have a problem (at least not this anyway ;).
> We're both talking about different ways to do the same thing. 
> My point again is that udev can handle the task of creating 
> well-known, consistent device names for uniquely identifiable 
> disks. And that it makes sense to me to just configure udev 
> properly and you do not need to do anything xen specific to 
> solve this problem. And it is not iSCSI specific either.

... and you just use phy:by-id/name as for disk exporting then.
Sure, that would work.

The block-iscsi script has the advantage that it's possible
to connect to iSCSI target only when needed and disconnect
once you are done. This helps you when migrating VMs from
one physical machine to another. I don't know exactly the
semantics of multiple parallel connections to an iSCSI target.
Probably it should not cause problems, in which case you'd
get away with your phy: solution.

> As I said, I don't know for sure how to make udev do 
> this for iSCSI. For FC you can use the scsi_id callout to 
> get the UID and then have a udev rule to use to generate a 
> device name. There may not exist an analog of scsi_id for
> iSCSI. It's the same as what you are suggesting except it's
> Linux-wide and not xen only :)

You're trying to solve the persistant device naming problem.

Mark and I are trying to connect and disconnect to iSCSI 
targets on demand (and have the possibility to solve the 
 persistent device name problem along the way for xen 
 -- if needed.)

Anyway, we're far off-topic the original post now.

Kurt Garloff, Head Architect, Director SUSE Labs (act.), Novell Inc.

Attachment: pgpUWbPzxgT2b.pgp
Description: PGP signature

Xen-devel mailing list



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