| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Switching to dest instead of path for lineinfile. path is the name for
ansible 2.3+ though dest will work for 2.2 and 2.3.
Ref: http://docs.ansible.com/ansible/lineinfile_module.html
|
|
|
|
| |
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1450310
|
|
|
|
| |
Requires: https://github.com/projectatomic/atomic/pull/999
|
|
|
|
|
| |
The package is required so that openshift_facts is able to use the
docker client to gain information on the versions.
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| | |
This flag is currently being set within the system container via
the init.sh
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
| |
Instead of providing every possible key in the daemon.json configuration
file, this update only provides keys which are actively set/used by the
installer.
|
|\
| |
| | |
lower case in /etc/daemon.json and correct block-registry
|
| | |
|
|\ \
| |/
|/| |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| | |
We did this in 3.5 but never on master and we never came back to add
migration support. So we'll revert this on master and if/when we add
migration support we'll switch the default.
|
| |
| |
| |
| |
| | |
The daemon.json configuration key is block-registries. The code and
installer bits call it blocked-registries.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of using bare lists and dicts this change converts variables
into json for use with daemon.json. jinja2 does have an ability to do
this in side of templates, however it is only available in 2.9+. Until
then the use of ansible's to_json in the playbook is being used.
Refs:
- http://jinja.pocoo.org/docs/2.9/templates/#tojson
- http://docs.ansible.com/ansible/playbooks_filters.html#filters-for-formatting-data
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change allows for the use of either the traditional package install
of docker OR a system container install of docker.
Two new inventory options, openshift_docker_use_system_container and
openshift_docker_systemcontainer_image_registry_override, have been
added which are be used to install with a system container. By default
this option is commented out.
One new fact has been added:
- docker.service_name: docker by default, container-engine-docker
for system container
|
| |
|
|
|
|
| |
string everywhere it is used.
|
|
|
|
|
| |
Allows controlling 'selinux-enabled' docker options
Can be set to true or false
|
| |
|
| |
|
|
|
|
|
| |
* Added checks to make ci for yaml linting
* Modified y(a)ml files to pass lint checks
|
|
|
|
|
|
| |
* Ansible systemd module used in place of service module
* Refactored command tasks which are no longer necessary
* Applying rules from openshift-ansible Best Practices Guide
|
| |
|
|
|
|
|
| |
The Ansible package module will call the correct package manager for the
underlying OS.
|
|
|
|
|
|
|
|
|
| |
Docker service is started prior to configuration changes being applied.
The service is then not restarted by the handlers, so configuration
changes are not applied.
We now start the docker service only once all config changes have been
made.
|
|
|
|
|
|
|
|
|
|
|
| |
The docker role requires iptables-services to be installed. Added
dependency on so_firewall role to ensure the iptables service is
installed first. Currently this will only work with iptables and
not with firewalld.
* Added allow_duplicates to os_firewall role meta
* Removed unused task from docker/tasks
* Corrected os_firewall Defaults in README
|
|
|
|
|
|
|
|
|
|
| |
The docker service adds rules to the iptables configuration to support proper
network functionality for running containers. If the service is started prior
to iptables, these rules are not properly created.
* Ensure iptables is started prior to docker
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1390835
|
| |
|
|
|
|
|
|
|
|
| |
This improves the situation further and prevents configuration changes
from accidentally triggering docker restarts, before we've evacuated
nodes. Now in two places, we skip the role entirely, instead of previous
implementation which only skipped upgrading the installed version.
(which did not catch config issues)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
If Docker 1.8.2 is pre-installed, and no docker_version was requested,
role will now error out because 1.9.1 is required.
If docker_version is set to <= 1.9.1, we also error out as this is not
supported.
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The variable here must be explicitly passed to the docker role, if it's
passed sometimes and not others, the docker config changes triggers a
docker restart effectively killing everything on the node in an unsafe
manner.
Instead lets make sure the value is set.
|
|/ |
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Bug 1338726 - never abort install if the latest version of docker is already installed
|