The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Support planned requirments
Requirements
Test Automation
...
- Test Automation
CMCC, HuaweiJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-337 - CNTP
HuaweiJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-339
TSC must have
| Requirement | JIRA Story | Commitment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| REQ-380 |
| Huawei | ||||||||
| REQ-361 |
| Huawei | ||||||||
| REQ-351 |
| Huawei | ||||||||
| REQ-349 |
| Huawei |
Minimum Viable Product
- Add support for discover and auto-register of schema
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=cli and issuetype in (epic) AND fixVersion = "Guilin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=cli and issuetype in (story) AND fixVersion = "Guilin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
As CLI is critical in devops environment, in future, CLI will be extended to use in VNF boot scripts and Integration projects to make the ONAP integration point smoother and easier.
Release Deliverable
Deliverable Name | Deliverable Description |
|---|---|
| CLI Nexus zip archive | ZIP archive used to install the CLI manually |
| CLI docker container | Docker container to run the ONAP command and will integrate into demo environment |
| Documentation | Developer guide User guide Release notes Architecture open-cli-schema-1.0 specification |
Sub-Components
NIL
Architecture
High level architecture diagram
...
Following sample YAML shows the YAML file used to create the microservice in Open-O using CLI
openo microservice-create
Platform Maturity
Please fill out the centralized wiki page:Frankfurt Guilin Release Platform Maturity
API Incoming Dependencies
...
NOTE: This project delivers CLI and not API
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.
Gaps identified | Impact |
|---|---|
| NIL | NIL |
Known Defects and Issues
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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
NO
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- 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
- ...
...