Re: [Libvir] RFC 'xen like scripts'

On Mon, 5 May 2008, Daniel P. Berrange wrote: > > For the iscsi backend, like we have discussed before, just discovery needs > > to be implemented. The problem with the NetApp implementation is that it > > exports all 'luns' at the same time. Technically this can be done 'host > > based', but still *far* from implementable in libvirt using the current > > configuration. > > I'm struggling to understand where there's needs to be a netapp specific > impl of the iSCSI backend. Either netapp complies with iSCSI spec or it > doesn't. The iSCSI backend is inteded to work with any compliant server. > Or are you trying to use to netapp specific functionality that isn't > actually part of its iSCSI support ? Short answer: NetApp puts *all* iSCSI luns on one connection. Add 'automatic' lunnumbering and no explicit exported comments in Vendor names etc. to the scenario and you see my ballpark. So to make it more simple: OpenSolaris NetApp All Luns exported Per hostgroup export of all assigned luns Maintains 'use' Doesn't know if a specifc lun is used Uses an identifier Uses one iSCSI identifier, needs rescanning lun can be fetched from 'configuration interface' Due to the reason all LUNs are exported over one connection, a rescan before usage a rescan is always required. LUN numbering is not stable, nor they can be found at the client side.