CloudArchive

Differences between revisions 79 and 80
Revision 79 as of 2020-07-06 19:59:49
Size: 4111
Editor: petermatulis
Comment: Page review
Revision 80 as of 2020-07-06 22:17:48
Size: 6072
Editor: petermatulis
Comment: Ceph and Juju additions
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
Canonical’s Ubuntu Cloud Archive (UCA) gives users the ability to install newer releases of !OpenStack on an Ubuntu LTS release 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. There are no plans to make available !OpenStack packages for non-LTS releases in the cloud archive. 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.
Line 12: Line 12:

A UCA !OpenStack release can be enabled on exactly one Ubuntu LTS release.
Line 27: Line 29:
== Enabling the Cloud Archive == == Using the UCA ==
Line 29: Line 31:
In terms of timing, the release schedule of !OpenStack and Ubuntu are generally synchronised. An !OpenStack release is therefore available (in the UCA) to an LTS release six months after its own release, coinciding with the next release of Ubuntu. As !OpenStack releases become available in the UCA and as releases fall out of support this section will be updated. The release schedule of !OpenStack and Ubuntu are generally synchronised. An !OpenStack release is therefore available (in the UCA) to an LTS release six months after its own release, coinciding with the next release of Ubuntu. As !OpenStack releases become available in the UCA and as releases fall out of support this section will be updated.
Line 31: Line 33:
A UCA !OpenStack release can be enabled on exactly one Ubuntu LTS release and is done with the `add-apt-repository` command. The UCA can be leveraged in two ways. With:

 1. Traditional tooling
 1. Juju !OpenStack charms

=== Traditional tooling ===

With traditional tooling, a UCA !OpenStack release is enabled on a host with the `add-apt-repository` command.
Line 35: Line 44:
=== 20.04 === ==== 20.04 ====
Line 39: Line 48:
=== 18.04 === ==== 18.04 ====
Line 43: Line 52:
==== Ussuri ==== ===== Ussuri =====
Line 49: Line 58:
==== Train ==== ===== Train =====
Line 55: Line 64:
==== Stein ==== ===== Stein =====
Line 61: Line 70:
==== Rocky ==== ===== Rocky =====
Line 67: Line 76:
=== 16.04 === ==== 16.04 ====
Line 71: Line 80:
==== Queens ==== ===== Queens =====
Line 77: Line 86:
=== 14.04 === ==== 14.04 ====
Line 81: Line 90:
==== Mitaka ==== ===== Mitaka =====
Line 86: Line 95:

=== Juju OpenStack charms ===

The UCA is made available to [[https://docs.openstack.org/charm-guide/ | Charmed OpenStack]] through a configuration option passed to a charm at deployment time.

There are two configuration options available, depending on whether the software is an actual !OpenStack project or whether it is considered supportive of !OpenStack:

 * `openstack-origin`
 * `source`

The special value of 'distro' given to either of these options designates the normal package archives available to a Juju machine's Ubuntu release.

Examples:

 1. Deploy Keystone from !OpenStack Train on Bionic

 {{{
 juju deploy --config openstack-origin=cloud:bionic-train keystone
 }}}

 1. Deploy a Ceph OSD that is compatible with Charmed !OpenStack Train on Bionic

 {{{
 juju deploy --config source=cloud:bionic-train ceph-osd
 }}}

Although this information is passed to an individual charm, the underlying host is nonetheless configured system-wide. The end result is equivalent to that of the traditional tooling method.

== Ceph and the UCA ==

The below table shows the mapping of UCA pocket to Ceph release, and includes what will result from a Ubuntu release's default archive ("distro").

|| '''Ceph release''' || '''Default archive''' || '''UCA pocket''' ||
|| Octopus || Focal || - ||
|| Octopus || - || bionic-ussuri ||
|| Nautilus || - || bionic-train ||
|| Nautilus || - || bionic-stein ||
|| Mimic || - || bionic-rocky ||
|| Luminous || Bionic || - ||
|| Luminous || - || xenial-queens ||
|| Jewel || Xenial || - ||
|| Jewel || - || trusty-mitaka ||
|| Firefly || Trusty || - ||

The Ubuntu Cloud Archive

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.

In order to allow for relatively easy upgrades, and still adhere to Ubuntu processes and policy, Canonical elected to have ubuntu-cloud.archive.canonical.com be the home of the cloud archive. Update paths will exist for each OpenStack release. For example, enabling "bionic-ussuri" will provide access to all OpenStack Ussuri packages built for Ubuntu 18.04 LTS (binary and source), any updated dependencies required, and bug/security fixes made after release.

Packages go through various stages as they make their way towards a publicly available UCA pocket. See the Version Tracking page for details.

A UCA OpenStack release can be enabled on exactly one Ubuntu LTS release.

For more details on OpenStack release end of life see: Ubuntu OpenStack release cycle.

Reporting bugs

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.

Using the UCA

The release schedule of OpenStack and Ubuntu are generally synchronised. An OpenStack release is therefore available (in the UCA) to an LTS release six months after its own release, coinciding with the next release of Ubuntu. As OpenStack releases become available in the UCA and as releases fall out of support this section will be updated.

The UCA can be leveraged in two ways. With:

  1. Traditional tooling
  2. Juju OpenStack charms

Traditional tooling

With traditional tooling, 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.

20.04

On Ubuntu 20.04 LTS, OpenStack Victoria and OpenStack X are supported for 18 months each, and OpenStack W 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).

18.04

On Ubuntu 18.04 LTS, OpenStack Rocky and OpenStack Train are supported for 18 months each, and OpenStack Stein for 36 months. When 20.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 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

Rocky

sudo add-apt-repository cloud-archive:rocky

16.04

On Ubuntu 16.04 LTS, 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

14.04

On Ubuntu 14.04 LTS, 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

Juju OpenStack charms

The UCA is made available to Charmed OpenStack through a configuration option passed to a charm at deployment time.

There are two configuration options available, depending on whether the software is an actual OpenStack project or whether it is considered supportive of OpenStack:

  • openstack-origin

  • source

The special value of 'distro' given to either of these options designates the normal package archives available to a Juju machine's Ubuntu release.

Examples:

  1. Deploy Keystone from OpenStack Train on Bionic

     juju deploy --config openstack-origin=cloud:bionic-train keystone
  2. Deploy a Ceph OSD that is compatible with Charmed OpenStack Train on Bionic

     juju deploy --config source=cloud:bionic-train ceph-osd

Although this information is passed to an individual charm, the underlying host is nonetheless configured system-wide. The end result is equivalent to that of the traditional tooling method.

Ceph and the UCA

The below table shows the mapping of UCA pocket to Ceph release, and includes what will result from a Ubuntu release's default archive ("distro").

Ceph release

Default archive

UCA pocket

Octopus

Focal

-

Octopus

-

bionic-ussuri

Nautilus

-

bionic-train

Nautilus

-

bionic-stein

Mimic

-

bionic-rocky

Luminous

Bionic

-

Luminous

-

xenial-queens

Jewel

Xenial

-

Jewel

-

trusty-mitaka

Firefly

Trusty

-

OpenStack/CloudArchive (last edited 2020-08-11 04:46:33 by taihsiangho)