Compatibility¶
System requirements¶
The table below shows the system requirements of version 8 of the Inmanta Service Orchestrator.
Component |
Required version |
|---|---|
PostgreSQL |
13 |
Python |
3.11 |
RHEL |
[9, 8] |
Note
This information is also available in a machine-consumable format in the compatibility.json file.
Module compatibility ranges¶
We develop and distribute some core modules alongside the product. For these modules, we uphold the same compatibility guarantees as for the product itself. Therefore, some versions of a module may be developed for a specific version of the product (e.g. a breaking change in a module is intended only for the next major iso release).
We achieve this by using a specific module versioning scheme, and we accompany each iso version with a compatibility range for each of these core modules. This compatibility range declares which versions of each module have been developed and tested for this product version. This does not mean that other versions will not work, only that they may not.
For stability reasons, when you depend on these modules, make sure you use the appropriate versions for the iso version you’re using. This can be achieved one of two ways:
Using a specific pip index (or git repos) per ISO version and making sure it only contains the compatible versions of the modules. e.g. the indexes we make available for an iso version only contain compatible module versions.
Using a generic pip index (or git repos) containing module versions for different ISO versions and adding a constraint file for each ISO version in which the compatible module ranges are specified.
The table below shows the most relevant modules. These are the most commonly used ones, and they also happen to be the ones that integrate tightly with the orchestrator (and are therefore the most sensitive to changes in the orchestrator). These are the module versions that are compatible with version 8 of the Inmanta Service Orchestrator:
Module |
Compatible range |
|---|---|
lsm |
Not pinned yet |
std |
Not pinned yet |
Note
The compatible ranges for these modules (and other less commonly used modules) is available in a machine-consumable format in the compatibility.json file.