DRAFT PROPOSAL FOR COMMENTS
...
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
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.
...
| Name | Description | Version |
|---|---|---|
| Consul | Consul is a distributed, highly-available, and multi-datacenter aware tool for service discovery, configuration, and orchestration. | 1..4.3 |
| OpenResty | OpenResty® is a full-fledged web platform that integrates the standard Nginx core, LuaJIT, many carefully written Lua libraries, lots of high quality 3rd-party Nginx modules, and most of their external dependencies. It is designed to help developers easily build scalable web applications, web services, and dynamic web gateways. | 1.11.2.3 |
| Redis | Redis is an in-memory data structure store, used as a database, cache and message broker. | 3.2.8 |
...
| 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.