Versions Compared

Key

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

Table of Contents

Top level

...

Overview

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

  • feature parent for the feature bundles and distribution.
  • docker images for nonrtric-o1-controller
  • feature bundles 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
serverSystem Jira
serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
keyOAM-83
 

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: 

(A) feature bundles to
directoryrepo:pathArtifact groupBuild resultsdescriptionJenkins jobs
oam:distribution/
(C) docker images to nexusSource for image creationci-management/jjb/oam/oam-distribution.yaml
oam:docs/
Documentation → readTheDocsreadTheDocs source
oam:features/org.o-ran-sc.oam.featuresfeature bundles → nexusFeature bundles

ci-management/jjb./oam/oam-features.yaml

oam-features-maven-verify-master-mvn35-openjdk8
oam-features-maven-merge-master
oam-features-maven-stage-master
oam-features-release-merge
oam-features-release-verify

oam:parent/
(B) feature parent bundles to nexts→ nexusParents depending on ONAP ParentsmodelUsed in the sourcesyang model related contributions

A,B,C are three YAML-Definitions in ci-management for OAM.

...

ci-management/jjb/oam/oam-parent.yaml
oam:info.yaml


ci-management/jjb/oam/oam.yaml
scp/oam/modeling:features/org.o-ran-sc.scp.oam.modeling.featuresfeature bundles → nexusyang model generated code
scp/oam/modeling:info.yaml


ci-management/jjb/scp-oam-modeling/scp-oam-modeling.yaml

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.

...