Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Projects NameOOMNotes
Health CheckPASSED
  • Tested on Local microK8S with OOM

The healthcheck done on the frontend is propagated to the backend, therefore it validates both at the same time.

CLAMP ↔ DCAE (SB-01)

IN PROGRESS
  • 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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCLAMP-804
CLAMP ↔ Policy (SB-01)PASSED
  • 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, Status of the policies (SENT AND DEPLOYED)
    •                                                         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
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCLAMP-801
CLAMP ↔ SDC (SB-01)PASSED

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

CLAMP  → AAF (SB-01)PASSED
  • Tested on Local microK8s with OOM
  • Tested on SB-01, authentication successful with P12 certificate
CLAMP ↔ CDS (SB-00)IN PROGRESSThis requires additional testing on SB-01, still need the right CDS parameters

...