Brenton Leanhardt 590e5582ed Bug 1322788 - The IMAGE_VERSION wasn't added to atomic-openshift-master-api and atomic-openshift-master-controllers %!s(int64=9) %!d(string=hai) anos
..
defaults 590e5582ed Bug 1322788 - The IMAGE_VERSION wasn't added to atomic-openshift-master-api and atomic-openshift-master-controllers %!s(int64=9) %!d(string=hai) anos
handlers 8f7b31051d improve ordering of systemd units %!s(int64=9) %!d(string=hai) anos
meta 2c608429d8 Bug 1320829 - Ensure docker installed for facts %!s(int64=9) %!d(string=hai) anos
tasks 67fda43df0 Add AWS cloud provider support. %!s(int64=9) %!d(string=hai) anos
templates 93d48b330e make docker service want ose containerized services %!s(int64=9) %!d(string=hai) anos
vars 590e5582ed Bug 1322788 - The IMAGE_VERSION wasn't added to atomic-openshift-master-api and atomic-openshift-master-controllers %!s(int64=9) %!d(string=hai) anos
README.md 1b3fff6248 Atomic Enterprise related changes. %!s(int64=9) %!d(string=hai) anos

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