CloudArchive

Differences between revisions 1 and 54 (spanning 53 versions)
Revision 1 as of 2012-04-23 14:51:43
Size: 6730
Editor: robbiew
Comment:
Revision 54 as of 2017-09-06 18:14:14
Size: 3201
Editor: corey.bryant
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from ServerTeam/CloudArchive
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 4: Line 6:
Canonical’s Ubuntu Cloud archive allows users the ability to install newer releases of OpenStack on Ubuntu Server 12.04 LTS (and the dependencies) as they become available up through the next Ubuntu LTS release (presumably 14.04). 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 for at least 18 months after they release. Canonical will stop introducing new releases of OpenStack for Ubuntu Server 12.04 LTS into the Ubuntu Cloud archive with the version shipped in the next Ubuntu Server LTS release (presumably 14.04). 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. 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.
Line 6: 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 archive.canonical.com be the home of the Ubuntu Cloud archive. They will enable update paths for each !OpenStack release.
Line 8: Line 10:
 * e.g. Enabling “precise-folsum” in the archive will provide access to all OpenStack Folsum packages built for Ubuntu Server 12.04 LTS (binary and source), any updated dependencies required, and bug/security fixes made after release.  * e.g. Enabling “xenial-pike” in the archive will provide access to all !OpenStack Pike packages built for Ubuntu Server 16.04 LTS (binary and source), any updated dependencies required, and bug/security fixes made after release.
Line 10: Line 12:
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. 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.

=== 14.04 ===
Starting with the Ubuntu Server 14.10 release, newer releases of !OpenStack will be available via Cloud archive for the Ubuntu Server 14.04 LTS release. Juno and Liberty will be supported for 18 months each, and Kilo for 36 months. Mitaka, 16.04's !OpenStack version, is supported in the Cloud Archive for 3 years, i.e. until the end of the Ubuntu 14.04 LTS lifecycle.

=== 16.04 ===
Starting with the Ubuntu Server 16.10 release, newer releases of !OpenStack will be available via Cloud archive for the Ubuntu Server 16.04 LTS release. Newton and Pike will be supported for 18 months each, and Ocata for 36 months. When 18.04's !OpenStack version is released that will be added to the Cloud Archive with support for 3 years, i.e. until the end of the Ubuntu 16.04 LTS lifecycle.

For more details on !OpenStack release end of life see: https://www.ubuntu.com/info/release-end-of-life

