This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Add gNB Integrator howto #205
Closed
Closed
Changes from all commits
Commits
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
# Integrate SD-Core with an Externally Managed Radio | ||
|
||
For simplicity in managing deployments, the gNB Name and TAC can be supplied via a charm integration. This is the purpose of the sdcore-gnb-integrator charm. | ||
|
||
## Pre-requisites | ||
|
||
- A Kubernetes cluster capable of handling the load from both SD-Core and one additional container per represented gNB | ||
- [Charmed 5G Terraform modules][Charmed 5G Terraform modules] Git repository cloned onto the Juju host machine | ||
- Charmed 5g already deployed using Terraform | ||
|
||
You need to have the following information ready: | ||
|
||
- A name for the gNB | ||
- The name of the juju model for the gNB integrator | ||
- The TAC (represented in hex) that the gNB is serving | ||
- The name of the control plane model | ||
|
||
## Deploying gNB Integrator | ||
|
||
Given the following: | ||
|
||
- Model name: `gnb-integration` | ||
- GNB Name: `gnb01` | ||
- TAC: `B01F` | ||
- Control Plane Model: `control-plane` | ||
|
||
Either create a new `.tf` file, or add the following content to you existing `main.tf`. | ||
|
||
```console | ||
module "gnb01" { | ||
app_name = "gnb01" | ||
source = "git::https://github.com/canonical/sdcore-gnb-integrator//terraform" | ||
model_name = "gnb-integration" | ||
channel = "1.4/edge" | ||
config = { | ||
tac: B01F | ||
} | ||
} | ||
|
||
resource "juju_offer" "gnb01-fiveg-gnb-identity" { | ||
model = "gnb-integration" | ||
application_name = module.gnb01.app_name | ||
endpoint = module.gnb01.fiveg_gnb_identity_endpoint | ||
} | ||
|
||
resource "juju_integration" "nms-gnb01" { | ||
model = "control-plane" | ||
|
||
application { | ||
name = module.sdcore-control-plane.nms_app_name | ||
endpoint = module.sdcore-control-plane.fiveg_gnb_identity_endpoint | ||
} | ||
|
||
application { | ||
offer_url = juju_offer.gnb01-fiveg-gnb-identity.url | ||
} | ||
} | ||
``` | ||
|
||
[Charmed 5G Terraform modules]: https://github.com/canonical/terraform-juju-sdcore-k8s |
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.
Re-reading this, it doesn't make sense to force the gNB integrator to the same k8s cluster as the core, so maybe this is not needed?