The Platform Maturity requirements are a set of non-functional requirements with the goal of improving the overall ONAP platform. The current areas covered include:
- Performance
- Stability
- Resiliency
- Security
- Scalability
- Manageability
- Usability
These requirements are also called S3P (Stability, Security, Scalability, Performance).
Beijing Release
Beijing's Platform Maturity Requirements: Platform Maturity Requirements (aka Carrier Grade)
The summary of priorities and levels are at Platform Maturity Level proposal 13Dec2017v2.pdf
Project status for Platform Maturity in Beijing: Beijing Release Platform Maturity
Casablanca Release
In preparation for Casablanca, we are gathering feedback on the platform maturity requirements here: Casablanca Platform Maturity S3P Planning
Dublin Release (draft)
Summary
Due to the significant number of other requirements (functional & non-functional) in Dublin, most platform maturity requirement levels are unchanged from Cassablanca. The TSC-level Dublin requirements related to platform maturity are:
- Footprint Optimization
- Document as You Code
- Service Mesh (currently NO-GO)
- Upgrade Capabilities
- Geo-redundancy
- Logging Capabilities
Details
Specific requirement levels & guidance for each platform maturity category can be found on the following sub-pages:
- Performance
- Stability
- Resiliency
- Security
- Scalability
- Manageability
- Usability