Avoid LUN 0 for FC Cinder volume

asked 2015-08-13 10:36:57 -0500

jjp gravatar image

updated 2015-08-14 02:22:37 -0500


I am using 3PAR FC as cinder volume backend, and my hypervisors (KVM and Hyper-V) boots from 3PAR as well, (and those boot volumes use LUN 0)

I have multiple Arrays, and when I create volume via api or horizon, seems like on different array they are getting mapped as LUN 0 to hypervisors, and that is rendering my hypervisors non-bootable as now these new volumes are being tried as boot volume if I have to reboot my hypervisors for any reason.

So the question is, is there any config options available where I can avoid LUN 0, or can provide usable LUN ID range etc for cinder.conf


edit retag flag offensive close merge delete