Versions Compared

Key

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

...

  1. achieve the Casablanca S3P requirement for Casablanca in the limits the available resources permit.
  2. making the support of new micro-service generic(no code development needed to support new mS)
    by implementing policy-models concept (together with DCAE-DS/SDC, Policy-engine).
ScopePriorityCommitter LeadCommitter LeadResources CommittedEpic Dependencies 
 CLAMP Architecture high Gervais-Martial Ngueko AT&T, Nokia 

 

  

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-260

 Policy, SDC
      
S3P  high Gervais-Martial Ngueko Nokia 

 

 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-258

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-265

 



Use Cases

The existing use cases are still going to be supported and additional use cases will be supported for the Casablanca Release (as defined by the Control loop sub committee: auto-scale out use case, BBS use case is a stretch goal depending on resources committed by interested companies)

Minimum Viable Product

The minimum viable product that we aim to reach within R4 is to have the CLAMP application Casablanca(R3) features at least running with, the new policy-model and blueprint template, as artifact exchanged between CLAMP and DCAE-D.

...