-
Notifications
You must be signed in to change notification settings - Fork 24
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
Changes to adapt to R2 cluster configurations #11
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
0e09eec
Removing capacity and data network not used in r2
josephthaliath 66db7fc
Adding README details
josephthaliath db508db
updating readme
josephthaliath 9bce7c6
updating according to new cluster setup
josephthaliath 9667031
Changes to readme file
josephthaliath File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,100 @@ | ||
# OAI Packages | ||
|
||
Packages for deploying the following are stored here | ||
Packages for deploying the following are stored in the folder | ||
|
||
- OAI RAN custom controller | ||
- OAI CU-CP | ||
- OAI CU-UP | ||
- OAI DU | ||
- OAI UE SIM | ||
- Network for RAN and Core deployments | ||
- Workload cluster for RAN and Core deployments | ||
|
||
PackageVariant and PackageVariantSets for deploying OAI RAN are also stored in this folder. | ||
|
||
# Steps to manually deploy OAI RAN on Nephio | ||
|
||
Note: Scripts to automatically deploy OAI RAN on Nephio, will be available here: https://github.com/nephio-project/test-infra/tree/main/e2e/tests/oai | ||
|
||
## Step 0: Prerequisite | ||
|
||
1. Nephio should be installed. | ||
2. Verify Network required for OAI RAN and Core should should be installed. | ||
Perform the following to verify in the Nephio management cluster. | ||
3. Catalog repository need to be registered. | ||
Since the OAI RAN packages are in workloads/oai of https://github.com/nephio-project/catalog.git repository, | ||
we need to register the repository with --directory option | ||
|
||
e.g. kpt alpha repo register --namespace default https://github.com/nephio-project/catalog.git --directory=workloads/oai | ||
|
||
Also the following tags need to be created for upstream repository(https://github.com/nephio-project/catalog.git) used: | ||
1. workloads/oai/oai-ran-operator/v1 | ||
2. workloads/oai/pkg-example-cucp-bp/v1 | ||
3. workloads/oai/pkg-example-cuup-bp/v1 | ||
4. workloads/oai/pkg-example-du-bp/v1 | ||
5. workloads/oai/pkg-example-ue-bp/v1 | ||
|
||
```bash | ||
kubectl get networks | ||
``` | ||
Verify output as shown below. | ||
|
||
```console | ||
NAME REPO_STATUS | ||
vpc-cu-e1-srl True | ||
vpc-cudu-f1-srl True | ||
vpc-internal-srl True | ||
vpc-internet-srl True | ||
vpc-ran-srl True | ||
``` | ||
3. OAI core components should be deployed before deploying OAI RAN. | ||
Steps are mentioned here: https://github.com/OPENAIRINTERFACE/oai-packages/blob/r2/README.md | ||
|
||
|
||
## Step 2: Deploy OAI RAN NF operator | ||
|
||
Execute the command as shown below in Nephio Management cluster | ||
|
||
```bash | ||
kubectl apply -f package-variants/oai-ran-operator.yaml | ||
``` | ||
Check OAI RAN operators pods are in running state in all clusters. | ||
|
||
```bash | ||
kubectl get pods -n oai-ran-operators | ||
``` | ||
|
||
## Step 3: Deploy OAI RAN NFs | ||
|
||
Deploy OAI CU CP using the below command in Nephio Management cluster | ||
|
||
```bash | ||
kubectl apply -f package-variants/oai-cucp.yaml | ||
``` | ||
Check OAI CU CP pod is in running state in regional cluster. | ||
|
||
```bash | ||
kubectl get pods -n oai-ran-cucp | ||
``` | ||
Deploy OAI CU UP using the below command in Nephio Management cluster | ||
|
||
```bash | ||
kubectl apply -f package-variants/oai-cuup.yaml | ||
``` | ||
|
||
Check OAI CU UP pod is in running state in edge cluster. | ||
|
||
```bash | ||
kubectl get pods -n oai-ran-cuup | ||
``` | ||
Deploy OAI DU using the below command in Nephio Management cluster | ||
|
||
```bash | ||
kubectl apply -f package-variants/oai-du.yaml | ||
``` | ||
|
||
Check OAI DU pod is in running state in edge cluster. | ||
|
||
```bash | ||
kubectl get pods -n oai-ran-du | ||
``` |
6 changes: 3 additions & 3 deletions
6
...ds/oai/packagevariants/edge-oai-cucp.yaml → workloads/oai/package-variants/oai-cucp.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,16 @@ | ||
apiVersion: config.porch.kpt.dev/v1alpha1 | ||
kind: PackageVariant | ||
metadata: | ||
name: edge-oai-cucp | ||
name: regional-oai-cucp | ||
spec: | ||
upstream: | ||
repo: catalog | ||
package: pkg-example-cucp-bp | ||
revision: v1 | ||
downstream: | ||
repo: edge02 | ||
repo: regional | ||
package: oai-ran-cucp | ||
annotations: | ||
approval.nephio.org/policy: initial | ||
injectors: | ||
- name: edge02 | ||
- name: regional |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have found apply-replacements with delimiters to be very fragile, I would avoid them if possible (maybe a future update, or eventually I would hope these become unnecessary with the implementation of CEL for function inputs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure @johnbelamaric , we will consider it in the next updates.