All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-api@lists.xen.org, Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Driver domains and device handling
Date: Wed, 12 Dec 2012 13:35:07 +0100	[thread overview]
Message-ID: <50C879FB.7060208@citrix.com> (raw)
In-Reply-To: <1355309001.10554.13.camel@zakaz.uk.xensource.com>

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@lists.xen.org.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-12-12 12:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 19:46 Driver domains and device handling Roger Pau Monné
2012-12-12 10:43 ` Ian Campbell
2012-12-12 12:35   ` Roger Pau Monné [this message]
2012-12-13 16:56     ` Handling iSCSI block devices (Was: Driver domains and device handling) Roger Pau Monné
     [not found]     ` <50CA08AE.80102@citrix.com>
2012-12-13 18:23       ` Ian Jackson
     [not found]       ` <20682.7487.598565.547405@mariner.uk.xensource.com>
2012-12-14 10:49         ` Roger Pau Monné
     [not found]         ` <50CB0429.9070300@citrix.com>
2012-12-14 12:30           ` Ian Jackson
     [not found]           ` <20683.7116.546352.141787@mariner.uk.xensource.com>
2012-12-14 15:20             ` Roger Pau Monné
     [not found]             ` <50CB43A9.3040806@citrix.com>
2012-12-14 15:46               ` Ian Jackson
     [not found]               ` <20683.18895.282490.216230@mariner.uk.xensource.com>
2012-12-14 17:33                 ` Roger Pau Monné
     [not found]                 ` <50CB62CD.7020103@citrix.com>
2012-12-14 18:26                   ` Ian Jackson
     [not found]                   ` <20683.28487.926648.451291@mariner.uk.xensource.com>
2012-12-14 18:38                     ` Roger Pau Monné
     [not found]                     ` <50CB721C.5010006@citrix.com>
2012-12-17 11:47                       ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50C879FB.7060208@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-api@lists.xen.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.