75751a3f89
In doc we say that only N->N+1 is tested, while it's not true for SLURP releases anymore. Change-Id: I85637092368ef14aadc7c734eaaf68ffacfae1f1
33 lines
1.1 KiB
ReStructuredText
33 lines
1.1 KiB
ReStructuredText
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 between releases only for ``source`` deployments. This
|
|
also includes CI testing of upgrade path between SLURP releases.
|
|
|
|
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: :ref:`compatibility-matrix-legacy`.
|
|
|
|
Operating systems with experimental support are marked with ``E`` in the table.
|
|
|
|
.. raw:: html
|
|
:file: os-compatibility-matrix.html
|