OpenShift hosts

Internal

• OpenShift 3.5. Installation

Overview

Documentation for https://github.com/NovaOrdis/playground/blob/master/openshift/3.5/hosts

Defaults are available here:

https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_metrics/defaults/main.yaml

Ansible Configuration

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.

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.

General Settings

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: Change the Log Level for OpenShift Processes.

containerized

If set to true, containerized OpenShift services (instead of RPM-based) are run on all nodes. The default is "false", which means the default RPM method is used. RHEL Atomic Host requires the containerized method, which is automatically selected for you based on the detection of the /run/ostree-booted file. Since 3.1.1.

deployment_type

Deployment type ("origin" or "openshift-enterprise").

For more details see:

https://docs.openshift.com/container-platform/3.5/install_config/install/advanced_install.html#advanced-install-deployment-types

Logging Configuration

OpenShift Logging Concepts

openshift_hosted_logging_deploy

Logging infrastructure deployment is disabled by default. It can be enabled by setting:

openshift_hosted_logging_deploy=true

openshift_logging_es_cluster_size

For a HA installation, ElasticSearch should be deployed with a cluster size of at least three for resiliency to node failures.

openshift_logging_image_prefix

The prefix for logging component images. For example, setting the prefix to "registry.access.redhat.com/openshift3/" creates "registry.access.redhat.com/openshift3/logging-fluentd:latest".

openshift_logging_image_version

The version for logging component images. For example, setting the version to "v3.5" creates "registry.access.redhat.com/openshift3/logging-fluentd:v3.5".

openshift_logging_use_ops

If set to "true", configures a second Elasticsearch cluster and Kibana for operations logs. Fluentd splits logs between the main cluster and a cluster reserved for operations logs. The operations logs consist of /var/log/messages on nodes and the logs from the projects "default", "open shift", and "openshift-infra". This means a second Elasticsearch and Kibana are deployed. The deployments are distinguishable by the -ops suffix included in their names and have parallel deployment options, listed below.