From c7caaa6e1edc74a72005166c313f82a6024775d4 Mon Sep 17 00:00:00 2001 From: Larry Peterson Date: Thu, 1 Aug 2024 10:39:59 -0700 Subject: [PATCH] fixed host.ini for oai Signed-off-by: Larry Peterson --- onramp/blueprints.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/onramp/blueprints.rst b/onramp/blueprints.rst index f1d53f9..c3a5ed7 100644 --- a/onramp/blueprints.rst +++ b/onramp/blueprints.rst @@ -499,14 +499,14 @@ The blueprint includes the following: * Global vars file ``vars/main-oai.yml`` gives the overall blueprint specification. -* Inventory file ``hosts.ini`` uses label ``[oai_gnb_nodes]`` to - denote the server(s) that host the gNB and label ``[oai_ue_nodes]`` - to denote the server(s) that host the UE. (The latter is necessary - only when running in simulation mode.) The expected configuration is - to run both the gNB and UE on the same server as Kubernetes (where - the 5G Core runs). Another possible configuration is to co-locate - the gNB and UE on one server, with the 5G Core running on a separate - server. +* Inventory file ``hosts.ini`` uses label ``[oai_nodes]`` to denote + the server(s) that host the gNB and (when configured in simulation + mode) the UE. As with gNBsim, ``[oai_nodes]`` can identify the same + server as Kubernetes (where the 5G Core runs). Another possible + configuration is to co-locate the gNB and UE on one server, with the + 5G Core running on a separate server. (Although not required in + principle, the current playbooks require the gNB and simulated UE be + co-located on the same server.) * New make targets, ``oai-gnb-install`` and ``oai-gnb-uninstall``, to be executed along with the standard SD-Core installation (see below).