<div dir="ltr"><div><div>Thanks all for feedback.<br><br></div>Is anyone aware of any documented procedures on how to apply minor releases? Maybe worth having a section in the documentation?<br><br></div><div>Dani<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 8:49 PM, Kevin Bringard (kevinbri) <span dir="ltr"><<a href="mailto:kevinbri@cisco.com" target="_blank">kevinbri@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
><br>
> Yes, you can run mismatched versions of openstack projects. In general move away from thinking of openstack as a single system that must be upgraded in lock-step and think of openstack as a loosely coupled individual set of projects. Where you can run mismatched versions. Possible to even run say: Master version of keystone, 2014.2.2 version of nova/neutron and 2014.1.2 version of heat (Note: I have no clue if that config actually works - assuming all those versions supplied the required features it *should* work.)<br>
<br>
</span>We've had luck mismatching major versions as outlined above. Specifically, running Juno (2014.2.x) versions of heat/ceilometer with Icehouse (2014.1.x) versions of everything else. But, also to Kris's point, I'd probably be careful to keep nova/neutron in pretty close lockstep as there's a lot of dependencies between the two.<br>
<br>
I should also point out, doing the above creates some logistical issues. Specifically: ceilometer-compute-agent needs to be juno version, but it runs on the compute nodes so you need to be careful about dependencies between it and nova-compute, the ovs-agent and whatever other things you've got running on the node. This was something we discussed a little bit at the operators meet-up in Philly (venvs, VMs, containers, etc.), but it's worth pointing out that in some cases it's possible you'll run into similar situations with minor versions' requirements as well.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Kevin<br>
</font></span><span class="im HOEnZb"><br>
> ____________________________________________<br>
><br>
> Kris Lindgren<br>
> Senior Linux Systems Engineer<br>
> GoDaddy, LLC.<br>
><br>
><br>
> From: Daniel Comnea <<a href="mailto:comnea.dani@gmail.com">comnea.dani@gmail.com</a>><br>
> Date: Monday, March 30, 2015 at 1:19 PM<br>
> To: Daniel Comnea <<a href="mailto:comnea.dani@gmail.com">comnea.dani@gmail.com</a>><br>
> Cc: "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>" <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>>, "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Subject: Re: [Openstack-operators] [Openstack-dev][all] how to apply security/back-ported release to Icehouse production<br>
><br>
> No thoughts?<br>
><br>
><br>
><br>
> On Sat, Mar 28, 2015 at 10:35 PM, Daniel Comnea <<a href="mailto:comnea.dani@gmail.com">comnea.dani@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> Can anyone shed some light as to how you upgrade/ applies the security/back-ported patches?<br>
><br>
> E.g - let's say i already have a production environment running Icehouse 2014.1 as per the link [1] and i'd like to upgrade it to latest Icehouse release 2014.1.4.<br>
><br>
> Also do you have to go via sequential process like<br>
><br>
> 2014.1 -> 2014.1.1 -> 2014.1.2 -> 2014.1.3 -> 2014.4 or i can jump from 2014.1 to 2014.1.4?<br>
><br>
> And the last questions is: can i cherry pick which bugs part of a project to pull? Can i pull only 1 project - e.g HEAT from latest release 2014.1.4?<br>
><br>
><br>
> Thanks,<br>
> Dani<br>
><br>
> [1] <a href="https://wiki.openstack.org/wiki/Releases" target="_blank">https://wiki.openstack.org/wiki/Releases</a><br>
><br>
</span><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div></div></blockquote></div><br></div>