CLAMP Metadata Automation Composition Management using TOSCA
CLAMP supports the definition, deployment, and life cycle management of automation composition elements using Metadata described in TOSCA.
- Automation Composition Management: Architecture and Design
- ACM States
- Participant Replica State
- Automation Composition Type State
- Automation Composition Element Type State
- Automation Composition Instance State
- Automation Composition Element Instance State
- Automation Composition State with fail and timeout
- Automation Composition Instance Sub State
- How State are saved in DB
- Automation Composition Instance DeployState
- Automation Composition Instance Lock State
- Automation Composition Instance Sub State
- Defining Automation Compositions in TOSCA for CLAMP
- CLAMP TOSCA Automation Composition APIs and Protocols
- CLAMP TOSCA Automation Composition Components: Design and Implementation
- Allowed operations in ACM
- ACM user guide
- Participant developer guide
- Automation Composition Participants
- Design considerations for a participant
- Interfaces to Implement
- Abstract class AcElementListenerV3
- Abstract class AcElementListenerV2
- Abstract class AcElementListenerV1
- APIs to invoke
- In/Out composition Properties
- In/Out instance Properties
- Example of Implementation
- Allowed state from the participant perspective
- AC Element states in failure scenarios
- Handle states and failure scenarios from the participant perspective
- Clamp ACM Integration Tests
Note
Policy/CLAMP was merged into the Policy Framework in the Honolulu release of ONAP. Prior to that release, it was a separate project. The release notes for CLAMP when it existed as a separate project are located below.