Page Comparison

• Tested on local Clamp to Windriver DCAE (10.12.7.33:30471)

Deploy / Undeploy

test DONE with TCA blueprint

• Tested on SB-01, issue detected

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CLAMP-804

• After the fixes new test with TCA, DCAE deploy operation has been started on DCAE as we can see here:
• Image Added
• Operation has been reported by DCAE as SUCCESSFUL as we can see hereImage Added

• Undeploy has been tried as well and was successfully executed by DCAEImage Added
• Bug found for undeploy status

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CLAMP-807

  but there is a workround

• Tested on local Clamp to Windriver Policy (

• 10.12.6.1:30210) Submit / Deploy OK - Stop / Restart OK  - PDP group selection and update in the different policies OK - Policy model synchronization, so policies available for loop instance OK - UI generation from policy models OK

• Tested on SB-01,

• Policy synchro (Dynamic policies based on tosca model) OKImage Added
• Status of the policies (SENT AND DEPLOYED) after having added a frequency limiter policy (tested with Apex too)
  
  • Image Added                                                        Submit / Deploy

• • OK - Stop / Restart

• • OK  - PDP group

• • selection and update in the different policies OK - Policy model synchronization, so policies available for loop instance OK - UI generation from policy models OK.               Bug found and Fixed

    Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CLAMP-801

  • Bug found when re-submitting the policies

    Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CLAMP-808

    but there is a workaround

Tested on SB-01, Distribution done with the new DCAE blueprint TCA, the loop template was available, so it was possible to create a loop instance and submit to policy

Image Added

Artifacts deployed 2 so it's well ok for CLAMP, the template is well in the CLAMP DB

Image Added

It prooves the communication with DCAE at this point is also ok, artifact well deployed by SDC on DCAE

• Tested on Local microK8s with OOM
• Tested on SB-01, authentication successful with P12 certificate
• Image Added
• All permissions are well retrieved
• Image Added

• Tested Locally by Vidya
• Tested on SB-01
• Sdc distribution of the right artifact (triggering CDS), the one selected here:
• Image Added
• After creating a Loop instance from that template, we have added an APEX policy model (got from policy), the policy config UI well show the CDS info for the payload field:
• Image AddedThe remaining bug in that area is

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CLAMP-809