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

Re: [Xen-API] [Xen-devel] Driver domains and device handling



On 12/12/12 11:43, Ian Campbell wrote:
> On Tue, 2012-12-11 at 19:46 +0000, Roger Pau Monnà wrote:
>> just launch Qemu, and if we decide to use an in-kernel initiator we only
>> have to launch a hotplug script with something like: iscsiadm -m node -T
>> <iqn> -p <ip:port>.
> 
> isn't there also a iscsiadm login which is needed at some point?

Login is done during the plug by adding --login to the above command,
but I think you can also perform the login in a discovery, and I guess
this login is keep by iscsid, so you don't need to perform it when
plugin the devices. But I'm not sure if is worth performing a discovery
just to login.

> In any case almost any iscsiadm command has the potential to be slow
> compared to the amount of downtime we would like to aim for during a
> migration.

I will do some more research and timming about iscsiadm, to see if
there's anyway in which we can speedup the actual connection of the device.

>> I'm sure there's people on the list with more experience than me on this
>> field, and I would like to ask for some use-cases where this
>> "preparatory" phase would be useful, and what actions will be performed
>> on it.
> 
> Might we worth including xen-api in this discussion since the xapi guys
> have a fair bit of knowledge of the requirement here.

I agree, let's CC xen-api@xxxxxxxxxxxxxx


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

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