...
- ACM in UNINITIALIZED state: all elements of a ACM are in UNINITIALIZED state, all applications are not deployed and policy types are not deployed and not present in Api.
- User triggers to move ACM from UNINITIALIZED to RUNNING: all elements of a ACM are runtime-acm moves elements from UNINITIALIZED state to UNINITIALIZED_TO_PASSIVE.
- Element in UNINITIALIZED_TO_PASSIVE, all applications are getting deployed and policy types are getting created :
- participant-ks8: deploys applications
- participant-policy: creates policy types in Api and
- deploys them with Pap.
- participant-http: do nothing.
- Element ACM in UNINITIALIZED_TO_PASSIVE_ERROR state: got error during deploy.
- ACM in UNINITIALIZED_TO_PASSIVE_ERROR state: at least one element is in UNINITIALIZED_TO_PASSIVE_ERROR state.
- Element in PASSIVE state: application is deployed or a policy type is
- participant-ks8: applications are deployed.
- participant-policy: policy types are create in Api and deployed with Pap.
- participant-http: applications are not configured yet.
- ACM in PASSIVE state: all elements are moved to PASSIVE, all applications are deployed, but not configured yet. In this state, runtime-ACM triggers moves elements in from PASSIVE state to PASSIVE_TO_RUNNING.
- Element in PASSIVE_TO_RUNNING:
- participant-ks8: do nothing (maybe checks if application are running).
- participant-policy: do nothing (maybe checks if policy types are running).
- participant-http: configures applications.
- Element applications are getting configured.ACM in PASSIVE_TO_RUNNING_ERROR state: error during configuration.
- ACM in PASSIVE_TO_RUNNING_ERROR state: at least one element is in PASSIVE_TO_RUNNING_ERROR state.
- Element in RUNNING state:
- participant-ks8: applications are deployed.
- participant-policy: policy types are create in Api and deployed with Pap.
- participant-http: applications are configured.
- ACM in RUNNING state: all elements of a ACM are in RUNNING state, all applications are running.
...