Versions Compared

Old Version 10

changes.mady.by.user Srinivasa Addepalli

Saved on

compared with

New Version 11

changes.mady.by.user Srinivasa Addepalli

Saved on

Key

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

Purpose

Enable support for deploying Virtualized and Containerized networking workloads in Kubernetes based Cloud regions through MultiCloud/k8s plugin.


Scope:

  • Enable the support for Helm charts based deployment.
  • Show case using vFirewall use case.
    • Show case Legacy model (where firewall, traffic generator and sink are VMs)
    • Show case Hybrid model (where firewall is a container, traffic generator as a container and sink is VMs)
  • Show case using EdgeXFoundry use case.


Owner: Former user (Deleted) and Kiran

Contributing companies:  Intel, VMWare

Interested Operators : Verizon,  ATT

Use Case Name

Showcase VNFTest EnvironmentIntegration Team Liaison
vFirewallIntel/Windriver lab

Akhila Kishore (Deactivated) and Former user (Deleted)

EdgeXFoundryIntel/Windriver lab

Akhila Kishore (Deactivated) and Kiran


Development Status

ProjectPTLJIRA Epic / User Story*Requirements
MultiCloud

Bin Yang

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-350

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-349

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-337

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-348

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-353

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-351

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-364

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-409

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-336
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-464
  1. Add Helm Charts support
  2. Manage and store Cloud artifacts
  3. Enable the K8s plugin in MultiCloud/Framework project
  4. OVN4NFV Integration.
  5. Modify plugin functional tests to support EdgeXFoundry
  6. SDC Client to receive cloud specific artifacts (e.g Helm)
AAI
James Forsyth

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-356

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-355

  1. Reach ability information
  2. Plugin consume AAI information
SDC

Ofir Sonsino

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-335

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2041

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2045

  1. Add non-HEAT files support to SDC
  2. Add K8S plugin artifact support
  3. Add User and Password for multicloud client
SO

Seshu Kumar Mudiganti

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-339

  1. Make it more cloud agnostic
IntegrationHelen Chen

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-403

  1. Create CSIT
OOM

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-363

  1. Create Helm chars for deploying the K8s plugin service

*Each Requirement should be tracked by its own User Story in JIRA 

Testing

Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links


End to End flow to be Tested

**This should be a summary level Sequence diagram done in Gliffy** 

Gliffy
nameSummary SeqDia Template
pagePin1

Test Cases and Status


#Test CaseStatus
1There should be a test case for each item in the sequence diagram

Status
titleNot yet tested

2create additional requirements as needed for each discreet step

Status
colourGreen
titleComplete

3Test cases should cover entire Use Case

Status
colourYellow
titlePartially Complete

4  Test Cases should include enough detail for testing team to implement the test

 

Status
colourRed
titleFailed