| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Requirement Description
The requirement is to
...
d. Core endpoint cannot be populated in UUI, as the IP address of CNFs are available after slice allocation. (Deviation of #2 in Requirement Description)
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
General Information:
RAN and Core NF's IP addresses are assigned as below:
- If the NFs are deployed as VNFs, VNFM takes care of the IP address assignment
- If the NFs are deployed as CNFs, Kubernetes assigns a unique IP address to the pod. If it is a single container, docker daemon itself acts as a DHCP server and assigns an IP address to the container.
In both the above cases, assigning an IP address is taken care by the cloud provider itself.
In Core Slicing, netbox-ip-assign microservice is used by SDNC to assign IP address to the VF modules and VNFs. But this is not used effectively by CDS and the multicloud. Kubernetes itself assigns the IP address, moreover assigning a static IP is not a best practice in Kubernetes.
Back-haul endpoints Discovery:
...
API exposed by SO:
Get AN &CN EndPoints
Method | URL |
|---|---|
| POST | /onap/so/infra/3gppservices/v1/QueryEndPointInfo |
Request Example:
| JSON Viewer | ||
|---|---|---|
| ||
{
"subnetType": [
"AN",
"CN"
],
"coverageAreaTAList": "Beijing;Beijing;HaidianDistrict;WanshouluStreet"
} |
...
Response from SDNC:
Topology
|
4. SO ↔ AAI
API Used:
To Fetch PNF's:
...