diff --git a/doc/source/admintasks/kubernetes/oran-o2-application-b50a0c899e66.rst b/doc/source/admintasks/kubernetes/oran-o2-application-b50a0c899e66.rst index e2716a03d..a1328fb31 100644 --- a/doc/source/admintasks/kubernetes/oran-o2-application-b50a0c899e66.rst +++ b/doc/source/admintasks/kubernetes/oran-o2-application-b50a0c899e66.rst @@ -13,9 +13,17 @@ interface between the O-Cloud (|prod|) and the Service Management & Orchestratio The O2 interfaces enable the management of the O-Cloud (|prod|) infrastructure and the deployment life-cycle management of |O-RAN| cloudified |NFs| that run on -O-Cloud (|prod|). See `O-RAN O2 General Aspects and Principles 2.0 -`__, and `INF O2 -documentation `__. +O-Cloud (|prod|). For more information see: + +- O-RAN O2 complies with the specifications of `INF O2 IMS and DMS Spec Compliance `__. + + .. note:: + This O-RAN specification on O2 |IMS| support for alarm acknowledgment and + clearing was defined in **G** Release. See `Welcome to INF O2 documentation `__. + This feature is supported in |v_r9| version. Therefore, |v_r8| version + follows the older specification which does not have this API definition. + +- `INF O2 Services API `__. The |O-RAN| O2 application is integrated into |prod| as a system application. The |O-RAN| O2 application package is saved in |prod| during system @@ -313,6 +321,12 @@ of O-RAN cloudified |NFs|. See the following API reference for details: - `API O-RAN O2 interface `__ +.. note:: + |O-RAN| O2 interface limitations: + + - In the |prod| |v_r8| version, in the ``GET:/o2ims-infrastructureMonitoring/v1/alarm`` + API resource, alarm clearing events are not recorded. + --------- Uninstall ---------