s Containerized VNF support ONAP Multiple VIMsClouds OSS

s Containerized VNF support

ONAP & Multiple VIMs/Clouds OSS BSS APP Orchestrators ONAP Multi Cloud Service (OS and K 8 S support) Edge (*) Edge (With Openstack VIM) • Support for both Openstack based Edges and K 8 S based Edges. • Support for K 8 S based Edges that do both VM and Container VNF management • Fabric Control to manage switch (Manage Stratum, d. NOS based switches) SDNC (Fabric Control) (Two logical edges – Openstack for VMs and K 8 S for containers) Edge (With K 8 S for both VMs and Containers)

ONAP & Multiple VIMs/Clouds – Push ONAP down APP Orchestrators OSS BSS ONAP - Parent Multi Cloud ONAP – Child Multi Cloud Edge (with OS) ONAP - Child Fabric Control Multi Cloud Edge (with K 8 S) Fabric Control Edge (OS) Edge (OS/K 8 S) Fabric Control

ONAP & Multiple VIMs/Clouds – Push ONAP down & Pull control up APP Orchestrators OSS BSS ONAP - Parent Multi Cloud ONAP – Child (Child SO, Child DCAE) Multi Cloud Fabric Control ONAP - Child Multi Cloud Fabric Control Regional controller sites Central Control (VIM) Openstack Edge (No local VIM) K 8 S Edge (No local VIM) Fabric Control Edge (OS) Edge (OS/K 8 S)

Architecture Sub-committee - Request • AT&T Bin Hu presented need for doing some Po. C and need for creating a repository for various companies to add code. • Discussions (as suspected) went back to Container architecture in ONAP • ARs taken: • Come out with architecture (big picture). • Flow diagrams • Where Po. C fits

Items that came up in various meetings – For Discussions 1. Co-existence of VMs and containers in NSD and granularity a) Would a VNF contain all VMs or container or is the mix needed? b) Would VMs and container can come up on same compute node? 2. TOSCA Orchestration a) Support for TOSCA capabilities to represent container workloads b) Support for Helm charts for VNFC c) Support for POD deployment spec for VNFC 3. Networking: a) ONAP controlling network across VMs and containers – Which CNI? b) Multi-Cloud plugin to program CNI 4. Placement decisions (Should not bypass OOF) a) Taking advantage of SO and OOF for placement decisions. Can SO decompose NSD to VNFC level? (Some work to be done at SO and OOF) b) Does SO call Multi-Cloud VIM for each VNFC? It needs to be for container support (Yes) c) Would all workloads in a VNF in one location or would there be requirement to put them in different regions? 5. Overlapping features between K 8 S and ONAP - Monitoring, Replication, Liveness checks etc. . Use ONAP, Use K 8 S? 6. Bare-metal containers – Yes 7. Containers in VMs – Topics for discussions 8. Support for other Container orchestration systems (Dockerswarm) & Orchestration management systems (Openshift, Rancher 2. 0 etc…) 9. Others? ? ?

Next steps • • Brainstorm with community on few items (last slide) Prepare comprehensive architecture high level picture and flows Get the approval from architecture subcommittee Identify POC scope and get approval for the same

s