RightScale uses mirrors (see RightScale Mirrors) to maintain the following software repositories in order to ensure that your deployments stay current and up-to-date with the latest software versions.  Software repositories are archived each day, however RightScale does not keep track of what versions of software packages are frozen on a particular day.  The purpose of the frozen repositories is to ensure that a server will be launched with the same versions of software regardless of when that server is launched again in the future.

RightScale ServerTemplates are published with frozen repositories and are associated with a particular RightImage^TM.  It's important to understand that there is no guarantee that newer RightImages will work correctly using older versions of software packages in the frozen repositories.  To ensure that an older ServerTemplate works with one of the newer RightImages, you need to clone the template and refreeze the software repositories to a more recent date where the RightImage and the repositories are compatible.  Always check to make sure that a server boots correctly.

Note: You can only freeze software repositories in RightImage V4.1.0 or higher.

• CentOS Base
• CentOS Updates
• CentOS Add-ons
• CentOS Extras
• CentOS Plus
• Epel
• RightScale Software Epel
• RubyGems
• Ubuntu Hardy
• Ubuntu Intrepid
• Ubuntu Jaunty
• Ubuntu Lucid

• Ubuntu Maverick

Note: enterprise linux distributions (such as RedHat or SLES) operate separate repositories that cannot be frozen.

There may be situations where you want to "freeze" or lockdown particular software repositories.  For exampe, your current application is not compatible with the latest version of CentOS.  You now have the ability to freeze the CentOS repository to a particular date in time.  This ensures that your servers are always launched with the appropriate version of CentOS.