Versions Compared

Key

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

...

What is this release trying to address?

CLAMP want to consolidate Beijing achievement by

  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)
  3. using service template as Tosca as artifact received from DCAE-D to describe the Control Loop flow

CLAMP will also support the auto scale out of VF-module use case.....


Use Cases

The existing use cases are still going to be supported and additional use cases will be supported for the CasablancaRelease Casablanca Release (as defined by the Control loop sub committee: auto-scale out use case)

Minimum Viable Product

The minimum viable product that we aim to reach within R3 is to have the CLAMP application Beijing(R2) features at least running in with the new UI separation modelservice template as artifact exchanged between CLAMP and DCAE-D.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerykey in (CLAMP-76,CLAMP-179,CLAMP-189)
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Another Key long term goal is to provide a better user experience by separating clearly the UI in 2 entities : one for the design time and one for the runtimehaving more flexibility to add mico-service without code development.

A Dashboard is also going to be has been introduced to allow the user to get a quick overview of the status of running control loops.

...