...

Running SO BPMN infra on standalone camunda

[grabinsk@localhost ~]$ docker run --rm --name camunda -p 8080:8080 -v /home/grabinsk/dev/onap/so/bpmn/mso-infrastructure-bpmn/target/mso-infrastructure-bpmn-1.4.0-SNAPSHOT.war:/camunda/webapps/mso.war:z camunda/camunda-bpm-platform:7.10.0

...

patch file with changes applied on top of dublin release:namepoc_on_top_of_dublin.patchheight250  View filehttps://gerrit.onap.org/r/c/so/+/101907

can be build with:

mvn clean  install -DskipTests=true -Dmaven.test.skip=true -Dcheckstyle.skip

(2 out of 20 tests in  mso-infrastructure-bpmn started to fail - needs checking)

Deploying and

...

testing on Lab

• change mso-bpmn-infra deployment (  kubectl edit deployment -n onap dev-so-so-bpmn-infra  )
  • image: camunda/camunda-bpm-platform:7.10.0
  • containerPort: 8080    #originally it was 8081, but we can not change that in camunda image → we will need to update that in so-bpmn-infra service definition

  • in "volumeMounts:" add

    Code Block
    - mountPath: /camunda/webapps name: webapps

    
    

  • in "volumes:" add

    Code Block
    - hostPath: path: /dockerdata-nfs/webapps type: "" name: webapps

    
    

  • livenessProbe section causes that bpmn pod restarts every 10 min (this is for further investigation). Delete the following:
    

    livenessProbe:
       failureThreshold: 3
       httpGet:
          path: /manage/health
          port: 8081
         scheme: HTTP
       initialDelaySeconds: 600
       periodSeconds: 60
       successThreshold: 1
       timeoutSeconds: 10

• create 'webapps' in /dockerdata-nfs, add writeaccess for everybody to webapps dir (tomcat will want to extract war in that location)
• copy the mso.war to /dockerdata-nfs/webapps (war file name must be 'mso' since it will appear in URL's of exposed services)
• change target port of so-bpmn-infra to 8080 (  kubectl -n onap edit service so-bpmn-infra  ))
  
  

...

Patch set on top of dublin including building cammunda-based so-bpmn-infra image with hardcoded onap-ca.crt View filenamepoc_on_top_of_dublin_with_cert.patchheight250: https://gerrit.onap.org/r/c/so/+/101907

Logging

Current POC implementation is not using origianl onap - style logback logging config that stores application logs in some files

...

Therefore for the purpose of this POC a war with simple SO BuildingBlock style workflow is created. The workflow consists of single task that delegates execution to a simple Spring bean that performs some logging. Gliffy Diagramsize300nameFooBB.bpmnpagePin1

The test wofklow workflow application is created here: https://gitlabe2.ext.net.nokia.com/grabinsk/

The foo.war can be produced by simple 'mvn package' execution.

...

INSERT INTO orchestration_status_state_transition_directive
(RESOURCE_TYPE, ORCHESTRATION_STATUS, TARGET_ACTION, FLOW_DIRECTIVE)
VALUES('SERVICE', 'ACTIVE', 'CUSTOM', 'CONTINUE');

...

Running modified Service-Macro-Create workflow

Start the macro create srevice service workflow from VID.

Image Removed

It should also be possible to see the log entries produced during Foo java delegate execution

2019-11-07 12:32:48.656  INFO 6 --- [pool-2-thread-1] org.onap.so.foo.Foo                      : _________________________________________________ FOO !!!
2019-11-07 12:32:48.656  INFO 6 --- [pool-2-thread-1] org.onap.so.foo.Foo                      : variable: `gBuildingBlockExecution`: org.onap.so.bpmn.common.DelegateExecutionImpl@3cbbf5bb
2019-11-07 12:32:48.656  INFO 6 --- [pool-2-thread-1] org.onap.so.foo.Foo                      : variable: `mso-request-id`: a9b386b2-8abe-4407-b4d7-fa9959e4c251

full log:

...