Versions Compared

Key

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

Table of Contents
outlinetrue

Overview

...

ScopePriorityCommitter LeadResources CommittedEpicDependencies
Do Not Break the BuildHighestYang XuYang Xu Marco Platania

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-849


oParent Update for Security VulnerabilityHighest

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-833


Use Case TestingHighesteveryone in integration team, see use case owners below

ONAP CI EnhancementHighest

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-834


Maintain ONAP Integration Testing InfrastructureHighest

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-835


S3P Testing EnhancementHigh

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-836


vCPE Use Case Test AutomationHigh

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-837


Use Case Development for vFW and ScalingHigh

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-838


CIA ProjectHigh

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-542

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-543

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-544

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-545



Use Cases


Use Case Test Cases

Lab

Responsible

EPIC

1vFW / vDNS

Intel / Windriver


2

vCPE Integration Test Case

Intel / Windriver


3

vCPE with TOSCA VNF Test Case

CMCC


4

5G - Real Time PM and High Volume Stream Data Collection - Integration Test Status

TLab


5

5G - PNF PnP - Integration Test Status

TLab
6

5G - Bulk PM - Test Status

Intel / Windriver


7

5G - OOF and PCI - Integration Test Cases

Intel / Windriver





8

Scale Out - Integration Test Cases and Status

Intel / Windriver


9CCVPN Integration Test CasesCMCC


10

vFW/vDNS HPA Regression and Enhancement Testing

(HPA & Cloud Agnostic Intent - R3 Test Plan)

Intel / Windriver


11Change Management - Flexible Designer & OrchestratorIntel / Windriver



12Change Management - Traffic Management-Intel / Windriver



13

Change Management - 5G PNF in-place software upgrade

Intel / Windriver



14Change Management - Schedule optimizationIntel / Windriver


15

BBS (Broadband Service)
BBS Use Case Tracking (Dublin Release)

Swisscom, CMCC, Huawei, Nokia
165G Slicing (scope is not clear, need to wait for TSC requirement)AT&T, Nokia, Ericsson
17vFW on ARM (no integration commitment, vendor will cover all tests)ARM, ENEA
18Model driven control loop designAT&T, NokiaTesting confirmed by AT&T
19K8S based cloud region supportIntel, VMWareTesting confirmed by Intel
20Distributed Analytics as a Service (Dublin Summary) - Edge AutomationVMWare, IntelTesting confirmed by Intel
21Consistent ID of a Cloud Region Windriver, AT&T, CMCCNeed to talk to Bin Yang about testing resource

...

  • Cross-project Continuous System Integration Testing (CSIT)
  • End-to-End (ETE) release use cases testing with VNFs with repeatability
  • CI/CD to ONAP community integration labs
  • Reference VNFs that can be used to show how the ONAP platform handles

Release Deliverables

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

ManageabilityNot Measured1, partial of 2
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
PerformanceNot MeasuredNot Measured
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Resiliency23

Will cover geo-redundancy if lab env supports it.

All Integration team will perform platform-level testing similar to:

Beijing Release Resiliency Testing Status

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
ScalabilityNot MeasuredNote Measured
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
SecurityNot MeasuredNot Measured
  • 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
Stability22

Integration team will perform platform-level testing similar to:

Beijing Release Stability Testing Status (w/ OOM)

Beijing Release Stability Testing Status (w/ HEAT)

  • 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
UsabilityNot MeasuredNot Measured
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

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 identifiedMitigation PlanContingency Plan
Need additional lab resources (RAM, disk, network bandwidth, etc.)NoneNone
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...