Date: Fri, 29 Mar 2024 06:48:55 +0000 (UTC)
Message-ID: <1942468571.16089.1711694935701@aws-us-west-2-oran-confluence-1.web.codeaurora.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_16088_375003954.1711694935700"
------=_Part_16088_375003954.1711694935700
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Done
- Moving to next ODL version Sodium =E2=86=92 module testing ongoing=
- Update to JAVA 11 =E2=86=92 module testing ongoing
Activities
- Analysis of the "Application LCM" use case
- Contributions by Samsung
- comparison of App deployment by<=
/span>
- ONAP SO/CDS CSAR (Cloud Service=
ARchive) packages
- ONAP DCAE =C2=B5Services =
span>
- Current view
- Enhancements of the DCAE ap=
p deployment seems fitting best
- CSAR could be used as O2 pre-spe=
c deployment option for =
O-RAN VNF/CNF (near-rt-ric, O-CU-UP, O-CU-CP, O-DU)
- Open
- Updates of O1-TR069-Adapter
- Modularization of the currently =
"monolithic" YANG module.
- Preparation of supporting gRPC f=
or Transport (WG9)
Challenges
- No feedback from OTF team
- No feedback from RIC Dashboard team
- OAM project uses and contributes directly to
- ONAP CCSDK, SDNC project based on OpenDaylight project=
, based on Apache Karaf
- O1 NetConf termination of the SMO according to O-RAN-OAM Architecture a=
nd OAM interface specification and according to O-RAN FrontHaul m-Plane (WG=
4)
- ONAP DCAE VES colletctor
- O1 VES termination of the SMO according to O-RAN-OAM Architecture =
and OAM interface specification
- ONAP DCAE File Collector
- O1 FTPeS termination of the SMO according to O-RAN-OAM Architectur=
e and OAM interface specification
- ONAP DMaaP as communication channel between the different O1 terminatio=
n functions based on Apache Kafka
- ONAP LOG
- Centralized logging service based on ElasticStack (ElasticSearc=
h, Logstash und Kibana)
- ONAP AAF
- ONAP OOM
- Deployment of the solution based on Docker, Kubernetes and Helm
- ElasticSearch as local Cache/database.
- Alpine Linux as operating system<=
/span>
- JAVA, No=
de, TypeScript, Python, =
OpenStack, Eclipse, vsCode.=
Papyrus, MaterialUI and many, many more for Developm=
ent
A few examples from ONAP wiki:
o REQ-327: Standards Defined Notifications over VES
=EF=82=A7 Introducing the capability to receive, validate and process stand=
ards defined notifications encapsulated in VES events in ONAP.
=EF=82=A7 Components impacted: (DCAE; Modeling SC; VNF Req)
o REQ-352: Enhancing the A1 adapter/interface capabilities in ONA=
P to manage A1 Policies
=EF=82=A7 Support multiple A1 targets in the RAN and multi-version A1 inter=
face for different A1 targets, introduce secure TLS communication.
=EF=82=A7 Components impacted: (CCSDK/CDS; SDN-C (SDN-R); Modeling SC)
o REQ-345: Optimization and SON functions for 5G RAN. Self-optimi=
zation, Self-Healing, Self-configuration
=EF=82=A7 Components impacted: (CCSDK/CDS; DCAE; OOF; Policy; SDN-C (SDN-R)=
)
o REQ-318: PNF Plug and Play allows for ONAP to support PNF regis=
tration and discovery
=EF=82=A7 Components impacted: (SO; Modeling SC)
o REQ-324: The xNF Software Upgrade use case allows for ONAP to u=
pdate the xNF software
=EF=82=A7 Components impacted: (AAI; SDC; SO; VID)
o REQ-381: Bulk PM data collection control provides a dynamic and=
efficient way to configure performance measurement collection
=EF=82=A7 Components impacted: (DCAE)
------=_Part_16088_375003954.1711694935700--