OpenShift hosts
Internal
Examples
- OpenShift 3.5: https://github.com/openshift/openshift-ansible/blob/release-1.5/inventory/byo/hosts.ose.example and corresponding defaults: https://github.com/openshift/openshift-ansible/blob/release-1.5/roles/openshift_metrics/defaults/main.yaml
- OpenShift 3.6: https://github.com/openshift/openshift-ansible/blob/release-3.6/inventory/byo/hosts.ose.example and corresponding defaults: https://github.com/openshift/openshift-ansible/blob/release-3.6/roles/openshift_metrics/defaults/main.yaml
- Configured template that worked for noper430 OpenShift 3.5 HA installation: https://github.com/NovaOrdis/playground/blob/master/openshift/3.5/hosts
Overview
The default Ansible inventory file is /etc/ansible/hosts. It is used by the Ansible playbook to install the OpenShift environment. The inventory file describes the configuration and the topology of the OpenShift cluster. A generally accepted method is to start from a template like the ones linked from Examples above and customize it to match the environment.
Configuration Elements
Ansible Configuration
If anything else than "root" is used for installation, both "ansible_ssh_user" and "ansible_become" must be set.
ansible_ssh_user
The ssh user used by Ansible to connect to hosts. This user should allow ssh based authentication without requiring a password, and also it should allow passwordless sudo to root. If using ssh key based authentication, then the key should be managed by an ssh agent. Also see ansible_become. See Support Node for O/S level configuration required by an "ansible" user.
ansible_become
If ansible_ssh_user is not root, ansible_become must be set to true and the user must be configured for passwordless sudo.
General Settings
openshift_enable_unsupported_configurations
Enable unsupported configurations, things that will yield a partially functioning cluster but would not be supported for production use.
debug_level
Describes which INFO messages are logged to the systemd-journald.service. Set one of the following:
- 0 to log errors and warnings only
- 2 to log normal information (default)
- 4 to log debugging-level information
- 6 to log API-level (request/response) debugging information
- 8 to log body-level API debugging information
This can also be configured after installation by following the procedure described here:
Organizatorium
If the target nodes have multiple network interfaces, and the network interface used to cluster OpenShift is NOT associated with the default route, modify the inventory file as follows:
... openshift_set_node_ip=true ... [nodes] master1.openshift35.local openshift_ip=172.23.0.4 ...
Network Configuration
Logging Configuration
openshift_hosted_logging_deploy
Logging infrastructure deployment is disabled by default. It can be enabled by setting:
openshift_hosted_logging_deploy=true