1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
11 - `Types of Users and Usage
12 Instructions: <#DCAEMODUserGuide(draft)-TypesofUsersand>`__
14 - `1. Deployment of DCAE MOD components via Helm
15 charts <#DCAEMODUserGuide(draft)-1.DeploymentofD>`__
17 - `Using DCAE MOD without an Ingress
18 Controller <#DCAEMODUserGuide(draft)-UsingDCAEMODwit>`__
20 - `2. Configuring DCAE
21 mod <#DCAEMODUserGuide(draft)-2.ConfiguringDC>`__
23 - `3. Design & Distribution
24 Flow <#DCAEMODUserGuide(draft)-3.Design&Distri>`__
27 Types of Users and Usage Instructions:
28 ======================================
30 +-------+-----------------------------+-----------------------------+
31 | Sr.No | User | Usage Instructions |
32 +=======+=============================+=============================+
33 | 1. | Developers who are looking | - Access the Nifi |
34 | | to onboard their mS | Web UI url provided to you |
36 | | | - Follow steps 2.c |
39 | | | - You should be able |
40 | | | to see your microservices |
41 | | | in the Nifi Web UI by |
42 | | | clicking and dragging |
43 | | | ‘Processor’ on the canvas, |
44 | | | and searching for the name |
47 | | | ervice/component/processor. |
48 +-------+-----------------------------+-----------------------------+
49 | 2. | Designers who are building | - Access the Nifi |
50 | | the flows through UI and | Web UI url provided to you |
51 | | triggering distribution | |
52 | | | - Follow steps 3 to |
53 | | | the end of the document |
54 +-------+-----------------------------+-----------------------------+
55 | 3. | Infrastructure/ Admins who | - Follow start to |
56 | | want to stand up DCAE Mod | the end |
57 | | and validate it | |
58 +-------+-----------------------------+-----------------------------+
61 1. Deployment of DCAE MOD components via Helm charts
62 =======================================================
64 The DCAE MOD components are deployed using the standard ONAP OOM
65 deployment process. When deploying ONAP using the helm deploy command,
66 DCAE MOD components are deployed when the dcaemod.enabled flag is set to
67 true, either via a --set option on the command line or by an entry in an
68 overrides file. In this respect, DCAE MOD is no different from any
71 The default DCAE MOD deployment relies on an nginx ingress controller
72 being available in the Kubernetes cluster where DCAE MOD is being
73 deployed. The Rancher RKE installation process sets up a suitable
74 ingress controller. In order to enable the use of the ingress
75 controller, it is necessary to override the OOM default global settings
76 for ingress configuration. Specifically, the installation needs to set
77 the following configuration in an override file::
82 baseurl: "simpledemo.onap.org"
84 When DCAE MOD is deployed with an ingress controller, several endpoints
85 are exposed outside the cluster at the ingress controller's external IP
86 address and port. (In the case of a Rancher RKE installation, there is
87 an ingress controller on every worker node, listening at the the
88 standard HTTP port (80).) These exposed endpoints are needed by users
89 using machines outside the Kubernetes cluster.
91 +--------------+--------------------------------------------------+--------------------------+
92 | **Endpoint** | ** Routes to (cluster | **Description** |
93 | | internal address)** | |
94 +==============+==================================================+==========================+
95 | /nifi | http://dcaemod-designtool:8080/nifi | Design tool Web UI |
97 +--------------+--------------------------------------------------+--------------------------+
98 | /nifi-api | http://dcaemod-designtool:8080/nifi-api | Design tool API |
100 +--------------+--------------------------------------------------+--------------------------+
101 | /nifi-jars | http://dcaemod-nifi-registry:18080/nifi-jars | Flow registry listing of |
102 | | | JAR files built from |
103 | | | component specs |
104 +--------------+--------------------------------------------------+--------------------------+
105 | /onboarding | http://dcaemod-onboarding-api:8080/onboarding | Onboarding API |
107 +--------------+--------------------------------------------------+--------------------------+
108 | /distributor | http://dcaemod-distributor-api:8080/distributor | Distributor API |
110 +--------------+--------------------------------------------------+--------------------------+
112 | To access the design Web UI, for example, a user would use the URL :
113 http://*ingress_controller_address:ingress_controller_port*/nifi.
114 | *ingress_controller_address* is the the IP address or DNS FQDN of the
115 ingress controller and
116 | *ingress_controller_port* is the port on which the ingress controller
117 is listening for HTTP requests. (If the port is 80, the HTTP default,
118 then there is no need to specify a port.)
120 There are two additional *internal* endpoints that users need to know,
121 in order to configure a registry client and a distribution target in the
122 design tool's controller settings.
124 +------------------------+--------------------------------------------+
125 | **Configuration Item** | **Endpoint URL** |
126 +========================+============================================+
127 | Registry client | http://dcaemod-nifi-registry:18080 |
128 +------------------------+--------------------------------------------+
129 | Distribution target | http://dcaemod-runtime-api:9090 |
130 +------------------------+--------------------------------------------+
132 With Guilin release, OOM/ingress template has been updated to enable virtual host by default.
133 All MOD API's and UI access via ingress should use dcaemod.simpledemo.onap.org.
135 In order to access Design UI from local, add an entry for dcaemod.simpledemo.onap.org in /etc/hosts with the correct IP (any K8S node IP can be specified).
138 Using DCAE MOD without an Ingress Controller
141 Not currently supported
144 2. Configuring DCAE mod
145 ==========================
147 **a. Configure Nifi Registry url**
149 Next check Nifi settings by selecting the Hamburger button in the Nifi
150 UI. It should lead you to the Nifi Settings screen
156 Add a registry client. The Registry client url will be
157 http://dcaemod-nifi-registry:18080
162 **b. Add distribution target which will be the runtime api url**
164 Set the distribution target in the controller settings
168 Distribution target URL will be
169 `http://dcaemod-runtime-api:9090 <http://dcaemod-runtime-api:9090/>`__
173 Now let’s access the Nifi (DCAE designer) UI - http://dcaemod.simpledemo.onap.org/nifi
175 IPAddress is the host address or the DNS FQDN, if there is one, for one of the Kubernetes nodes.
180 **c. Get the artifacts to test and onboard.**
182 Let's fetch the artifacts/ spec files
184 **Component Spec for DCAE-VES-Collector :** https://git.onap.org/dcaegen2/collectors/ves/tree/dpo/spec/vescollector-componentspec.json
186 **Component Spec for DCAE-TCAgen2 :** https://git.onap.org/dcaegen2/collectors/ves/tree/dpo/spec/vescollector-componentspec.json
188 **VES 5.28.4 Data Format :** https://git.onap.org/dcaegen2/collectors/ves/tree/dpo/data-formats/VES-5.28.4-dataformat.json
190 **VES 7.30.2.1 Data Format :** https://git.onap.org/dcaegen2/collectors/ves/tree/etc/CommonEventFormat_30.2.1_ONAP.jsonormat.json
192 **VES Collector Response Data Format :** https://git.onap.org/dcaegen2/collectors/ves/tree/dpo/data-formats/ves-response.json
194 **TCA CL Data Format :** https://git.onap.org/dcaegen2/analytics/tca-gen2/tree/dcae-analytics/dpo/dcaeCLOutput.json
197 For the purpose of onboarding, a Sample Request body should be of the type -::
199 { "owner": "<some value>", "spec": <some json object> }
201 where the json object inside the spec field can be a component spec json.
203 Request bodies of this type will be used in the onboarding requests you make using curl or the onboarding swagger interface.
205 **The prepared Sample Request body for a component dcae-ves-collector looks like
208 See :download:`VES Collector Spec <./Sample-Input-Files/Request-body-of-Sample-Component.json>`
210 **The prepared Sample request body for a sample data format looks like so -**
212 See :download:`VES data Format <./Sample-Input-Files/Request-body-of-Sample-Data-Format.json>`
216 **d. To onboard a data format and a component**
218 Each component has a description that tells what it does.
220 These requests would be of the type
222 curl -X POST http://<onboardingapi host>/onboarding/dataformats -H "Content-Type: application/json" -d
223 @<filepath to request>
225 curl -X POST http://<onboardingapi host>/onboarding/components -H "Content-Type: application/json" -d
226 @<filepath to request>
230 curl -X POST http://dcaemod.simpledemo.onap.org/onboarding/dataformats -H "Content-Type: application/json" -d @<filepath to request>
232 curl -X POST http://dcaemod.simpledemo.onap.org/onboarding/components -H "Content-Type: application/json" -d @<filepath to request>
236 **e. Verify the resources were created using**
238 curl -X GET http://<IPAddress>/onboarding/dataformats
240 curl -X GET http://<IPAddress>/onboarding/components
242 **f. Verify the genprocessor (which polls onboarding periodically to convert component specs to nifi processor), converted the component**
244 Open http://dcaemod.simpledemo.onap.org/nifi-jars in a browser.
246 These jars should now be available for you to use in the nifi UI as
251 3. Design & Distribution Flow
252 ================================
255 **a**. To start creating flows, we need to create a process group first. The
256 name of the process group will be the name of the flow. Drag and Drop on
257 the canvas, the ‘Processor Group’ icon from the DCAE Designer bar on the
263 Now enter the process group by double clicking it,
265 You can now drag and drop on the canvas ‘Processor’ icon from the top
266 DCAE Designer tab. You can search for a particular component in the
267 search box that appears when you attempt to drag the ‘Processor’ icon to
272 If the Nifi registry linking worked, you should see the “Import” button
273 when you try to add a Processor or Process group to the Nifi canvas,
278 By clicking on the import button, we can import already created saved
279 and version controlled flows from the Nifi registry, if they are
284 We can save created flows by version controlling them like so starting
285 with a 'right click' anywhere on the canvas-
289 Ideally you would name the flow and process group the same, because
290 functionally they are similar.
294 When the flow is checked in, the bar at the bottom shows a green
299 Note: Even if you move a component around on the canvas, and its
300 position on the canvas changes, it is recognized as a change, and it
301 will have to recommitted.
303 You can add additional components in your flow and connect them.
305 DcaeVesCollector connects to DockerTcagen2.
313 Along the way you need to also provide topic names in the settings
314 section. These can be arbitrary names.
318 To recap, see how DcaeVesCollector connects to DockerTcagen2. Look at
319 the connection relationships. Currently there is no way to validate
320 these relationships. Notice how it is required to name the topics by
323 The complete flow after joining our components looks like so
328 **b. Submit/ Distribute the flow:**
330 Once your flow is complete and saved in the Nifi registry, you can
331 choose to submit it for distribution.
335 If the flow was submitted successfully to the runtime api, you should
336 get a pop up a success message like so -
340 At this step, the design was packaged and sent to Runtime api.
342 The runtime is supposed to generate the blueprint out of the packaged
343 design/flow and push it to the DCAE inventory and the DCAE Dasboard.
345 **c. Checking the components in the DCAE Dashboard**
347 You should see the generated artifact/ blueprint in the DCAE Dashboard
348 dashboard at https://<IPAddress>:30418/ccsdk-app/login_external.htm in
349 our deployment. The name for each component will be appended by the flow
350 name followed by underscore followed by the component’s name.
352 The credentials to access the DCAE Dashboard
364 The generated Blueprint can be viewed.
368 Finally, the generated Blueprint can be deployed.
372 You can use/import the attached input configurations files to deploy. Drag and Drop these sample JSON files to fill in the configuration values.
373 See :download:`VES Collector Input Configuration <./Sample-Input-Files/ves-deploy.input.json>`
374 See :download:`Tcagen2 Input Configuration <./Sample-Input-Files/tca-deploy.input.json>`
380 .. |image0| image:: ../images/1.png
383 .. |image1| image:: ../images/2.png
386 .. |image2| image:: ../images/3.png
389 .. |image3| image:: ../images/4.png
392 .. |image4| image:: ../images/5.png
395 .. |image5| image:: ../images/6.png
398 .. |image6| image:: ../images/7.png
401 .. |image7| image:: ../images/8.png
404 .. |image8| image:: ../images/9.png
407 .. |image9| image:: ../images/10.png
410 .. |image10| image:: ../images/11.png
413 .. |image11| image:: ../images/12.png
416 .. |image12| image:: ../images/13.png
419 .. |image13| image:: ../images/14.png
422 .. |image14| image:: ../images/15.png
425 .. |image15| image:: ../images/16.png
428 .. |image16| image:: ../images/17.png
431 .. |image17| image:: ../images/18.png
434 .. |image18| image:: ../images/19.png
437 .. |image19| image:: ../images/20.png
440 .. |image20| image:: ../images/21.png
443 .. |image21| image:: ../images/22.png
446 .. |image22| image:: ../images/23.png
449 .. |image23| image:: ../images/24.png
452 .. |image24| image:: ../images/25.png
455 .. |image25| image:: ../images/26.png
456 .. |image26| image:: ../images/27.png