1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
Building DCAE
=============
Description
-----------
DCAE has multiple code repos and these repos are in several different languages. All DCAE projects are built in similar fashion, following Maven framework as Maven projects. Although many DCAE projects are not written in Java, adopting the Maven framework does help including DCAE projects in the overall ONAP building methodology and CICD process.
All DCAE projects use ONAP **oparent** project POM as ancestor. That is, DCAE projects inherent all parameters defined in the oparent project which include many ONAP wide configuration parameters such as the location of various artifact repos.
A number of DCAE projects are not written Java. For these projects we use the CodeHaus Maven Execution plugin for triggering a Bash script at various stages of Maven lifecycle. The script is mvn-phase-script.sh, located at the root of each non-Java DACE project. It is in this script that the actual build operation is performed at different Maven phases. For example, for a Python project, Maven test will actually trigger a call to tox to conduct project unit tests.
Below is a list of the repos and their sub-modules, and the language they are written in.
* dcaegen2
- docs (rst)
- platformdoc (mkdoc)
* dcaegen2.analytics
* dcaegen2.analytics.tca
- dcae-analytics-aai (Java)
- dcae-analytics-cdap-common (Java)
- dcae-analytics-cdap-plugins (Java)
- dcae-analytics-cdap-tca (Java)
- dcae-analytics-common (Java)
- dcae-analytics-dmaap (Java)
- dcae-analytics-it (Java)
- dcae-analytics-model (Java)
- dcae-analytics-tca (Java)
- dcae-analytics-test (Java)
- dpo (Java)
* dcaegen2.collectors
- dcaegen2.collectors.snmptrap (Python)
- dcaegen2.collectors.ves (Java)
* dcaegen2.deployments
- bootstrap (bash)
- cloud_init (bash)
- scripts (bash, python)
* dcaegen2.platform
* dcaegen2.platform.blueprints
- blueprints (yaml)
- check-blueprint-vs-input (yaml)
- input-templates (yaml)
* dcaegen2.platform.cli (Python)
- component-json-schemas (yaml)
- dcae-cli (Python)
* dcaegen2.platform.configbinding (Python)
* dcaegen2.platform.deployment-handler (Python)
* dcaegen2.platform.inventory-api (Clojure)
* dcaegen2.platform.plugins
- cdap (Python)
- dcae-policy (Python)
- docker (Python)
- relationships (Python)
* dcaegen2.platform.policy-handler (Python)
* dcaegen2.platform.servicechange-handler (Python)
* dcaegen2.utils
- onap-dcae-cbs-docker-client (Python)
- onap-dcae-dcaepolicy-lib (Python)
- python-discovery-client (Python)
- python-dockering (Python)
- scripts (bash)
Environment
-----------
Building is conducted in a Linux environment that has the basic building tools such as JDK 8, Maven 3, Python 2.7 and 3.6, docker engine, etc.
Steps
-----
Because of the uniform adoption of Maven framework, each project can be built by running the standard Maven build commands: mvn clean, install, deploy, etc. For projects with submodules, the pom file in the project root will descent to the submodules and complete the submodule building.
Artifacts
---------
Building of DCAE projects produce three different kinds of artifacts: Java jar files, raw file artifacts (including yaml files, scripts, wagon packages, etc), Pypi packages, and docker container images.
|
