RackN Provided Bootenv Lifecycle¶

RackN provides a set of bootenvs that are used to provision machines. These bootenvs are used to provide the necessary files to deploy upstream OSes. The lifecycle of these bootenvs are managed by RackN. They are created and maintained as needed.

When an upstream OS version is noted as end of life (EOL), the bootenvs associated with those EOL OSes will be marked as deprecated. Those bootenvs will no longer be tested and support will end for them.

It is at the discretion of RackN how long a deprecated bootenv will remain available in the RackN managed catalog. The general guideline is for previously deprecated bootenvs to remain for at least one minor release cycle of DRP before being removed.

Some of the current upstream lifecycle documents RackN tracks are listed below.

RHEL: https://access.redhat.com/support/policy/updates/errata
CentOS: https://www.centos.org/centos-linux-eol/
Alma: https://wiki.almalinux.org/FAQ.html#how-long-will-almalinux-be-supported
Rocky: https://wiki.rockylinux.org/rocky/version/
Fedora: https://docs.fedoraproject.org/en-US/releases/eol/
Ubuntu: https://ubuntu.com/about/release-cycle
Debian: https://wiki.debian.org/LTS
Oracle Linux: https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf
Photon: https://blogs.vmware.com/vsphere/2023/05/announcing-photon-os-5-0-general-availability.html