Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablana |
| Project Lifecycle State | Core |
| Participating Company | Amdocs, AT&T, Bell Canada, etc. |
Scope
What is this release trying to address?
During the Casablanca release OOM will further the "Production" aspects of ONAP deployments by enabling geographic distribution, backup & restores, and elimination of extraneous database instances. In addition, during this release the OOM team will start to transfer ownership of OOM artifacts to the project teams should that wish to do so and accept the inherent responsibility of doing so.
Use Cases
OOM isn't impact by, nor does it impact ONAP use cases.
Minimum Viable Product
All of the changes being proposed enhance existing OOM capabilities and none are required to have a viable product.
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.
Epics
Stories
Longer term roadmap
OOM will evolve to improve the production qualities of ONAP deployments and enable a wider variety of Cloud types including Kubernetes native public clouds.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| Helm charts | Further enhancements to the existing set of ONAP helm charts. |
| Helm charts | Examples of custom deployment specifications to enable new features like auto-scaling. |
| Documentation | Read-the-docs documentation of new features. |
Sub-Components
The Helm repo requested by the OOM team during the Beijing release is required (See LF #53102).
Architecture
High level architecture diagram
Not applicable. OOM is the ONAP manager not an ONAP component.
Platform Maturity
OOM has already and will continue to provide capabilities to the project teams to fulfill 'platform maturity' but in itself can't achieve any of these goals. As for usability, no significant changes are planned to the OOM documentation. Test coverage doesn't apply as this is a DevOps project without traditional source code.
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.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | *N/A | *N/A |
| |
| Stability | *N/A | *N/A |
| |
| Resiliency | *N/A | *N/A |
| |
| Security | *N/A | *N/A |
| |
| Scalability | *N/A | *N/A |
| |
| Manageability | *N/A | *N/A |
| |
| Usability | 1 | 1 | docs updated as required |
|
*N/A - as mentioned above, OOM will support other projects to achieve their S3P requirements
API Incoming Dependencies
None.
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 |
|---|---|---|
| Kubernetes | Cloud Manager | 1.8.10+ |
| Helm | Cloud Package Manager | 2.8.2+ |
| Consul | Health Monitor / State Management | latest |
The Integration team only tests with a Rancher deployment of K8s.
Testing and Integration Plans
Testing continues to be done by deploying ONAP and monitoring Robot automated tests including health checks.
Gaps
N/A
Known Defects and Issues
List of all known project bugs:
Risks
As OOM is fully functional as is there are no significant risks to project.
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Team Internal Milestone
N/A
Documentation, Training
- No significant changes to the existing OOM documents are planned.
- The following is the current OOM document structure:
- ONAP Operations Manager Project
- OOM Quick Start Guide
- OOM User Guide
- OOM Developer Guide
- OOM Cloud Setup Guide
- Release Notes
- ONAP on Kubernetes with Rancher
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.