summaryrefslogtreecommitdiffstats
path: root/roles/openshift_node/templates/openvswitch.docker.service
Commit message (Collapse)AuthorAgeFilesLines
* Remove openshift_node_facts roleMichael Gugino2017-12-181-1/+1
| | | | | This commit removes the remainder of openshift_node_facts role.
* Implement container runtime roleMichael Gugino2017-12-011-4/+4
|
* Update systemd units to use proper container service nameSteve Milner2017-05-091-4/+4
| | | | | | | - If using a system container: container-engine - If using a package install: docker Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1448800
* use RestartSec to avoid default rate limit in systemdBrenton Leanhardt2016-04-121-0/+1
| | | | Lifted from https://github.com/openshift/origin/pull/8317
* make docker service want ose containerized servicesSeth Jennings2016-03-281-1/+1
| | | | | | | | | | | | | | | | There are points where the docker service is restarted during the install. Sometimes the services that are PartOf docker.service do not get restarted when docker is restarted. https://bugzilla.redhat.com/show_bug.cgi?id=1318948 Systemd documentation recommends using "wants" as the perferred means of creating startup linkages between units. This patch makes the ose services wanted by the docker service rather than multi-user.target. This creates a downward link from the docker service to the ose containerized services.
* improve ordering of systemd unitsJason DeTiberus2016-03-141-0/+1
|
* Correctly set the image tag for containerized installs (and upgrades)Brenton Leanhardt2016-03-031-1/+2
|
* Give openvswitch container some time to startJan Provaznik2016-01-291-0/+1
| | | | | | It's possible that openshift containers are started sooner than openvswitch starts/sets networking (this typically happens when docker service is restarted).
* Containerization work by @sdodsonScott Dodson2015-12-151-0/+13
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-15 23:37:39 +0000