Understandable.
But we have a rule that we do not backport “new” functionality.
That puts pressure on many asks for FFE.
Should we revisit that rule a bit?
From: Dmitry Tantsur <dtantsur@redhat.com>
Sent: Thursday, September 26, 2019 9:26 AM
To: Julia Kreger
Cc: pramchan@yahoo.com; BIN HU; alanmeadows@att.com; jgu@suse.com; openstack-discuss@lists.openstack.org; rg445d@att.com; rp2723@att.com
Subject: Re: [ironic] FFE: Add idrac HW type Redfish virtual media boot interface (Ruby Loo)
I’m afraid 13.0.0 has been released which is what we targeted to release for Train.
Is there any reason Ironic can’t release 13.1.0 in say a month? I ask since there should be no hard requirement with Ironic in starting with the stable/train branch.
The reason is the stable policy. We've committed to following it, and it doesn't allow feature backports.
An important detail is Airship 2.0 slated for release. If we’re trying to co-ordinate everything across communities, that seems like it is going to be very problematic.
It would be ideal if such requirements could be determined a bit in advance, not later than M3.
We in airship 2.0 need vIrtual media boot up for our work in remoteboot direct using Ironic redfish interface. This is to use both for Ehemeral BareMetalHost as well for target cluter BareMetal Nodes redfish based Virtual Media booting.
We in Airship community strongly endorse the exception to include this feature in Train.
I am copying few of our TC & WC members who too can confirm my ask on behalf of Airship 2.0 team.