Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Lifecycle Management > Deployment Management > Performing Upgrades in the Cloud > Major Software Upgrade Scenarios

Major Software Upgrade Scenarios

Table of Contents
No headers

Fortunately, there are several ways to perform major software upgrades in the Cloud.  Since each website and application is unique, each person might have a different upgrade strategy.  When discussing upgrade strategies, it's important to realize that one upgrade strategy does not fit all.  Remember, the goal is always the same--to have a safe and successful upgrade with minimal site downtime and impact to your users.  However, determining the best steps to achieve that goal may be different for each person.  Use the upgrade scenarios below as general guidelines for developing your own upgrade strategy.

A major upgrade is generally reserved for performing large scale changes that would otherwise break you current application.  In such cases, site downtime is mandatory.  For example, if you drastically change the database schema or use completely new ServerTemplates that might install new versions of software (e.g. migrating from MySQL v5.1 to v5.2).  Essentially, if you ever have any compatibility concerns whatsoever that your changes could possibly break your current application, you will need a solid upgrade strategy.

You must to post a comment.
Last modified
23:00, 16 May 2013



This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.