Hello OpenStackers
I just had a question for those here that may use iSCSI-based Cinder
back-ends;
In your implementations do you have the ability for hypervisors and
controllers to only hold iSCSI sessions open to Cinder LUNs that they
require, but not others?
That is, a hypervisor should only have iSCSI sessions active to targets
it needs, or none if they're not hosting instances mounting iSCSI backed
Cinder volumes. Perhaps this could be orchestrated through the Cinder
driver for the storage, if not Cinder itself.
We've been using a NexentaStor appliance for iSCSI Cinder storage, but
have come across the behavior that (as it was configured) controllers
and hypervisors hold iSCSI sessions open to all of the targets present
on the backend, which strikes me as potentially unsafe. So I'm curious
whether the situation is different for any other iSCSI Cinder backends
that may be in general use.
Many thanks,
Paul Browne
--
*******************
Paul Browne
Research Computing Platforms
University Information Services
Roger Needham Building
JJ Thompson Avenue
University of Cambridge
Cambridge
United Kingdom
E-Mail: pf...@cam.ac.uk
Tel: 0044-1223-746548
*******************
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
