Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

DC move: iad => rdu3, 10.3. => 10.16.

Browse source 
And remove some obsolete things.

Signed-off-by: Nils Philippsen <nils@redhat.com>
This commit is contained in:
Nils Philippsen 2025-07-04 11:55:02 +02:00
parent f3756ceb83
commit b4afb2f945
83 changed files with 386 additions and 429 deletions
Download patch file Download diff file Expand all files Collapse all files

12
modules/sysadmin_guide/pages/sop_graceful_startup_ocp_cluster.adoc
View file

@ -21,12 +21,12 @@ To connect to `idrac`, you must be connected to the Red Hat VPN. Next find the m
On the `batcave01` instance, in the dns configuration, the following bare metal machines make up the production/staging OCP4 worker nodes.
----
oshift-dell01 IN A 10.3.160.180 # worker01 prod
oshift-dell02 IN A 10.3.160.181 # worker02 prod
oshift-dell03 IN A 10.3.160.182 # worker03 prod
oshift-dell04 IN A 10.3.160.183 # worker01 staging
oshift-dell05 IN A 10.3.160.184 # worker02 staging
oshift-dell06 IN A 10.3.160.185 # worker03 staging
oshift-dell01 IN A 10.16.160.180 # worker01 prod
oshift-dell02 IN A 10.16.160.181 # worker02 prod
oshift-dell03 IN A 10.16.160.182 # worker03 prod
oshift-dell04 IN A 10.16.160.183 # worker01 staging
oshift-dell05 IN A 10.16.160.184 # worker02 staging
oshift-dell06 IN A 10.16.160.185 # worker03 staging
----
Login to the `idrac` interface that corresponds with each worker, one at a time. Ensure the node is booting via harddrive, then power it on.