| Table of Contents |
|---|
Overview
Structure of OAM uses the structure of the ONAP base components and the Opendaylight Karaf/OSGi approach.
In this project all parts for a Repositories managed by OAM project
- oam - main repo
- oam-nf-oam-adopter - Network Function Adopter for model and protocol conversion according to O-RAN OAM specifications.
- oam-tr069-adapter - Converts BBF-TR069 oam SOAP interface into NETCONF/YANG
- scp/oam/modeling - yang data models and yang-tools generated classes
Repositories are used to provide osgi bundles and docker images for nonrtric-o1-controller are within one repository. The jenkins results of this repository are
- feature parent for the feature bundles and distribution.
- docker images for nonrtric-o1-controller
- feature bundles and
- feature parent for the controller.
- for specific devicemanagers
- model bundles with classes for generated classes from yanf files, representing specific standards
Setup tasks/sub-tasks of jenkins are bundled via
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Target environments
- ONAP Honolulu: Maven 3.8, Java 11
- ONAP Istanbul: Maven 3.8 Java 11
Structure and Jenkins jobs
The following sub structure is used:
| repo:path | Artifact group | Build results | description | Jenkins jobs | |||
|---|---|---|---|---|---|---|---|
| oam:distribution/ | (C) docker images to → nexus | Source for image creation | ci-management/jjb/oam/oam-distribution.yaml | ||||
| oam:docs/ | Documentation → readTheDocs | readTheDocs source | |||||
| oam:features/ | (A) org.o-ran-sc.oam.features | feature bundles to → nexus | Feature bundles | ci-management/jjb./oam/oam-features.yaml oam-features-maven-verify-master-mvn35-openjdk8 | |||
| oam:parent/ | (B) feature parent bundles to nexts→ nexus | Parents depending on ONAP Parents | ci-management/jjb/oam/oam-parent.yaml | model/ | Used in the sources | yang model related contributions | |
| oam:info.yaml | ci-management/jjb/oam/oam.yaml | ||||||
| scp/oam/modeling:features/ | org.o-ran-sc.scp.oam.modeling.features | feature bundles → nexus | yang model generated code | ||||
| scp/oam/modeling:info.yaml | ci-management/jjb/scp-oam-modeling/scp-oam-modeling.yaml |
A,B,C are three YAML-Definitions in ci-management for OAM.
Artifacts groupId "org.o-ran-sc.oam.features".
List of all artifacts as provided under this group in repository layout
| Code Block |
|---|
org.o-ran-sc.oam.features
├── devicemanager
│ ├── devicemanager-oran-ru-fh-feature
│ ├── devicemanager-oran-ru-fh-installer
│ ├── devicemanager-oran-ru-fh-model
│ ├── devicemanager-oran-ru-fh-provider
│ ├── devicemanager-oran-ru-fh-top
│ ├── devicemanager-xran-ru-fh-feature
│ ├── devicemanager-xran-ru-fh-installer
│ ├── devicemanager-xran-ru-fh-model
│ ├── devicemanager-xran-ru-fh-provider
│ └── devicemanager-xran-ru-fh-top
├── features-top
│ ├── 0.7.1-SNAPSHOT
│ └── maven-metadata-local.xml
└── parent
├── binding-parent
├── odlparent-lite
├── parent-top
└── single-feature-parent |
Directory oam:features containing specific devicemanagers
devicemanager - top level for devicemanager
...
- ru-fh - radio unit - front haule
- tr069 - TR069 standard
Artifact ids
Using ONAP Frankfurt
Example with devicemanager xran/ru-fh for top pom file.
...