-
Notifications
You must be signed in to change notification settings - Fork 36
Update o-ran-integration.md #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
17263a9
3d18518
65e5b1f
f046ef9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -109,7 +109,7 @@ As of this release, the O-RAN Alliance has not specified O2ims provisioning inte | |
| The primary role of the NFO and DMS services is to provide for the lifecycle management of the cloud deployments for O-RAN NFs. These services have identified the following O-Cloud capabilities that are planned to be developed using Nephio capabilities: | ||
|
|
||
| - NF Deployment Lifecycle Management | ||
|
|
||
| - NF Termination Lifecycle Management | ||
| #### NF Deployment Lifecycle Management | ||
|
|
||
| ##### Introduction | ||
|
|
@@ -123,7 +123,27 @@ NF Deployment Lifecycle Management services implemented using Nephio capabilitie | |
| {{% alert title="Note" color="primary" %}} | ||
|
|
||
| In R3 Nephio use cases and component architectures have been defined for the Deploy O-RAN NF use case. | ||
| In R3, NFO supports OAI O-RAN(OCU-CP, OCU-UP, ODU) NF deployments using the REST APIs below. | ||
|
|
||
| ## input will be packagevariant of OAI NF. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't this should be a level 2 heading and I don't understand what it means.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @liamfallon , these are the API's of NFO to trigger OAI NF deployment. In R3 we don't have FOCOM support so NFO talks directly with Porch over the API. |
||
|
|
||
| ##### NFO API For OAI DU NF Deployment: | ||
|
|
||
| POST: BASE_URL/nfo/api/v1/operator/du/ | ||
| GET: BASE_URL/nfo/api/v1/operator/du/ | ||
| DELETE: BASE_URL/nfo/api/v1/operator/du/ | ||
|
|
||
| ##### NFO API For OAI CU_CP NF Deployment: | ||
|
|
||
| POST: BASE_URL/nfo/api/v1/operator/cucp/ | ||
| GET: BASE_URL/nfo/api/v1/operator/cucp/ | ||
| DELETE: BASE_URL/nfo/api/v1/operator/cucp/ | ||
|
|
||
| ##### NFO API For OAI CU_UP NF Deployment: | ||
|
|
||
| POST: BASE_URL/nfo/api/v1/operator/cuup/ | ||
| GET: BASE_URL/nfo/api/v1/operator/cuup/ | ||
| DELETE: BASE_URL/nfo/api/v1/operator/cuup/ | ||
| {{% /alert %}} | ||
|
|
||
| ##### Deploy O-RAN NF | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.