Tim Bielawa 0b8e8cd5b2 Fix up some broken markdown formatting (mostly tables) 8 rokov pred
..
defaults 926c3d5c7b Move os_firewall_allow from defaults to role dependencies. 8 rokov pred
handlers 1b720085f2 Fixed openvswitch not upgrading. 9 rokov pred
meta 926c3d5c7b Move os_firewall_allow from defaults to role dependencies. 8 rokov pred
tasks a704c30b3a Enable additional 'virt_sandbox_use_nfs' seboolean as per documentation: 8 rokov pred
templates 6e3c6dda93 Make /var/lib/origin mounted rslave 8 rokov pred
vars 590e5582ed Bug 1322788 - The IMAGE_VERSION wasn't added to atomic-openshift-master-api and atomic-openshift-master-controllers 9 rokov pred
README.md 0b8e8cd5b2 Fix up some broken markdown formatting (mostly tables) 8 rokov pred

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