Page Comparison

Currently ACM-Runtime fetches "maxStatusWaitMs" from properties file, uses that value to calculate the timeout for all operations.

What can be implemented:

Add more specific value for each operation in properties file as defaultFor each operation, continue to use the maxStatusWaitMs property as default value
Add specific value for each operation in composition definition or into the instance that override the default value

application.yaml

Code Block

language	yml

runtime:
  topics:
    operationTopic: policy-acruntime-participant
    syncTopic: acm-ppnt-sync
  participantParameters:
    heartBeatMs: 20000
    maxStatusWaitMs: 200000
    primeTimeoutMs: 200000
    deprimeTimeoutMs: 200000
    deployTimeoutMs: 1000000
    undeployTimeoutMs: 200000
    updateTimeoutMs: 1000000
    migrateTimeoutMs: 1000000
    deleteTimeoutMs: 200000

Proposed solution 1

Add specific value for each operation in composition definition into metadata.

Example of composition definition

service template

Code Block

language	yml

tosca_definitions_version: tosca_simple_yaml_1_3
  metadata:
    primeTimeoutMs: 200000
    deprimeTimeoutMs: 200000
    deployTimeoutMs: 1000000
    undeployTimeoutMs: 200000
    updateTimeoutMs: 1000000
    migrateTimeoutMs: 1000000
    deleteTimeoutMs: 200000

Proposed solution 2

Add specific value for each operation into the instance.

Example of composition instance

composition instance

Code Block

Proposed solution 3

Add specific value for each operation into the instance element.