aboutsummaryrefslogtreecommitdiffstats
path: root/docs/userguide/running-bp-processor-in-ide.rst
blob: 1404c42b520e44f38fafe48bb6f5800f616d8512 (plain)
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
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
.. This work is a derivative of https://wiki.onap.org/display/DW/Running+Blueprints+Processor+Microservice+in+an+IDE
.. This work is licensed under a Creative Commons Attribution 4.0
.. International License. http://creativecommons.org/licenses/by/4.0
.. Copyright (C) 2020 Deutsche Telekom AG.

Running Blueprints Processor Microservice in an IDE
====================================================

Objective
~~~~~~~~~~~~

Have the blueprint processor running locally is to use the IDE to run the code, while having the database running in a container.
This way, code changes can be conveniently tested and debugged.


Check out the code
~~~~~~~~~~~~~~~~~~~

Check out the code from Gerrit: https://gerrit.onap.org/r/#/admin/projects/ccsdk/cds

Build it locally
~~~~~~~~~~~~~~~~~~

In the checked out directory, type

.. code-block:: bash

   mvn clean install -Pq -Dadditionalparam=-Xdoclint:none

Spin up a Docker container with the database
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Blueprints Processor project uses a database to store information about the blueprints
and therefore it needs to be online before attempting to run it.

One way to create the database is by using the :file:`docker-compose.yaml`
file present on the distribution module. This database will require a local directory to mount a volume, before running docker-compose remember to create following directory:

.. code-block:: bash

   mkdir -p -m 755 /opt/app/cds/mysql/data

Navigate to the docker-compose file in the distribution module:

.. tabs::

   .. group-tab:: Latest

      .. code-block:: bash

         cd ms/blueprintsprocessor/application/src/main/dc

   .. group-tab:: Frankfurt

      .. code-block:: bash

         cd ms/blueprintsprocessor/application/src/main/dc

   .. group-tab:: El Alto

      .. code-block:: bash

         ms/blueprintsprocessor/distribution/src/main/dc

   .. group-tab:: Dublin

      .. code-block:: bash

         ms/blueprintsprocessor/distribution/src/main/dc

And run docker-composer:

.. code-block:: bash

    docker-compose up -d db

This should spin up a container of the MariaDB image in the background.
To check if it has worked, this command can be used:

.. code-block:: bash

    docker-compose logs -f

The phrase ``mysqld: ready for connections`` indicates that the database was started correctly.

From now on, the Docker container will be available on the computer; if it ever gets stopped,
it can be started again by the command:

.. code-block:: bash

   docker start <id of mariadb container>


Set permissions on the local file system
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Blueprints processor uses the local file system for some operations and, therefore,
need some existing and accessible paths to run properly.

Execute the following commands to create the needed directories, and grant access to the current user to modify them:

.. code-block:: bash

   mkdir -p -m 755 /opt/app/onap/blueprints/archive
   mkdir -p -m 755 /opt/app/onap/blueprints/deploy
   mkdir -p -m 755 /opt/app/onap/scripts
   sudo chown -R $(id -u):$(id -g) /opt/app/onap/

