| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Attempt to fix containerized node start failure with Docker 1.10.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It appears that in some situations (can't reliably reproduce yet), node
will fail to start. This appears to be related to the node-dep service
and possibly it's environment file.
This file is also an EnvironmentFile for the node service, but it's only
created by the node-dep service, and it looks like it may try to read
it's environment before the node-dep service has fully started and
created the file.
Workaround with a an explicit service start.
|
|/
|
|
|
|
| |
Docker 1.10 is not widely available in RHEL / CentOS yet, lets remove
the restriction for users of master / origin. We can revert as soon as
it's available publically.
|
|\
| |
| | |
Add lower case proxy variables
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some applications expect the *_PROXY variables to be lower case.
To support this too inject them in addition to the upper case ones.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Reviewed-by: Fabio Huser <fabio.huser@siemens.com>
|
|\ \
| | |
| | | |
Bug 1338726 - never abort install if the latest version of docker is already installed
|
| | | |
|
| | |
| | |
| | |
| | | |
installed
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Docker 1.10 is no longer tolerant of commands like "docker pull
myimage:" when we do not have an image tag in play.
Adjust all occurrences with one that only includes the : if a version is
defined.
Adjust the containerized CLI wrappers for a similar problem.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds a separate playbook for Docker 1.10 upgrade that can be run
standalone on a pre-existing 3.2 cluster. The upgrade will take each
node out of rotation, and remove *all* containers and images on it, as
this is reportedly faster and more storage efficient than performing the
in place 1.10 upgrade.
This process is integrated into the 3.1 to 3.2 upgrade process.
Normal config playbooks now become 3.2 only, and require Docker 1.10.
Users of older environments will have to use an appropriate
openshift-ansible version.
Config playbooks no longer are in the business of upgrading or
downgrading docker.
|
|\ \ \ \
| | | | |
| | | | | |
Ansible 2.1 support.
|
| |/ / / |
|
| | | |
| | | |
| | | |
| | | | |
dependencies.
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Add flag to manage htpasswd, or not.
|
| | | |
| | | |
| | | |
| | | | |
Also move file mode to the file-exists check to not specify twice.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Setting `openshift_master_manage_htpasswd` falsy will disable managing
the htpasswd file. It won't get overwritten/generated.
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Configure default docker logging options.
|
| |/ / |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Fix error with stopping services that may not exist.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Causes a hard failure due to missing etcd/atomic-openshift-master
services. Instead, check that the services exist before ensuring they're
stopped/disabled.
|
|\ \ \
| | | |
| | | | |
[v2] Move os_firewall_allow from defaults to role dependencies.
|
| | | | |
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
wait metrics-deployer complete (need to configure nodes before hosted…
|
| | | |
|
|\ \ \
| | | |
| | | | |
Switch to using CentOS SIG repos for Origin installs
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Separate master and haproxy config playbooks.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Move haproxy configuration to a separate openshift-loadbalancer play.
* Move the haproxy role to openshift_loadbalancer.
* Add openshift_loadbalancer* facts which drive haproxy configuration.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Cleanup following move to openshift-tools
|
| | | | |
| | | | |
| | | | |
| | | | | |
openshift-tools
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Add openshift_clock role
|
| | | | |
| | | | |
| | | | |
| | | | | |
openshift_etcd
|
| | | | | |
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix resolv conf
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
According to the man page for resolv.conf # needs to be in the first collumn in
order to start a comment. While this didn't seem to affect glibc's resolver it
did really confuse the kubelet which parses the host's resolv.conf
|
|\ \ \ \
| |/ / /
|/| | | |
Refactor openshift certificate roles
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Conditionally bind mount /usr/bin/docker-current when it is present
* fix upgrade
* add atomic-openshift-node-dep files to uninstall playbook
* Fix variable expansion
|
|\ \ \
| | | |
| | | | |
99-origin-dns.sh adds a comment to /etc/resolv.conf on every execution of NetworkManager dispatcher
|