...
- Platform Maturity (i.e., S3P items)
- Resiliency
- Level 1 - test only based on the work from Beijing
- Scalability
- Level 0
- Stability
- Level 1 will be a regression run on Casablanca release - anticipate this to be test only
- Level 2 requirement is expected to be covered by the Integration team.
- Security
- Required Level 1
- reach Reach CI bagging badging passing level
- encrypted Encrypted communication enable https support. sdc will work in a mixe mode http interface will continue working but internal comunication will be done using https.
- aaf integration is a strach stretch goal based on the a risk from portal.
- Performance
- level 0 no work required.
- Manageability
- level 1
- align with onap logging spec 1.2
- Usability
- level 1
- User guide created update
- Deployment documentation update
- API documentation update
- All new API’s must adhere to the ONAP API Common Versioning
- Resiliency
- Documentation updates (readthedocs) for Casablanca, such as, but not limited to:
- Release Notes.
- enhance Enhance the available documentation to cover more of the application functionality and usability.
- functional Functional requirments:
- HPA
- SDC will support the work done to support HPA in ONAP with the help from intel.
- Change Management
- SDC will support the work being done for the change management work
- SDC will enhance our capability in designing workflows and complete the E2E flow between SDC and so with the help from Amdocs.
- Scaling
- SDC will support the work being done for the scaling work.
- 5G/PNF
- the PNF support in sdc will be based on the capabilities from Beijing, no additional work is planned.
- Architecture Alignment
- sdc will start creating an infrastructure to support RTC
- start supporting the the sol004 csar pckage
- HEAT support
- sdc will continue to support the heat based deployment
- Testing
- enhance the sdc csit test scope
- create cd testing for the sdc sub-components workflow and dcae-ds
- add unit test coverage for the ui and reach 10% coverage
- Enhancementsenhancements
- add more functionality to the sdc generic designer support
...
CCVPN(Cross Domain and Cross Layer VPN) USE CASE
OpenSource Access Manager (OSAM) Use Case
SDC will continue to support:
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 0 | 0 |
| |
| Stability | 1 | 2 |
| |
| Resiliency | 1 | 1 |
| |
| Security | 1 | 1+ AAF integration and https support |
| |
| Scalability | 0 | 0 |
| |
| Manageability | 1 | 1+loggin alignement with 1.2 loging spec |
| |
| Usability | 1 | 1 |
|
API Incoming
...
Dependencies
List the API this release is expecting from other 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.
...
| 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 description |
...
| Portal | user management APIs | crou api for user management | avilable | exposed by portal sdk |
| destribution client | apis for retriving artifacts from catalog | download artifacts | avilable | exposed by sdc part of external apis. |
API Outgoing Dependencies
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||||
|---|---|---|---|---|---|---|---|---|---|
| dmaap | using Cambria client | api for pushing and retrieving notifications | avilable | sdk | 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 description |
Third Party Products Dependencies -TBD
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 | |||
|---|---|---|---|---|---|
| Cassandra | Open-source distributed storage system | 2.1.19 | |||
| Docker | VM container | ||||
| ElasticSearch | Search framework | 2.4.6 | |||
| titan | Open-source, distributed graph database | 1.0.0 | |||
| Jetty | Open-source application server | | |||
| Ubuntu | Open-source software operating system | 16.0.4-LTS | |||
| kibana | analytic disply server | | |||
| vnc | vnc server used for ui testing | | To fill out | To fill out | To fill out
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.
- validate uses cases and pairwise testing of sdc with other components
- enhance the csait to include more tests
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 | ||
|---|---|---|---|
| N/A | N/A | To fill out | To fill out |
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 materialize (contingency).
| Risk identified | Mitigation Plan | Contingency Plan | |||
|---|---|---|---|---|---|
| sdc aaf integration | none | move integration to dublin | To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
- 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...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
...