User Story: NF Orchestration Using SMO

[arora-sagar]

• Prerequisite
• [ ] SMO (FOCOM, NFO) and OSC components are deployed on the management cluster.
• [ ] FOCOM creates the K8s edge cloud (workload cluster) and DMS(k8S api) is brought up in this process
• [ ] FOCOM installs the necessary CRDs and Operators required to handle the NF Deployment in the desired K8S Cluster
• [ ] Cluster registration (DMS will register its information in IMS DB)
• [ ] NF deployment Kpt Packages/Helm-charts or other dependent artifacts should be available and accessible via NFO
• NF Deployment:
• [X] NFO should fetch DMS information
• [ ] NFO will receive the request for CU-CP deployment and will bring up CU-CP
• [ ] NFO will receive the request for CU-UP and DU deployment and will bring up CU-UP and DU
• [ ] We will use the KPT packages based deployment if and when ready. (Nephio)
• [ ] This will be first implemented in OSC and then ported to the Nephio.
• Integration test
• [ ] The trigger to deploy would be initiated as a Nephio O-RAN CR/REST call to NFO (for the time being).
• [ ] Stretch: Deploy NR-UE (Emulated package used in Nephio R2 and can be deployed via NFO because they are expressed as helm-charts) and make an end to end call

OSC pre-requisite task

Development of NFO

• [x] Design NFO NBI and SBI (Porch and DMS) in Django. Note: Currently no NBI APIs are defined for NFO in OSC.
• [x] Deploy OAI helm-charts via NBI of NFO
• [ ] Deploy OAI RAN NFs Via KPT packages

Timeline: Targeted for O-RAN J release and Nephio R3

External resources

• https://docs.google.com/presentation/d/1ZQSlloQ3TzXa__IMz-OvjpiMLCEZxTjRiBUQyEsdBQU/edit#slide=id.g2673cb868d0_1_0
• https://docs.google.com/document/d/1kQ0cru_ujqWM3lEjKYSWsJalzKlB6Mpv/edit

[vamshi-namilikonda]

The NFO NBI APIs goes like these as of today.

GET [http://<HOST>:<PORT>/nfo/api/v1/applications/]
POST [http:// <HOST>:<PORT>/nfo/api/v1/applications/]
PUT [http:// <HOST>:<PORT>/nfo/api/v1/applications/<app_id]
DELETE [http:// <HOST>:<PORT>/nfo/api/v1/applications/<app_id]

GET [http:// <HOST>:<PORT>/nfo/api/v1/oai/]
POST [http:// <HOST>:<PORT>/nfo/api/v1/oai/]
PUT [http:// <HOST>:<PORT>/nfo/api/v1/oai/<chart_id]
DELETE [http:// <HOST>:<PORT>/nfo/api/v1/oai/<chart_id]

[rravindran123]

The NFO NBI APIs goes like these as of today.

GET [http://<HOST>:<PORT>/nfo/api/v1/applications/]
POST [http:// <HOST>:<PORT>/nfo/api/v1/applications/]
PUT [http:// <HOST>:<PORT>/nfo/api/v1/applications/<app_id]
DELETE [http:// <HOST>:<PORT>/nfo/api/v1/applications/<app_id]

GET [http:// <HOST>:<PORT>/nfo/api/v1/oai/]
POST [http:// <HOST>:<PORT>/nfo/api/v1/oai/]
PUT [http:// <HOST>:<PORT>/nfo/api/v1/oai/<chart_id]
DELETE [http:// <HOST>:<PORT>/nfo/api/v1/oai/<chart_id]

@vamshi-namilikonda , what is the context of these APIs in the NB ?, who uses them ?, don't think this is relevant to the FOCOM/NFO i/f to get the cluster information, right ?

[arora-sagar]

NFO code commit --> https://gerrit.o-ran-sc.org/r/c/smo/o2/+/12850 OAI helm-charts used by NFO --> https://gitlab.eurecom.fr/oai/cn5g/charts/helm-charts/-/packages