Diff for "OpenStack/CloudArchive"

CloudArchive

Differences between revisions 94 and 95

Contents

The Ubuntu Cloud Archive
SRU process
Using the UCA
Ceph and the UCA
Reporting a bug

The Ubuntu Cloud Archive

Canonical’s Ubuntu Cloud Archive (UCA) gives users the ability to install recent OpenStack releases on the latest Ubuntu LTS release.

Ubuntu and OpenStack release a new version every six months at approximately the same time. Each Ubuntu release therefore includes a new OpenStack release by default. It is this OpenStack release that is backported to the latest LTS via the UCA. The Ubuntu OpenStack release cycle represents this visually over time.

SRU process

The SRU process for OpenStack and the UCA is used during the development of a new UCA release and when backporting any updated dependencies and bug/security fixes to an existing UCA release. For example, in terms of a new UCA release, Ubuntu Impish ships with OpenStack Xena by default. In this timeframe, the latest LTS is Ubuntu 20.04 (Focal). Xena packages (binary and source) are therefore backported to Focal via the Xena UCA release. In order for this to happen, individual Impish packages are backported according to this staged process:

impish -> xena-staging -> xena-proposed -> xena-updates

When backporting fixes to an existing UCA release the original Ubuntu release must also get the update:

impish-proposed -> xena-staging -> xena-proposed -> impish-updates -> xena-updates

When Impish reaches end-of-life, Xena package updates will be uploaded directly to the Xena UCA (impish stage).

This process can be monitored live with the Ubuntu Cloud Archive Tracker. It includes package versions for each of the above stages and for all UCA releases. The first stage is called Ubuntu and represents the first stage in the above two scenarios.

Using the UCA

The release schedule of OpenStack and Ubuntu are generally synchronised: a new OpenStack release becomes available in the UCA every six months and coincides with each release of Ubuntu. As OpenStack releases are added to the UCA and as releases fall out of support this section will be updated.

A UCA OpenStack release is enabled on a host with the add-apt-repository command (it is recommended to run sudo apt update both before and after).

Ubuntu 20.04 LTS

On 20.04, OpenStack Victoria and OpenStack Xena are supported for 18 months each, and OpenStack Wallaby for 36 months. When 22.04's default OpenStack version is released it will be added to the UCA with support for 3 years (i.e. until the end of the Ubuntu 20.04 LTS lifecycle).

Xena

sudo add-apt-repository cloud-archive:xena

Wallaby

sudo add-apt-repository cloud-archive:wallaby

Victoria

sudo add-apt-repository cloud-archive:victoria

Ubuntu 18.04 LTS

On 18.04, OpenStack Rocky and OpenStack Train are supported for 18 months each, and OpenStack Stein for 36 months. OpenStack Ussuri, 20.04's default OpenStack version, is supported in the UCA for 3 years (i.e. until the end of the Ubuntu 18.04 LTS lifecycle).

Ussuri

sudo add-apt-repository cloud-archive:ussuri

Train

sudo add-apt-repository cloud-archive:train

Stein

sudo add-apt-repository cloud-archive:stein

Ubuntu 16.04 LTS

I On 16.04, OpenStack Newton and OpenStack Pike are supported for 18 months each, and OpenStack Ocata for 36 months. OpenStack Queens, 18.04's default OpenStack version, is supported in the UCA for 3 years (i.e. until the end of the Ubuntu 16.04 LTS lifecycle).

Queens

sudo add-apt-repository cloud-archive:queens

Ubuntu 14.04 LTS

On 14.04, OpenStack Juno and OpenStack Liberty are supported for 18 months each, and OpenStack Kilo for 36 months. OpenStack Mitaka, 16.04's default OpenStack version, is supported in the UCA for 3 years (i.e. until the end of the Ubuntu 14.04 LTS lifecycle).

Mitaka

sudo add-apt-repository cloud-archive:mitaka

Ceph and the UCA

The below table shows the relationship between UCA release, Ceph release, Ubuntu LTS release, and Ubuntu default archive ("distro").

Ceph release	Default archive	UCA release	Ubuntu LTS release
Pacific	-	focal-xena	Focal
Pacific	-	focal-wallaby	Focal
Octopus	yes	-	Focal
Octopus	-	bionic-ussuri	Bionic
Nautilus	-	bionic-train	Bionic
Mimic	-	bionic-stein	Bionic
Mimic	-	bionic-rocky	Bionic
Luminous	yes	-	Bionic
Luminous	-	xenial-queens	Xenial
Jewel	yes	-	Xenial
Jewel	-	trusty-mitaka	Trusty
Firefly	yes	-	Trusty

Reporting a bug

To report bugs against packages from the UCA, please use the ubuntu-bug tool.

For example:

ubuntu-bug nova-compute

This will ensure that bugs are raised against the cloud-archive project on Launchpad.

OpenStack/CloudArchive (last edited 2025-05-21 14:44:58 by gboutry)

-  ⇤ ← Revision 94 as of 2022-02-16 20:49:40 → 
  Size: 6111
  Editor: petermatulis
  Comment: Add focal-xena for the Ceph table
+   ← Revision 95 as of 2022-03-30 19:15:10 → ⇥
  Size: 5872
  Editor: petermatulis
  Comment: Big review
-Deletions are marked like this.
+Additions are marked like this.
 Line 6:
