Scott Dodson 6217d75e10 Get rid of openshift_node_config_file entirely 8 éve
..
defaults 0c7433838c Work towards determining openshift_version when unspecified. 8 éve
handlers 9890ee74b5 Check for use_openshift_sdn when restarting openvswitch. 8 éve
meta 7ab9792006 Move role dependencies to playbooks. 8 éve
tasks 6217d75e10 Get rid of openshift_node_config_file entirely 8 éve
templates 1f2276fff1 Fix OpenStack cloud provider 8 éve
README.md 0b8e8cd5b2 Fix up some broken markdown formatting (mostly tables) 8 éve

README.md

OpenShift/Atomic Enterprise Node

Node service installation

Requirements

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
openshift_node_debug_level openshift_debug_level Verbosity of the debug logs for node
oreg_url UNDEF (Optional) Default docker registry to use

From openshift_common:

Name Default Value
openshift_debug_level 2 Global openshift debug log verbosity
openshift_public_ip UNDEF (Required) Public IP address to use for this host
openshift_hostname UNDEF (Required) hostname to use for this instance

Dependencies

openshift_common

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 --evacuate ${NODE} oadm manage-node --schedulable=true ${NODE} `

TODO

License

Apache License, Version 2.0

Author Information

TODO