| Table of Contents |
|---|
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 |
|---|
distribution - source for imange creation
docs - read the docs source
feature - features and bundles
...
| Jenkins build results | description | |
|---|---|---|
| distribution | docker images to nexus | Source for image creation |
| docs | readTheDocs | readTheDocs source |
| features | feature bundles to nexus | Feature bundles |
| parent | feature bundles to nexts | Parents depending on ONAP Parents |
| model | Used in the sources | yang model related contributions |
feature containing specific devicemanagers
devicemanager - top level for devicemanager
...
- ru-fh - radio unit - front haule
Artifact ids
Using ONAP Frankfurt
Example with devicemanager xran/ru-fh for top pom file.
...