settingsLogin | Registersettings

[openstack-dev] [stable] Preping for the stable/newton EOL

0 votes

Hi All,
This is a quick update on the process for tagging stable/newton as
EOL:

The published[1][2] timeline is:
Sep 29 : Final newton library releases
Oct 09 : stable/newton branches enter Phase III
Oct 11 : stable/newton branches get tagged EOL

Given that those key dates were a little disrupted I'm proposing adding
a week to each so the new timeline looks like:
Oct 08 : Final newton library releases
Oct 16 : stable/newton branches enter Phase III
Oct 18 : stable/newton branches get tagged EOL

The transition to Phase II is important to set expectation about what
backports are applicable while we process the EOL.

I'll prep the list of repos that will be tagged EOL real soon now for
review.

Yours Tony.

[1] https://releases.openstack.org/index.html
[2] https://releases.openstack.org/queens/schedule.html


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

asked Oct 25, 2017 in openstack-dev by Tony_Breeds (19,660 points)   3 6 10

13 Responses

0 votes

On Wed, Oct 25, 2017 at 10:11:01AM +0100, Jean-Philippe Evrard wrote:
On 25 October 2017 at 03:57, Tony Breeds tony@bakeyournoodle.com wrote:

On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote:

On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote:

On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:

I'll prep the list of repos that will be tagged EOL real soon now for
review.

As promised here's the list. The fomat is new, It's grouped by project
team so it should be easy for teams to find repos they care about.

The only wart may be repos I couldn't find an owning team for, so check
the '-' as the owning team.

I'm proposing to EOL all projects that meet one or more of the following
criteria:

  • The project is openstack-dev/devstack, openstack-dev/grenade or
    openstack/requirements (although these wil be done last)
  • The project has the 'check-requirements' job listed as a template in
    project-config:zuul/layout.yaml
  • The project gates with either devstack or grenade jobs
  • The project is listed in governance:reference/projects.yaml and is tagged
    with 'stable:follows-policy'.

Based on previous cycles I have opted out:
- 'openstack/group-based-policy'
- 'openstack/openstack-ansible' # So they can add EOL tags

Also based on recent email's with tripleo I have opted out:
- 'openstack/instack'
- 'openstack/instack-undercloud'
- 'openstack/os-apply-config'
- 'openstack/os-collect-config'
- 'openstack/os-net-config'
- 'openstack/os-refresh-config'
- 'openstack/puppet-tripleo'
- 'openstack/python-tripleoclient'
- 'openstack/tripleo-common'
- 'openstack/tripleo-heat-templates'
- 'openstack/tripleo-puppet-elements'
- 'openstack/tripleo-validations'
- 'openstack/tripleo-image-elements'
- 'openstack/tripleo-ui'

I've also removed the following repos as the have open release requests
for stable/newton
- openstack/nova
- openstack/ironic
- openstack/openstack-ansible*

And at the request of the docs team I've omitted:
- openstack/openstack-manuals

to facilitate 'badging' of the newton docs.

The repos listed in http://lists.openstack.org/pipermail/openstack-dev/2017-October/123910.html
have been retired.

There were a couple of issues
- openstack/deb-python-os-cloud-config
- openstack/bareon
My clones of both had stale gerrit remotes that has been corrected
manually.

The timing of the next phase is uncertain right now but I'd like to take
care of:

  • openstack/nova
  • openstack/ironic
  • openstack/openstack-ansible*
  • openstack/openstack-manuals

before the summit if possible.

Thanks to the infra team for enabling this to happen today.

Tony.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Hello Tony,

We'd like to continue doing as before: updating all our upstream
projects to their EOL tag, then creating an EOL release based on our
roles that would successfully deploy those EOL upstream projects.
If any role need a change, due to latest upstream changes, we need to be ready.

TL:DR; I'll submit a patch soon to bump our upstream roles to EOL,
when nova/ironic will have their EOL tag :p

Yup that was my assumption, sorry it wasn't clear from my
talking-to-myself email thread ;p

So I see it working more or less like:

  1. ironic and releases happen and repos tagged
  2. The existing OSA review is merged
  3. A new review is created for OSA using the tags for $all_projects
    that's merged and released
  4. a review in openstack-ansible pins the OSA roles to that from 3. (I'm
    making that bit up is it right?)
  5. openstack-ansible* repos tagged EOL

Where'd I get it wrong?

Yours Tony.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Oct 25, 2017 by Tony_Breeds (19,660 points)   3 6 10
0 votes

On Wed, Oct 25, 2017 at 01:11:53PM +0200, Dmitry Tantsur wrote:

The last ironic newton release was done, we're ready for EOL.

Thanks that must've happened overnight.

Yours Tony.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Oct 25, 2017 by Tony_Breeds (19,660 points)   3 6 10
0 votes

On Wed, Oct 25, 2017 at 10:24:59AM -0500, Matt Riedemann wrote:
On 10/24/2017 9:57 PM, Tony Breeds wrote:

The timing of the next phase is uncertain right now but I'd like to take
care of:

  • openstack/nova

Just a status update, but the final nova newton release is waiting on two
changes:

  1. https://review.openstack.org/#/c/514685/ - in the gate, should be merged
    today.

Okay.

  1. https://review.openstack.org/#/c/514339/ - we need a fix for that in
    master and then to get backported through to stable/newton. This is a fix
    for a regression introduced in pike which was unfortunately backported to
    newton, so I think we need to fix the regression we introduced into
    stable/newton before EOL.

Okay. This is a good outcome to a bad situation.

Yours Tony.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Oct 25, 2017 by Tony_Breeds (19,660 points)   3 6 10
...