K8S based Cloud Region Support

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 VNF

Test Environment

Integration Team Liaison

Showcase VNF

Test Environment

Integration Team Liaison

vFirewall

Intel/Windriver lab

@Akhila Kishore (Deactivated) and @Former user (Deleted)

EdgeXFoundry

Intel/Windriver lab

@Akhila Kishore (Deactivated) and @Kiran



Development Status

Project

PTL

JIRA Epic / User Story*

Requirements

Status

Project

PTL

JIRA Epic / User Story*

Requirements

Status

MultiCloud

@Bin Yang

ONAPARC-350: MultiCloud K8S plugin - Helm Charts supportClosed

ONAPARC-349: K8S Plugin in Multi-Cloud to follow the instantiation NB API of Multi-CloudClosed

ONAPARC-337: Multi-Cloud to support storing Cloud specific artifactsClosed

ONAPARC-348: Multi-Cloud K8S Plugin to support profiles for resource-bundle Environment and Day0 Configurations Closed

MULTICLOUD-454: Provider network support when OVN is usedClosed

ONAPARC-351: Multi-Cloud Network subplugin & OVN supportClosed

ONAPARC-364: vFirewall CSARsOpen

MULTICLOUD-409: EdgeXFoundry use caseClosed

https://lf-onap.atlassian.net/browse/ONAPARC-336MULTICLOUD-464: Day 2 configuration ClosedMULTICLOUD-502: KRD should not instantiate K8S plugin Closed

  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

https://lf-onap.atlassian.net/browse/ONAPARC-356

ONAPARC-355: K8S Cloud region reach ability information in ESR/A&AIOpen

  1. Reach ability information

  2. Plugin consume AAI information



SDC

@Ofir Sonsino

ONAPARC-335: Supporting Cloud specific artifacts in CSARsClosed

SDC-2041: SDC supports K8S plugin to add cloud specific artifacts Closed

https://lf-onap.atlassian.net/browse/SDC-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

https://lf-onap.atlassian.net/browse/ONAPARC-339

  1. Make it more cloud agnostic



Integration

@Helen Chen

https://lf-onap.atlassian.net/browse/MULTICLOUD-403

  1. Create CSIT



OOM



https://lf-onap.atlassian.net/browse/ONAPARC-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** 

Test Cases and Status



#

Test Case

Status

#

Test Case

Status

1

There should be a test case for each item in the sequence diagram

Not yet tested

2

create additional requirements as needed for each discreet step

Complete

3

Test cases should cover entire Use Case

Partially Complete

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

 Failed