...
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.
- Platform Maturity Requirements (S3P)-Dublin targets/guides on implementation
Area | Actual Level | Targeted Level for current Release | How, Evidences | Minimum Levels (Dublin) | Comments |
---|
Performance | 1 | 1 | DMaaP Message Router Performance Test Results | - Closed-loop projects: Level 2
- All other projects: Level 0 (Stretch goal: Level 1)
| - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
Stability | 1 | 1 | 72 Hour Stability Testing | | - 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 | 2 | 2 | Recovery in case of a failure was supported by the Kubernetes and manual recovery was verified.Refer the screenshot for details. DMAAP_Message_Router_Resiliency_Test.jpg
| - Runtime Projects: Level 2 (stretch goal Level 3)
- NOTE: For Dublin, the building blocks will be put in place for Level 3 geo-redundancy, and a few projects will pilot it
- All other Projects: Level 1 (stretch goal Level 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 |
| - Platform Level 2
- Additional recommendations:
| - 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 | 1 | 1 | Met the single site horizantal scaling | - Runtime Projects: Level 1
- NOTE: For Dublin, the building blocks will be put in place for Level 2 geographic scaling, and a few projects will pilot it
- All other Projects: Level 0
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
Manageability | 1 | 1 | DMaaP uses EELF logging framework through the application | - All Projects: Level 2
- Stretch Goal: Level 3
| - 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 | DMaaP documentation is availablle at http://onap.readthedocs.io/en/latest/submodules/dmaap/messagerouter/messageservice.git/docs/index.html | - All Projects: Level 2
- Stretch Goal: External APIs also follow the Versioning Strategy
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|
API Incoming 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 | To fill out | To fill out | To fill out |
---|
AJSC | Java services container | ? 3.0.6-oss |
Kafka | Distributed messaging platform | ? 0.11.0 |
Zoo Keeper | Centralized service for maintaining configuration information | ? 3.4.6 |
Spring | Spring Framework | ? 1.4 |
Docker | Container engine | ? 1.12 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...