| Table of Contents | ||
|---|---|---|
|
Overview
| Project NameEnter the name of the project | Data movement as a platform |
|---|---|
| Target Release Name | Beijing Release |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Tech Mahindra |
...
DMaaP is a premier platform for high performing and cost effective data movement services that transports and processes data from any source to any target with the format, quality, security, and concurrency required to serve the business and customer needs.
Release Deliverables
...
| Deliverable Name | Deliverable Description |
|---|---|
AAF integration with Data Router | DMaap Git repository |
| Data Router source code | DMaap Git repository |
| Data Router library | ONAP Nexus repository |
| Data Router API description | ONAP wiki |
| Data Router Release Notes | ONAP wiki |
| Data Routee Documentation | DMaap Git repository |
...
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
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 | 1 | Baseline performance criteria will be defined |
|
| Stability | 1 | 1 | 72 hours soak test with random transactions |
|
| Resiliency | 2 | 2 |
| |
| Security | 0 | 21 |
| |
| Scalability | 1 | 1 | Level 1 single site horizontal scaling |
|
| Manageability | 1 | 1 | Using EELF common framework for logging |
|
| Usability | 1 | 2 | API documentation and swagger API provided |
|
...
| 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).
...
No known risks so far.
Resources
Updated
Resources
Fill out the Resources Committed to the Release centralized page .
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
...
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
- ...
...
| title | Note |
|---|
...
- .
Other Information
Vendor Neutral
...