OpenShift 3.6 Ingress Guest Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 7: Line 7:
Use the [[OpenShift_3.6_Basic_Guest_Template#Overview|basic template]] as a base image and clone it, as described below.  
Use the [[OpenShift_3.6_Basic_Guest_Template#Overview|basic template]] as a base image and clone it, as described below.  


{{Warn|While cloning the guest, make sure to provision a directly-mapped network interface.}}
While cloning the guest, make sure to:
* Adjust the memory and the number of virtual CPUs.
* Provision a directly-mapped network interface.


{{Internal|Linux Virtualization Cloning a KVM Guest Virtual Machine|Cloning a Guest}}
{{Internal|Linux Virtualization Cloning a KVM Guest Virtual Machine|Cloning a Guest}}

Revision as of 02:39, 9 November 2017

Internal

Clone the Basic Template

Use the basic 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 a directly-mapped network interface.
Cloning a Guest

The process will produce a ocp36.ingress.

External Access Configuration

Create external accounts to be exposed publicly and configure their ssh access (~/.ssh/authorized_keys).








Access/Proxy Host Configuration

Clone the Template

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

Post-Cloning

  • Turn off external root access.
  • Add external users.
  • Disable and remove Docker.

There is no need to install HAProxy manually to serve as master node load balancer, the OpenShift installation procedure will do it.

  • Add the IP addresses for masters, support and lb (itself) to /etc/hosts, the DNS server may not be operational when we need it.
192.168.122.10 in in.local lb lb.local
192.168.122.12 support support.local
192.168.122.13 master1 master1.local
192.168.122.14 master2 master2.local
192.168.122.16 master3 master3.local