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

ocp4 sops moved into sysadmin_guide

Browse source 
Signed-off-by: David Kirwan <davidkirwanirl@gmail.com>
This commit is contained in:
David Kirwan 2024-07-22 10:37:01 +01:00
parent 1d17fd8610
commit c0d6947dba
No known key found for this signature in database
GPG key ID: A5893AB6474AC37D
35 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

88
modules/sysadmin_guide/pages/sop_graceful_startup_ocp_cluster.adoc Normal file
View file

@ -0,0 +1,88 @@
= Graceful Startup of an Openshift 4 Cluster
This SOP should be followed in the following scenarios:
- Graceful start up of an Openshift 4 cluster.
== Steps
Prequisite steps:
=== Start the VM Control Plane instances
Ensure that the control plane instances start first.
----
# Virsh command to start the VMs
----
=== Start the physical nodes
To connect to `idrac`, you must be connected to the Red Hat VPN. Next find the management IP associated with each node.
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
----
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.
=== Once the nodes have been started they must be uncordoned if appropriate
----
oc get nodes
NAME STATUS ROLES AGE VERSION
dumpty-n1.ci.centos.org Ready,SchedulingDisabled worker 77d v1.18.3+6c42de8
dumpty-n2.ci.centos.org Ready,SchedulingDisabled worker 77d v1.18.3+6c42de8
dumpty-n3.ci.centos.org Ready,SchedulingDisabled worker 77d v1.18.3+6c42de8
dumpty-n4.ci.centos.org Ready,SchedulingDisabled worker 77d v1.18.3+6c42de8
dumpty-n5.ci.centos.org Ready,SchedulingDisabled worker 77d v1.18.3+6c42de8
kempty-n10.ci.centos.org Ready,SchedulingDisabled worker 106d v1.18.3+6c42de8
kempty-n11.ci.centos.org Ready,SchedulingDisabled worker 106d v1.18.3+6c42de8
kempty-n12.ci.centos.org Ready,SchedulingDisabled worker 106d v1.18.3+6c42de8
kempty-n6.ci.centos.org Ready,SchedulingDisabled master 106d v1.18.3+6c42de8
kempty-n7.ci.centos.org Ready,SchedulingDisabled master 106d v1.18.3+6c42de8
kempty-n8.ci.centos.org Ready,SchedulingDisabled master 106d v1.18.3+6c42de8
kempty-n9.ci.centos.org Ready,SchedulingDisabled worker 106d v1.18.3+6c42de8
nodes=$(oc get nodes -o name | sed -E "s/node\///")
for node in ${nodes[@]}; do oc adm uncordon $node; done
node/dumpty-n1.ci.centos.org uncordoned
node/dumpty-n2.ci.centos.org uncordoned
node/dumpty-n3.ci.centos.org uncordoned
node/dumpty-n4.ci.centos.org uncordoned
node/dumpty-n5.ci.centos.org uncordoned
node/kempty-n10.ci.centos.org uncordoned
node/kempty-n11.ci.centos.org uncordoned
node/kempty-n12.ci.centos.org uncordoned
node/kempty-n6.ci.centos.org uncordoned
node/kempty-n7.ci.centos.org uncordoned
node/kempty-n8.ci.centos.org uncordoned
node/kempty-n9.ci.centos.org uncordoned
oc get nodes
NAME STATUS ROLES AGE VERSION
dumpty-n1.ci.centos.org Ready worker 77d v1.18.3+6c42de8
dumpty-n2.ci.centos.org Ready worker 77d v1.18.3+6c42de8
dumpty-n3.ci.centos.org Ready worker 77d v1.18.3+6c42de8
dumpty-n4.ci.centos.org Ready worker 77d v1.18.3+6c42de8
dumpty-n5.ci.centos.org Ready worker 77d v1.18.3+6c42de8
kempty-n10.ci.centos.org Ready worker 106d v1.18.3+6c42de8
kempty-n11.ci.centos.org Ready worker 106d v1.18.3+6c42de8
kempty-n12.ci.centos.org Ready worker 106d v1.18.3+6c42de8
kempty-n6.ci.centos.org Ready master 106d v1.18.3+6c42de8
kempty-n7.ci.centos.org Ready master 106d v1.18.3+6c42de8
kempty-n8.ci.centos.org Ready master 106d v1.18.3+6c42de8
kempty-n9.ci.centos.org Ready worker 106d v1.18.3+6c42de8
----
== Resources
- [1] https://docs.openshift.com/container-platform/4.5/backup_and_restore/graceful-cluster-restart.html[Graceful Cluster Startup]
- [2] https://docs.openshift.com/container-platform/4.5/backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.html#dr-restoring-cluster-state[Cluster disaster recovery]