OpenShift 3.6 Support Guest Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 5: Line 5:
=Clone the Generic Template=
=Clone the Generic Template=


Use the [[OpenShift_3.6_Generic_Guest_Template#Overview|basic template]] as a base image and clone it, as described below.  
Use the [[OpenShift_3.6_Generic_Guest_Template#Overview|generic template]] as a base image and clone it, as described below.  


While cloning the guest, make sure to:
While cloning the guest, make sure to:

Revision as of 03:13, 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.
  • Remove docker and docker storage.
  • Provision NFS storage.
Cloning a Guest

The process will produce a ocp36.ingress.


Support Host Configuration

Clone the Template

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

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

bind DNS Server Installation
Retrieved from "https://kb.novaordis.com/index.php?title=OpenShift_3.6_Support_Guest_Configuration&oldid=30701"