aboutsummaryrefslogtreecommitdiffstats
path: root/common/src/main/resources/tosca/KubernetesControlLoopElementType.yaml
AgeCommit message (Collapse)AuthorFilesLines
2022-02-18Rename TOSCA Control Loop to ACMliamfallon1-76/+0
This commit renames the TOSCA Control Loop functionality in CLAMP to Automation Composition Management. This review is a direct renaming review and, as everything is renamed together it is large. Issue-ID: POLICY-3939 Change-Id: I28f0a6dd889bf3570a4c1365ae9e71fc58db6d6c Signed-off-by: liamfallon <liam.fallon@est.tech>
2021-07-09Update CL TOSCA definitions, Add Guidance UCliamfallon1-10/+10
This patch makes some minor updates to the TOSCA definitions, mainly the introduction of common parameters. It also introduces the first draft of a "Gentle Guidance" control loop that can be used for testing, verification, documenting and explaining the TOSCA control loop framework. Issue-ID: POLICY-3341 Change-Id: Ie2d5379bd362f088d7c500402f83745cc7e6aca3 Signed-off-by: liamfallon <liam.fallon@est.tech>
2021-07-05Add ONAP standard Control Loop Element typesliamfallon1-0/+76
The Policy, DCAE, HTTP, Kubernetes, and CDS Control Loop Elements run on participants delivered with and packaged with ONAP. These TOSCA files define the properties for Control Loop Elements on these participants as TOSCA node types. Developers who wish to run Control Loop Elements on these participants write a TOSCA Topology Template, which uses the Control Loop Element Node Types defined in these files. These Node type definitions should be preloaded into the Runtime database, which will be done in a future review. Issue-ID: POLICY-3341 Change-Id: Icc565bdfa1a59e1c1c551f13c48348ee6a8a4e27 Signed-off-by: liamfallon <liam.fallon@est.tech>