...
The following are the dependencies for the project based on the scope for the Beijing Release. The required dependencies have been identified based on the current homing requirements for the vCPE use case, and the potential dependencies are tentative dependencies that may exist based on how the information required for homing (e.g., Hardware Platform Enablement, VIM attributes) is available.
Image Removed
The dependency graph in a wiki-editable format
| Gliffy Diagram |
|---|
|
gliffy | | |
|---|
| size | 900 |
|---|
| name | oof-dependencies |
|---|
|
...
OOF Alignment with ONAP Target Architecture (Projects view):
Image Removed
OOF-HAS High level architecture diagram:
view):
Source: original image from 2018-01-09 version of the ONAP Beijing Architecture slides from the Architecture Tiger Team Contributions section in the Architecture Tiger Team wiki page.
Image Added
OOF-HAS High level architecture diagram:
Image Added
Source: Slide from the presentation: FCAPS Telemetry - "Standardized Infrastructure Class statistics Model" (at the developer workshop: ONAP Project Developer Event: September 25 - 28, 2017, Saclay, France).Image Removed
Sequence Diagram showing OOF interaction with other ONAP components during the Service Instantiation workflow of SO:
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 0 | 1 | | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OPTFRA-35 |
|---|
|
- 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 |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| 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 |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OPTFRA-37 |
|---|
|
- Seed-code natively supports manual failure and recovery. 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 |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OPTFRA-38 |
|---|
|
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 with CII badging.
| - 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 |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OPTFRA-39 |
|---|
|
- 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 |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OPTFRA-40 |
|---|
|
- 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 |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OPTFRA-41 |
|---|
|
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|
...
