OpenShift 3.6 Node Guest Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 2: Line 2:


* [[OpenShift_3.6_Installation#Guest_Configuration|OpenShift 3.6 Installation]]
* [[OpenShift_3.6_Installation#Guest_Configuration|OpenShift 3.6 Installation]]
For each master, infranode and node:


=Clone the Generic Template=
=Clone the Generic Template=
Line 15: Line 17:
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).


===OpenShift Node Configuration===
=Configure Docker Storage=
 
Clone the template following the procedure described here [[Linux_Virtualization_Cloning_a_KVM_Guest_Virtual_Machine|Cloning a KVM Guest]]. While cloning, consider the following:


Adjust the memory and the number of virtual CPUs.
Repeat the template docker storage setup procedure:


Configure the DNS client to use the DNS server that was installed as part of the procedure. See "[[/etc/resolv.conf#Manual_resolv.conf_Configuration|manual /etc/resolv.conf Configuration]]" and https://docs.openshift.com/container-platform/3.5/install_config/install/prerequisites.html#prereq-dns
{{Internal|OpenShift_3.6_Generic_Guest_Template#Docker_Storage_Setup|Guest Template Docker Storage Setup}}


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


  systemctl stop docker
  systemctl enable docker
  unalias rm
  systemctl disable docker-storage-setup
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

Latest revision as of 07:00, 9 November 2017

Internal

For each master, infranode and node:

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).

Configure Docker Storage

Repeat the template docker storage setup procedure:

Guest Template Docker Storage Setup

Activate at boot:

systemctl enable docker
systemctl disable docker-storage-setup