...
| 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?
...
The minimum viable product that we aim to reach within R2 is to have the CLAMP application Amsterdam (R1) features at least running in the new UI separation model. CLAMP team plans also to increase maturity level to support single site High Availability.
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 Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 2025 jqlQuery project=clamp and issuetype in (story) and fixVersion="Beijing Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
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.
| Area | Actual level | Targeted level for current release | How, Evidences | Comments | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 0 | 0 | Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Amsterdam |
| ||||||||||||||||
| Stability | 0 | 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
|
| ||||||||||||||||
| Resiliency | 1 | 1 |
|
| ||||||||||||||||
| Security | 0 | 1 | Reach CII passing badge, increasing test coverage as remaining item
|
| ||||||||||||||||
| Scalability | 1 | 1 | Level 1 single site horizontal scaling
|
| ||||||||||||||||
| Manageability | 1 | 1 | Already using EELF common framework for logging |
| ||||||||||||||||
| Usability | 1 | 1 | Documentation only for this release - Stretch to have automated API docs (Swagger)
|
|
API Incoming Dependencies
List the API this release is expecting from other ONAP component(s) releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
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) |
|---|
| Same as Amsterdam | 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 Amsterdam | API exposed by SDC to publish Closed Loop template going to DCAE | Already available | ||
| Same as Amsterdam | API exposed by Policy to create/update policies | Already available | ||
| Same as Amsterdam | API exposed by DCAE to start/stop a Closed Loop | Already available | ||
| Same as Amsterdam | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | ||
| Same as Amsterdam | API exposed by DCAE to get status of a Closed Loop | Already available |
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 |
|---|
Resources
Link toward the Resources Committed to the Release centralized page.
Release Milestone
...
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
- ...
...
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.