Integrations¶
OpenOP reaches infrastructure through TF-SDK adapters running inside SRM. Configure each backend as an explicit control path in the unified bootstrap, then bind the relevant zone capabilities to it. Control path, capability and the other platform terms are defined in the OOP Glossary.
Release 2 backends¶
Implementation support and platform test coverage are separate. The Release 2 support matrix records operations, accepted fields, unsupported inputs and verification limits. A pipeline's generated feature report records what actually ran with its specific images and provider configuration.
| Adapter type | Executable SDK capabilities | Platform lab coverage | Guide |
|---|---|---|---|
kubernetes |
Workload lifecycle, with container and helm runtimes |
Container lifecycle and the bundled test chart | Kubernetes |
oai |
QoD sessions, location queries, Traffic Influence | EURECOM NEF/CoreSim with one simulated IPv4 device | EURECOM NEF |
open5gs |
QoD sessions and location queries | No backend qualification in this lab | SDK source, limits |
open5gcore |
QoD sessions | No backend qualification in this lab | SDK source, limits |
i2edge, i2cat_ric |
No advertised capabilities in Release 2; retained legacy clients | Not tested | Support matrix |
aeros, juniper_ric |
No registered contract adapter in Release 2 | Not tested | Support matrix |
Choose a guide¶
- Connect a local or remote Kubernetes cluster, including credentials, namespace permissions and application endpoints.
- Set up EURECOM NEF and CoreSim, then use the network APIs.
- Write an adapter for another backend using the Release 2 contract.
- Run the platform E2E lab and inspect its report before claiming a combination is tested.