Ask Your Question

jjp's profile - activity

2016-03-04 11:38:44 -0500 received badge  Famous Question (source)
2015-11-25 01:55:18 -0500 received badge  Popular Question (source)
2015-11-25 01:55:18 -0500 received badge  Famous Question (source)
2015-11-25 01:55:18 -0500 received badge  Notable Question (source)
2015-09-18 14:03:23 -0500 received badge  Notable Question (source)
2015-09-18 14:03:23 -0500 received badge  Popular Question (source)
2015-08-14 02:22:40 -0500 received badge  Student (source)
2015-08-13 10:36:57 -0500 asked a question Avoid LUN 0 for FC Cinder volume

Hi,

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

Thanks,

2015-08-06 12:44:34 -0500 asked a question any config options available where I can avoid LUN 0 for 3PAR FC backend

Hi,

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 hyperviros for any reason.

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

Thanks,