OpenShift 3.6 Node Guest Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 14: Line 14:


The process will produce a ocp36.master (smaller docker storage), ocp36.infanode, ocp36.node1, ocp36.node2, etc.
The process will produce a ocp36.master (smaller docker storage), ocp36.infanode, ocp36.node1, ocp36.node2, etc.
=Resources=
Verify resources (memory, CPU).





Revision as of 06:27, 9 November 2017

Internal

Clone the Generic Template

Use the generic template as a base image and clone it, as described below.

While cloning the guest, make sure to:

  • Adjust the memory and the number of virtual CPUs.
  • Provision docker storage sized proportionally with the nature of the node.
Cloning a Guest

The process will produce a ocp36.master (smaller docker storage), ocp36.infanode, ocp36.node1, ocp36.node2, etc.

Resources

Verify resources (memory, CPU).


OpenShift Node Configuration

Clone the template following the procedure described here Cloning a KVM Guest. While cloning, consider the following:

Adjust the memory and the number of virtual CPUs.

Configure the DNS client to use the DNS server that was installed as part of the procedure. See "manual /etc/resolv.conf Configuration" and https://docs.openshift.com/container-platform/3.5/install_config/install/prerequisites.html#prereq-dns

Configure docker disk (note that the sequence described blow needs a modified /usr/bin/docker-storage-setup):

systemctl stop docker
unalias rm
rm -r /var/lib/docker
cat /dev/null > /etc/sysconfig/docker-storage
pvs
fdisk /dev/vdb
/usr/bin/docker-storage-setup --force
systemctl is-enabled docker
systemctl start docker
systemctl status docker