Open Stack

Thanks all for feedback.

Is anyone aware of any documented procedures on how to apply minor
releases? Maybe worth having a section in the documentation?

Dani

On Mon, Mar 30, 2015 at 8:49 PM, Kevin Bringard (kevinbri) <
kevinbri at cisco.com> wrote:

>
> >
> > 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.)
>
> 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.
>
> 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.
>
> -- Kevin
>
> > ____________________________________________
> >
> > Kris Lindgren
> > Senior Linux Systems Engineer
> > GoDaddy, LLC.
> >
> >
> > From: Daniel Comnea <comnea.dani at gmail.com>
> > Date: Monday, March 30, 2015 at 1:19 PM
> > To: Daniel Comnea <comnea.dani at gmail.com>
> > Cc: "openstack-operators at lists.openstack.org" <
> openstack-operators at lists.openstack.org>, "OpenStack Development Mailing
> List (not for usage questions)" <openstack-dev at lists.openstack.org>
> > Subject: Re: [Openstack-operators] [Openstack-dev][all] how to apply
> security/back-ported release to Icehouse production
> >
> > No thoughts?
> >
> >
> >
> > On Sat, Mar 28, 2015 at 10:35 PM, Daniel Comnea <comnea.dani at gmail.com>
> wrote:
> > Hi all,
> >
> > Can anyone shed some light as to how you upgrade/ applies the
> security/back-ported patches?
> >
> > 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.
> >
> > Also do you have to go via sequential process like
> >
> > 2014.1 -> 2014.1.1 -> 2014.1.2 -> 2014.1.3 -> 2014.4 or i can jump from
> 2014.1 to 2014.1.4?
> >
> > 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?
> >
> >
> > Thanks,
> > Dani
> >
> > [1] https://wiki.openstack.org/wiki/Releases
> >
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150331/7139373b/attachment.html>