...
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Beijing Release |
| Project Lifecycle State | Incubation.( Refer to ONAP Charter, section 3.3 Project Lifecycle for further information) |
| Participating Company | AT&T, ZTE, Nokia.... (TBC) |
Scope
What is this release trying to address?
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | Deliverable location |
|---|---|---|
| CLAMP Docker container | Docker images available on nexus3 | Nexus3 docker registry |
| Source Code | Code of the Designer and run time of CLAMP | CLAMP git repository |
| Deployment scripts | Scripts that can be used to help with the container instantiation and configuration | CLAMP git repository |
| Property Files | Properties files that can be used to tune the configuration of CLAMP depending on the environment | CLAMP git repository |
| Documentation | Release specific documentation (Release Note, user guide, deployment guide) provided through readthedocs | CLAMP git repository |
Sub-Components
There is no currently no sub-components in CLAMP, the R2 application embeds both the designer and runtime parts.
...
CLAMP will thus control the typical following control loop flow within ONAP :
Platform Maturity
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.
| Performance | 0 | TBD |
| |
| Stability | 0 | 2 (assumption is that 72 hour soak test will be done by Integration team testing); not separate testing will be done at component level |
| |
| Resiliency | 1 | 1 |
| |
| Security | 0 | 1 |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1 |
| |
| Usability | 1 | 1 |
|
API Incoming Dependencies - To Be Reviewed for Beijing
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | API exposed by SDC to get list of Alarms and service information's | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| API exposed by SDC to publish Closed Loop template going to DCAE | ||||
| API exposed by Policy to create/update policies | ||||
| API exposed by DCAE to start/stop a Closed Loop | ||||
| API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | ||||
| API exposed by DCAE to get status of a Closed Loop |
API Outgoing Dependencies
API this release of CLAMP is delivering to other ONAP Component(s) releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| N/A |
Third Party Products 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 |
| Docker | Container engine | 1.12 |
| MariaDB | database container | 10.1.11 |
| Spring boot | Spring boot Framework dependencies | 1.4.1 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
| Testing/Integration | limited testing of final product |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...
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 |
|---|---|---|
| Availability of SDC UI/UX SDK | Keep SDC team in the loop to follow up on the SDK | Fall Back to Loose integration or Temporary independent UI |
Resources
Link toward the Resources Committed to the Release centralized page.
...
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | sdc | sdc UI/UX SDK |
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...