...
OOF is currently a non-MVP project, and is an incubation project in the Beijing release cycle (seed-code is upstreamed in this release). Therefore, some of the "Actual levels" for the platform maturity indicate a level 0, which is commensurate with the project's current incubation status. The Our goal is to align with the Architecture committee's recommendation on using common tools/libraries for platform maturity, and therefore we will be dependent on the tools/libraries provided by these projects to achieve some of these targets. The Architecture Subcommittee's recommendations for the projects on achieving the platform maturity can be found here (ONAP Beijing Architecture Jan 9b.pptx).
0 | Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 0 | 1 | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-35 |
|---|
|
|
Stretch goal (Level 1)
1 – - Will need to work with the Benchmarking team to define baseline criteria for Optimization requests.
| - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
| Stability | 0 | 1 | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-36 |
|---|
|
| - 0 – none
- 1 – 72 hours component level soak w/random transactions
- 2 – 72 hours platform level soak w/random transactions
- 3 – 6 months track record of reduced defect rate
|
| Resiliency | 1 | 2 | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-37 |
|---|
|
|
Will need recommendations and support from OOM/Music teams
0 – none- Seed-code natively supports manual failure and recovery
|
(< 30 minutes)2 – automated detection and recovery (single site)3 – automated detection and recovery (geo redundancy)Security | 0 | 1 | | Jira Legacy |
|---|
- . In R2, OOF components are stateless (or can rebuild cached state during runtime), and no rollbacks are required. This may change when reservations are supported in R3 and beyond.
- Will need work with OOM/Music team to understand the tools/mechanisms they will be providing for Runtime projects for automated failure detection and recovery.
| - 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
|
| Security | 0 | 1 | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-38 |
|---|
|
|
Plan - Since the seed-code is being on-boarded as a part of Beijing release, we plan to reach 30% code coverage in R2, with a stretch goal of 50% code coverage.
- Will need help
|
for | - 0 – none
- 1 – CII Passing badge + 50% Test Coverage
- 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
- 3 – CII Gold
|
| Scalability | 0 | 1
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-39 |
|---|
|
|
Will need recommendations and support from OOM/Music teams- Need to work with OOM team to identify ways support for single site horizontal scaling.
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
| Manageability | 0 | 1
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-40 |
|---|
|
|
Will need recommendations from Logging team- Need to work with the Logging team for their recommendations. The two components of OOF (OSDF and HAS) needs to use the same logging system.
| - 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
|
| Usability | 1 | 1 | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OPTFRA-41 |
|---|
|
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|
API Incoming Dependencies
...