OpenShift 3.6 Support Guest Configuration
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.
- Remove docker storage support from domain definition, but replace it with NFS storage support.
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
- The support host needs an additional block storage device, but it won't be used for Docker storage and it will be different in size.
Post-Cloning
- Remove docker and docker storage.
- Provision NFS storage.
- Turn off docker and disable it
- Remove the docker logical volume
- Replace the docker storage with nfs storage - it should still be /dev/vdb1
NFS Server Installation
Install and configure an NFS server. 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. 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.