Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

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 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

Jiras are   OAM-83 - Getting issue details... STATUS  and subtasks

Envorinment

  • ONAP Frankfurt: Maven 3.5, Java 8
  • ONAP Guilin: Maven 3.5, Java 8 and Maven 3.6 Java 11

Structure and Jenkins jobs

The following sub structure is used: 

pathBuild resultsdescriptionJenkins jobs
distribution/(C) docker images to nexusSource for image creationci-management/jjb/oam/oam-distribution.yaml
docs/readTheDocsreadTheDocs source
features/(A) feature bundles to 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

parent/(B) feature bundles to nextsParents depending on ONAP Parentsci-management/jjb/oam/oam-parent.yaml
model/Used in the sourcesyang model related contributions
info.yaml

ci-management/jjb/oam/oam.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

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 "features" containing specific devicemanagers

devicemanager -  top level for devicemanager

      - o-ran    - Open RAN standard

          - ru-fh        - device related radio unit - front haule


     - x-ran    - X RAN standard

         - ru-fh        - radio unit - front haule

Artifact ids

Using ONAP Frankfurt

Example with devicemanager xran/ru-fh for top pom file.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>org.onap.ccsdk.parent</groupId>
        <artifactId>odlparent-lite</artifactId>
        <version>1.5.2-SNAPSHOT</version>
        <relativePath/>
    </parent>

    <groupId>org.o-ran-sc.oam.features.devicemanager</groupId>
    <artifactId>devicemanager-oran-ru-fh-top</artifactId>
    <version>0.7.1-SNAPSHOT</version>
    <packaging>pom</packaging>

    <name>o-ran-sc-features :: ${project.artifactId}</name>

    <properties>
        <feature-name>devicemanager-oran-ru-fh</feature-name>
    </properties>

    <modules>
        <module>model</module>
        <module>provider</module>
        <module>feature</module>
        <module>installer</module>
    </modules>

</project>
  • No labels