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

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Roger Pau Monne writes ("Re: Handling iSCSI block devices (Was: Driver domains 
and device handling)"):
> Script <foo> 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 work as possible from
> the "add" call, which is done during the blackout phase of migration. In
> the prepare state, the backend xenstore entries have not yet been created.
> 
>  * add: called to connect the device. Xenstore backend entries exist,
> and backend state is 2 (XenbusStateInitWait).
> 
>  * remove: called to disconnect the device. Xenstore backend entries
> exists, and backend state is 6 (XenbusStateClosed).

I assume we need an unprepare here too.

> Environment variables the script can use (set by the caller):
...
> I'm not sure where HOTPLUG_PATH should reside, does
> /local/domain/<backend_domid>/libxl/hotplug/<domid>/<devid>/ sound ok?

I think that would be fine.

Ian.

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