- There seems to be no way in TOSCA_lab to generate a blueprint with multiple dcae.nodes.policy nodes attached to the component node. We need that behavior in R2.
- TOSCA_lab needs to be enhanced to support creating multiple nodes in the blueprint with the new node-type of dcae.nodes.policies that contains the policy_filter data structure that mimics the PDP /getConfig API to allow the component developer attaching any varying collection of policies to the component.
- lower priority - we need an option in TOSCA_lab to separate the generation of the component blueprint (from component spec) from the generation of the policy models (from policy spec) because
- the relationship is many-to-many between the policies and components – there is no way to have that defined in a single spec
- the same policy can be applicable to more than one component => should be modeled upfront and then just attached to the component
- decoupling the development of the blueprint of the component from the policy structure will simplify the onboarding process of the component into DCAE Controller
- relates to
-
SDC-2620
Alternative manual setting for generating Blue Print in TOSCA-lab
-
- Closed
-
-
DCAEGEN2-249
variable collection of policies per component in DCAE
-
- Closed
-
-
DCAEGEN2-346
R2 DCAE-Controller to stop merging policies into app config and deliver the whole policy body objects to component
-
- Closed
-