We've released 13.0.0 and we had been planning on releasing it last week (thanks to gate issues things got delayed to this week). Given the late request and how everyone has already been working hard, I'd prefer that it land in Ussuri and we do a release for that.

Having said that, if two cores are willing to review and do the necessary paperwork, that is fine with me :)

--ruby

On Tue, Sep 24, 2019 at 12:58 PM Julia Kreger <juliaashleykreger@gmail.com> wrote:

I am in support of getting this in, but ironic is essentially at the time for our release window for 13.0.0 as we need to create the stable/train branch. To do this will force 13.1 to be the final version to train if we need to back-port this patch. I can review it tonight after my meetings, and possibly Dmitry or another core can review and if they feel that it can be approved tomorrow.

I guess the deterrent for me mentally at this point is we’ve already geared documentation towards 13.0.0 being the Train release.

-Julia

On Mon, Sep 23, 2019 at 8:10 PM <Richard.Pioso@dell.com> wrote:

Hi,

I request a late feature freeze exception (FFE) for https://review.opendev.org/#/c/672498/ -- "Add Redfish vmedia boot interface to idrac HW type". There is high demand from operators for this feature. They would be delighted if it were included in Train.

We believe it is a low risk change, because of the following:

1) It affects only the idrac hardware type.
2) The highest priority boot interfaces supported by the idrac hardware type remain so. 'ipxe' and 'pxe' continue to have the highest priority, and the new 'idrac-redfish-virtual-media' has the lowest priority. The new order from highest to lowest priority is 'ipxe', 'pxe', and 'idrac-redfish-virtual-media'.
3) The new interface is based on and almost entirely leverages an already merged interface implementation, 'redfish-virtual-media'. [1]

Please let me know if you have any concerns or questions. Thank you for your consideration.

Rick


[1] https://review.opendev.org/#/c/638453/