Il 24/07/2013 13:03, Daniel P. Berrange ha scritto:
Can you make the pool active, but at the same time not expose it as devices on the host? LUNs can be discovered by talking directly to the target (similar to the iscsi-ls command included with libiscsi).
I've never considered that actually. From the API POV, what we need to know is the list of LUNS and their sizes. We don't require that they have files visible in the host - for example the VMWare storage pool impls don't expose files on the host.
So adding a mode for the pool which let you enumerate LUNs, but not expose them in the FS would be an option.
In other words, perhaps mode='host' vs. mode='direct' could be a property of the pool rather than the disk? That would certainly work fine for me.
It doesn't neccessarily need to be exclusive. If the pool used mode='host' we could still allow mode=host|direct in the guest. Only if the pool used mode=direct, would have to restrict it to mode=direct in the guest. We could make the guest config setting for "mode" default to match the pool's config.
Cool! Sounds like a plan. libvirt itself could use libiscsi to support discovery for mode='direct' pools. Paolo