Hi Lucas.

Are there links related to any upstream work be added to the BZ?

Thanks

(In reply to Paul Christensen from comment #3)
> Hi Lucas.
> 
> Are there links related to any upstream work be added to the BZ?
> 
> Thanks

Hi Paul,

Yes there are, I will link it in this BZ.

(In reply to Lucas Alvares Gomes from comment #4)
> (In reply to Paul Christensen from comment #3)
> > Hi Lucas.
> > 
> > Are there links related to any upstream work be added to the BZ?
> > 
> > Thanks
> 
> Hi Paul,
> 
> Yes there are, I will link it in this BZ.

I'm sorry I may have confused BZ's here... This work is about the be2iscsi driver? Not boot from volume, right ?

If so, why we need two BZs for it?

Hi Dmitry,

Could you please add 'Doc Text' describing this change, so that it can be included with the release notes?

Thank you!

Ramon, could you please do it? I think you have more actual experience with $subj.

Hi Charelle, the purpose of this RFE is to support booting a node from a SAN. Currently, we have a note saying it's not supported [1]:

"Booting an overcloud node from the SAN (FC-AL, FCoE, iSCSI) is not yet supported"

We intend to support boot from SAN over FC and over iSCSI, with iSCSI being a lower priority test, i.e. if QA proves there are limitations with iSCSI that require patches in the code then we'll plan it for a later release.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/#sect-Overcloud_Requirements

As for the the doc text, it would be something like "Support for booting Overcloud nodes from SAN over Fibre Channel". And if iSCSI passes the QA then we'll add iSCSI.

Yolanda worked on the iSCSI part and documented the process here: http://teknoarticles.blogspot.com.es/2017/10/customize-openstack-images-for-booting.html

This can be marked as verified

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462