...
The other ONAP projects CLAMP depends on are:
- SDC/DCAE-D : Rest based interface exposed by the SDC, Distribution of service to DCAE + SDC UX UI SDKDistribution of Templates to CLAMP via SDC distribution client jar
- DCAE: Rest based interface exposed by DCAE, Common Controller Framework, DCAE microservices onboarded (TCA, Stringmatch, Holmes (optional))
- Policy: Rest based interface (the Policy team provide a "jar" to handle the communication), both XACML and Drools PDP, APIs to App-C/VF-C/SDN-C
- DMaaP: Message bus within DCAE and cross-ONAP
- VNF use cases : defines what type(s) of control loop(s) can be implemented and configured by CLAMP
...
•CLAMP is separated in 2 areas, which are currently (in seed code) both supported by a single application:
- Design Time(Cockpit/UI to define to Configure the templates)
- the Templates are pushed to (service template) are defined in DCAE-D and distributed to CLAMP by SDC. The template templates format is TOSCA. Aside of the service template the corresponding blueprint , those blueprints will be pushed/provisioned, by SDCis also generated by DCAE-D and pushed, by SDC, to DCAE orchestration engine.
- policies (configuration and operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
- The DCAE team needs to provide models to Policy team in order for the Configuration policy to be built.
- Run time(DCAE-Policy, grabbing events and triggering policies based actions)
- In the first release of CLAMP, the triggering to deploy(and then effectively start the closed loop) a blueprint will be manual (via CLAMP cockpit) an automatic deployment based on an event will come in future release.
- The CLAMP cockpit will support the following action at runtime:
- start (start the provisioned Closed Loop on DCAE)
- stop (stop a provisioned Closed loop on DCAE)
...
| 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 AmsterdamBeijing |
| ||||||||||||||||||
| Stability | 1 | 01 | 1 (assumption is that 72 hour soak test will be done by Integration team testing); not separate testing will be done at component level | Participate to Stability runs Level 1
Participate to Stability runs Level 1
|
| |||||||||||||||||
| Resiliency | 1 | 1 |
|
| ||||||||||||||||||
| Security | 01 | 1 |
|
| ||||||||||||||||||
| Scalability | 1 | 1 | Level 1 single site horizontal scaling
|
| ||||||||||||||||||
| Manageability | 1 | 1 Already using EELF common framework for logging(2, if CLAMP can get more resource from the community) |
| |||||||||||||||||||
| Usability | 1 | 1 | Documentation only for this release - Stretch to have automated API docs (Swagger)
| (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 Beijing | 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 Beijing | 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)template) | Already available | ||
| API exposed by Policy to create/update guard policies (used for scale out use case operational policies) | ongoing | TBD | ||
| Same as Beijing | API exposed by Policy to create/update policies | Already available | ||
| Same as Beijing | API exposed by DCAE to start/stop a Closed Loop | Already available | ||
| Same as Beijing | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | ||
| Same as Beijing | API exposed by DCAE to get status of a Closed Loop | Already available |
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
|
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
| Risk identified | Mitigation Plan | Contingency Plan | |||
|---|---|---|---|---|---|
| new policy api(and contents) for guard policies creation not defined yet | |||||
| "vf_module_id" usage for scale out use case not yet completely confirmed | implement textbox to manually enter target parameter(for policy api call) | use the textbox to enter the value of whatever vf_module id's we need to make the CL works | Risk identified | Mitigation Plan | Contingency Plan
Resources
Link toward the Resources Committed to the Release centralized page.
Release Milestone
...