Release Date: April 14, 2010
Apr 28, 2010 -- Support was added for Amazon's first Asia Pacific Region ('AWS-AP') in Singapore. You can now use the Dashboard or RightScale API to launch and manage cloud resources in that AWS region. Check out our blog post to learn more about how it's Accelerating Cloud Adoption.
Reminder: ServerTemplates and RightImages are typically released 3-7 days after the new release of the RightScale Cloud Management Platform. See the ServerTemplate and MultiCloud Images Release Notes.
Release Date: April 14, 2010
Release Time: 9:00pm Pacific
The focus of this release is:
Please read the release notes in their entirety for a more exhaustive understanding of what comprises this release.
ServerTemplates and MultiCloud Images are released approximately 1 week after a Dashboard release. Planned highlights include:
See the ServerTemplate and MultiCloud Images Release Notes.
Note: Any numbers in parentheses below are for internal RightScale use only. Please ignore them, they are simply tracking numbers.
- Disclaimer -
The following new features have been added to the RightScale Cloud Management Platform. Be sure to read the documentation, follow best practice principles, and thoroughly test any new functionality before making any changes to your production deployment.
In the October 2009 Dashboard Release we introduced the MultiCloud Marketplace, which shows an aggregated list of all RightScale objects that are available to the RightScale account. Below are the main features of the new MultiCloud Marketplace Interface:
You now have the ability to stop and start EC2 Instances. The ability to stop/start an instance is only supported on instances that are launched with an EBS-based machine image. If you have an EC2 instance that was launched with an S3-based machine image, the "start" and "stop" buttons will not be displayed.
Please see Server States and FAQ 149 - What's the difference between Terminating and Stopping an EC2 Instance? to learn more. (gr-7980)
In RightScale, you can now launch Spot Instances on EC2. At the Server level you can now specify whether you want to launch an on-demand or spot instance. Currently, RightScale does not support spot instance groups. Please see Instance Purchase Options to learn more. (gr-8049)
RightScale released a new AWS Gem that supports Ruby 1.9. There is also support for EC2 Spot Instances, m2.xlarge instance types, security groups for Eucalyptus private clouds, and more. See right_aws Release Notes. (gr-9321)
There is now "beta" support for Windows.
We now offer RightLink Installers for Ubuntu, CentOS, or Windows instances. Follow the tutorials below to create an AMI that is RightScale-enabled with RightLink. RightLink must be installed on an instance in order to enable all of the automation features available through the RightScale platfom, as well as the ability to run Chef recipes. The following tutorials only apply to users who are not using v5 RIghtImages, which have RightLink preinstalled. See Creating RightScale-enabled Images with RightLink.
Changes to the software are listed here. Changes usually refer to enhancements to existing features, minor UI changes, additional logging or messaging, etc.
The following enhancements have been made to the RightScale API:
Performance has been improved with API queries, in particular the following queries are more efficient (gr-6199w):
Note: New rdoc posted 4/16/2010.
The previous release of the Dashboard introduced the MultiCloud Image (MCI). With that release, a ServerTemplate could only reference a single MCI. This release allows a ServerTemplate to include multiple MCIs. Published ServerTemplates from RightScale will have a list of MultiCloud Images that the template was tested with prior to release. A ServerTemplate will have a default MCI selected, but you can select any of the other MultiCloud Images that are listed. This added functionality requires additional fields in the Add Server dialog. The new fields are for specifying the MultiCloud Image and Instance Type. The Add Server dialog box with its updated fields is used in several locations within the Dashboard. Such as:
Additionally, there is a new Images tab when designing ServerTemplates. If you select the Add MultiCloud Image action button on the Images tab, you are presented with a MCI Imager selector dialog box.
Previously, at the Server level, once you created a Server from a ServerTemplate, the appropriate image for that cloud was selected. Now there is an MCI that's defined at the Server level. By default, a Server will inherit the MCI that's defined by the ServerTemplate. However, you can select a different MCI (Manage -> Servers -> Inactive tab -> Edit action button includes a new MCI drop down menu) or even select a completely different machine image (one that's not referenced by an MCI) just like before, although this is not a recommended best practice.
When you share a HEAD version of a RightScale object that supports versioning (ServerTemplates, RightScripts, MultiCloud Images), you now have the ability to control when the subscribers to that HEAD version will see your latest changes. Previously, subscribers would immediately inherit any changes that a publisher saved to a HEAD version. In order to push changes to a HEAD version in the MultiCloud Marketplace, use the "Republish to MultiCloud Marketplace" action button. Currently, there is no way to perform a diff between the publisher's HEAD version in their local collection and the published version (that people are subscribing to) that's in the MultiCloud Marketplace.
Previously, if ISV Partners wanted to share their published components (ServerTemplates, RightScripts, Macros, etc.) with other RighScale users, they had to make them available for use to everyone. All RightScale accounts would be able to find their published components in the MultiCloud Marketplace, import them to their local collection and use them as-is or clone them. Now, there is also a way for Partners to limit the use of their published components to only premium RightScale customers. Although, all RightScale accounts will still be able to view these shared components in the MultiCloud Marketplace, users of RightScale Free Edition will not have access to import these components unless they become premium customers.
To learn more see Publishing RightScale Components.
You can now create a Eucalyptus ServerTemplate, define a Server, and run a RightScript on a Eucalyptus VMI.
You now have the ability to set the 'username' for Eucalyptus cloud accounts. The username is used to identify ownership of cloud related assets like images. Cloud resources can only be edited by their owner. Previously, RightScale was unable to distinguish which user account created a cloud resource. However, now that you can enter your Eucalyptus username in the Dashboard, RightScale will be able to fiter through your cloud's resources and grant editing privileges accordingly. To add your Eucalyptus username, go to Settings -> Account -> Clouds tab.
With the new support for AWS Spot Instances, which can have a variable cost associated with them, we had to change our rate framework in order to get more accurate usage estimates. (For example, when viewing usage estimates from Dashboard -> Oveview tab.) The cost for instance usage is not necessarily a constant. We now have a more flexible rating framework that will work with all types of Cloud infrastructures and the instance types they use. Support for Windows has also been added. (bl-6232w, bl-6191w)
In order to promote consistency across all ServerTemplates published by RightScale, we've performed a minor migration where we've renamed some existing ServerTemplates that were already published in the MultiCloud Marketplace as well as committed new revisions of other templates in order to provide consistent and descriptive commit messages (e.g. Sprint 17 release - 03/04/2010).
Renaming Existing ServerTemplates
Most renaming changes were very minor and will probably not even be noticed by most users, however, previously imported ServerTemplates will inherit the changed name. No changes were made to the ServerTemplate itself. Only the name was changed.
|Old Name ||New Name |
|LB Nginx+HAproxy v1||Nginx + HAProxy v1|
|MONO App Server v5||Mono App Server v5|
|MONO FrontEnd v4||Mono Front End v4|
|MySQL Bootstrap v13||MySQL S3 Bootstrap v13|
|MySQL S3 Slave v13||MySQL S3 Additional v13|
|MySQL S3/EBS Toolbox||MySQL S3 to EBS Migration Toolbox|
|PHP App Server ELB (Ubuntu Alpha)||PHP App Server for ELB (Alpha)|
|PHP FrontEnd (Ubuntu) (Chef Alpha)||PHP FrontEnd (Chef Alpha)|
|Rails All-In-One Demo (Chef Alpha)||Rails All-In-One Trial (Chef Alpha)|
|Rails-Passenger FrontEnd (Ubuntu) (Chef Alpha)||Rails-Passenger FrontEnd (Chef Alpha)|
|MySQL (Chef Alpha)||MySQL Manager (Chef Alpha)|
Publishing Updated ServerTemplates
A new revision of the following ServerTemplates were published in order to provide a more helpful commit message. No changes were made to the ServerTemplate itself.
|Name ||New Commit Message|
|RightGrid Toolbox||Sprint 12 release - 08/10/09|
|Hadoop Toolbox||Sprint 12 release - 08/10/09|
|Memcached Toolbox||Sprint 12 release - 08/10/09|
|New Relic Performance Monitoring Toolbox||Sprint 12 release - 08/10/09|
|RightImage Creator - CentOS (Beta)||Sprint 16 release - 03/04/2010|
|RightImage Creator - Ubuntu (Beta)||Sprint 16 release - 03/04/2010|
|RightImage Migrator S3 to EBS (Beta)||Sprint 16 release - 03/04/2010|
|Tomcat6 App Server v9||Sprint 17 release - 04/09/2010|
|Tomcat6 FrontEnd v9||Sprint 17 release - 04/09/2010|
|Rails-Passenger App Server (Chef Alpha)||Sprint 17 release - 04/09/2010|
|PHP App Server (Chef Alpha)||Sprint 17 release - 04/09/2010|
|MySQL S3 Slave v13||Sprint 17 release - 04/09/2010|
|MySQL 5.1 EBS v2 (Beta)||Sprint 17 release - 04/09/2010|
|Mephisto All-In-One v8||Sprint 17 release - 04/09/2010|
|LAMP v4 Trial||Sprint 17 release - 04/09/2010|
|LAMP v4 All-In-One||Sprint 17 release - 04/09/2010|
|Apache + HAproxy v9||Sprint 17 release - 04/09/2010|
The following bugs have been resolved in this release.
Previously, if you changed your Credentials it would effectively break all of your RightScript attachments, requiring you to go through each one and re-attach them (Design -> RightScripts -> ScriptName -> Attachments tab) before the ServerTemplates that make use of the RightScript would work. This issue has been resolved, eliminating this manual step. (gr-6238w)
Starting in January 2010, the bandwidth usage for all AWS accounts was reporting $0.00. That is, the estimates factored into Reports -> Usage for AWS bandwidth (GB of data transfer into or out of AWS) was zero. This has been resolved and the correct estimate should be displayed. (bl-6278w)
If you created a Server based on a ServerTemplate that used a EBS based image for Linux or Windows and then launched it, two EBS volumes attached without error, however a third "phantom" volume attempted to attach resulting in an error and an audit entry similar to the following:
Snapshot to instance attachment failed due to: InvalidParameterValue . . .
This error could occur whether you used the "Attach Snapshot" or "Attach Blank Volume" action buttons from the Server's Volumes tab. (gr-6148w)
Previously, when a user attempted to update a macro through API, a "Permission Denied" error would be reported. However, the macro would still be updated. This has now been fixed so that the update action returns a success (204 No Content) subject to valid permissions. (gr-5717w)
Under rare circumstances the following error could occur:
EBS snapshot to EC2 instance task is queued. Snapshot to instance attachment failed due to: undefined method `name' for nil:NilClass
This error was not consistantly reproducible, but seemed more likely to occur with the following combination: Windows EBS based instance launched inside AWS Virtual Private Cloud (VPC). (gr-6125w)
Previously in the Dashboard, the HEAD version of some imported templates were shown as unpublished, when they were actually published. This has now been fixed so that the latest template is correctly shown as published and versionable. (bl-6166w)
Previously, the ISV Usage Report showed incorrect Server Template usage and erroneously displayed aggregate usage from several accounts using a particular Server Template as one entry. The report has been fixed so that each account now reports only the correct number of Server Template hours. (bl-6342w)
An error was noted in usage reports for some templates used by ISVs wherein the number of hours usage was doubled. This condition has been fixed and the correct number of hours usage per server template usage is now being reported. (bl-6453w)
Please report issues to: email@example.com
© 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.