Blame docs/operations/ci/graceful_startup_ocp_cluster.md

47c289
# Graceful Startup of an Openshift 4 Cluster
47c289
This SOP should be followed in the following scenarios:
47c289
47c289
- Starting up an Openshift 4 cluster. 
47c289
47c289
47c289
## Steps
47c289
47c289
Prequisite steps:
47c289
47c289
68716f
### Start the physical nodes : 
47c289
68716f
  - Production uses `adhoc-ipmi-poweron.yml` playbook to stop/start/restart nodes : 
47c289
68716f
```
68716f
ansible-playbook playbooks/adhoc-ipmi-poweron.yml -l ocp-ci
68716f
```
68716f
  - Staging uses `adhoc-seamicro-poweron.yml` playbook to start the powered off seamicro compute nodes
68716f
68716f
```
68716f
ansible-playbook playbooks/adhoc-seamicro-poweron.yml # This will prompt for nodes, just use `ocp-ci` as group
68716f
```
68716f
68716f
### Once the nodes have been started they must be uncordoned if appropriate
47c289
47c289
```
47c289
oc get nodes
47c289
NAME                       STATUS                     ROLES    AGE    VERSION
47c289
dumpty-n1.ci.centos.org    Ready,SchedulingDisabled   worker   77d    v1.18.3+6c42de8
47c289
dumpty-n2.ci.centos.org    Ready,SchedulingDisabled   worker   77d    v1.18.3+6c42de8
47c289
dumpty-n3.ci.centos.org    Ready,SchedulingDisabled   worker   77d    v1.18.3+6c42de8
47c289
dumpty-n4.ci.centos.org    Ready,SchedulingDisabled   worker   77d    v1.18.3+6c42de8
47c289
dumpty-n5.ci.centos.org    Ready,SchedulingDisabled   worker   77d    v1.18.3+6c42de8
47c289
kempty-n10.ci.centos.org   Ready,SchedulingDisabled   worker   106d   v1.18.3+6c42de8
47c289
kempty-n11.ci.centos.org   Ready,SchedulingDisabled   worker   106d   v1.18.3+6c42de8
47c289
kempty-n12.ci.centos.org   Ready,SchedulingDisabled   worker   106d   v1.18.3+6c42de8
47c289
kempty-n6.ci.centos.org    Ready,SchedulingDisabled   master   106d   v1.18.3+6c42de8
47c289
kempty-n7.ci.centos.org    Ready,SchedulingDisabled   master   106d   v1.18.3+6c42de8
47c289
kempty-n8.ci.centos.org    Ready,SchedulingDisabled   master   106d   v1.18.3+6c42de8
47c289
kempty-n9.ci.centos.org    Ready,SchedulingDisabled   worker   106d   v1.18.3+6c42de8
47c289
47c289
nodes=$(oc get nodes -o name  | sed -E "s/node\///")
47c289
47c289
for node in ${nodes[@]}; do oc adm uncordon $node; done
47c289
node/dumpty-n1.ci.centos.org uncordoned
47c289
node/dumpty-n2.ci.centos.org uncordoned
47c289
node/dumpty-n3.ci.centos.org uncordoned
47c289
node/dumpty-n4.ci.centos.org uncordoned
47c289
node/dumpty-n5.ci.centos.org uncordoned
47c289
node/kempty-n10.ci.centos.org uncordoned
47c289
node/kempty-n11.ci.centos.org uncordoned
47c289
node/kempty-n12.ci.centos.org uncordoned
47c289
node/kempty-n6.ci.centos.org uncordoned
47c289
node/kempty-n7.ci.centos.org uncordoned
47c289
node/kempty-n8.ci.centos.org uncordoned
47c289
node/kempty-n9.ci.centos.org uncordoned
47c289
47c289
oc get nodes
47c289
NAME                       STATUS   ROLES    AGE    VERSION
47c289
dumpty-n1.ci.centos.org    Ready    worker   77d    v1.18.3+6c42de8
47c289
dumpty-n2.ci.centos.org    Ready    worker   77d    v1.18.3+6c42de8
47c289
dumpty-n3.ci.centos.org    Ready    worker   77d    v1.18.3+6c42de8
47c289
dumpty-n4.ci.centos.org    Ready    worker   77d    v1.18.3+6c42de8
47c289
dumpty-n5.ci.centos.org    Ready    worker   77d    v1.18.3+6c42de8
47c289
kempty-n10.ci.centos.org   Ready    worker   106d   v1.18.3+6c42de8
47c289
kempty-n11.ci.centos.org   Ready    worker   106d   v1.18.3+6c42de8
47c289
kempty-n12.ci.centos.org   Ready    worker   106d   v1.18.3+6c42de8
47c289
kempty-n6.ci.centos.org    Ready    master   106d   v1.18.3+6c42de8
47c289
kempty-n7.ci.centos.org    Ready    master   106d   v1.18.3+6c42de8
47c289
kempty-n8.ci.centos.org    Ready    master   106d   v1.18.3+6c42de8
47c289
kempty-n9.ci.centos.org    Ready    worker   106d   v1.18.3+6c42de8
47c289
```
47c289
47c289
68716f
## Resources
47c289
47c289
- [1] [Graceful Cluster Startup](https://docs.openshift.com/container-platform/4.5/backup_and_restore/graceful-cluster-restart.html)
47c289
- [2] [Cluster disaster recovery](https://docs.openshift.com/container-platform/4.5/backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.html#dr-restoring-cluster-state)