Top level
Structure of OAM uses the structure of the ONAP base components and the Opendaylight Karaf/OSGi approach.
The following sub structure is used:
| directory | Build results | description | Jenkins jobs |
|---|---|---|---|
| distribution | (C) docker images to nexus | Source for image creation | |
| docs | readTheDocs | readTheDocs source | |
| features | (A) feature bundles to nexus | Feature bundles | 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 nexts | Parents depending on ONAP Parents | |
| model | Used in the sources | yang model related contributions |
A,B,C are three YAML-Definitions in ci-management for OAM.
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>