Skip to content
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

fixed host.ini for oai #15

Merged
merged 1 commit into from
Aug 1, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions onramp/blueprints.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down