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: user-00d66 and Kiran Kamineni

Contributing companies:  Intel, VMWare

Interested Operators : Verizon,  ATT

Use Case Name

Showcase VNFTest EnvironmentIntegration Team Liaison
vFirewallIntel/Windriver lab

Akhila Kishore and user-00d66

EdgeXFoundryIntel/Windriver lab

Akhila Kishore and Kiran Kamineni

Development Status

ProjectPTLJIRA Epic / User Story*RequirementsStatus
MultiCloud

Bin Yang

ONAPARC-350 - Getting issue details... STATUS

ONAPARC-349 - Getting issue details... STATUS

ONAPARC-337 - Getting issue details... STATUS

ONAPARC-348 - Getting issue details... STATUS

ONAPARC-353 - Getting issue details... STATUS

ONAPARC-351 - Getting issue details... STATUS

ONAPARC-364 - Getting issue details... STATUS

MULTICLOUD-409 - Getting issue details... STATUS

ONAPARC-336 - Getting issue details... STATUS MULTICLOUD-464 - Getting issue details... STATUS MULTICLOUD-502 - Getting issue details... STATUS
  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

ONAPARC-356 - Getting issue details... STATUS

ONAPARC-355 - Getting issue details... STATUS

  1. Reach ability information
  2. Plugin consume AAI information

SDC

Ofir Sonsino

ONAPARC-335 - Getting issue details... STATUS

SDC-2041 - Getting issue details... STATUS

SDC-2045 - Getting issue details... STATUS

  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

ONAPARC-339 - Getting issue details... STATUS

  1. Make it more cloud agnostic

IntegrationHelen Chen

MULTICLOUD-403 - Getting issue details... STATUS

  1. Create CSIT

OOM

ONAPARC-363 - Getting issue details... STATUS

  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** 

Summary SeqDia Template

Test Cases and Status


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

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

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

 FAILED

6 Comments

  1. Damian Nowak

    Updated SDC PTL to Ofir Sonsino

  2. Perry Dong

    Does this use case apply to the VFC flows?


    1. Srinivasa Addepalli

      In R4, only helm charts based application (including VNFs)  description is supported. And hence SO based flows would be supported in R4.  TOSCA and ksonnet based VNF/application description are for future releases. Since VFC expects TOSCA based description, VFC flows are not supported in this release.

  3. Perry Dong

    Thanks, Srini. One additional question, is there plan to create a VNF Helm charts requirements (similar to what VNFRQTS has done for heat template)? I don't find such work items in this page or the VNFRQTS page.

    1. Srinivasa Addepalli

      That is something in our plate. But, we will be doing towards end of Dublin release. But, note that many of the service design, onboarding requirements are similar to HEAT based VNFs, except for adding new artifact types and Day 0 configuration profiles. With respect to monitoring too, I don't see much difference from  HEAT based VNFs.  We may want to provide more options though for monitoring such as 'usage of node-exporter' or prometheus client in the VNF.   On the configuration side, we like to add additional option of configuration using K8S operators.

      Srini

      1. Perry Dong

        Thanks, Srini! These are great information.