<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>At the midcycle, we had only 1 session on upgrade, and we didn’t come to any clear consensus on how it should be handled. I took a stab at writing what I think are the requirements for upgrade in this blueprint:</div>
<div><br>
</div>
<div><a href="https://blueprints.launchpad.net/kolla/+spec/upgrade-strategy">https://blueprints.launchpad.net/kolla/+spec/upgrade-strategy</a></div>
<div><br>
</div>
<div>The blueprint can be edited (yellow exclamation point) if someone thinks I missed some requirements.</div>
<div><br>
</div>
<div>This blueprint is in the discussion phase. I’d like to sort out our technical implementation and approach – and to do that, we need to have a discussion in the blueprint. Most folks are aware, but you can use the whiteboard to have a discussion. Add
a —ircnick after so we know who originated the idea. I’ll leave the blueprint in the discussion phase until August 31st, after which point we have approximately 1 month to sort this problem out.</div>
<div><br>
</div>
<div>We need all the work that is necessary to do an upgrade post liberty to land in the source base. Extra points for actually finishing the job on upgrade throughout the codebase and within Ansible itself. One of the major rationales for using containers
is they make upgrade atomic – lets actually deliver on that!</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
</body>
</html>