...
| Project Name | Enter the name of the project |
|---|
| Target Release Name | Guilin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Nokia, Ericsson, Wipro, ChinaMobile, T-Mobile, Huawei |
...
Green color → Target level ( details see Platform Maturity below)
- Performance: Level 1
- Stability: Level 2
- Resiliency: Level 2
- Security: Level 1+
- Scalability: Level 1
- Manageability: Level 1+
- Usability: Level 1+
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Resouce and Repositories in the centralized page.
...
Anyone reading this section should have a good understanding of all the interacting modules.
Image Removed
Image Added
Platform Maturity
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 1 | 1 |
| - Level 0: no performance testing done
- Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
- Level 2: performance improvement plan created
- Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)
|
| Stability | 2 | 2
|
| - Level 0: none beyond release requirements
- Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
- Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
- Level 3: track record over 6 months of reduced defect rate
|
| Resiliency | 2 | 2 |
| - 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
|
| Security | 1 | 1+ (Most DCAE components are complaint; will address remaining in Guilin based on resource availability) |
| - Level 0: None
- Level 1: CII Passing badge
- Including no critical and high known vulnerabilities > 60 days old
- Level 2: CII Silver badge, plus:
- All internal/external system communications shall be able to be encrypted.
- All internal/external service calls shall have common role-based access control and authorization using CADI framework.
- Level 3: CII Gold badge
|
| Scalability | 1 | 1
|
| - Level 0: no ability to scale
- Level 1: supports single site horizontal scale out and scale in, independent of other components
- Level 2: supports geographic scaling, independent of other components
- Level 3: support scaling (interoperability) across multiple ONAP instances
|
| Manageability | 1 | 1+ (Except logging, all other requirements are met) |
| - Level 1:
- All ONAP components will use a single logging system.
- Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint
- Level 2:
- A component can be independently upgraded without impacting operation interacting components
- Component configuration to be externalized in a common fashion across ONAP projects
- All application logging to adhere to ONAP Application Logging Specification v1.2
- Implement guidelines for a minimal container footprint
- Level 3
- Transaction tracing across components
|
| Usability | 1 | 1+
|
| - Level 1:
- User guide created
- Deployment documentation
- API documentation
- Adherence to coding guidelines
- Level 2:
- Level 3
- Consistent UI across ONAP projects
- Usability testing conducted
- API Documentation
- Level 4
|
...
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.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|
Cloudify support for Python 3.x not available currently, expected in by Aug 2020 timeframe. This impacts migration of Cloudify and associated plugins in Guilin (REQ-373) | Continue Frankfurt version of Cloudify and Plugins under python 2.7 | None |
Fill out the Resources Committed to the Release centralized page
...