Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

On 30 October 2017 at 15:16, Julia Kreger wrote: ... >>> When I tried it I got this >>> [ 370.704896] dracut-initqueue[387]: Warning: iscistart: Could not >>> get list of targets from firmware. >>> >>> perhaps we could alter iscistart to not complain if there are no

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Sorry! A little late to the discussion with how busy I was last week. Replies/thoughts in-line with trimmed text. >> When I tried it I got this >> [ 370.704896] dracut-initqueue[387]: Warning: iscistart: Could not >> get list of targets from firmware. >> >> perhaps we could alter iscistart to

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

This is a bit offtopic, but a couple of comments on BFV. On 10/25/2017 03:55 PM, Derek Higgins wrote: On 25 October 2017 at 13:03, Dmitry Tantsur wrote: (ooops, I somehow missed this email. sorry!) Hi Yolanda, On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote: Hi

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

On 25 October 2017 at 13:03, Dmitry Tantsur wrote: > (ooops, I somehow missed this email. sorry!) > > Hi Yolanda, > > On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote: >> >> Hi >> Recently i've been helping some customers in the boot from ISCSI feature. >> So far everything

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

> Hmm, are we talking about IPA or user images? IPA always PXE boots, no > matter what boot_option we use. For user images with boot_option=local our > only bet is using the ansible deploy interface, I think (please review it!) > User images, i'm talking about user images (specifically about

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

On 10/25/2017 02:15 PM, Yolanda Robla Mota wrote: Answering inline... Note that we only support BFV in the form of booting from a cinder volume officially. We haven't looked into iBFV in depth. I have been testing that on the context of booting from SAN. It is at deploy time, in the

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Answering inline... Note that we only support BFV in the form of booting from a cinder volume > officially. We haven't looked into iBFV in depth. > I have been testing that on the context of booting from SAN. It is at deploy time, in the context of TripleO, in the undercloud. At that point no

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

(ooops, I somehow missed this email. sorry!) Hi Yolanda, On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote: Hi Recently i've been helping some customers in the boot from ISCSI feature. So far everything was working, but we had a problem when booting the deployment image. It needed specifically

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Hi Julia Yes, you are right on your assumptions here. The missing feature here, is the ability of Ironic to provide a mechanism to append standard kernel arguments, when not netbooting. Having a way to append default parameters to bootloader would be very useful and avoid the need of manual hacks,

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Greetings Yolanda! I guess I'm slightly not clear. In fact, I may be slightly even more confused since we've discussed this directly. Thinking out loud, there are two different scenarios of booting from iSCSI. 1) Human created/assigned/associated LUN off of a SAN which we want a node to boot

[openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Hi Recently i've been helping some customers in the boot from ISCSI feature. So far everything was working, but we had a problem when booting the deployment image. It needed specifically a flag rd.iscsi.ibft=1 rd.iscsi.firmware=1 in the grub commands. But as the generated deployment image doesn't