Age | Commit message (Collapse) | Author | Files | Lines |
|
Refactor Supported ACM element types
and align element type version in all examples
Issue-ID: POLICY-4512
Change-Id: Ic810fc1a98237d1b6fb816dccb1fcbe61a675c1e
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>
|
|
Issue-ID: POLICY-4538
Change-Id: I9f6d8830f64ef1178d3e20c7d00374156a84b59e
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>
|
|
Issue-ID: POLICY-4225
Change-Id: Ib069dec0acfdd85e45659deffb45398f7eae5e54
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>
|
|
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>
|
|
Issue-ID: POLICY-3696
Change-Id: If01447c94e5f86144cbf3e244f2c1f977e931a32
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
The constraiont for greater or equal (>=) should be greater_or_equal,
not greater-or-equal.
Also, we need a startDelay parameter in order to synchronize the control
loop element starts.
Issue-ID: POLICY-3676
Change-Id: I20ecbafb1205c8af5364e75ac36a2cb879b9fe47
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Add policy deployment and undeployment to the policy-participant
Allow user to specify pdpGroup and pdpdType as part of the
deployment or undeployment of policies
Change-Id: I8b37ee96305d35db0784cde3e4564150feaf477d
Issue-ID: POLICY-3584
Signed-off-by: Wayne Dunican <wayne.dunican@est.tech>
|
|
Currently, the Policy Participant only stores the policy to policy-api.
It does not distribute the policy.
This commit adds a parameter for the PDP group to the Policy Framework
Control Loop Element metadata.
Issue-ID: POLICY-3508
Change-Id: Ia182b4ea08ac1d3aec9cca4509f8e33723c80fc5
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
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>
|
|
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>
|
|
This file contains the fundamental concepts that must exist in the TOSCA
universe in order for a Control Loop to be defined in TOSCA
Issue-ID: POLICY-3341
Change-Id: I4c1be9162b84f42388e56fea051a07f901bf92a6
Signed-off-by: liamfallon <liam.fallon@est.tech>
|