DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out |
|---|---|---|---|---|---|---|---|---|
| Link toward the detailed API descriptionAAF | Authentication and Authorization Framework | TBD | March 08 2010 | TBD |
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
Third Party Products Dependencies
...
| Publishing | API used to post a message to the Topic | Sept 11 2017 | March 08 2018 | DMaap API |
| Subscribing | API used to subscribe a message from the Topic | Sept 11 2017 | March 08 2018 | DMaap API |
| Provisining | API for creating,deleting and listing the administrative objects | Sept 11 2017 | March 08 2018 | DMaap API |
| Admin API | API for the admin access | Sept 11 2017 | March 08 2018 | DMaap API |
Third Party Products Dependencies
| Name | Description | Version |
|---|---|---|
| AJSC | Java services container | 1.0.0 |
| Kafka | Distributed messaging platform | 0.8.2.1 |
| Zoo Keeper | Centralized service for maintaining configuration information | 3.4.6 |
| Spring | Spring Framework | 1.4 |
| Docker | Container engine | 1.12 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
Gaps
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.
...
- Unit test: Unit tests has atleast 30% code coverage.
- Functional test: Leverage the robot framework infrastructure to provide the functional test.
- Integration test: Support integration team to provide the end to end integration test.
- All the above should be automation tests run on the LF Jenkins Infrastructure.
Gaps
No gaps identified so far
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...