== How to Enable and Use ==
Line 13: Line 25:
Q&A === Pike ===
{{{
NOTE: Pike cloud archive only supported on Xenial
Line 15: Line 29:
Why Not Use Stable Release Updates? sudo add-apt-repository cloud-archive:pike
}}}
Line 17: Line 32:
Ubuntu's release policy states that once an Ubuntu release has been published, updates must follow a special procedure called a stable release update, or SRU, and are delivered via the -updates archive. These updates are restricted to a specific set of characteristics: === Ocata ===
{{{
NOTE: Ocata cloud archive only supported on Xenial
Line 19: Line 36:
severe regression bugs
security vulnerabilities (via the -security archive)
bugs causing loss of user data
"safe" application layer bugs
hardware enablement
partner archive updates
Exceptions to the SRU policy are possible. However, for this to occur the Ubuntu Technical Board must approve the exception, which must meet their guidelines:
sudo add-apt-repository cloud-archive:ocata
}}}
Line 27: Line 39:
Updates to new upstream versions of packages must be forced or substantially impelled by changes in the external environment, i.e. changes must be outside anything that could reasonably be encapsulated in a stable release of Ubuntu. Changes internal to the operating system we ship (i.e. the Ubuntu archive), or simple bugs or new features, would not normally qualify.
A new upstream version must be the best way to solve the problem. For example, if a new upstream version includes a small protocol compatibility fix and a large set of user interface changes, then, without any judgement required as to the benefits of the user interface changes, we will normally prefer to backport the protocol compatibility fix to the version currently in Ubuntu.
The upstream developers must be willing to work with Ubuntu. A responsive upstream who understands Ubuntu's requirements and is willing to work within them can make things very much easier for us.
The upstream code must be well-tested (in terms of unit and system tests). It must also be straightforward to run those tests on the actual packages proposed for deployment to Ubuntu users.
Where possible, the package must have minimal interaction with other packages in Ubuntu. Ensuring that there are no regressions in a library package that requires changes in several of its reverse-dependencies, for example, is significantly harder than ensuring that there are no regressions in a package with a straightforward standalone interface that can simply be tested in isolation. We would not normally accept the former, but might consider the latter.
Once approved by the Tech Board, the exception must have a documented update policy, e.g. http://wiki.ubuntu.com/LandscapeUpdates. Based on these guidelines and the core functionality OpenStack serves in Ubuntu Cloud, the Ubuntu Server team did not feel it was in the best interest of their users, nor Ubuntu in general, to pursue an SRU exception.
=== Newton ===
{{{
NOTE: Newton cloud archive only supported on Xenial
Line 34: Line 43:
What about using Ubuntu Backports? sudo add-apt-repository cloud-archive:newton
}}}
Line 36: Line 46:
The Ubuntu Backports process (excludes kernel) provides us a mechanism for releasing package updates for stable releases that provide new features or functionality. Changes were recently made to `apt` in Ubuntu 11.10, whereby it now only installs packages from Backports when they are explicitly requested. Prior to 11.10, `apt` would install everything from Backports once it was enabled, which led to packages being unintentionally upgraded to newer versions. The primary drawbacks with using the Backports archive is that the Ubuntu Security team does not provide updates for the archive, it’s a bit of a hassle to enable per package updates, and Canonical doesn’t traditionally offer support services for the packages hosted there. Furthermore, with each new release of OpenStack, there are other applications that OpenStack depends on that also must be at certain levels. By having more than one version of OpenStack in the same Backports archive, we run a huge risk of having backward compatibility issues with these dependencies.
Line 38: Line 47:
How Will You Ensure Stability and Quality? === Mitaka ===
{{{
NOTE: Mitaka cloud archive only supported on Trusty (Xenial includes Mitaka by default)
Line 40: Line 51:
In order for us to ensure users have a safe and reliable upgrade path, we will establish a QA policy where all new versions and updated dependencies are required to pass a specific set of regression tests with a 100% success rate. In addition: sudo add-apt-repository cloud-archive:mitaka
}}}
Line 42: Line 54:
Unit testing must cover a minimum set of functionality and APIs
System test scenarios must be executed for 24, 48 and 72 hours uninterrupted.
Package testing must cover: initial installation, upgrades from the previous OpenStack release, and upgrades from the previous LTS and non-LTS Ubuntu release.
All test failures must be documented as bugs in Launchpad, with regressions marked Fix Released before the packages are allowed to exit QA.
Test results are posted publicly and announced via a mailing list specifically created for this effort only.
Only upon successfully exiting QA will packages be pushed into the Ubuntu Cloud archive.
=== Kilo ===
{{{
NOTE: Kilo cloud archive only supported on Trusty
Line 49: Line 58:
What Happens With OpenStack Support and Maintenance in 14.04? sudo add-apt-repository cloud-archive:kilo
}}}
Line 51: Line 61:
Good question. The cycle could repeat itself, however at this point Canonical is not making such a commitment. If the rate of innovation and growth of the OpenStack project matures to a point where users become less likely to need the next release for its improved stability and/or quality, and instead just want it for a new feature, then we would likely return to our traditional LTS maintenance and support model. === Then 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:

{{{
ubuntu-bug nova-compute
}}}

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

The Ubuntu Cloud Archive

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.

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.

  • e.g. Enabling “xenial-pike” in the archive will provide access to all OpenStack Pike packages built for Ubuntu Server 16.04 LTS (binary and source), any updated dependencies required, and bug/security fixes made after release.

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.

14.04

Starting with the Ubuntu Server 14.10 release, newer releases of OpenStack will be available via Cloud archive for the Ubuntu Server 14.04 LTS release. Juno and Liberty will be supported for 18 months each, and Kilo for 36 months. Mitaka, 16.04's OpenStack version, is supported in the Cloud Archive for 3 years, i.e. until the end of the Ubuntu 14.04 LTS lifecycle.

16.04

Starting with the Ubuntu Server 16.10 release, newer releases of OpenStack will be available via Cloud archive for the Ubuntu Server 16.04 LTS release. Newton and Pike will be supported for 18 months each, and Ocata for 36 months. When 18.04's OpenStack version is released that will be added to the Cloud Archive with support for 3 years, i.e. until the end of the Ubuntu 16.04 LTS lifecycle.

For more details on OpenStack release end of life see: https://www.ubuntu.com/info/release-end-of-life

How to Enable and Use

Pike

NOTE: Pike cloud archive only supported on Xenial

sudo add-apt-repository cloud-archive:pike

Ocata

NOTE: Ocata cloud archive only supported on Xenial

sudo add-apt-repository cloud-archive:ocata

Newton

NOTE: Newton cloud archive only supported on Xenial

sudo add-apt-repository cloud-archive:newton

Mitaka

NOTE: Mitaka cloud archive only supported on Trusty (Xenial includes Mitaka by default)

sudo add-apt-repository cloud-archive:mitaka

Kilo

NOTE: Kilo cloud archive only supported on Trusty

sudo add-apt-repository cloud-archive:kilo

Then 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:

ubuntu-bug nova-compute

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

OpenStack/CloudArchive (last edited 2019-07-12 14:00:25 by corey.bryant)