OpenShift Runtime: Difference between revisions
No edit summary |
|||
| Line 36: | Line 36: | ||
===master controller Daemon=== | ===master controller Daemon=== | ||
Unit: <tt>atomic-openshift-master-controllers.service</tt> | |||
Unit File: <tt>/usr/lib/systemd/system/atomic-openshift-master-controllers.service</tt> | |||
Working Directory: <tt>/var/lib/etcd</tt> | |||
Configuration File: <tt>/etc/etcd/etcd.conf</tt> | |||
Process: | |||
<pre> | |||
/usr/bin/etcd --name=master1.rdu20.internal --data-dir=/var/lib/etcd --listen-client-urls=https://192.199.0.199:2379 | |||
</pre> | |||
===master api Daemon=== | ===master api Daemon=== | ||
Revision as of 20:40, 17 May 2017
Internal
Master Node
The master node runs, in order, these services:
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 controller daemon and master api daemon and 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 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