Versions Compared

Old Version 37

changes.mady.by.user user-165cf

Saved on

compared with

New Version Current

changes.mady.by.user user-30c9d

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Updated: 17 Nov 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities



Updated: 20 Oct 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities


Updated:  15th Sept 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities

Updated:  7th July 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - Done
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - Done
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - Done
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release (Irrespective of FDD or TDD stack)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - Done
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction is completed
      • Code changes for Config update over F1 interface is completed
      • O1 Integration for O-DU  for CLA is completed ( Cell stop and Cell restart)
      • Blocker : code segmentation is observed, analysis is going on (code optimization is required to be scoped in E release)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - Done
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters
      • Further debug sessions needed to close the ongoing issues.
      • There is no breakthrough even after several debug sessions with O-DU Low
      • SIB1 detection at L1 is successful. PHY.XML is updated with removing the hardware accelerator (<dpdkBasebandFecMode> from 1 to 0 to force the SW encoder)
      • For the CLA usecase, Cell stop request is received from O-DU high to low but O-DU low sends stop indication multiple times. This issue is fixed in L1 later binary 20.08. This binary update will happen in D-maintenance phase. 
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - Done
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM configured as per H/W and S/W requirements of Radisys CU
      • The Network interfaces and CentOS version needs to be revisited for the CU machine. This is achieved with limited OSC lab setup.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - Done
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.
      • Debug session is planned on 23rd June to achieve SSB and SIB1 transmission till UE simulator and then follow with RACH procedure.
      • Latest issue: the eCPRI packets differentiation between control plane and user plane through vlan id is supported by Intel, however O-RU support the packet differentiation based on eCPRI packet type. hence the fronthaul transmission validation is blocked.
      • Intel shall update the L1 package supporting C/U plane differentiation using eCPRI packet type in the D-release maintainance phase.

Updates from HCL:

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.
  • Intel/Viavi to confirm successful decoding of SSB/SIB1 at UE sim (TM500).


Updated:  30th June 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - Done
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - Done
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - Done
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release (Irrespective of FDD or TDD stack)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - Done
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction is completed
      • Code changes for Config update over F1 interface is completed
      • O1 Integration for O-DU  for CLA is completed ( Cell stop and Cell restart)
      • Blocker : code segmentation is observed, analysis is going on (code optimization is required to be scoped in E release)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters
      • Further debug sessions needed to close the ongoing issues.
      • There is no breakthrough even after several debug sessions with O-DU Low
      • SIB1 detection at L1 is successful. PHY.XML is updated with removing the hardware accelerator (<dpdkBasebandFecMode> from 1 to 0 to force the SW encoder)
      • For the CLA usecase, Cell stop request is received from O-DU high to low but O-DU low sends stop indication multiple times. This issue is fixed in L1 later binary 20.08. This binary update will happen in D-maintenance phase. 
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM configured as per H/W and S/W requirements of Radisys CU
      • The Network interfaces and CentOS version needs to be revisited for the CU machine.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.
      • Debug session is planned on 23rd June to achieve SSB and SIB1 transmission till UE simulator and then follow with RACH procedure.
      • Latest issue: the eCPRI packets differentiation between control plane and user plane through vlan id is supported by Intel, howver O-RU support the packet differentiation based on eCPRI packet type. hence the fronthaul transmission validation is blocked.

Updates from HCL:

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.
  • Viavi to confirm successful decoding of SSB/SIB1 at UE sim (TM500).



Updated:  23rd June 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - Done
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - Done
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - Done
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release (Irrespective of FDD or TDD stack)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - Done
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction is completed
      • Code changes for Config update over F1 interface is completed
      • O1 Integration for O-DU  for CLA is completed ( Cell stop and Cell restart)
      • Blocker : code segmentation is observed, analysis is going on (code optimization is required to be scoped in E release)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters
      • Further debug sessions needed to close the ongoing issues.
      • There is no breakthrough even after several debug sessions with O-DU Low
      • SIB1 detection at L1 is successful. PHY.XML is updated with removing the hardware accelerator (<dpdkBasebandFecMode> from 1 to 0 to force the SW encoder)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM configured as per H/W and S/W requirements of Radisys CU
      • The Network interfaces and CentOS version needs to be revisited for the CU machine.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.
      • Debug session is planned on 23rd June to achieve SSB and SIB1 transmission till UE simulator and then follow with RACH procedure.

Updates from HCL:

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.
  • Viavi to confirm successful decoding of SSB/SIB1 at UE sim (TM500).


