11 VNF Instantiation across Multi Cloud / Multi Tenant / Multi Network
VNFM supports multi-cloud, multi-tenant, and multi network deployment for DSR and SDS VNF.
List of VNF deployment of multi cloud/tenant:
Table 11-1 Multi cloud/tenant deployment
Tenant-1/Cloud-1 | Tenant-2/Cloud-2 |
---|---|
DSR-NOAM | DSR-Signaling |
DSR-NOAM | DSR-DR-NOAM |
SDS-NOAM | SDS-Signaling |
SDS-NOAM | SDS-DR-NOAM |
List of VNF deployment of multi network:
Table 11-2 Multi Network Deployment
Network-1 | Network-2 |
---|---|
DSR-NOAM | DSR-DR-NOAM |
SDS-NOAM | SDS-DR-NOAM |
Note:
- While deploying DSR Signaling/DSR DR VNF, vnfInstanceId of DSR Noam should be passed in additional params.
- While deploying SDS Signaling/SDS DR VNF, vnfInstanceId of SDS Noam should be passed in additional params.
- The "
vnfInstanceId
" is the mandatory parameter while multi-cloud/tenant VNF deployment only incase of passing OpenStack resource IDs for the XMI IPs from both NOAM VMs.
Sample Request
Sample Request Body of additional parameter changes for DSR Signaling VNF in case of multi tenant/cloud
"additionalParams": {
"xmiNetwork": {
"name": "ext-net3",
"subnet": [{
"name": "ext-net3-subnet",
"ipVersion": "IPv4"
}]
},
"imiNetwork": {
"name": "imi-private",
"subnet": [{
"name": "imi-private-sub",
"ipVersion": "IPv4"
}]
},
"xsiNetwork": [{
"name": "ext-net2",
"subnet": [{
"name": "ext-net2-sub",
"ipVersion": "IPv4"
}]
},
{
"name": "ext-net5",
"subnet": [{
"name": "ext-net5-sub",
"ipVersion": "IPv4"
}]
}
],
"ntpServerIp": "10.250.32.10",
"primaryNoamVmName": "NOAM00-32cd6138",
"noamSgName": "dsrNetworkOam_NOAM_32cd6138_SG",
"vnfInstanceId": "dsrNetworkOam-4e99a1cd-77b7-478b-9b28-32cd6138"
}