a few missed doc references in renaming baremetal to multinode (#559)

ansible/roles/create-inventory/tasks/main.yml

@@ -1,7 +1,7 @@
 ---
 # create-inventory tasks
 #
-# For Bare Metal clusters:
+# For Multi node clusters:
 # * First machine is bastion
 # * Following 3 machines are controlplane nodes (master)
 # * Remaining are worker nodes (depending upon worker_node_count)
@@ -85,7 +85,7 @@
       cluster_name: "vlan{{ (vlan_info.stdout | from_json).table[0].vlan_id }}"
     when: lab == "performancelab"
 
-- name: Bare metal cluster and remote worker node cluster type tasks
+- name: Multi node cluster and remote worker node cluster type tasks
   when: cluster_type == "mno" or cluster_type == "rwn"
   block:
   - name: MNO/RWN - Set inventory variables

docs/deploy-mno-performancelab.md

@@ -1,12 +1,12 @@
-# Deploy a Bare Metal cluster via Jetlag from a Performance Lab Bastion Machine quickstart
+# Deploy a Multi node cluster via Jetlag from a Performance Lab Bastion Machine quickstart
 
 Assuming you received an Performance lab allocation named `cloud99`, this guide will walk you through getting a multi node cluster up in your allocation. For purposes of the guide the systems in `cloud99` will be Dell r650s. You should run Jetlag directly on the bastion machine. Jetlag picks the first machine in an allocation as the bastion. You can [trick Jetlag into picking a different machine as the bastion](tips-and-vars.md#override-lab-ocpinventory-json-file) but that is beyond the scope of this quickstart. You can find the machines in your cloud allocation on
 [the Performance lab wiki](http://wiki.rdu3.labs.perfscale.redhat.com/)
 
 _**Table of Contents**_
 
 <!-- TOC -->
-- [Deploy a Bare Metal cluster via Jetlag from a Performance Lab Bastion Machine quickstart](#deploy-a-bare-metal-cluster-via-jetlag-from-a-performance-lab-bastion-machine-quickstart)
+- [Deploy a Multi node cluster via Jetlag from a Performance Lab Bastion Machine quickstart](#deploy-a-bare-metal-cluster-via-jetlag-from-a-performance-lab-bastion-machine-quickstart)
   - [Bastion setup](#bastion-setup)
   - [Configure Ansible vars in `all.yml`](#configure-ansible-vars-in-allyml)
     - [Lab \& cluster infrastructure vars](#lab--cluster-infrastructure-vars)

docs/disconnected-ipv6-cluster-access.md

@@ -1,6 +1,6 @@
 # Accessing a disconnected/ipv6 cluster deployed by Jetlag
 
-Jetlag includes the installation of a HAProxy instance on the bastion machine with ipv6/disconnected environment setup.  The HAProxy instance allows you to proxy traffic over ports 6443, 443, and 80 into the deployed disconnected cluster. Port 6443 is for access to the cluster api (Ex. oc cli commands), and ports 443/80 are for ingress routes such as console or grafana. This effectively allows you to reach the disconnected cluster from your local laptop. In order to do so you will need to edit your laptop's `/etc/hosts` and insert the routes that map to your cluster. While running the `setup-bastion.yml` playbook, an example copy of the hosts file is dumped into `bastion_cluster_config_dir` which is typically `/root/mno` for bare-metal cluster type.
+Jetlag includes the installation of a HAProxy instance on the bastion machine with ipv6/disconnected environment setup.  The HAProxy instance allows you to proxy traffic over ports 6443, 443, and 80 into the deployed disconnected cluster. Port 6443 is for access to the cluster api (Ex. oc cli commands), and ports 443/80 are for ingress routes such as console or grafana. This effectively allows you to reach the disconnected cluster from your local laptop. In order to do so you will need to edit your laptop's `/etc/hosts` and insert the routes that map to your cluster. While running the `setup-bastion.yml` playbook, an example copy of the hosts file is dumped into `bastion_cluster_config_dir` which is typically `/root/mno` for multi node cluster type.
 
 Example:
 

docs/order-hardware-ibmcloud.md

@@ -15,7 +15,7 @@ Browse to Catalog and filter 'Compute'. Select Bare Metal Servers from the list
 
 You can select the location/datacenter and the Server profile based on cost estimates
 
-For baremetal deployment, you will need:
+For multi node deployment, you will need:
 
 * One server to be provisioned as your bastion machine
 * Three additional servers to serve as control-plane nodes

docs/tips-and-vars.md

@@ -44,7 +44,7 @@ Performance lab chart is available [here](https://wiki.rdu3.labs.perfscale.redha
 ## Extra vars for by-path disk reference
 
 > [!TIP]
-> For bare-metal deployment of OCP 4.13 or greater it is advisable to
+> For multi node deployment of OCP 4.13 or greater it is advisable to
 > set the extra vars for by-path reference for the installation as sometimes disk
 > names get swapped during boot discovery (e.g., sda and sdb). Using the PCI
 > paths (in a homogeneous Scale or Performance lab cloud) should be consistent across