...
- achieve the Casablanca S3P requirement for Casablanca in the limits the available resources permit.
- 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).
Scope | PriorityPrioriryPPriority | Committer LeadCommitter Lead | Resources Committed | Epic | Dependencies | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CLAMP Architecture | high | Gervais-Martial Ngueko | AT&T, Nokia |
|
| Policy, SDC | ||||||||||
S3P | high | Gervais-Martial Ngueko | Nokia |
|
Use Cases
|
Use Cases
The existing 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 ProductMinimum 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.
...
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
see also Platform Maturity Requirements (S3P).
Area | Actual level | Targeted level for current release | How, Evidences | Comments | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Performance | 0 | 0 (given CLAMP is design time there is no point to adhere to L2 requirement) | Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Beijing |
minimum level for Dublin is 0 except for Control Loop projects. | ||||||||||||||||
Stability | 11 | 2 | Participate to Stability runs Level 1
Integration Team is responsible to run the platform test to prove level 2. |
minimum level for Dublin:2 see Stability levels | ||||||||||||||||
Resiliency | 1 | 1 (given CLAMP is design time there is no point to adhere to L2 requirement) |
|
| Security | 1 | 1 |
| ||||||||||||
Scalability | 1 | 1 | Level 1 single site horizontal scaling
|
| ||||||||||||||||
Minimum Levels (Dublin)
| ||||||||||||||||||||
Security | 1 | 1 | same as in Casablanca, not enough resource to allocate to this effort. | see Security Levels | ||||||||||||||||
Scalability | 1 | 1 | Level 1 single site horizontal scaling
|
Minimum Levels (Dublin)
| ||||||||||||||||
Manageability | 1 | 1 (2, if CLAMP can get more resource from the community) |
Minimum Levels (Dublin)
| Manageability | 1 | 1 (2, if CLAMP can get more resource from the community) | 2 – ability to upgrade a single component; tracing across components; externalized configuration management | |||||||||||||
Usability | 1 | 1 (2, if CLAMP can get more resource from the community) | CLAMP is not anticipating new API at this point, so we are technically compliant with API CVS at this point |
|
API Incoming Dependencies
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
Same as Casablanca | API exposed by SDC to get list of Alarms and service information's | Date for which the API is reviewed and agreed | Already available | Link toward the detailed API description |
Same as Casablanca | SDC Client(jar library provided by SDC team) used to get service template (describing control loop flow) and blueprint id( to know which blueprint has been distributed to DCAE for this Control Loop template) | Already available | ||
API exposed by Policy to create/update guard policies (used for scale out use case operational policies) | ongoing | TBDTBD | ||
API exposed by Policy to create/update policies | ongoing | TBD (new set of api based on policy-models) | ||
Same as Casablanca | API exposed by DCAE to start/stop a Closed Loop | Already available | ||
Same as Casablanca | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | ||
Same as Casablanca | API exposed by DCAE to get status of a CLAMP deployed µS | Already available | ||
API exposed by DCAE to get status of all µS | ongoing | TBD |
API Outgoing Dependencies
...
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
Name | Description | Version |
---|---|---|
AJSC | java container | 6 |
AJSC-Camunda | Camunda integration into AJSC | 6 |
Camel | framework to define routing and mediation rules | 2.22.1 |
Docker | Container engine | 1.12 |
MariaDB | database container | 10.1.11 |
Spring boot | Spring boot Framework dependencies | 1.4.1 |
...
Risk identified | Mitigation Plan | Contingency Plan | |
---|---|---|---|
new policy api(and contents) for CRUD operations on policies not defined yet | use old policy API | create config. policy the old("R3 release") way | |
blueprint generated by DCAE-D (SDC) might not be compatible with DCAE | keep current manual blueprint onboarding in SDC (as VFI). | manually created blueprint with correct format manually on boarded in SDC and distributed to CLAMP and DCAE. | |
new DCAE API to get status of µS not yet defined | use current DCAE api | monitor only µS created by CLAMP |
Resources
Link toward the Resources Committed to the Release centralized page.
Release Milestone
...