Stable Release Updates for OpenStack and the Ubuntu Cloud Archive

The SRU process for OpenStack and the Ubuntu Cloud Archive (UCA) follows the same process as Ubuntu Stable Release Updates. This page summarises the process for the cloud archive and adds some points that apply specifically to it.

NOTE: This process is followed for OpenStack packages and supporting dependencies such as Open vSwitch and Ceph.

Package List

OpenStack packages

Supporting packages

SRU Expectations

QA Process

Once stable package updates have been accepted by the ubuntu-sru (or Cloud Archive) team into -proposed pockets, the following SRU verification process is followed:

For updates where there is risk of regression as a result of the package upgrade process, the same testing process is followed as above, deploying from archive excluding proposed, testing using Tempest, upgrading the deployed cloud to proposed and then re-verifying the cloud using Tempest.

This testing process is automated by the Ubuntu OpenStack CI system.

Additionally, any specific test cases covered in SRU bug reports should be explicitly tested as well.

SRU Template

== Begin SRU Template ==
[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements.

The update contains the following package updates:

   * <TODO: Create list with package names and versions>

[Test Case]
The following SRU process was followed:
https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed.  A successful run of all available tests will be required before the
proposed packages can be let into -updates.

The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug.

[Discussion]
<TODO: other background>

== End SRU Template ==

Nominating a Bug for a Series

A sponsor can be asked to nominate a bug for a particular series. You can find the following sponsors in #ubuntu-server on freenode:

Getting permission to target a bug for a series:

Nominating a new package for an SRU Exception

To propose adding a new package to this exception, you should send an email to ubuntu-release@lists.ubuntu.com that requests inclusion for the named package, as well as a justification of why it can be included. For example: 

== Begin Exception Template ==
Subject: Request New OpenStack SRU Exception for Heat

Hello SRU Team,

I'd like to request that Heat be included in the OpenStack SRU Exception list at https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates.

Heat is the orchestration project in OpenStack.

Heat is already included in our regression testing and is validated via Tempest smoke tests.

Thanks,
Me

== End Exception Template ==

Getting Package Source

Depending on the package and the release, there are different ways to download the package source:

OpenStack/StableReleaseUpdates (last edited 2023-04-18 12:06:24 by james-page)