OpenShift Runtime

Internal

• OpenShift Operations
• OpenShift Configuration Files

Master Node

The master node runs, in order, these services:

• etcd
• master daemon or daemons (api, then controller)
• node daemon

The master daemon (or daemons) must be started after etcd is started, they depend on etcd. They are started before the node service.

etcd Daemon

Unit: etcd.service

Unit File: /usr/lib/systemd/system/etcd.service

Working Directory: /var/lib/etcd

Configuration File: /etc/etcd/etcd.conf

Process:

/usr/bin/etcd --name=master1.rdu20.internal --data-dir=/var/lib/etcd --listen-client-urls=https://192.199.0.199:2379

master Daemons

In a non-HA deployment, the master api daemon and master controller daemon are coalesced in a single process. In HA environments, they are separated, so the master api daemon processes can be load-balanced among, while the master controller daemon run in an active/passive configuration, there is just one active master controller daemon instance in the cluster.

master api Daemon

Depends On: etcd

Unit: atomic-openshift-master-api.service

Unit File: /usr/lib/systemd/system/atomic-openshift-master-api.service

Working Directory: /var/lib/origin

Configuration Files:

• /etc/sysconfig/atomic-openshift-master-api, which contains command line options for the process.
• /etc/origin/master/master-config.yaml

Process:

/usr/bin/etcd --name=master1.rdu20.internal --data-dir=/var/lib/etcd --listen-client-urls=https://192.199.0.199:2379

master controller Daemon

Unit: atomic-openshift-master-controllers.service

Unit File: /usr/lib/systemd/system/atomic-openshift-master-controllers.service

Working Directory: /var/lib/etcd

Configuration File: /etc/etcd/etcd.conf

Process:

/usr/bin/etcd --name=master1.rdu20.internal --data-dir=/var/lib/etcd --listen-client-urls=https://192.199.0.199:2379