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
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
|
#
# ============LICENSE_START==========================================
# org.onap.dmaap
# ===================================================================
# Copyright © 2018 AT&T Intellectual Property. All rights reserved.
# ===================================================================
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ============LICENSE_END============================================
# ECOMP is a trademark and service mark of AT&T Intellectual Property.
#
#
DMaaP Bus Controller API
=======================
Data Movement as a Platform (DMaaP) Bus Controller provides an API for other ONAP infrastructure components to provision DMaaP resources.
A typical DMaaP resource is a Data Router Feed or a Message Router Topic, and their associated publishers and subscribers.
Other infrastucture resources such as DR Nodes and MR Clusters are also provisioned through this API.
### Build Instructions for a Continuous Integration environment using Jenkins
When this component is included in a Continuous Integration environment, such as structured by the Linux Foundation, the artifacts can be created and deployed via Jenkins. The following maven targets are currently supported in the Build step:
```
clean install
```
### Build Instructions for external developers
This project is organized as a mvn project for a jar package.
After cloning from this git repo:
```
mvn clean install
```
### Docker Packaging
We can utilize docker to build and register the buscontroller container in a local dev repository.
Note the Dockerfile follows ONAP convention of running app as root.
```
<assuming DOCKER_HOST is set appropriately for your environment>
$ mvn -P docker docker:build
```
### ONAP deployment
Two styles of deployment are supported for ONAP.
1. OOM - by the time of Release Casablanca, this is the preferred deployment method which relies on a kubernetes environment, and uses helm charts. Buscontroller is part of a larger overall dmaap chart which also deploys Message Router and Data Router. See https://gerrit.onap.org/r/#/admin/projects/oom
2. HEAT - an older style deployment which assumes VM running docker.
#### ONAP OOM Deployment
The default DMaaP charts for an OOM deployment should be able to be used without modification because the interdependencies between components rely on kubernetes service names.
However, overrides can be made to the buscontroller values.yaml file (found in oom/kubernetes/dmaap/charts/dmaap-bus-controller/values.yaml) as needed.
Following a convention where Release is set to the component name (--name=dmaap) and using a dev namespace:
```
<clone oom>
cd kubernetes
<edit values.yaml if necessary>
make dmaap
helm install dmaap --debug --name=dmaap --namespace=dev
```
#### ONAP Heat deployment
Prior to starting container, place environment specific vars in /tmp/docker-databus-controller.conf on the Docker host,
and map that file to /opt/app/config/conf.
Run the buscontroller image which starts execution of the dmaapbc deploy command, which will update the container runtime properties appropriately, and start the Bus Controller.
For example, in ONAP Future Lab environment, /tmp/docker-databus-controller.conf looks like:
```
# DMaaP Bus Controller OpenSource environment vars
CONT_DOMAIN=demo.dmaap.onap.org
DMAAPBC_INSTANCE_NAME=ONAPfuture
# The https port
# set to 0 if certificate is not ready
DMAAPBC_INT_HTTPS_PORT=0
DMAAPBC_KSTOREFILE=/opt/app/dcae-certificates
DMAAPBC_KSTOREPASS=foofoofoo
DMAAPBC_PVTKEYPASS=barbarbar
DMAAPBC_PG_ENABLED=true
DMAAPBC_PGHOST=zldciad1vipstg00.simpledemo.openecomp.org
DMAAPBC_PGCRED=test234-ftl
DMAAPBC_DRPROV_FQDN=zldciad1vidrps00.simpledemo.openecomp.org
DMAAPBC_AAF_URL=https://aafapi.${CONT_DOMAIN}:8095/proxy/
DMAAPBC_TOPICMGR_USER=m99751@dmaapBC.openecomp.org
DMAAPBC_TOPICMGR_PWD=enc:zyRL9zbI0py3rJAjMS0dFOnYfEw_mJhO
DMAAPBC_ADMIN_USER=m99501@dcae.openecomp.org
DMAAPBC_ADMIN_PWD=enc:YEaHwOJrwhDY8a6usetlhbB9mEjUq9m
DMAAPBC_PE_ENABLED=false
DMAAPBC_PE_AAF_ENV=TBD
```
Then the following steps could be used to pull and run the Bus Controller. (onap-nexus is just an example)
```
$
$ docker pull nexus3.onap.org:10003/onap/dmaap/buscontroller:latest
$ docker run -d -p 18080:8080 -p 18443:8443 -v /tmp/docker-databus-controller.conf:/opt/app/config/conf nexus3.onap.org:10003/onap/dmaap/buscontroller:latest
```
### Properties
This section is intended to describe the behavior customization of Bus Controller that can be obtained via properties file used by the dbcapi library.
By default, this file is located in etc/dmaapbc.properties.
However, a java argument -DConfigFile can be set to a different path. (Our kubernetes deployment relies on this and points to a configmap, for example.)
The table below lists all the settings, default values (if not set), and shows any explicit setting in ONAP oom kubernetes deployment.
|-|-|-|-|
| Property | Description | Default | Kubernetes Setting |
|-|-|-|-|
|UseAAF | Flag for whether AAF authz API is to be used | false | false |
|-|-|-|-|
|csit | Flag for stubbing out many southbound calls in a CSIT environment | No | No |
|-|-|-|-|
|DR.provhost | FQDN of Data Router Provisioning Server (deprecated - now set via API) | notSet | dcae-drps.domain.not.set |
|-|-|-|-|
|ProvisioningURI | URI to retrieve dynamic DR configuration | /internal/prov | /internal/prov |
|-|-|-|-|
|Feed.deleteHandling | indicator for handling feed delete request | DeleteOnDR | SimulateDelete |
| | DeleteOnDR - means use the DR API to DELETE a feed. (default for backwards compatibility) | | |
| | SimulateDelete - means preserve the feed on DR (after cleaning it up), and mark as DELETED in DBCL. | | |
|-|-|-|-|
|UsePGSQL | flag indicates whether to retain data in Postgresql | false | true |
| | when false, objects will be kept in memory but will be | | |
| | lost on restart and not shared between instances | | |
|-|-|-|-|
|DB.host | FQDN or service name of Postresql host | dcae-pstg-write-ftl.domain.notset.com | dbc-pg-primary |
|-|-|-|-|
|DB.name | name of Postresql database | dmaap | |
|-|-|-|-|
|DB.schema | name of database schema | public | |
|-|-|-|-|
|DB.user | username for Postgresql access | dmaap_admin | |
|-|-|-|-|
|DB.cred | password for Postrgresql access | test234-ftl | onapdemodb |
|-|-|-|-|
|MR.multisite | Indicates if there can be multiple sites (locations) where MR is deployed | true | false |
|-|-|-|-|
|MR.CentralCname | FQDN or service name of MR (deployed in central if multilocation is true) | MRcname.not.set | message-router |
|-|-|-|-|
|MR ClientDeleteLevel | MR Client Delete thoroughness | 0 | 1 |
| | 0 = don't delete | | |
| | 1 = delete from persistent store (PG) | | |
| | 2 = delete from persistent store (PG) and authorization store (AAF) | | |
|-|-|-|-|
|MR.TopicFactoryNS | AAF namespace used to create perms for MR topics | MR.topicFactoryNS.not.set | org.onap.dmaap.mr.topicFactory |
|-|-|-|-|
|MR.TopicMgrRole | AAF Role used by Buscontroller to create topics on MR | MR.TopicMgrRole.not.set | org.onap.dmaap-bc-topic-mgr.client |
|-|-|-|-|
|MR.projectID | Value for some constructs of fully qualified topic names | 99999 | ONAP |
|-|-|-|-|
|cadi.properties | Path to CADI properties file | /opt/app/osaaf/local/org.onap.dmaap-bc.props | /opt/app/osaaf/lcoal/org.onap.dmaap-bc.props |
|-|-|-|-|
|aaf.URL | URL of the AAF server | https://authentication.domain.netset.com:8095/proxy/ | https://aaf-authz/ |
|-|-|-|-|
|aaf.TopicMgrUser | AAF Identity of Topic Mgr | noMechId@domain.netset.com | dmaap-bc-topic-mgr@dmaap-bc-topic-mgr.onap.org |
|-|-|-|-|
|aaf.TopicMgrPassword | AAF Credential for Topic Mgr | notSet | demo123456! |
|-|-|-|-|
|aaf.AdminUser | AAF Identity of user with Admin role for API namespace | noMechId@domain.netset.com | aaf_admin@people.osaaf.org |
|-|-|-|-|
|aaf.AdminPassword | AAF credential of AdminUser | notSet | demo123456! |
|-|-|-|-|
|CredentialCodeKeyfile | location of the codec keyfile used to decrypt passwords | LocalKey | etc/LocalKey |
| | in this properties file before they are passed to AAF | LocalKey | etc/LocalKey |
|-|-|-|-|
|AafDecryption.Class | Specifies the Class to be used for decryption | org.onap.dmaap.dbcapi.aaf.ClearDecrypt | |
|-|-|-|-|
|ApiNamespace | Root namespace for AAF perms related to dbcapi access | apiNamespace.not.set | org.onap.dmaap-bc.api |
|-|-|-|-|
|ApiPermission.Class | the Class that determines if a call to API is authorized| allow | |
|-|-|-|-|
|MM.ProvRole | AAF Role of client publishing MM prov cmds | notSet | org.onap.dmaap-bc-mm-prov.prov |
|-|-|-|-|
|MM.ProvUserMechId | AAF Identity when publishing to MM command topic | notSet | dmaap-bc-mm-prov@dmaap-bc-mm-prov.onap.org|
|-|-|-|-|
|MM.ProvUserPwd | AAF credenital for ProvUserMechId | notSet | demo123456! |
|-|-|-|-|
|MM.AgentRole | AAF Role of client susbcribing to MM command topic | notSet | org.onal.dmaap-bc-mm-prov.agent |
|-|-|-|-|
|HttpAllowed | flag indicating whether http is supported | false | true |
|-|-|-|-|
|IntHttpPort | Internal port for http service | 80 | 8080 |
|-|-|-|-|
|IntHttpsPort | Internal port for https service (0 if no cert is avail) | 443 | 8443 |
|-|-|-|-|
|ExtHttpsPort | Externally advertised port for https service (deprecated)| 443 | 443 |
|-|-|-|-|
|KeyStoreType | Format of Java keystore | jks | jks |
|-|-|-|-|
|KeyStoreFile | Path to java keystore | etc/keystore | etc/keystore |
|-|-|-|-|
|KeyStorePassword | Password for keystore | changeit | <provided by Certificate Authority> |
|-|-|-|-|
|KeyPassword | Password for private key in the https keystore | changeit | <provided by Certificate Authority> |
|-|-|-|-|
|TrustStoreType | Format of Trust Store file | jks | jks |
|-|-|-|-|
|TrustStoreFile | Path to Trust Store file | | etc/org.onap.dmaap-bc.trust.jks |
|-|-|-|-|
|TrustStorePassword | Password for Trust Store | | <provided by Certificate Authority> |
|-|-|-|-|
|QuiesceFile | Path to file which signals needs to queiesce | | etc/SHUTDOWN |
|-|-|-|-|
### Environment Variables
The following environment variables can be set in the container environment to further effect behavior:
- DMAAPBC_WAIT_TOEXIT=Y when set this will attempt to keep the dmaap-bc container running. Sometimes needed to get a better look at logs when the main proces is exiting for some reason.
- CONFIGMAP_ROOT defaults to /opt/app/config/conf but can be overwritten if needed. This value serves as the root to where the buscontroller.env file is found.
- CONFIGMAP_PROPS defaults to /opt/app/config/conf/dmaapbc.properties but can be overwritten if needed
|
