The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Deliverable Name | Deliverable Description | Deliverable Location |
---|---|---|
CCSDK Source Code | Source code for CCSDK project | ONAP gerrit |
CCSDK Maven Artifacts | Compiled code that can be referenced in other projects as maven dependencies | ONAP Nexus |
CCSDK Docker Containers | Docker containers associated with SDNC project:
| ONAP Nexus |
Documentation | User and developer guides | ONAP Wiki |
CCSDK CI/CD automation | Scripts to automate compilation and deployment of maven artifacts and docker containers | ONAP gerrit ONAP Jenkins |
Sub-Components
Subcomponents of each ONAP project may be found on the Resources and Repositories (Deprecated) page on this wiki. Please see the CCSDK section of that page for subcomponent list of CCSDK.Please see the INFO.yaml files associated with each repo as the authoritative sources of information - https://gerrit.onap.org/r/admin/repos/q/filter:ccsdk
Architecture
High level architecture diagram
...
Please fill out the centralized wiki page: Guilin Honolulu Release Platform Maturity
API Incoming Dependencies
...
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.
N/A - CCSDK does not have direct interfaces of its own. It is tested as part of its client (SDNC)
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.
...
None
Known Defects and Issues
Please refer to "Bugs" section above
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).
Please update any risk on the centralized wiki page - Guilin Honolulu Risks
Resources
Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information - https://gerrit.onap.org/r/admin/repos/q/filter:ccsdk
Release Milestone
The milestones are defined at the Release LevelPlanning: Honolulu and all the supporting project agreed to comply with these dates.
...
Please update the following centralized wiki:Frankfurt Honolulu Documentation
That includes
- 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
- ...
...