Page Comparison

 Work in progress

...

Schema that currently can by used by Policy to generate form to configure Micro-service policy

{
  "MyTestModelNameConfiguration": {
    "param1": "java.lang.String:defaultValue-NA:required-true:MANY-false",
 "param2": "java.lang.String:defaultValue-NA:required-false:MANY-true",
  "param3": "java.lang.String:defaultValue-NA:required-false:MANY-false",
  "param4": "java.lang.String:defaultValue-NA:required-false:MANY-true",
  "param5": "java.lang.String:defaultValue-NA:required-false:MANY-true",
  "param6": "java.lang.String:defaultValue-NA:required-false:MANY-false"
 }
}

Micro-service policy (instance)

...

1. Deployment Artifact design using SDC DCAE-D

   • In this step user should design and add to service 2 deployment artifacts:

     1. AC blueprint (DCAE_BLUEPRINT)

     2. Policy model (example: policy.yaml)

2. Distribution of CSAR containing Policy model and AC blueprint  (SDC)

   • Both Policy and Clamp should receive Artifact distribution notification.

     1. Gliffy
        name Policy Model saving (Policy) pagePin 9

         

     2. Gliffy
        name CL model saving (Clamp) pagePin 5

        
        

3. AC configuration (CLAMP)

   Gliffy
   name Generic AT Policy Configuration pagePin 1

   
   
   • Policy should extract logic of creating forms for configuring Policy using micro-service policy schema (in this confluence it's called Policy SDK)
   • Clamp should use Policy SDK to create generic form out of saved micro-service policy schema.

4. Action Policy configuration (CLAMP)

5. CL submit (CLAMP)

6. CL deploy (CLAMP)

...