Import the project into the IDE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. tabs::

   .. tab:: IntelliJ IDEA

      Go to *File | Open* and choose the :file:`pom.xml` file of the cds directory:

      |imageImportProject|

      Sometimes it may be necessary to reimport Maven project:

      |imageReimportMaven|


      **Override some application properties:**

      After the project is compiled, a Run Configuration profile overriding some application properties
      with custom values needs to be created, to reflect the local environment characteristics.

      .. tabs::

         .. group-tab:: Latest

            Navigate to the main class of the Blueprints Processor, the BlueprintProcessorApplication class:

            ``ms/blueprintsprocessor/application/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/BlueprintProcessorApplication.kt``.

            Right-click inside it, at any point, to load the context menu and select create
            BlueprintProcessorApplication configuration from context:

            |imageCreateRunConfigkt|

            **The following window will open:**

            |imageRunConfigKt|

            **Add the following in the field `VM Options`:**

            .. code-block:: bash
               :caption: **Custom values for properties**

               -Dspring.profiles.active=dev

            You can override any value from **application-dev.properties** file here. Use the following pattern:

            .. code-block:: java

               -D<application-dev.properties key>=<application-dev.properties value>

         .. group-tab:: Frankfurt

            Navigate to the main class of the Blueprints Processor, the BlueprintProcessorApplication class:

            ``ms/blueprintsprocessor/application/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/BlueprintProcessorApplication.kt``.

            Right-click inside it, at any point, to load the context menu and select create
            BlueprintProcessorApplication configuration from context:

            |imageCreateRunConfigkt|

            **The following window will open:**

            |imageRunConfigKt|

            **Add the following in the field `VM Options`:**

            .. code-block:: bash
               :caption: **Custom values for properties**

               -Dspring.profiles.active=dev

            You can override any value from **application-dev.properties** file here. Use the following pattern:

            .. code-block:: java

               -D<application-dev.properties key>=<application-dev.properties value>

         .. group-tab:: El Alto

            Navigate to the main class of the Blueprints Processor, the BlueprintProcessorApplication class:

            ``ms/blueprintsprocessor/application/src/main/java/org/onap/ccsdk/cds/blueprintsprocessor/BlueprintProcessorApplication.java.``

            Right-click inside it, at any point, to load the context menu and select create
            BlueprintProcessorApplication configuration from context:

            |imageCreateRunConfigJava|

            **The following window will open:**

            |imageRunConfigJava|

            **Add the following in the field `VM Options`:**

            .. code-block:: bash
               :caption: **Custom values for properties**

               -Dspring.profiles.active=dev

            You can override any value from **application-dev.properties** file here. Use the following pattern:

            .. code-block:: java

               -D<application-dev.properties key>=<application-dev.properties value>

         .. group-tab:: Dublin

            Navigate to the main class of the Blueprints Processor, the BlueprintProcessorApplication class:

            ``ms/blueprintsprocessor/application/src/main/java/org/onap/ccsdk/cds/blueprintsprocessor/BlueprintProcessorApplication.java``.

            Right-click inside it, at any point, to load the context menu and select create
            BlueprintProcessorApplication configuration from context:

            |imageCreateRunConfigJava|

            **The following window will open:**

            |imageRunConfigJava|

            **Add the following in that field:**

            .. code-block:: java
               :caption: **Custom values for properties**

               -DappName=ControllerBluePrints
               -Dms_name=org.onap.ccsdk.apps.controllerblueprints
               -DappVersion=1.0.0
               -Dspring.config.location=opt/app/onap/config/
               -Dspring.datasource.url=jdbc:mysql://127.0.0.1:3306/sdnctl
               -Dspring.datasource.username=sdnctl
               -Dspring.datasource.password=sdnctl
               -Dcontrollerblueprints.loadInitialData=true
               -Dblueprintsprocessor.restclient.sdncodl.url=http://localhost:8282/
               -Dblueprintsprocessor.db.primary.url=jdbc:mysql://localhost:3306/sdnctl
               -Dblueprintsprocessor.db.primary.username=sdnctl
               -Dblueprintsprocessor.db.primary.password=sdnctl
               -Dblueprintsprocessor.db.primary.driverClassName=org.mariadb.jdbc.Driver
               -Dblueprintsprocessor.db.primary.hibernateHbm2ddlAuto=update
               -Dblueprintsprocessor.db.primary.hibernateDDLAuto=none
               -Dblueprintsprocessor.db.primary.hibernateNamingStrategy=org.hibernate.cfg.ImprovedNamingStrategy
               -Dblueprintsprocessor.db.primary.hibernateDialect=org.hibernate.dialect.MySQL5InnoDBDialect
               -Dblueprints.processor.functions.python.executor.executionPath=./components/scripts/python/ccsdk_blueprints
               -Dblueprints.processor.functions.python.executor.modulePaths=./components/scripts/python/ccsdk_blueprints,./components/scripts/python/ccsdk_netconf,./components/scripts/python/ccsdk_restconf
               -Dblueprintsprocessor.restconfEnabled=true
               -Dblueprintsprocessor.restclient.sdncodl.type=basic-auth
               -Dblueprintsprocessor.restclient.sdncodl.url=http://localhost:8282/
               -Dblueprintsprocessor.restclient.sdncodl.username=admin
               -Dblueprintsprocessor.restclient.sdncodl.password=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
               -Dblueprintsprocessor.grpcEnable=false
               -Dblueprintsprocessor.grpcPort=9111
               -Dblueprintsprocessor.blueprintDeployPath=/opt/app/onap/blueprints/deploy
               -Dblueprintsprocessor.blueprintArchivePath=/opt/app/onap/blueprints/archive
               -Dblueprintsprocessor.blueprintWorkingPath=/opt/app/onap/blueprints/work
               -Dsecurity.user.password={bcrypt}$2a$10$duaUzVUVW0YPQCSIbGEkQOXwafZGwQ/b32/Ys4R1iwSSawFgz7QNu
               -Dsecurity.user.name=ccsdkapps
               -Dblueprintsprocessor.messageclient.self-service-api.kafkaEnable=false
               -Dblueprintsprocessor.messageclient.self-service-api.topic=producer.t
               -Dblueprintsprocessor.messageclient.self-service-api.type=kafka-basic-auth
               -Dblueprintsprocessor.messageclient.self-service-api.bootstrapServers=127.0.0.1:9092
               -Dblueprintsprocessor.messageclient.self-service-api.consumerTopic=receiver.t
               -Dblueprintsprocessor.messageclient.self-service-api.groupId=receiver-id
               -Dblueprintsprocessor.messageclient.self-service-api.clientId=default-client-id
               -Dspring.profiles.active=dev
               -Dblueprintsprocessor.httpPort=8080
               -Dserver.port=55555


      **Browse Working Directory to your application path**  ``.../cds/ms/blueprintsprocessor/application``
      **if path is not already specified correctly.**

      **Add/replace the following in Blueprint's application-dev.properties file:**

      .. code-block:: java

         blueprintsprocessor.grpcclient.remote-python.type=token-auth
         blueprintsprocessor.grpcclient.remote-python.host=localhost
         blueprintsprocessor.grpcclient.remote-python.port=50051
         blueprintsprocessor.grpcclient.remote-python.token=Basic Y2NzZGthcHBzOmNjc2RrYXBwcw==

         blueprintprocessor.remoteScriptCommand.enabled=true


      **Run the application:**

      Select either run or debug for this Run Configuration to start the Blueprints Processor:

      |imageRunDebug|

      |imageBuildLogs|

   .. tab:: Visual Studio Code

      .. tabs::

         .. group-tab:: Latest

            * **Step #1** - Make sure your installation of Visual Studio Code is up to date. This guide was writen using version 1.48
            * **Step #2** - Install `Kotlin extension from the Visual Studio Code Marketplace <https://marketplace.visualstudio.com/items?itemName=fwcd.kotlin>`_
            * **Step #3** - On the top menu click *Run | Open Configurations*

            .. warning:: This should open the file called `launch.json` but in some cases you'll need to wait for the Kotlin Language Server to be installed before you can do anything.
               Please watch the bottom bar in Visual Studio Code for messages about things getting installed.

            * **Step #4** - add configuration shown below to your configurations list.

            .. code-block:: json

               {
                     "type": "kotlin",
                     "request": "launch",
                     "name": "Blueprint Processor",
                     "projectRoot": "${workspaceFolder}/ms/blueprintsprocessor/application",
                     "mainClass": "-Dspring.profiles.active=dev org.onap.ccsdk.cds.blueprintsprocessor.BlueprintProcessorApplicationKt"
               }

            .. warning:: The `projectRoot` path assumes that you created your Workspace in the main CDS repository folder. If not - please change the path accordingly

            .. note:: The `mainClass` contains a spring profile param before the full class name. This is done because `args` is not supported by Kotlin launch.json configuration.
               If you have a cleaner idea how to solve this - please let us know.

            **Add/replace the following in Blueprint's application-dev.properties file:**

            .. code-block:: java

               blueprintsprocessor.grpcclient.remote-python.type=token-auth
               blueprintsprocessor.grpcclient.remote-python.host=localhost
               blueprintsprocessor.grpcclient.remote-python.port=50051
               blueprintsprocessor.grpcclient.remote-python.token=Basic Y2NzZGthcHBzOmNjc2RrYXBwcw==

               blueprintprocessor.remoteScriptCommand.enabled=true

            **Currently the following entries need to be added in VSC too:**

            .. code-block:: java

               logging.level.web=DEBUG
               logging.level.org.springframework.web: DEBUG

               #Encrypted username and password for health check service
               endpoints.user.name=eHbVUbJAj4AG2522cSbrOQ==
               endpoints.user.password=eHbVUbJAj4AG2522cSbrOQ==

               #BaseUrls for health check blueprint processor services
               blueprintprocessor.healthcheck.baseUrl=http://localhost:8080/
               blueprintprocessor.healthcheck.mapping-service-name-with-service-link=[Execution service,/api/v1/execution-service/health-check],[Resources service,/api/v1/resources/health-check],[Template service,/api/v1/template/health-check]

               #BaseUrls for health check Cds Listener services
               cdslistener.healthcheck.baseUrl=http://cds-sdc-listener:8080/
               cdslistener.healthcheck.mapping-service-name-with-service-link=[SDC Listener service,/api/v1/sdclistener/healthcheck]

               #Actuator properties
               management.endpoints.web.exposure.include=*
               management.endpoint.health.show-details=always
               management.info.git.mode=full

            In VSC the properties are read from target folder, thats why the following maven command needs to be rerun:

            .. code-block:: bash

               mvn clean install -DskipTests=true -Dmaven.test.skip=true -Dmaven.javadoc.skip=true -Dadditionalparam=-Xdoclint:none

            Click Run in Menu bar.

            |imageLogsVSC|


