2022-06-14-CWS deep dive

Present

• Williamson, Rob
• Morrisey, Scott
• Gutta, Srinva
• Brown, Leo

Discussion

• camunda application yaml
• camunda auto-deployment config
  • rough outline of auto-deployment shared
    1. Scan java classpath for .bpmn files (might be .xml as well)
    2. Parse each bpmn
    3. For each process id in each file
    4. Select on ACT_RE_PROCDEF to see if the process is present
    5. Compare db and in memory hash to determine if deployment is necessary
    6. {if hash is diff} INSERT
• apollo-camunda-orchestrator inc. bpmn
• apollo docker config
• cct-camunda-orchestrator inc. bpmn
• new relic of specific apollo orchestrator pod
• recorded memory and cpu requests (k8s and jvm config)
• k8s report

Actions

1. Backlog tickets to review Readiness / Liveness probe timeouts to be in line with the app requirements - need domain understanding
2. Increase CPU Requests for Camunda and possibly other CPU hungry services to distribute better??
3. Remove CPU limits from all services
4. Check Java XMX and XMS are in line with k8s limits
5. Find out what the defaults
6. Camunda turn off auto deployment of processes – and build in a process to update BPMN on the deployments

• test on Thursday