-Canonical’s Ubuntu Cloud Archive (UCA) gives users the ability to install newer releases of !OpenStack on an Ubuntu LTS release (only) as they become available up through to the next Ubuntu LTS release. Bug processing and patch contributions will follow standard Ubuntu practice and policy where applicable.
+Canonical’s [[https://ubuntu-cloud.archive.canonical.com | Ubuntu Cloud Archive (UCA)]] gives users the ability to install recent !OpenStack releases on the latest Ubuntu LTS release.
 Line 8:
-In order to allow for relatively easy upgrades, and still adhere to Ubuntu processes and policy, Canonical elected to have 	
[[http://ubuntu-cloud.archive.canonical.com | ubuntu-cloud.archive.canonical.com]] be the home of the cloud archive. Update paths will exist for each !OpenStack release. For example, enabling "cloud-archive:xena" will provide access to all !OpenStack Xena packages built for Ubuntu 20.04 LTS (binary and source), any updated dependencies required, and bug/security fixes published after release.
+[[https://wiki.ubuntu.com/Releases | Ubuntu]] and [[https://releases.openstack.org/ | OpenStack]] release a new version every six months at approximately the same time. Each Ubuntu release therefore includes a new !OpenStack release by default. It is this !OpenStack release that is backported to the latest LTS via the UCA. The [[https://ubuntu.com/about/release-cycle#openstack-release-cycle | Ubuntu OpenStack release cycle]] represents this visually over time.
-Line 11:
+Line 10:
-Packages go through various stages as they make their way towards a publicly available UCA release. See the [[OpenStack/VersionTracking | Version Tracking]] page for details.
+== SRU process ==
-Line 13:
+Line 12:
-Any given UCA !OpenStack release can be enabled on exactly one Ubuntu LTS release.
+The [[OpenStack/StableReleaseUpdates | SRU process for OpenStack and the UCA]] is used during the development of a new UCA release and when backporting any updated dependencies and bug/security fixes to an existing UCA release.
For example, in terms of a new UCA release, Ubuntu Impish ships with !OpenStack Xena by default. In this timeframe, the latest LTS is Ubuntu 20.04 (Focal). Xena packages (binary and source) are therefore backported to Focal via the Xena UCA release. In order for this to happen, individual Impish packages are backported according to this staged process:
 Line 15:
-For more details on !OpenStack release end of life see: [[https://ubuntu.com/about/release-cycle#openstack-release-cycle | Ubuntu OpenStack release cycle]].
+'''impish -> xena-staging -> xena-proposed -> xena-updates'''
 Line 17:
-=== Reporting bugs ===
+When backporting fixes to an existing UCA release the original Ubuntu release must also get the update:
 Line 19:
-To report bugs against packages from the UCA, please use the `ubuntu-bug` tool.
+'''impish-proposed -> xena-staging -> xena-proposed -> impish-updates -> xena-updates'''
 Line 21:
-For example:
+When Impish reaches end-of-life, Xena package updates will be uploaded directly to the Xena UCA ('''impish''' stage).
 Line 23:
-{{{
ubuntu-bug nova-compute
}}}

This will ensure that bugs are raised against the [[https://launchpad.net/cloud-archive | cloud-archive]] project on Launchpad.
+This process can be monitored live with the [[https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/index.html | Ubuntu Cloud Archive Tracker]]. It includes package versions for each of the above stages and for all UCA releases. The first stage is called '''Ubuntu''' and represents the first stage in the above two scenarios.
-Line 33:
+Line 29:
-A UCA !OpenStack release is enabled on a host with the `add-apt-repository` command.

'''Important''': It is good practice to run `sudo apt update` both before and after the `add-apt-repository` command.
+A UCA !OpenStack release is enabled on a host with the `add-apt-repository` command (it is recommended to run `sudo apt update` both before and after).
-Line 40:
+Line 34:
-Line 83:
+Line 76:
+I
-Line 104:
+Line 97:
-The below table shows the relationship between UCA release, Ceph release, Ubuntu release, and Ubuntu default archive ("distro").
+The below table shows the relationship between UCA release, Ceph release, Ubuntu LTS release, and Ubuntu default archive ("distro").
-Line 106:
+Line 99:
-|| '''Ceph release''' || '''Default archive''' || '''UCA release'''    || '''Ubuntu release''' ||
+|| '''Ceph release''' || '''Default archive''' || '''UCA release'''    || '''Ubuntu LTS release''' ||
-Line 120:
+Line 113:
+== Reporting a bug ==
-Line 121:
+Line 115:
-== Package Back-Porting Policy ==
+To report bugs against packages from the UCA, please use the `ubuntu-bug` tool.
-Line 123:
+Line 117:
-The packages in the cloud archive will follow a policy similar to Ubuntu release back-porting policy. For example, Openstack Train originated in Eoan and is back-ported to the Train cloud archive, and Openstack Queens originated in Bionic and is back-ported to the Queens cloud archive.
+For example:
-Line 125:
+Line 119:
-You may also refer to [[http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/|these tables]] to see what the package version per Openstack release in the cloud archive. Here is an practical case of the qemu package. Openstack train originated in Eoan, and its qemu is 1.4.0-based. The default qemu version of Bionic is 1.2.0-based. Thus 1.4.0 is back-ported to the Bionic Train cloud archive. By using this Bionic Train cloud archive with your Ubuntu Bionic release, the original 1.2.0-based qemu in your Ubuntu Bionic system will be replaced/upgraded to 1.4.0-based qemu.
+{{{
ubuntu-bug nova-compute
}}}

This will ensure that bugs are raised against the [[https://launchpad.net/cloud-archive | cloud-archive]] project on Launchpad.

Ubuntu Wiki