ONAP Casablanca Use Case in CMCC Lab
China Mobile: Yan Yang Intel: Haibin Huang
CMCC Lab Overview
Physical Lab Overview @CMCC
ONAP Deployment Env (POD3) Titaninum Cloud R4 (Newton), ONAP Deployment Controller nodes:2 , Compute nodes: 3 Env & VNF Env (POD5) Core Switch Titaninum Cloud 16.10 (Mitaka), OpenVPN Leaf Switch Controller nodes:2 , Compute nodes: 2 VPN Client Firewall Server LOM Management, Admin, Private, Public networks inside Leaf Switch Leaf Switch DC 1 DC 2 ONAP Deployment Leaf Switch (POD1) (POD2) Env & VNF Env VIO 4.0 (Ocata) (POD4) Controller node:2 Titaninum Cloud 16.10 (Mitaka), Titaninum Cloud 16.10 (Mitaka), Compute nodes: 6 Controller nodes:2 , Compute nodes: 2 Controller nodes:2 , Compute nodes: 9 Hardware: R5300/E9000, 3 rack servers and 1 blade server with 6 blades
Use Case Deployment @CMCC
vCPE CCVPN
CMCC Domain :Casablanca VDF Domain : Casablanca Casablanca (POD3) vCPE vCPE (POD4) OS (POD5) OS
rd Integrate with 3 Part Integrate with 3rd Part Specific Components Specific Components
vDHCP vAAA SD-WAN OTN SD-WAN OTN OS OS Controller Controller Controller Controller vBNG vGMUX vxxx (Huawei) (Huawei) (ZTE) (ZTE) OS OS OS (POD1)
Key Data @CMCC
CMCC Lab key data
ONAPs ：3
Cloud ：5 windrive(4) and (1)
Physical hardware ：73
Participating member ：8
CCVNP Use Case
CCVPN Overview
CCVPN(Cross Domain and Cross Layer VPN) by ONAP Peering Orchestration Between SPs
ONAP (CMCC) ONAP (VDF)
SOTN SD-WAN SOTN SD-WAN Controller Controller Controller Controller
uCPE vCPE Internet vCPE uCPE
Connection（ E-Line） Connection（ E-Line） UNI UNI Site Site UNI UNI Site Site
CCVPN Network Topology
Lab CMCC portal Vodafone portal
CMCC ONAP Vodafone ONAP
OTN OTN SD-WAN OTN SD-WAN Controller Controller Controller Controller Controller Server A Server B Server Server (HW) L3 (HW) (HW) (ZTE) (ZTE)
vCPE vCPE uCPE GE/10GE/OTU (HW) (ZTE) (HW) uCPE OTN OTN (ZTE) OTN network Domain A Domain B L2 (ZTE) (HW) (HW)
GE/10GE/OTU
CCVPN Test Case
Topology Discovery Service Provisioning Closed Loop
ONAP(CMCC) ONAP(VDF)
OTN OTN SD-WAN SD-WAN OTN Controller Controller Controller Controller Controller
OTN OTN OTN CPE Domain Domain vGW vGW CPE Domain 1 2 L3 L3 L2 Underlay PNF L2 Underlay (EoODU) L3 VNF Handoff Handoff VNF (EoODU) L3 PNF
CCVPN Service vCPE Use Case
vCPE Test Case
Key Test Case: ESR Registration, Model Design, Service Deployment, Service Recovery
Model ESR Service Service Design Registration Deployment Recovery
• VNF Onboarding • Vim Registration • Instantiation • VM shutdown • NS Design • VNFM Registration • Termination • Triger Healing
CPE
vGRE vINFRA Healing VNF vGMUX vBNG vGW Instantiation
vCPE NS VNF Destruction CPE
vCPE – Overall Sequence
Design Time
Run Time
Design Time
vCPE – Package Design & Distribution
SDC
4.2 E2E Service Pkg Distribution 3.Service Package Design Service CPE E2E Package SO vCPE E2E Service Package
2.NS Package Design 4.4 Query NS Pkg CPE NS NS Package Policy
1.VNF Package Upload 4.3 Query VNF Pkg GW\BNG\... VNF Package VFC Catalog NS/VNFs Package
Usecase UI
vCPE – Package Design & Distribution
VNF Package Onboarding in UUI
NS Design in SDC
NS Package Onboarding in UUI
ESR Registration
VIM Configuration
. NIC configure We can refer to [1] before “Launching instances with SR-IOV ports” pci_passthrough_whitelist = { "devname": "eth3", "physical_network": "physnet2"}
. Create aggregate $ openstack aggregate create --property sriov_nic=sriov-nic-intel-1234-5678-physnet1:1 aggr11
. Create flavor $ openstack flavor create onap.flavor1 --id auto --ram 512 --disk 40 --vcpus 4 $ openstack flavor set onap.flavor1 --property sriov_nic=sriov-nic-intel-1234-5678-physnet1:1
. Create provider network
10 MultiCloud register and HPA discovery
VIM & GVNFM Registration via ESR GUI
GVNFM Registration VIM Registration
AAI information
sriov_nic=sriov-nic-
sriov-nic-intel-1234-5678-physnet1:1 sriov-nic-mellanox-2345-6543-physnet1:1
10 Run Time
ONAP – Run Time
Lifecycle: Instantiate/terminate/heal…
3 OOF Policy
2
1 4 Multi- 5 WindRiver UUI VF-C Cloud (Openstack)
Policy
"flavorLabel":"vcpe.vgw", Customer "flavorProperties":[{ Input "hpa-feature": "sriovNICNetwork", "mandatory": "True", REST APIs "architecture": "generic", "hpa-version": "v1", Policy "directives" : [ { "type": "sriovNICNetwork_directives", Policy Creation "attributes": [ Administration {"attribute_name": "vgw_nic_type", "attribute_value": “direct"}, {"attribute_name": "vgw_provider_network", "attribute_value": “physnet1"} ] } ], "hpa-feature-attributes": [ Policy Driven { Decision & "hpa-attribute-key": "pciVendorId", Enforcement Policy DB "hpa-attribute-value": "1234", "operator": "=", "unit": "" }, Framework { "hpa-attribute-key": "pciDeviceId", "hpa-attribute-value": "5678", "operator": "=", "unit": "" }, { REST APIs/Event Driven Policy Distribution "hpa-attribute-key": "pciCount", "hpa-attribute-value": "1", "operator": ">=", "unit": "" }, { "hpa-attribute-key": "physicalNetwork", "hpa-attribute-value": "physnet1", "operator": "=", "unit": "“ } ] OOF SDC }, ]
VF-C — OOF Homing
OOF: ONAP Optimization Framework OSDF: Optimization Service Design Framework HAS: Homing Allocation Service ① VFC Policy 1. VFC sends out homing request to ② OOF(OSDF) containing resource info 2. OOF(OSDF) pulls all the related OOF- homing constraints from Policy OSDF ④ 3. OOF(HAS) check AAI database to pull
OOF - region(flavor) information HAS 4. OOF(OSDF) returns homing allocation ③ solution to VFC
AAI
OOF Homing
"flavorLabel":"vcpe.vgw", "flavorProperties":[{ "hpa-feature": "sriovNICNetwork", "mandatory": "True", "architecture": "generic", "hpa-version": "v1", "directives" : [ { "type": "sriovNICNetwork_directives", "attributes": [ {"attribute_name": “vgw_vnic_type", "attribute_value": "direct"}, {"attribute_name": “vgw_provider_network", "attribute_value": "physnet1"} ] } ], "hpa-feature-attributes": [ { "hpa-attribute-key": "pciVendorId", "hpa-attribute-value": "1234", "operator": "=", "unit": "" }, { "hpa-attribute-key": "pciDeviceId", "hpa-attribute-value": "5678", "operator": "=", "unit": "" }, { "hpa-attribute-key": "pciCount", "hpa-attribute-value": "1", "operator": ">=", "unit": "" }, { "hpa-attribute-key": "physicalNetwork", "hpa-attribute-value": "physnet1", "operator": "=", "unit": "“ } ] AAI }, Policy ]
VFC Create network and port
"type": "sriovNICNetwork_directives", "attributes": [ {"attribute_name": “vgw_vnic_type", "attribute_value": "direct"}, {"attribute_name": “vgw_provider_network", "attribute_value": "physnet1"}
a. Create network, ports # openstack network create --provider-network-type vlan --provider-physical-network physnet1 tst- network # openstack port create --name sriov-port --binding:vnic-type direct
b. Create server # openstack server create --flavor onap.hpa.flavor11 --image Ubuntu_16.04 --nic port-id= test-sriov-nic
MultiCloud
SO and VFC will call ONAP Framework Other Components
MultiCloud Framework
Plugin- Plugin- Plugin- Plugin- Pike StarlingX vmware windriver
Pike StarlingX vmware Windrvier
Thank you!