OpenShift Bot c5f4a60fdd Merge pull request #4234 from vshn/feature/oreg_url_masternode преди 7 години
..
defaults 7eb36e5ee1 Added Calico BGP Port 179 to Firewalld преди 8 години
handlers e266fb169d Workaround sysctl module issue with py3 by converting task to lineinfile. преди 7 години
meta 7eb36e5ee1 Added Calico BGP Port 179 to Firewalld преди 8 години
tasks c5f4a60fdd Merge pull request #4234 from vshn/feature/oreg_url_masternode преди 7 години
templates 7f805f9a0c node, systemd: change Requires to Wants for openvswitch преди 8 години
README.md 0ee812822a allow to configure oreg_url specifically for node or master. refs #4233 преди 7 години

README.md

OpenShift/Atomic Enterprise 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
openshift_node_debug_level openshift_debug_level Verbosity of the debug logs for node
oreg_url UNDEF (Optional) Default docker registry to use
oreg_url_node UNDEF (Optional) Default docker registry to use, specifically on the node

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 --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

TODO