<feed xmlns='http://www.w3.org/2005/Atom'>
<title>csa/devops/ansible-patches/openshift.git/playbooks/common/openshift-cluster/upgrades/openshift.docker.node.service, branch ands</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.master.suren.me/cgit/csa/devops/ansible-patches/openshift.git/'/>
<entry>
<title>Introduce 1.3/3.3 upgrade path.</title>
<updated>2016-07-25T15:16:16+00:00</updated>
<author>
<name>Devan Goodwin</name>
<email>dgoodwin@redhat.com</email>
</author>
<published>2016-07-15T18:50:31+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.master.suren.me/cgit/csa/devops/ansible-patches/openshift.git/commit/?id=31707737a5473bb5cf6545b6675b192a64a913c7'/>
<id>31707737a5473bb5cf6545b6675b192a64a913c7</id>
<content type='text'>
Refactored the 3.2 upgrade common files out to a path that does not
indicate they are strictly for 3.2.

3.3 upgrade then becomes a relatively small copy of the byo entry point,
all calling the same code as 3.2 upgrade.

Thus far there are no known 3.3 specific upgrade tasks. In future we
will likely want to allow hooks out to version specific pre/upgrade/post
tasks.

Also fixes a bug where the handlers were not restarting
nodes/openvswitch containers doing upgrades, due to a change in Ansible
2+.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Refactored the 3.2 upgrade common files out to a path that does not
indicate they are strictly for 3.2.

3.3 upgrade then becomes a relatively small copy of the byo entry point,
all calling the same code as 3.2 upgrade.

Thus far there are no known 3.3 specific upgrade tasks. In future we
will likely want to allow hooks out to version specific pre/upgrade/post
tasks.

Also fixes a bug where the handlers were not restarting
nodes/openvswitch containers doing upgrades, due to a change in Ansible
2+.
</pre>
</div>
</content>
</entry>
</feed>
