openstack/openstack-ansible
Code Issues Proposed changes
openstack-ansible/doc/source/admin/upgrades/compatibility-matrix.rst
Dmitriy Rabotyagov ecdac54b9e Split compatability matrix for legacy releases 
With time amount of operating systems in the table become hardly
managable, thus we split table into 2 parts, current one is going
to contain only currently supported releases, while all EM and EOL
are moved to the legacy one. Likely, with time we might want to split
these even more to have EOL and EM as a separate tables, but it's not
done now due to not having significant simplification of tables.

Change-Id: I4365c00de3561bfb4b1ac0b298ae670c1c00db93
2023-04-04 11:58:39 +02:00

1.1 KiB
Raw Blame History

Compatibility Matrix

All of the OpenStack-Ansible releases are compatible with specific sets of operating systems and their versions. Operating Systems have their own lifecycles, however we may drop their support before end of their EOL because of various reasons:

  • OpenStack requires a higher version of a library (ie. libvirt)
  • Python version
  • specific dependencies
  • etc.

However, we do try to provide upgrade releases where we support both new and old Operating System versions, providing deployers the ability to properly upgrade their deployments to the new Operating System release.

In CI we test upgrades from N to N+1 releases and only for source deployments.

Below you will find the support matrix of Operating Systems for OpenStack-Ansible releases.

Note

Compatability matrix for legacy releases of OpenStack-Ansible can be found on this page: compatibility-matrix-legacy.

Operating systems with experimental support are marked with E in the table.