Updated:  16th June 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction is completed
      • Code changes for Config update over F1 interface is completed
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters
      • Further debug sessions needed to close the ongoing issues.
      • There is no breakthrough even after several debug sessions with O-DU Low
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM configured as per H/W and S/W requirements of Radisys CU
      • The Network interfaces and CentOS version needs to be revisited for the CU machine.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

Updates from HCL:

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 is detected at L1 but cannot be processed at L1.  Debug sessions to be continued to address this. This is blocker to acheieve radio mode integration.
  • Viavi to confirm successful decoding of SSB at UE sim (TM500).


Updated:  9th June 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction under review
      • Code changes for Config update over F1 interface is completed
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters
      • Further debug sessions needed to close the ongoing issues.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM configured as per H/W and S/W requirements of Radisys CU
      • The Network interfaces and CentOS version needs to be revisited for the CU machine.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

Updates from HCL:

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 is detected at L1 but cannot be processed at L1.  Debug sessions to be continued to address this.
  • Viavi to confirm successful decoding of SSB at UE sim (TM500).

Updated:  2nd June 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • Awaiting inputs from Intel
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM to be configured as per H/W and S/W requirements of Radisys CU
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

Updates from HCL:

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.
  • Viavi to confirm successful decoding of SSB at UE sim (TM500).


Updated:  26th May 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
      • Code changes for UE registration flow in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
      • Code changes for UE registration flow in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
      • Code changes for UE registration flow in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Discussions on the O-DU PNF Registration and Activation process is ongoing
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified.
      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • Awaiting inputs from Intel
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM to be configured as per H/W and S/W requirements of Radisys CU
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Awaiting input from Viavi

Updates from HCL:

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.


Updated:  19th May 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • 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-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Discussions on the O-DU PNF Registration and Activation process is ongoing
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified.
      • UE delete functionality complete
      • Cell delete functionality complete
      • Code changes for CU Interaction under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • Awaiting inputs from Intel
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM to be configured as per H/W and S/Wrequirements of Radisys CU
  • https://jira.o-ran-sc.org/browse/ODUHIGH-327 - In review
    • 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-269 - WIP
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Awaiting input from Viavi
  • 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

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.


Updated:  12th May 2021

JIRA: Epics Status below:

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 allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • 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.

Updated:  28th April 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed.
      • RACH allocation in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed.
      • RACH allocation in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB and SIB1 completed.
      • RACH allocation in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Discussions on the O-DU PNF Registration and Activation process is ongoing
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified.
      • UE delete functionality complete
      • Cell delete functionality under review
      • Code changes for CU Interaction under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission w,r.t error observed at O-DU Low
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • Awaiting server allocation
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - TODO
    • As an O-DU L2 developer, I want to support End to End testing scenarios

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 allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • Unable to use valgrind with Intel libraries. Debugging must be carried out with Alternate methods.


Updated:  21st April 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Code changes and testing completed for SSB.
      • Resource allocation for SIB1 under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Code changes and testing completed for SSB.
      • Resource allocation for SIB1 under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Code changes and testing completed for SSB.
      • Resource allocation for SIB1 under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Discussions on the O-DU PNF Registration and Activation process is ongoing
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified.
      • UE delete functionality under review
      • Cell delete functionality under review
      • Code changes for CU Interaction in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission w,r.t symbol allocation/overlapping
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • Awaiting server allocation
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - TODO
    • As an O-DU L2 developer, I want to support End to End testing scenarios

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 allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • Unable to use valgrind with Intel libraries. Debugging issue with seg fault using Brute Force method.

Updated:  14th April 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Code changes and testing completed for SSB.
      • Resource allocation for SIB1 under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Code changes and testing completed for SSB.
      • Resource allocation for SIB1 under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Code changes and testing completed for SSB.
      • Resource allocation for SIB1 under review
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Discussions on the O-DU PNF Registration and Activation process is ongoing
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarifed.
      • UE delete functionality under review
      • Cell delete functionality under review
      • Code changes for CU Interaction in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • Awaiting server allocation
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - TODO
    • As an O-DU L2 developer, I want to support End to End testing scenarios

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.
  • Server allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • Unable to use valgrind with Intel libraries. Debugging issue with seg fault using Brute Force method.

Updated:  7th April 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.
  • Server allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • Unable to use valgrind with Intel libraries. Debugging issue with seg fault using Brute Force method.


Updated:  31st March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.
  • Server allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 


Updated:  24th March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.
  • SSB integration testing with O-DU Low in Radio mode. Awaiting debug session with Intel.


Updated:  17th March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.


Updated:  10th March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.

Updated:  03 March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.

Updated:  24 February 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.

Updated:  17 February 2021

JIRA: Epics Status below:


Updated: 16 December 2020

Documentation and release related activities for Cherry release have been completed

...