Ajay Lotan Thakur | 05ce5ce | 2022-09-25 20:36:16 -0700 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
| 5 | .. _aiab5g-guide: |
| 6 | |
| 7 | Aether In a Box - 5G |
| 8 | ==================== |
| 9 | |
| 10 | Setting Up Aether-in-a-Box - 5G |
| 11 | ________________________________ |
| 12 | |
| 13 | Aether-in-a-Box (AiaB) provides an easy way to deploy Aether’s SD-CORE |
| 14 | components and run basic tests to validate the installation. This guide |
| 15 | describes the steps to set up AiaB. |
| 16 | |
| 17 | AiaB can be set up with a 4G or 5G SD-CORE. We use SimApp to configure |
| 18 | the required subscribers & network slices in SD-CORE for testing core |
| 19 | functionality. |
| 20 | |
| 21 | Helm charts are the primary method of installing the SD-CORE resources. |
| 22 | AiaB offers a great deal of flexibility regarding which Helm chart |
| 23 | versions to install: |
| 24 | |
| 25 | * Local definitions of charts (for testing Helm chart changes) |
| 26 | * Latest published charts (for deploying a development version of Aether) |
| 27 | * Specified versions of charts (for deploying a specific Aether release) |
| 28 | |
| 29 | AiaB can be run on a bare metal machine or VM. System prerequisites: |
| 30 | |
| 31 | * Ubuntu 18.04 or later |
| 32 | * Kernel 4.15 or later |
| 33 | * Haswell CPU or newer |
| 34 | |
| 35 | Clone Repositories |
| 36 | __________________ |
| 37 | |
| 38 | To initialize the AiaB environment, first clone the following repository:: |
| 39 | your Gerrit ID:: |
| 40 | |
| 41 | cd ~ |
| 42 | git clone "https://gerrit.opencord.org/aether-in-a-box" |
| 43 | |
| 44 | mkdir -p ~/cord |
| 45 | cd ~/cord |
| 46 | git clone "https://gerrit.opencord.org/sdcore-helm-charts" |
| 47 | |
| 48 | .. note:: |
| 49 | Only one version of the SD-CORE (4G or 5G) can be installed in AIAB environment |
| 50 | at a time. The first time you build AiaB, it takes a while because it sets up the |
| 51 | Kubernetes cluster. Subsequent builds will be much faster if you follow below steps |
| 52 | to delete & redeploy SD-Core (4G/5G) without destroying the Kubernetes |
| 53 | |
| 54 | Running 5G Test |
| 55 | ________________ |
| 56 | |
| 57 | To deploy 5G SD-CORE using local helm charts:: |
| 58 | |
| 59 | make 5g-core |
| 60 | |
| 61 | To deploy and test 5G SD-CORE using local helm charts:: |
| 62 | |
| 63 | make 5g-test |
| 64 | |
| 65 | The above step uses gNBSim to perform Registration + UE-Initiated PDU Session |
| 66 | Establishment + User Data Packets. To test other procedures, modify *gnb.conf* |
| 67 | in *~/aether-in-a-box/sd-core-5g-values.yaml* (refer gNBSim documentation :ref:`gNB-Simulator`) |
| 68 | |
| 69 | Developer Loop |
| 70 | ______________ |
| 71 | |
| 72 | Suppose you wish to test a new build of a 5G SD-CORE services. You can deploy |
| 73 | custom images by editing ~/aether-in-a-box/sd-core-5g-values.yaml, for example:: |
| 74 | |
| 75 | images: |
| 76 | tags: |
| 77 | webui: omecproject/5gc-webui:master-7f96cfd |
| 78 | |
| 79 | To upgrade a running 5G SD-CORE with the new image, or to redeploy the 5G SD-CORE |
| 80 | with the image:: |
| 81 | |
| 82 | make reset-5g-test # delete 5G deployment if it was already started before updating image |
| 83 | make 5g-core #now this deployment will use new webui image |
| 84 | |
| 85 | Troubleshooting / Known Issues |
| 86 | ______________________________ |
| 87 | |
| 88 | Deployment Status |
| 89 | """""""""""""""""" |
| 90 | If you suspect a problem, first verify that all pods are in Running state:: |
| 91 | |
| 92 | kubectl -n omec get pods |
| 93 | |
| 94 | If the pods are stuck in ImagePullBackOff state, then it’s likely an issue |
| 95 | with image name. |
| 96 | |
| 97 | Test Failure |
| 98 | """""""""""" |
| 99 | |
| 100 | If make 5g-test fails consistently, then try to debug the issue by looking |
| 101 | at logs at amf, smf. |