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 cluster(workload cluster) and deploys DMS(K8S API), NFO distributed components (ConfigSync).
• [ ] FOCOM installs NFDeployment and NFConfig CRDs required to handle the NF Deployment in the desired K8S Cluster
• [ ] Cluster registration (DMS will register its information in IMS DB)
• [ ] NF and its operator's Kpt Packages should be accessible via NFO

NF Deployment:

• [X] NFO should fetch DMS information
• [X] NFO will receive the request to deploy OAI-RAN operator and will bring up OAI-RAN operator
• [X] NFO will receive the request for CU-CP deployment and will bring up CU-CP
• [X] NFO will receive the request for CU-UP and DU deployment and will bring up CU-UP and DU
• [ ] Query NF Deployment status

NF Termination

• [ ] NF Termination request received by NFO
• [ ] Verify NF Deployment (Termination) status

Integration test

• [ ] Deploy all the RAN Operator and NFs via NFO Rest calls
• [ ] Terminate NF

Software development Task

Development of NFO (https://github.com/o-ran-sc/smo-o2/tree/master/nfo/k8s)

• [ ] Design NFO NBI and SBI (Porch and DMS) in Django. Note: No NBI APIs are defined for NFO in OSC.
  • [ ] To instantiate NF
  • [ ] To query NF deployment status
  • [ ] To terminate NF

Development in Nephio components

• [ ] Query NF actual/current deployment/running status via NFDeployment CR or packageVariant/packageRevision
• [ ] Auto approval for NF termination to avoid manually removing all package revisions.

External resources

• https://docs.google.com/presentation/d/1ZQSlloQ3TzXa__IMz-OvjpiMLCEZxTjRiBUQyEsdBQU/edit#slide=id.g2ef80c0e1e5_0_0
• https://github.com/o-ran-sc/smo-o2/tree/master/nfo/k8s

[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