Luke Meyer fbb4e1ca73 retry package operations		7 yıl önce
..
defaults	73bf3e7137 Combine openshift_node and openshift_node_dnsmasq	7 yıl önce
files	73bf3e7137 Combine openshift_node and openshift_node_dnsmasq	7 yıl önce
handlers	73bf3e7137 Combine openshift_node and openshift_node_dnsmasq	7 yıl önce
meta	b6af2d0e1f Merge pull request #6269 from mgugino-upstream-stage/clock-depends	7 yıl önce
tasks	fbb4e1ca73 retry package operations	7 yıl önce
templates	73bf3e7137 Combine openshift_node and openshift_node_dnsmasq	7 yıl önce
README.md	16ca0b65ae Remove some reminants of Atomic Enterprise	7 yıl önce

OpenShift Node

Node service installation

Requirements

Ansible 2.2
One or more Master servers
A RHEL 7.1 host pre-configured with access to the rhel-7-server-rpms, rhel-7-server-extras-rpms, and rhel-7-server-ose-3.0-rpms repos

Role Variables

From this role:

Name	Default value
oreg_url	UNDEF (Optional)	Default docker registry to use
oreg_url_node	UNDEF (Optional)	Default docker registry to use, specifically on the node

Dependencies

Example Playbook

Notes

Currently we support re-labeling nodes but we don't re-schedule running pods nor remove existing labels. That means you will have to trigger the re-schedulling manually. To re-schedule your pods, just follow the steps below:

oadm manage-node --schedulable=false ${NODE} oadm manage-node --drain ${NODE} oadm manage-node --schedulable=true ${NODE}`

If you are using version less than 1.5/3.5 you must replace --drain with --evacuate.

TODO

License

Apache License, Version 2.0

Author Information