Testing the application
~~~~~~~~~~~~~~~~~~~~~~~~~

There are two main features of the Blueprints Processor that can be of interest of a developer:
blueprint publish and blueprint process.

To upload custom blueprints,  the endpoint ``api/v1/execution-service/publish`` is used.

To process, the endpoint is ``api/v1/execution-service/process``.

Postman is a software that can be used to send these request, and an example of
them is present on https://www.getpostman.com/collections/b99863b0cde7565a32fc.

A detailed description of the usage of different APIs of CDS will follow.

Possible Fixes
~~~~~~~~~~~~~~~~~~~

Imported packages or annotiations are not found, Run Config not available?
*****************************************************************************

1. Rebuild with ``maven install ...`` (see above)
2. Potentially change Maven home directory in Settings
3. Maven reimport in IDE

Compilation error?
********************

* Change Java Version to 11


.. image alignment inside tabs doesn't work

.. |imageRunConfigJava| image:: media/run_config_java.png
   :width: 500pt
   :align: middle

.. |imageRunConfigKt| image:: media/run_config_kt.png
   :width: 500pt
   :align: middle

.. |imageCreateRunConfigJava| image:: media/create_run_config_java.png
   :width: 500pt
   :align: middle

.. |imageCreateRunConfigKt| image:: media/create_run_config_kt.png
   :width: 500pt
   :align: middle

.. |imageImportProject| image:: media/import_project.png
   :width: 300pt
   :align: middle

.. |imageReimportMaven| image:: media/reimport_maven.png
   :width: 400pt
   :align: middle

.. |imageRunDebug| image:: media/run_debug.png
   :width: 500pt
   :align: middle

.. |imageBuildLogs| image:: media/build_logs.png
   :width: 500pt
   :align: middle

.. |imageLogsVSC| image:: media/vsc_logs.png
   :width: 500pt
   :align: middle