Remove more references to BM instead of MNO

ansible/mno-post-deploy-add-bmc.yml

@@ -1,16 +1,16 @@
 ---
-# BM post-deploy add BMC to BareMetalHosts
+# MNO post-deploy add BMC to BareMetalHosts
 #
 # Example Usage:
 #
-# ansible-playbook -i ansible/inventory/cloud42.local ansible/bm-post-deploy-add-bmc.yml
+# ansible-playbook -i ansible/inventory/cloud42.local ansible/mno-post-deploy-add-bmc.yml
 #
 
-- name: BM post-deploy add BMC to BareMetalHosts
+- name: MNO post-deploy add BMC to BareMetalHosts
   hosts: bastion
   vars_files:
   - vars/lab.yml
   - vars/all.yml
   roles:
   - validate-vars
-  - bm-add-bmc
+  - mno-add-bmc

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

@@ -36,7 +36,7 @@
     ocpinventory_sno_nodes: []
     ocpinventory_hv_nodes: []
 
-- name: Public VLAN in BM cluster
+- name: Public VLAN in MNO cluster
   when: public_vlan and cluster_type == "mno"
   block:
   - name: Public VLAN - Configuring controlplane_network_interface_idx to the last interface

ansible/roles/ibmcloud-create-inventory/defaults/main/main.yml

@@ -11,7 +11,7 @@ sno_hardware_ids: []
 
 vendor_mapping: {}
 
-# Default install disks for bm
+# Default install disks for mno
 control_plane_install_disk: /dev/sda
 worker_install_disk: /dev/sda
 

docs/deploy-mno-ibmcloud.md

@@ -349,17 +349,17 @@ Next run the `ibmcloud-setup-bastion.yml` playbook ...
 ...
 ```
 
-Lastly, run the `ibmcloud-bm-deploy.yml` playbook ...
+Lastly, run the `ibmcloud-mno-deploy.yml` playbook ...
 
 ```console
-(.ansible) [root@<bastion> jetlag]# ansible-playbook -i ansible/inventory/ibmcloud.local ansible/ibmcloud-bm-deploy.yml
+(.ansible) [root@<bastion> jetlag]# ansible-playbook -i ansible/inventory/ibmcloud.local ansible/ibmcloud-mno-deploy.yml
 ...
 ```
 
 If everything goes well you should have a cluster in about 60-70 minutes. You can interact with the cluster from the bastion.
 
 ```console
-(.ansible) [root@<bastion> jetlag]# export KUBECONFIG=/root/bm/kubeconfig
+(.ansible) [root@<bastion> jetlag]# export KUBECONFIG=/root/mno/kubeconfig
 (.ansible) [root@<bastion> jetlag]# oc get no
 NAME         STATUS   ROLES    AGE     VERSION
 jetlag-bm1   Ready    master   3h34m   v1.21.1+051ac4f

docs/deploy-mno-performancelab.md

@@ -253,7 +253,7 @@ bastion_controlplane_interface: ens3f0
 
 Here you can see a network diagram for the multi node metal cluster on Dell r650 with 3 workers and 3 master nodes:
 
-![BM Cluster](img/mno_cluster.png)
+![MNO Cluster](img/mno_cluster.png)
 
 Double check your nic names with your actual bastion machine.
 

docs/deploy-sno-ibmcloud.md

@@ -12,10 +12,10 @@ _**Table of Contents**_
 <!-- /TOC -->
 
 <!-- Bastion setup is duplicated in multiple files and should be kept in sync!
-     - deploy-bm-byol.md
-     - deploy-bm-ibmcloud.md
-     - deploy-bm-performancelab.md
-     - deploy-bm-scalelab.md
+     - deploy-mno-byol.md
+     - deploy-mno-ibmcloud.md
+     - deploy-mno-performancelab.md
+     - deploy-mno-scalelab.md
      - deploy-sno-ibmcloud.md
      - deploy-sno-scalelab.md
      - deploy-sno-performancelab.md

docs/deploy-sno-performancelab.md

@@ -20,10 +20,10 @@ _**Table of Contents**_
 <!-- /TOC -->
 
 <!-- Bastion setup is duplicated in multiple files and should be kept in sync!
-     - deploy-bm-byol.md
-     - deploy-bm-ibmcloud.md
-     - deploy-bm-performancelab.md
-     - deploy-bm-scalelab.md
+     - deploy-mno-byol.md
+     - deploy-mno-ibmcloud.md
+     - deploy-mno-performancelab.md
+     - deploy-mno-scalelab.md
      - deploy-sno-ibmcloud.md
      - deploy-sno-scalelab.md
      - deploy-sno-performancelab.md