...
- https://jira.o-ran-sc.org/browse/ODUHIGH-247 - Done
- As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
- https://jira.o-ran-sc.org/browse/ODUHIGH-297 - Done
- As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
- https://jira.o-ran-sc.org/browse/ODUHIGH-322 - Done
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
- https://jira.o-ran-sc.org/browse/ODUHIGH-327 - Done
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
- https://jira.o-ran-sc.org/browse/ODUHIGH-328 - WIP
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
- Edit-config implementation for o-ran-sc-du-hello-world YANG (admin state changes), is done.
- Integration with O-DU code for cell down and up scenario in progress
- Integration testing with OAM in progress
- As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
Dependency/Blockers:
- O1 configuration for day-1 shall need to be completed to start with CLA. However basic configuration e.g. cell state/operational state/admin state shall be supported initially. Use admin state as unlocked to validate the RU link failure.
- Server(VM) configuration (H/W and S/W) to mount Radisys CU as a test fixture.
- Unable to use valgrind with Intel libraries. Debugging must be carried out with Alternate methods.
- SIB1 PDSCH reached L1 but cannot be observed in logs. Awaiting response from Intel.
- SSB reached O-RU. awaiting analysis from Viavi.
...