summaryrefslogtreecommitdiffstats
path: root/roles/openshift_node_upgrade/templates
Commit message (Collapse)AuthorAgeFilesLines
* Add node unit file on upgradeSteve Milner2017-06-062-0/+2
| | | | | | | | When rpm_upgrade is used for upgrading the node's unit file will be overridden. systemd is then reloaded if the files are templated successfully. Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1455843
* node, systemd: change Requires to Wants for openvswitchGiuseppe Scrivano2017-05-171-1/+1
| | | | | | | | | Sometimes the node container is not started on a container-engine restart. Use a weaker dependency on openvswitch that is causing this issue Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1451192 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* Update systemd units to use proper container service nameSteve Milner2017-05-093-10/+10
| | | | | | | - If using a system container: container-engine - If using a package install: docker Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1448800
* Make /rootfs mount rslaveScott Dodson2017-03-211-1/+1
| | | | Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1427807
* node/sdn: make /var/lib/cni persistent to ensure IPAM allocations stick ↵Dan Williams2017-03-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | around across node restart With the move to a CNI plugin, docker no longer handles IPAM, but CNI does through openshift-sdn's usage of the 'host-local' CNI IPAM plugin. That plugin stores IPAM allocations under /var/lib/cni/. If the node container gets restarted, without presreving /var/lib/cni, the IPs currently allocated to running pods get lost and on restart, openshift-sdn may allocate those IPs to new pods causing duplicate allocations. This never happened with docker because it has its own persistent IPAM store that does not get removed when docker restarts. Also because (historically) when docker restarted, all the containers died and the IP allocations were released by the daemon. Fix this by ensuring that IPAM allocations (which are tied to the life of the pod, *not* the life of the openshift-node process) persist even if the openshift-node process restarts. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1427789
* Move current node upgrade tasks under openshift_node_upgrade roleJan Chaloupka2017-02-015-0/+58