Metrics-for-apps: Typos
Signed-off-by: David Kirwan <dkirwan@redhat.com>
This commit is contained in:
parent
aa22a8945f
commit
15cee59da7
1 changed files with 8 additions and 8 deletions
|
@ -5,13 +5,13 @@ This SOP should be used in the following scenario:
|
|||
|
||||
|
||||
=== Resources
|
||||
- [1] https://access.redhat.com/solutions/4246261[How to add Openshift 4 RHCOS worker nodes in UPI <24 hours]
|
||||
- [2] https://access.redhat.com/solutions/4799921[How to add Openshift 4 RHCOS worker nodes to UPI >24 hours]
|
||||
- [1] https://access.redhat.com/solutions/4246261[How to add OpenShift 4 RHCOS worker nodes in UPI within the first 24 hours]
|
||||
- [2] https://access.redhat.com/solutions/4799921[How to add OpenShift 4 RHCOS worker nodes to UPI after the first 24 hours]
|
||||
- [3] https://docs.openshift.com/container-platform/4.8/post_installation_configuration/node-tasks.html[Adding RHCOS worker nodes]
|
||||
|
||||
|
||||
=== Steps
|
||||
1. Add the new nodes to the ansible inventory file in the appropriate group.
|
||||
1. Add the new nodes to the Ansible inventory file in the appropriate group.
|
||||
|
||||
eg:
|
||||
|
||||
|
@ -47,7 +47,7 @@ inventory/group_vars/proxies:ocp_nodes:
|
|||
inventory/group_vars/proxies_stg:ocp_nodes_stg:
|
||||
----
|
||||
|
||||
4. Changes must be made to the `roles/dhcp_server/files/dhcpd.conf.noc01.iad2.fedoraproject.org` file for DHCP to ensure that the node will receieve an IP address based on its MAC address, and tells the node to reach out to the `next-server` where it can find the UEFI boot configuration.
|
||||
4. Changes must be made to the `roles/dhcp_server/files/dhcpd.conf.noc01.iad2.fedoraproject.org` file for DHCP to ensure that the node will receive an IP address based on its MAC address, and tells the node to reach out to the `next-server` where it can find the UEFI boot configuration.
|
||||
|
||||
----
|
||||
host worker01-ocp { # UPDATE THIS
|
||||
|
@ -60,7 +60,7 @@ host worker01-ocp { # UPDATE THIS
|
|||
}
|
||||
----
|
||||
|
||||
5. Changes must be made to DNS. To do this, one must send a patch request to the Fedora Infra mailing list for review.
|
||||
5. Changes must be made to DNS. To do this one must be a member of `sysadmin-main`, if you are not, one must send a patch request to the Fedora Infra mailing list for review which will be merged by the sysadmin-main members.
|
||||
|
||||
See the following examples for the `worker01.ocp` nodes for production and staging.
|
||||
|
||||
|
@ -101,21 +101,21 @@ When a node is booted up, and reads this UEFI boot configuration, the menu optio
|
|||
|
||||
8. Connect to the `os-control01` node which corresponds with the ENV which the new node is being added to.
|
||||
|
||||
Verify that you are authenticated correctly to the Openshift cluster as the `system:admin` user.
|
||||
Verify that you are authenticated correctly to the OpenShift cluster as the `system:admin` user.
|
||||
|
||||
----
|
||||
oc whoami
|
||||
system:admin
|
||||
----
|
||||
|
||||
9. Contained within the UEFI boot menu configuration, is links to the web server running on the `os-control01` host specific to the ENV. This server should not be left running it should only run when we wish to reinstall an existing node or install a new node. Start it using systemctl manually:
|
||||
9. Contained within the UEFI boot menu configuration are the links to the web server running on the `os-control01` host specific to the ENV. This server should only run when we wish to reinstall an existing node or install a new node. Start it using systemctl manually:
|
||||
|
||||
----
|
||||
systemctl start httpd.service
|
||||
----
|
||||
|
||||
10. Boot up the node and select the appropriate menu entry to install the node into the correct cluster.
|
||||
From the console wait until the node displays a SSH login prompt with the nodes name. It may reboot several times during the process.
|
||||
Wait until the node displays a SSH login prompt with the nodes name. It may reboot several times during the process.
|
||||
|
||||
11. As the new nodes are provisioned, they will attempt to join the cluster. They must first be accepted.
|
||||
From the `os-control01` node run the following:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue