Versions Compared

Key

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

...

Platform Maturity

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.

AreaActual levelTargeted level for current releaseHow, EvidencesComments
Performance00Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Amsterdam
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01 (assumption is that 72 hour soak test will be done by Integration team testing); not separate testing will be done at component level

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)
Security01

Reach CII passing badge, increasing test coverage as remaining item

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

  • 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
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
Manageability11Already using EELF common framework for logging
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11

Documentation only for this release - Stretch to have automated API docs (Swagger)

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

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

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


API Incoming Dependencies

...


List the API this release is expecting from other ONAP component(s) releases.
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.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outSame as AmsterdamAPI exposed by SDC to get list of Alarms and service information'sDate for which the API is reviewed and agreedTo fill outAlready availableLink toward the detailed API description
Same as AmsterdamAPI exposed by SDC to publish Closed Loop template going to DCAE
Already available
Same as AmsterdamAPI exposed by Policy to create/update policies 
Already available
Same as AmsterdamAPI exposed by DCAE to start/stop a Closed Loop
Already available
Same as AmsterdamAPI exposed by DCAE to trigger the deployment/undeployment of a Control Loop template
Already available
Same as Amsterdam API exposed by DCAE to get status of a Closed Loop
Already available

API Outgoing Dependencies

...

Risk identifiedMitigation PlanContingency Plan



Resources

Link toward the Resources Committed to the Release centralized page.

Release Milestone

...

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.