...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Honolulu |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, CMCC, IBM, Tech Mahindra, ZTE |
Scope
What is this release trying to address?
- to address the S3P requirements, especially security vulnerabilities
- to fix the issues reported by other projects and users
- to support all the use cases (as a common service)
- to provide access to new version of ONAP APIs via MSB
- to address the S3P requirements, especially security vulnerabilities
- to fix the issues reported by other projects and users
Use Cases
The existing use cases and new use cases in the Honolulu release.
...
| Deliverable Name | Deliverable Description |
|---|---|
| Executable | Binaries, Docker Images and Helm charts. |
| API description | Introduction of MSB APIs and how to set up a MSB development environment. |
| Documentation | Installation manual, user guide, etc. |
| Release Note | Release note of the release |
| Source Code | The source code of the sub-components listed below. |
Sub-Components
Please refer to the Resources and Repositories page.see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:msb
Architecture
High level architecture diagram
...
- OOM deploy/start/stop ONAP components.
- Registrator watches the kubernetes event.
- Registrator reads the service definition from kubernetes deployment specs.
- Registrator sends service endpoints to MSB discovery when ONAP apps are deployed by OOM.
- Registrator registers service endpoint info to MSB. It also updates the service info to MSB when ONAP components are stopped/restarted/scaled by OOM
Platform Maturity
Guilin Honolulu Release Platform MaturityMaturity
API Incoming Dependencies
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
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:msb
Release Milestone
The milestones are defined at the Release LevelPlanning: Honolulu and all the supporting project agreed to comply with these dates.
...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
Please refer to : Honolulu Documentation
Other Information
Vendor Neutral
...
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.