Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Roger Pau Monné
On 14/12/12 19:26, Ian Jackson wrote: > Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver > domains and device handling)"): >> * remove: called to disconnect the device. Xenstore backend entries >> exists, and backend state is 6 (XenbusStateClosed). > > I assume we need an u

Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Ian Jackson
Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver domains and device handling)"): > Script will be called with only one of the following parameters: > > * prepare: called before start building the domain, this is specially > interesting during migration to offload as much w

Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Roger Pau Monné
On 14/12/12 16:46, Ian Jackson wrote: > Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver > domains and device handling)"): >> I was thinking of adding a new variable to aodev that can contain an >> extra parameter to pass to hotplug scripts, so we can directly pass the >> ful

Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Ian Jackson
Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver domains and device handling)"): > I was thinking of adding a new variable to aodev that can contain an > extra parameter to pass to hotplug scripts, so we can directly pass the > full diskspec to the hotplug script and the hotp

Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Roger Pau Monné
On 14/12/12 13:30, Ian Jackson wrote: > Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver > domains and device handling)"): >> According to RFC3270 and RFC1035 IQNs should follow this format: >> >> iqn.-mm.com.example:optional.string >> >> The problem is that Open-iSCSI se

Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Ian Jackson
Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver domains and device handling)"): > According to RFC3270 and RFC1035 IQNs should follow this format: > > iqn.-mm.com.example:optional.string > > The problem is that Open-iSCSI seems to accept almost anything, for > example

Re: [Xen-API] Handling iSCSI block devices (Was: Driver domains and device handling)

2012-12-14 Thread Roger Pau Monné
On 13/12/12 19:23, Ian Jackson wrote: > Roger Pau Monne writes ("Handling iSCSI block devices (Was: Driver domains > and device handling)"): >> [stuff] > > Most of this sounds sensible. > >> So the diskspec line would look like: >> >> portal=127.0.0.0:3260, authmethod=CHAP, user=foo, password=ba