[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: BKMs on upgrading openshift instance?



----- Original Message -----
> From: "Shoumeng Yan" <shoumeng yan intel com>
> To: dev lists openshift redhat com
> Sent: Tuesday, June 25, 2013 8:05:37 AM
> Subject: BKMs on upgrading openshift instance?
> 
> Hello there,
> 
> Are there any BKMs on upgrading an openshift instance with minimized
> downtime?
> 

I'm not sure we have any firm documentation on it but things sort of depend on your environment and installation.  It's best to treat the upgrade in three main parts.  The nodes, the broker/console and the gears.

The broker/console upgrades are fairly standard.  They're just websites, put a couple of them up behind a load balancer and do one at a time, making sure to take the other down as you go.

The nodes / gears are different.  You have to be careful during node upgrades because older versions of gears may not function the same with newer versions of the node libraries.  In those scenarios you'll have to examine your gears, probably test them in pre production environments and do the upgrades carefully across your environment.  The v2 cartridge format should make this easier in that we've designed the cartridges to be fairly self contained so even if an update breaks something, the cartridge should still run allowing users to create a new application (with the new node code) and migrate the application code as needed.

    -Mike

> Thanks,
> Shoumeng
> 
> 
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]