Issue-ID: POLICY-4827
Signed-off-by: rameshiyer27 <ramesh.murugan.iyer@est.tech>
Change-Id: I834b2cf5680e813c0551a2622b0b80142091e32c
the ACM elements.
Here we are defining various timeout properties and startPhase parameter that are common for all the AC elements.
the ACM elements.
Here we are defining various timeout properties and startPhase parameter that are common for all the AC elements.
- Note: This node type value can be customised if the user wants to change the default name. Please refer the
- "Configure custom namings for TOSCA node types" section of the Automation Composition Runtime design and implementation.
+ Note:
+ This node type value can be customised if the user wants to change the default name. Please refer the "Configure custom namings for TOSCA node types"
+ section of the Automation Composition Runtime design and implementation.
org.onap.policy.clamp.acm.K8SMicroserviceAutomationCompositionElement:
This node type is used to define AC elements that are associated with kubernetes operations. It is further derived from the
org.onap.policy.clamp.acm.K8SMicroserviceAutomationCompositionElement:
This node type is used to define AC elements that are associated with kubernetes operations. It is further derived from the
Primitive node type for defining Automation composition definitions that comprises one or more AC elements in it.
The AC definition of this type will be created under the Node templates.
Primitive node type for defining Automation composition definitions that comprises one or more AC elements in it.
The AC definition of this type will be created under the Node templates.
- Note: This node type value can be customised if the user wants to change the default name. Please refer the
- "Configure custom namings for TOSCA node types" section of the Automation Composition Runtime design and implementation.
+ Note:
+ This node type value can be customised if the user wants to change the default name. Please refer the "Configure custom namings for TOSCA node types"
+ section of the Automation Composition Runtime design and implementation.
.. literalinclude:: files/acm-nodetypes.yaml
:language: yaml
.. literalinclude:: files/acm-nodetypes.yaml
:language: yaml
In that scenario the message AUTOMATION_COMPOSITION_DEPLOY has been sent two times.
Configure custom namings for TOSCA node types
In that scenario the message AUTOMATION_COMPOSITION_DEPLOY has been sent two times.
Configure custom namings for TOSCA node types
-+++++++++++++++++++++++++++++++++++++++++++++
+*********************************************
The node type of the AC element and the Automation composition can be customised as per the user requirement.
These customised names can be used in the TOSCA node type definitions of AC element and composition. All the
The node type of the AC element and the Automation composition can be customised as per the user requirement.
These customised names can be used in the TOSCA node type definitions of AC element and composition. All the
-runtime:
- acmParameters:
- toscaElementName: customElementType
- toscaCompositionName: customCompositionType
+ runtime:
+ acmParameters:
+ toscaElementName: customElementType
+ toscaCompositionName: customCompositionType
If there are no values provided for customisation, the default node types "org.onap.policy.clamp.acm.AutomationCompositionElement"
and "org.onap.policy.clamp.acm.AutomationComposition" are used for the AC element and composition by the runtime-acm.
If there are no values provided for customisation, the default node types "org.onap.policy.clamp.acm.AutomationCompositionElement"
and "org.onap.policy.clamp.acm.AutomationComposition" are used for the AC element and composition by the runtime-acm.
-customNaming:
- toscaElementName: customElementName
- toscaCompositionName: customCompositionName
-
+ customNaming:
+ toscaElementName: customElementName
+ toscaCompositionName: customCompositionName
Design of managing messages
Design of managing messages