OpenShift 3.6 Support Guest Configuration

Internal

• OpenShift 3.6 Installation

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.
• Remove docker storage support from domain definition, but replace it with NFS storage support.

Cloning a Guest

The process will produce a ocp36.ingress.

Resources

Verify the memory and the number of virtual CPUs.

Remove Docker

systemctl stop docker
systemctl stop docker-storage-setup.service
systemctl disable docker
systemctl disable docker-storage-setup.service
yum remove docker

Reset the storage, in case docker got to initialize it.

vgremove docker_vg
pvremove /dev/vdb1
fdisk /dev/vdb

Prepare File System For NFS

The NFS server will serve storage for persistent volumes, metrics and logging. Build a dedicated storage device to be shared via NFS, but do not export individual volumes; the OpenShift installer will do that automatically.

Create the partition:

fdisk /dev/vdb
Command (m for help): n
Partition type:
  p   primary (0 primary, 0 extended, 4 free)
  e   extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-167772159, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-167772159, default 167772159):
Using default value 167772159
Partition 1 of type Linux and of size 80 GiB is set

Command (m for help): w

The partition table has been altered!

Create the filesystem:

mkfs.xfs /dev/vdb1

Follow the NFS server installation procedure, exposing it as /nfs:

Linux NFS Installation

Install and configure an NFS server. At this stage, make sure the storage is mounted, NFS server binaries are installed, and iptables is correctly configured to allow NFS to serve storage. A summary of these steps is presented in Provisioning and Installing a New Filesystem on a New Logical Volume and NFS Server Installation. All steps of the procedure must be executed, less the export part.

bind DNS Server Installation

During the next iteration, consider installing the DNS server on "in", as "in" is always on, and the load balancer also runs on "in" and it needs internal name resolution. Also make haproxy dependent on named.

Consider using master SkyDNS as the only name forwarder to the support DNS server.

bind DNS Server Installation