This knowledge base has moved to the documentation site. Please visit the knowledge base here for the most up to date content. This site is no longer maintained.

RETIRED: Cumulus Linux 1.5.z - 2.5.5 Support Lifecycle

Follow

PRODUCT NOT SUPPORTED

Cumulus Linux release versions 1.5.z to 2.5.5 are no longer supported by Cumulus Networks.

This article outlines the release version numbering structure, and support policies, for Cumulus Linux, from Cumulus Linux versions 1.5.z - 2.5.5. For the policy regarding Cumulus Linux 2.5 ESR and Cumulus Linux 3.0 and later, read this article.

{{table_of_contents}}

Environment

  • Cumulus Linux 1.5.z - 2.5.5

Release Schedule

Cumulus Linux will be released on a time-based schedule:

  • Cumulus Networks will launch one release every quarter, either a major or minor release.
  • Maintenance releases can occur at any time as needed.
  • A feature release cycle will always lead to a Long Term Support (LTS) release at some point in time.
  • One quarterly release per year will reach the status of LTS.
  • There are three types of releases: major, minor and maintenance; the version number indicates the type of release. Version numbering for each release type is defined below.

lifecycle.png

Version Numbering

The Cumulus Linux installation file name includes the version numbering and is of the form: CumulusLinux_X.Y.Z_TAG, where:

  • X is the major release version number.
  • Y is the minor release version number
  • Z is the maintenance release version number
  • TAG = RC (Release Candidate) or POC (Proof of Concept); the tag is dropped for the general availability (GA) release.

This number corresponds to the release version of Cumulus Linux, so CumulusLinux_1.5.2_RC would be the release candidate for the Cumulus Linux 1.5.2 maintenance release.

Release Cycle Definitions

Each type of release is defined as follows:

  • Each major release cycle will be updated quarterly (or more frequently for security updates) with minor or maintenance releases. All of the releases in a cycle will be supported until the cycle enters LTS. From that point forward, Cumulus Networks will support only the LTS release.
  • A maintenance release supersedes a previous minor or maintenance release. Customers are not required to upgrade until the LTS release is reached.
  • An LTS release (one of the quarterly releases) will be supported 3 years from the time of the LTS release.
  • Support is provided from the date of release. For instance, if the LTS release is reached in October 2013, and the release is 1.5.2, 1.5.2 will be supported until October 2016.

Definition of Supported

For either a standard or LTS release, the following is provided during the support period:

  • Qualified maintenance releases: critical and important security patches and package updates.
  • Urgent and selected high priority bug fixes released as they become available.
  • Other maintenance releases may be delivered as appropriate.
  • Subsequent updates may be released as appropriate as minor or maintenance releases. A subsequent release could be due to any of the following:
    • Any medium and higher priority issues.
    • If available, new or improved hardware enablement and select enhanced software functionality provided at the discretion of Cumulus Networks.
    • Hardware enablement that does not require substantial software changes may even be provided independent from subsequent updates at Cumulus Networks' discretion.
    • All available and qualified maintenance releases.
    • Subsequent updates are cumulative and include the contents of previously released updates.
    • Updated images/packages in the distribution.

New major features are not included in support releases since they are intended for upcoming major releases.

Upgrade Process

  • Since the LTS release subsumes all previous maintenance releases, all customers will be required to upgrade to the LTS version in that release cycle. 
  • Customers will use the apt-get mechanism to upgrade from one maintenance release to another in the same minor release. For example, to upgrade from 1.5.2 to 1.5.3, the customer is required to use apt-get update.
  • For customers deploying using Puppet/Chef, Cumulus Networks will provide a full installation image for each maintenance release, which will be provided as is. Thus, customers can choose to use apt-get update or they can do a full binary install.
  • The major and LTS releases are full packages that have been tested as a single entity. The LTS release is complete with patches so there will be a full upgrade package available.
  • If a customer upgrades a third-party software package in an LTS release, this will invalidate Cumulus Linux support. For example, do not upgrade the version of Quagga that is included in the LTS release.

Comments

This support portal has moved

Cumulus Networks is now part of the NVIDIA Networking Business Unit! The NVIDIA Cumulus Global Support Services (GSS) team has merged its operations with the NVIDIA Mellanox support services team.

You can access NVIDIA Cumulus support content from the Mellanox support portal.

You open and update new cases on the Mellanox support portal. Any previous cases that have been closed have been migrated to the Mellanox support portal.

Cases that are still open on the Cumulus portal will continue to be managed on the Cumulus portal. Once these cases close, they will be moved to the Mellanox support portal.

Powered by Zendesk