Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

see also Platform Maturity Requirements (S3P).

AreaActual levelTargeted level for current releaseHow, EvidencesComments
Performance0

0

(given CLAMP is design time there is no point to adhere to L2 requirement) 

Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Beijing
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11

Participate to Stability runs Level 1

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-100

  • 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
Resiliency11

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-83

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security11
  • Reach CII passing badge, increasing test coverage as remaining item
  • AAF CADI integration
  • Infrastructure setup for js test coverage



  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage, including no critical and high known vulnerabilities>60 days old
  • 2 – CII Silver badge; internal/external communication encrypted; role-based access control and authorization for all calls based on CADI
  • 3 – CII Gold
Scalability11

Level 1 single site horizontal scaling

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-102

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability1

1

(2, if CLAMP can get more resource from the community)


  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
    ; All application logging to adhere to
    ONAP Application Logging Specification v1.2

  • 3 - Transaction tracing across components

Usability1

1

(2, if CLAMP can get more resource from the community)

CLAMP is not anticipating new API at this point, so we are technically compliant with API CVS at this point

  • 1 – user guide; deployment documentation; API documentation
  • 2 – API documentation; usability testing; tutorial documentation;

    All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines; All existing APIs must be documented in Swagger 2.0

  • 3 - UI consistency; usability testing; API Documentation

    (changed and external APIs follow policy)

  • 4 - API Documentation (all follow policy)




     

...