Open Stack

On Mon, Mar 30, 2015 at 3:19 PM, Daniel Comnea <comnea.dani at gmail.com> wrote:
> No thoughts?

You don't need to do sequential upgrades, you *should* be able to
cherry pick which components to upgrade because there *shouldn't* be
and RPC format changes in back ports. That said I once had issues
becasue of an RPC change when I updated the Nova controller
(nova-api) but not the compute nodes though I forget how long ago that
was, it may have been Icehouse or may have been Havana.  Though even
with that just pulling the new point release on the compute nodes
fixed everything and no harm came to any existing instances.

In practice after testing in my test cloud, 'apt-get dist-upgrade' (on
Ubuntu LTS w/ cloudarchive packages) has worked for me all bu that one
time semi-noted above for point releases since 12.04/Essex now on
14.04/Juno.

My production cloud is relatively simple, single site, 75 compute
nodes, no cells or anything so not sure if thing get more fragile as
you add more complexity and components.

-Jon


> 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
>