[openstack-dev] [TripleO] Stable branch policy for Mitaka
Arkady_Kanevsky at DELL.com
Arkady_Kanevsky at DELL.com
Mon Feb 15 23:21:17 UTC 2016
I like any formal documented process.
Having only bug fixes for stable releases is a good and consistent stand.
But we are bumping into fundamental issue of integrated release.
By the time release comes out the new functionality of nova, or neutron or most other components do not triple heat templates that deploy and configure that functionality for overcloud. So as soon as somebody will try to use Triple O (or RDO manager or OSP director, or any other derivative) they try to remedy this shortcoming. Being good openstack citizens these folks submit heat templates upstream. We can state that we will not take them into stable release. They will push that community away from upstream and will diverge their deployment from it. Or they will pound on their openstack provider (if it is not upstream) to have a place to maintain them for them. Either way it is ugly. And will make upgrade and update for these Customers a nightmare.
TripleO is not a unique to that. Horizon, and others, has it in spades.
Do not know if we will be able to fix it in openstack itself or we rely on distros to handle it.
But we will need some place for users to provide their fixes and extension of current capabilities of TripleO to support existing configuration and new functionality of released core openstack.
From: Steven Hardy [mailto:shardy at redhat.com]
Sent: Monday, February 15, 2016 3:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [TripleO] Stable branch policy for Mitaka
On Wed, Feb 10, 2016 at 07:05:41PM +0100, James Slagle wrote:
> On Wed, Feb 10, 2016 at 4:57 PM, Steven Hardy wrote:
> Hi all,
> We discussed this in our meeting this week, and agreed a ML
> to gain consensus and give folks visibility of the outcome would be a
> In summary, we adopted a more permissive "release branch" policy for
> stable/liberty branches, where feature backports would be allowed,
> they worked with liberty and didn't break backwards compatibility.
> The original idea was really to provide a mechanism to "catch up" where
> features are added e.g to liberty OpenStack components late in the cycle
> and TripleO requires changes to integrate with them.
> However, the reality has been that the permissive backport policy has
> somewhat abused (IMHO) with a large number of major features being
> for backport, and in a few cases this has broken downstream (RDO)
> of TripleO.
> Thus, I would propose that from Mitaka, we revise our backport policy to
> simply align with the standard stable branch model observed by all
> Hopefully this will allow us to retain the benefits of the stable branch
> process, but provide better stability for downstream consumers of these
> branches, and minimise confusion regarding what is a permissable
> If we do this, only backports that can reasonably be considered
> "Appropriate fixes" will be valid backports - in the majority of
> this will mean bugfixes only, and large features where the risk of
> regression is significant will not be allowed.
> What are peoples thoughts on this?
> â**I'm in agreement. I think this change is needed and will help set
> better expectations around what will be included in which release.
> If we adopt this as the new policy, then the immediate followup is to set
> and communicate when we'll be cutting the stable branches, so that it's
> understood when the features have to be done/committed. I'd suggest that
> we more or less completely adopt the integrated release schedule. Which
> I believe means the week of RC1 for cutting the stable/mitaka branches,
> which is March 14th-18th.
> It seems to follow logically then that we'd then want to also be more
> aggresively aligned with other integrated release events such as the
> feature freeze date, Feb 29th - March 4th.
Yes, agreeing a backport policy is the first step, and aligning all our release policies with the rest of OpenStack is the logical next step.
> An alternative to strictly following the schedule, would be to say that
> TripleO lags the integrated release dates by some number of weeks (1 or 2
> I'd think), to allow for some "catchup" time since TripleO is often
> consuming features from projects part of the integrated release.
The risk with this approach is there remains some confusion about our deadlines, and there is an increased risk that our 1-2 weeks window slips and we end up with a similar problem to that which we have now.
I'd propose we align with whatever schedule the puppet community observes, given that (with out current implementation at least), it's unlikely we can land any features actually related to new-feature-in-$service type patches without that feature already having support in the puppet modules?
Perhaps we can seek out some guidance from Emilien, as I'm not 100% sure of the release model observed for the puppet modules?
If you look at the features we're backporting, most of them aren't related to features requiring "catchup", e.g IPv6, SSL, Upgrades - these are all cross-project TripleO features and there are very few (if any?) "catchup"
type requirements AFAICT.
Also, if you look at other projects, such as Heat and Mistral, which interact with many other services, they observe the same schedule as all other projects - so if you want $new_feature for some project integrated there, you have to get your patches for that integration posted before feature freeze. I'm thinking there is less room for confusion and deadline abuse if we just say TripleO is the same?
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev