You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-9Lines changed: 17 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ As it stands right now, the repo works for several installation usecases:
15
15
16
16
1. vSphere ESXi and vCenter 6.7 installed. For vCenter 6.5 please see a cautionary note below:
17
17
2. A datacenter created with a vSphere host added to it, a datastore exists and has adequate capacity
18
-
3. The playbook(s) assumes you are running a [helper node](https://github.com/RedHatOfficial/ocp4-helpernode)running in the same network to provide all the necessary services such as [DHCP/DNS/HAProxy as LB]. Also, the MAC addresses for the machines should match between helper repo and this. If not using the helper node, the minimum expectation is that the webserver and tftp server (for PXE boot) are running on the same external host, which we will then treat as a helper node.
18
+
3. The playbook(s) assumes you are running a [helper node](https://github.com/RedHatOfficial/ocp4-helpernode) in the same network to provide all the necessary services such as [DHCP/DNS/HAProxy as LB]. Also, the MAC addresses for the machines should match between helper repo and this. If not using the helper node, the minimum expectation is that the webserver and tftp server (for PXE boot) are running on the same external host, which we will then treat as a helper node.
19
19
4. The necessary services such as [DNS/LB(Load Balancer] must be up and running before this repo can be used
20
20
5. Ansible (preferably latest) with **Python 3** on the machine where this repo is cloned. Before you install Ansible, install the `epel-release`, run `yum -y install epel-release`
21
21
@@ -121,29 +121,35 @@ With all the details in hand from the prerequisites, populate the **group_vars/a
* If vCenter folder already exists with the template because you set the vCenter the last time you ran the ansible playbook but want a fresh deployment of VMs **after** you have erased all the existing VMs in the folder, append the following to the command you chose in the above step
141
+
* If you are re-running the installation playbook make sure to blow away any existing VMs (in `ocp4` folder) listed below:
142
+
1. bootstrap
143
+
2. masters
144
+
3. workers
145
+
4.`rhcos-vmware` template (if not using the extra param as shown below)
146
+
* If a template by the name `rhcos-vmware` already exists in vCenter, you want to reuse it and skip the OVA **download** from Red Hat and **upload** into vCenter, use the following extra param.
142
147
143
148
```sh
144
-
-e vcenter_preqs_met=true
149
+
-e skip_ova=true
145
150
```
146
-
* If would rather want to clean all folders `bin`, `downloads`, `install-dir` and re-download all the artifacts, append the following to the command you chose in the first step
151
+
152
+
* If you would rather want to clean all folders `bin`, `downloads`, `install-dir` and re-download all the artifacts, append the following to the command you chose in the first step
3. base64 encoded files (append-bootstrap.64, master.64, worker.64) for (append-bootstrap.ign, master.ign, worker.ign) respectiviely. This step assumes you have **base64** installed and in your **$PATH**
161
167
7. The **bootstrap.ign** is copied over to the web server in the designated location
162
-
8. A folder is created in the vCenter under the mentioned datacenter and the template file is imported
168
+
8. A folder is created in the vCenter under the mentioned datacenter and the template is imported
163
169
9. The template file is edited to carry certain default settings and runtime parameters common to all the VMs
164
170
10. VMs (bootstrap, master0-2, worker0-2) are generated in the designated folder and (in state of) **poweredon**
165
171
@@ -169,6 +175,7 @@ If everything goes well you should be able to log into all of the machines using
169
175
170
176
```sh
171
177
# Assuming you are able to resolve bootstrap.ocp4.example.com on this machine
178
+
# Replace the bootstrap hostname with any of the master or worker hostnames
0 commit comments