Skip to content

Commit c38e26c

Browse files
authored
Merge pull request #15 from opennetworkinglab/maintenance
fixed host.ini for oai
2 parents f0af026 + c7caaa6 commit c38e26c

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

onramp/blueprints.rst

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -499,14 +499,14 @@ The blueprint includes the following:
499499
* Global vars file ``vars/main-oai.yml`` gives the overall blueprint
500500
specification.
501501

502-
* Inventory file ``hosts.ini`` uses label ``[oai_gnb_nodes]`` to
503-
denote the server(s) that host the gNB and label ``[oai_ue_nodes]``
504-
to denote the server(s) that host the UE. (The latter is necessary
505-
only when running in simulation mode.) The expected configuration is
506-
to run both the gNB and UE on the same server as Kubernetes (where
507-
the 5G Core runs). Another possible configuration is to co-locate
508-
the gNB and UE on one server, with the 5G Core running on a separate
509-
server.
502+
* Inventory file ``hosts.ini`` uses label ``[oai_nodes]`` to denote
503+
the server(s) that host the gNB and (when configured in simulation
504+
mode) the UE. As with gNBsim, ``[oai_nodes]`` can identify the same
505+
server as Kubernetes (where the 5G Core runs). Another possible
506+
configuration is to co-locate the gNB and UE on one server, with the
507+
5G Core running on a separate server. (Although not required in
508+
principle, the current playbooks require the gNB and simulated UE be
509+
co-located on the same server.)
510510

511511
* New make targets, ``oai-gnb-install`` and ``oai-gnb-uninstall``, to
512512
be executed along with the standard SD-Core installation (see below).

0 commit comments

Comments
 (0)