CloudArchive

Differences between revisions 29 and 81 (spanning 52 versions)
Revision 29 as of 2014-05-30 15:45:26
Size: 2734
Editor: gaughen
Comment:
Revision 81 as of 2020-07-07 04:37:59
Size: 6185
Editor: petermatulis
Comment: Improvement to Ceph table
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Include(ServerTeam/Header)>>
## page was renamed from ServerTeam/CloudArchive
Line 7: Line 6:
Canonical’s Ubuntu Cloud archive allows users the ability to install newer releases of OpenStack on an Ubuntu Server (starting with 12.04) as they become available up through the next Ubuntu LTS release. Bug processing and patch contributions will follow standard Ubuntu practice and policy where applicable. Canonical commits to maintaining and supporting new OpenStack releases for Ubuntu Server 12.04 LTS in the Ubuntu Cloud archive until at least 3 months after the next LTS is released. For Ubuntu Server 12.04 LTS, Canonical stopped introducing new releases of OpenStack with the version shipped in the Ubuntu Server 14.04 LTS release. They will maintain and support this last updated release of OpenStack in the Ubuntu Cloud archive for 3 years, i.e. until the end of the Ubuntu 12.04 LTS lifecycle. Starting with the Ubuntu Server 14.10 Development release, newer releases of Openstack will be available via Cloud archive for the Ubuntu Server 14.04 LTS release. 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 9: Line 8:
In order to allow for relatively easy upgrades, and still adhere to Ubuntu processes and policy, Canonical elected to have archive.canonical.com be the home of the Ubuntu Cloud archive. They will enable update paths for each OpenStack release. 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 "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.
Line 11: Line 11:
 * e.g. Enabling “precise-folsom” in the archive will provide access to all OpenStack Folsom packages built for Ubuntu Server 12.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 [[OpenStack/VersionTracking | Version Tracking]] page for details.
Line 13: Line 13:
As of now, Canonical has no plans to build or host OpenStack packages for non-LTS releases of Ubuntu Server in the Ubuntu Cloud archive. The chart below explains the options.
{{attachment:plan.png}}
A UCA !OpenStack release can be enabled on exactly one Ubuntu LTS release.
Line 16: Line 15:
''[For information on JuJu and MAAS on Ubuntu LTS, see [[ServerTeam/CloudToolsArchive|Cloud Tools Archive]]]''
== How to Enable and Use ==
For more details on !OpenStack release end of life see: [[https://ubuntu.com/about/release-cycle#ubuntu-openstack-release-cycle | Ubuntu OpenStack release cycle]].
Line 19: Line 17:
=== Folsom === === Reporting bugs ===
Line 21: Line 19:
{{{
sudo add-apt-repository cloud-archive:folsom
}}}
To report bugs against packages from the UCA, please use the `ubuntu-bug` tool.
Line 25: Line 21:
=== Grizzly ===
{{{
sudo add-apt-repository cloud-archive:grizzly
}}}
=== Havana ===
{{{
sudo add-apt-repository cloud-archive:havana
}}}

=== Icehouse ===
{{{
sudo add-apt-repository cloud-archive:icehouse
}}}

Now run:
{{{
sudo apt-get update
}}}
to update your package listings and then proceed to install/upgrade your openstack packages.

== Reporting Bugs ==

To report bugs against packages from the Ubuntu Cloud Archive, please use the 'ubuntu-bug' tool, for example:
For example:
Line 53: Line 27:
This will ensure that bugs are raised against the cloud-archive project on Launchpad. This will ensure that bugs are raised against the [[https://launchpad.net/cloud-archive | 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
 1. 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 [[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 relationship between UCA pocket, Ceph release, Ubuntu release, and Ubuntu release default archive ("distro").

|| '''Ceph release''' || '''Default archive''' || '''UCA pocket''' || '''Ubuntu release''' ||
|| Octopus || yes || - || Focal ||
|| Octopus || - || bionic-ussuri || Bionic ||
|| Nautilus || - || bionic-train || Bionic ||
|| Nautilus || - || bionic-stein || Bionic ||
|| Mimic || - || bionic-rocky || Bionic ||
|| Luminous || yes || - || Bionic ||
|| Luminous || - || xenial-queens || Xenial ||
|| Jewel || yes || - || Xenial ||
|| Jewel || - || trusty-mitaka || Trusty ||
|| Firefly || yes || - || 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 relationship between UCA pocket, Ceph release, Ubuntu release, and Ubuntu release default archive ("distro").

Ceph release

Default archive

UCA pocket

Ubuntu release

Octopus

yes

-

Focal

Octopus

-

bionic-ussuri

Bionic

Nautilus

-

bionic-train

Bionic

Nautilus

-

bionic-stein

Bionic

Mimic

-

bionic-rocky

Bionic

Luminous

yes

-

Bionic

Luminous

-

xenial-queens

Xenial

Jewel

yes

-

Xenial

Jewel

-

trusty-mitaka

Trusty

Firefly

yes

-

Trusty

OpenStack/CloudArchive (last edited 2023-10-12 16:47:30 by corey.bryant)