Note: ServerTemplates and RightScripts are typically released 3-7 days after the new release of the RightScale Cloud Management Platform. Thanks for your patience!
Release Date: September 15, 2009
Release Time: 9:00pm PDT
Description: The focus of this release is:
Please read the release notes in their entirety for a more exhaustive understanding of what comprises this release.
Contact Information:
Terminology:
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.
You now have the ability to use Chef cookbooks in your ServerTemplates. Simply create a link to public or private Chef repositories. Then you can add Chef recipes as boot, operational, or decommission scripts, just like how you would add normal RightScripts. This will be our first release supporting Chef, so there is limited functionality at this time. Currently, you cannot perform a diff on cookbooks/recipes. You will not receive an orange ball icon next to a recipe if it has been changed. Repositories are fetched roughly every 10 minutes. You can also use the Refetch action button for on-demand pulls. Supporting documentation is a work in progress. It is currently posted here.
Amazon Reserved Instances are now supported. To purchase a reserved instance you must be an 'admin' user. Sub-account users cannot purchase reserved instances. Once you purchase a reserved instance, Amazon will need to process the request before you will be able to see the reserved instance listed.
In late August Amazon launched support for its Viritual Private Cloud (VPC) to help bridge the gap between existing IT infrastructures and its public cloud. (Note: The August release is considered beta from AWS.) The RightScale Dashboard UI supports VPC for Enterprise accounts. Please click here for a summary of features on VPC. Only an 'admin' user can create a VPC. You can only create one VPC per RightScale account. For Sales related information, please contact sales@rightscale.com. We will be posting supporting documentation from a Dashboard perspective in our Support Portal shortly. (Search on "virtual private cloud" for precise documents.) See Virtual Private Cloud (VPC).
Several enhancements have been made to the support of the Rackspace Cloud. Our support of Rackspace is still 'Alpha' and is not production ready. See Rackspace for details about current RightScale support. (or-5569a)
Supported Features
Unsupported Features
See Add Rackspace Cloud Credentials to RightScale and Create a Rackspace ServerTemplate for more information.
You now have the ability to copy input parameters between current and next servers. For example, if you change an input parameter to the current (operational) server, but you want to make sure that if that server is ever relaunched, that the modified input parameter will be preserved, you can now click the 'copy inputs' button and select which input parameters you want to copy over. Note the "copy Inputs" works both directions between current and next servers. (gr-4195w)
A new RightScale API call has been added to retrieve raw sketchy (monitoring) data. (gr-2819w)
URL: GET /api/acct/1/servers/000/get_sketchy_data
See the RightScale API Reference section, Servers for more information.
A new RightScale API call has been added to list all non-terminated instances in a server array. (gr-4314w)
URL: GET /api/acct/1/server_arrays/000/instances
See the RightScale API Reference section, Server Arrays for more information.
The following Improvements have been made for ebs_volume attachments:
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 improvements have been made to the table views within the Dashboard.
If an instance exists, an audit entry will be created if any alerts are enabled or disabled. (gr-4281w)
Previously, each array had a single 'resize by' value that was used for scaling up and scaling down. However, there may be situations where you want to scale up and scale down at different rates. Server arrays now have separate resize values: Resize Up by, Resize Down by. For existing server arrays, the same value will be used for both resize actions. (gr-4221w)
In order to provide a more accurate resizing of an array, we've changed how server arrays evaluate an "active" instance. Previously, instances that were not fully operational were considered as active instances even though they were not serviceable instances. Now, in order for instances to be considered 'active' they must have the following attributes: not terminated, stranded, or shutting down, and have been booting for < 3 times the 'resize_calm_time' value. (The resize calm time is the amount of time the array waits to act after a triggered action.) For instance, if there is a problem with the booting process and an instance gets stuck in a booting state and doesn't become operational, the server array will no longer view that instance as an 'active' instance. Therefore, if a user's calm time is set to 5 minutes (default), and the instance has been booting for three times as long (3 x 5min = 15min), then another instance will be launched. Similarly, if the 'max_count' of the array is 4 and you have 4 instances booting, the array will not launch more instances. The logic for calculating the 'max_count' has not been changed. You can have only {max_count} active instances (terminated_at = null, shutdown_at = null). If the 'max_count' of an array is 4 and 4 instances are booting, no more instances will be launched. (gr-4221w)
You now have the ability to terminate all instances in an array. Previously, you had to manually select which instances you wanted to terminate. (gr-4222w)
Previously, we would load data for all deployments even if there were no active servers in either the deployment or its server array. To optimize the load times of the listed deployments (Dashboard -> Deployments tab) we only load data for the deployments that have active servers or server array instances. The data for collapsed deployments that don't contain any active servers will be loaded on-demand. (gr-4270w)
The following bugs have been resolved in this release.
A bug was briefly introduced whereby the account administrator could not revoke the admin role from account memberships that had the "admin" privilege. (Settings -> Account -> Permissions tab) When the Edit action button was selected, the admin role remained grayed out (unselectable). Note: If you revoke the admin role from an account, that account gets added to the total number accounts that are non-admin. There is a limit of non-admin role accounts. The limit varies depending on the type of account. (e.g. developer, premium, ...) (bl-4216w)
Some attempts to search RightScripts resulted in an Internal Error. Specifically, when searching for a text pattern in non-private RightScripts. (Design -> RightScripts -> Search action button with Private, Shared or RightScripts check boxes selected.) (bl-4129w)
The e-mails from the Alert subsystem (alerter@my.rightscale.com) had some helpful information omitted. Specifically, the Server and description of the alert condition were not included in the Subject line. For example, the following helpful informaiton is back in the subject line:
"cpu-0/cpu-idle.value is 82.17"
This type of subject line information along with additional details in the message body have been added back into the e-mail notificaiton. (bl-4138w)
Each RightScale account can have a maximum of 5 admin users. Previously, if an account had more than 5 users, but less than 5 admin users, you were unable to successfully send account invitations because the logic check was incorrectly calculating how many non-admin users exist. This problem was fixed. (4190w)
When attempting to bundle a Windows AWS EC2 image, the following error message would be displayed (partial audit entry excerpt):
...Bundling an image from i-3c888248 failed: Validation failed: Multi cloud identifier can't be blank
The multi cloud identifier was not set, hence inserting the record into the database failed and produced this error. This issue has been resolved. (or-3172w)
When showing any Deployment (Manage -> Deployments -> <DeploymentName>), upon selecting the Edit action button the following error would be displayed in the Dashboard:
Internal NoMethodError: a notification will be sent to the admin.
this prohibited the editing of Deployments and the resolution was promptly implemented and pushed live in production. (or-4186w)
When registering your own private Eucalyptus Cloud with RightScale, in some rare instances the following flash error message could have been displayed in the Dashboard:
error: undefined local variable or method 'callback_url for Biz:Cloud:LocalGatewayProxySurrogate:Class'
The error stemmed from an improper URL being constructed. Similarly, the mishandling of temporary session data could result in a generic "Internal error" message. These issues have been resolved, and you should be able to successfully register your Eucalyptus cloud. (or-4217w, or-4198w)
Previously, users who did not have support for alerts still saw the Alerts tab. The Alerts tab is now hidden from such users. (gr-4127w)
Previously, if you clicked the SSH button, closed the SSH window, and then switched the Dashboard layout from Classic to Beta, the SSH window would re-open. This issue has been resolved. (gr-4148w)
Previously, if you locked an instance in your server array and then clicked the Scripts tab, you would received an internal error message because the instance did not have the @component or @server variables. This issue has been resolved. (gr-4297w)
When configuring a server array, the 'Default min count' field had to be less than the 'Default max count' value. However, if you want to set up time-based scaling, you might want these values to be equal to prevent any undesired scaling. You can now use the same value for both the default min and max count values on server arrays. (gr-4140w)
In order to have the html evaluated, we wrapped the string in raw(), which allows the flash message to be evaluated as html. raw() creates a new instance of the new Unsafestr class. (gr-3331w)
Previously, you could still terminate an instance in an array even if it was locked. Locked array instances can no longer be terminated using the terminate button. (gr-4298w)
When adding an alert from an existing ServerTemplate using the 'Copy As' button under the Alerts tab, the second panel in the selection process doesn't show any alerts, even if there are some available. The Alert list is now populated correctly. (gr-4218w)
Under certain accounts, if you clicked the Deployments view (Dashboard -> Deployments tab), an 'Internal Error' message would appear. The message would also appear if you attempted to sort the State column. This issue has been resolved. (gr-4219w)
You should be able to delete a RightScript that's currently not being used by any ServerTemplates in your account. However, if the RightScript was referenced by a previously deleted ServerTemplate, you could not delete it. The cross-reference checks for deleting a RightScript have been modified so that you can now successfully delete any unused RightScripts. (gr-4233w)
When attempting a relaunch, a check was not performed to check the state of the server. This issue has been resolved. Before attempting a relaunch, a check will be made to make sure that the server is operational. If a server is not operational, you will receive an invalid action error message. (gr-4238w)
Performance improvements have been made to many of the Dashboard tabs, including deployments and alerts.
There are no known unresolved issues.
Please report issues to: support@rightscale.com
New and significant changes for this release with respect to ServerTemplates and RightScripts are summarized below. New and updated ServerTemplates and RightScripts are typically released 3-7 days after the new release of the RightScale Cloud Management Platform. Updated status messages with respect to actual release date/time of the ServerTemplates and RightScripts will be found here within this document.
ServerTemplates and RightScripts are typically released 3-7 days after the new release of the RightScale Cloud Management Platform. Thanks for your patience!
Warning! - RightScale ServerTemplates are published with frozen repositories and are associated with a particular RightImage. There is no guarantee that newer RightImages (RightImages CentOS v4.1.15 and 4.1.20 for both the US and EU regions and 32- and 64-bit versions) 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 will 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 will boot correctly.
MySQL EBS v2 (CentOS Alpha) and MySQL EBS v2 (Ubuntu Alpha) use EBS striping to increase disk performance. For additional information, please read the ServerTemplate and associated RightScript Descriptions in the Dashboard. To learn more about migrating from MySQL EBS to MySQL EBS with striping, please click here. They are premium ServerTemplates and require a paid RightScale account.
© 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.