Documentation: Update ansible_host in inventory file to simplify development (#79)

* Update ansible_host in inventory file to simplify development

Signed-off-by: Arrobo, Gabriel <gabriel.arrobo@intel.com>

* Address validation issue

Signed-off-by: Arrobo, Gabriel <gabriel.arrobo@intel.com>

* Address Copilot's comments

Signed-off-by: Arrobo, Gabriel <gabriel.arrobo@intel.com>

* Alaigned documentation based on latest Onramp changes

Signed-off-by: Arrobo, Gabriel <gabriel.arrobo@intel.com>

---------

Signed-off-by: Arrobo, Gabriel <gabriel.arrobo@intel.com>

Author: gab-arrobo

onramp/ref.rst

@@ -169,6 +169,13 @@ Each blueprint is deployed to the set of servers identified in an
 Ansible inventory file (``hosts.ini``). The following identifies the
 `host groups` that OnRamp currently supports.
 
+In the default single-node inventory, the controller host is labeled
+``node1`` even when it resolves to ``127.0.0.1`` for local execution.
+The GitHub Actions workflows in the ``aether-onramp`` repository under
+``.github/workflows`` do not use that exact aliasing scheme: the
+single-node workflows generate ``hosts.ini`` with ``localhost`` and
+``ansible_connection=local``.
+
 .. list-table::
    :widths: 25 50
    :header-rows: 1

onramp/start.rst

@@ -135,7 +135,16 @@ four things to note:
    various installation playbooks. The default version of ``hosts.ini``
    included with OnRamp is simplified to run everything on a single
    server (the one you've cloned the repo onto), with additional lines
-   you may eventually need for a multi-node cluster commented out.
+   you may eventually need for a multi-node cluster commented out. In
+   the shipped single-node example, Ansible refers to that server as
+   ``node1``; the checked-in default inventory currently maps ``node1``
+   to ``127.0.0.1`` as a placeholder for local single-node execution.
+   For an actual deployment, replace the loopback address and
+   credentials with the values for your target server. The GitHub
+   Actions workflows in the ``aether-onramp`` repository under
+   ``.github/workflows`` generate their own ``hosts.ini`` and, for
+   single-node tests, use ``localhost ansible_connection=local``
+   instead of this checked-in ``node1`` example.
 
 Set Target Parameters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -147,15 +156,23 @@ deployment.
 The first set is in file ``hosts.ini``, where you will need to give the IP
 address and login credentials for the server you are working on. At
 this stage, we assume the server you downloaded OnRamp onto is the
-same server you will be installing Aether on.
+same server you will be installing Aether on. If your checkout still
+shows ``node1 ansible_host=127.0.0.1 ...``, that is only the local
+placeholder; change it to the server's reachable management address
+before running the playbooks remotely. The checked-in example keeps the
+active inventory entry minimal and shows password-based access only as
+an optional commented example.
 
 .. code-block::
 
-   node1  ansible_host=10.76.28.113 ansible_user=aether ansible_password=aether ansible_sudo_pass=aether
+   # Optional for password-based access:
+   # node1  ansible_host=10.76.28.113 ansible_user=<username> ansible_password=<password> ansible_sudo_pass=<sudo-password>
+   node1  ansible_host=10.76.28.113 ansible_user=aether
 
-In this example, address ``10.76.28.113`` and the three occurrences
-of the string ``aether`` need to be replaced with the appropriate
-values.
+In this example, address ``10.76.28.113`` and the username ``aether``
+need to be replaced with the appropriate values. If you use password
+authentication instead of SSH keys, uncomment the optional example and
+replace the placeholder values there as well.
 
 Note that if you set up your server to use SSH keys instead
 of passwords, update the ``hosts.ini`` with your private key (accordingly

onramp/testing.rst

@@ -6,6 +6,23 @@ Blueprints </onramp/blueprints>`. These tests exercise representative
 deployment scenarios and simulated 5G workloads used throughout this
 guide.
 
+The GitHub Actions workflows in the ``aether-onramp`` repository under
+``.github/workflows`` build ``hosts.ini`` dynamically before running
+the playbooks. The single-node workflows use ``localhost`` with
+``ansible_connection=local`` and do not set ``ansible_host``. This
+lets the workflows exercise the same playbooks without requiring SSH
+access back into the runner itself.
+
+The current integration-test inventory patterns are as follows:
+
+* Quick Start, Quick Start AMP, SD-RAN, OAI, and srsRAN run as
+  single-node tests, with both ``[master_nodes]`` and the
+  blueprint-specific host group pointing at ``localhost``.
+
+This means the checked-in inventory examples and the CI-generated
+inventories are similar in structure, but they do not use identical
+host aliases.
+
 Finally, note that the integration tests run a variety of simulated 5G
 workloads, including gNBsim, UERANSIM, OAI 5G RAN (in simulation
 mode), and srsRAN (in simulation mode). Of these, gNBsim provides the