...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverFrunkfurt |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended. | ATT, China Mobile, Intel, VMware, Wind River |
Scope
What is this release trying to address?
1, Align to S3P and security requirements and Architecture.
2, Enhance MultiCloud support to StarlingX 2.0 which offer a k8s cluster cloud platform by default.
Enhance MultiCloud support to Wind River Cloud Platform which is based on StarlingX 2.0
Requirements
vFW/vDNS
vCPE
TSC must have :
- Document current upgrade component strategy
- SECCOM Perform Software Composition Analysis - Vulnerability tables
- SECCOM Password removal from OOM HELM charts
- SECCOM HTTPS communication vs. HTTP
Minimum Viable Product
Enhanced MultiCloud Plugins Plugin for StarlingX, Wind River, Pike, FCAPS,
Enhanced MultiCloud Plugin for Wind River
Enhanced MultiCloud Plugin for k8s
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
| Deliverable Name | Deliverable Description | |
|---|---|---|
| To fill out | To fill outDocker Images | Docker images for all Multi-VIM/Cloud components |
| Documentations | Developer and user documentations for all Multi-VIM/Cloud components | |
| Maven Artifacts | Maven Artifacts for all Multi-VIM/Cloud components | |
| Release Note | Release Note cover all Multi-VIM/Cloud components | |
| Source Code | Source code for all Multi-VIM/Cloud components |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Anyone reading this section should have a good understanding of all the interacting modules.
The Diagram below shows how Multi-VIM/Cloud fits into ONAP architecture in a high level view
The Diagram below depicts the interaction between Multi-VIM/Cloud and related ONAP components
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.
...
List the API this project is expecting from other projects.
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.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| 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 |
API Outgoing Dependencies
...
| eventListener/v5 | VES collector event publish APIs | N/A since It is ready now | N/A since It is ready now | https://lf-onap.atlassian.net/wiki/download/attachments/16242677/ves.html?version=1&modificationDate=1503378662000&api=v2 |
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| OpenStack Proxy endpoint | OpenStack APIs (align to newton release) with proxied endpoints exposed by each plugin (OpenStack, VIO) | Ready Since Amsterdam Release | Ready Since Amsterdam Release | |
| VFC orientied APIs | abstract APIs for VFC which is inherited from OPENO for each plugin (OpenStack, VIO) |
| Ready Since Amsterdam Release | Ready Since Amsterdam Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html | ||
| OOF oriented APIs | Capacity check to filter out those underlying VIM/Cloud without adequate resources for VNF placement | Ready Since Beijing Release | Ready Since Beijing Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
| VIM/Cloud LCM API | Registry API is used to discover infrastructure's resources, including HPA and register them into AAI | Ready Since Amsterdam Release | Ready Since Amsterdam Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
| FCAPS configuration API | FCAPS configuration API is to provision VESagent with VES collector endpoint, metric to collect, event to report, etc. | Ready Since Beijing Release | Ready Since Beijing Release | |
| SO oriented APIs | Generic API for SO to adapt to various VIM/Cloud type with MultiCloud plugin | Ready Since Dublin Release | Ready Since Dublin Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
Third Party Products Dependencies
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 | To fill out | To fill out | To fill out|
|---|---|---|---|---|---|
memcached | Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) | 1.4.33-1 | |||
rabbitmq-server | RabbitMQ is an implementation of AMQP, the emerging standard for high performance enterprise messaging. The RabbitMQ server is a robust and scalable implementation of an AMQP broker | 3.6.6-1 | |||
uwsgi | uWSGI is a fast, self-healing and developer/sysadmin-friendly application container server | 2.0.17 | |||
celery | Celery is an asynchronous task queue based on distributed message passing | 4.0 | |||
keystoneauth1 | library for authenticating to an OpenStack-based cloud | 2.18.0 | |||
Django | A high-level Python Web framework that encourages rapid development and clean, pragmatic design. | 1.9.6 | |||
djangorestframework | A powerful and flexible toolkit for building Web APIs | 3.3.3 | |||
httplib2 | A comprehensive HTTP client library, httplib2 supports many features left out of other HTTP libraries. | 0.9.2 | |||
python-memcached | a Python interface to the memcached memory cache daemon | 1.59 | |||
onappylog | onap python logging library | 1.0.6 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
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.
- Unit Test: 50% above coverage
- Functional test: CSIT to cover major functionalities
- 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
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 | |
|---|---|---|
| To fill out | To fill outN/A | N/A |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...