Release Date: May 19, 2010
Reminder: ServerTemplates and RightScripts are typically released 3-7 days after the new release of the RightScale Cloud Management Platform.
Release Date: May 19, 2010
Release Time: 9:00pm Pacific
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.
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.
Support has been added to the Dashboard for creating streaming CloudFront distributions. Previously, you could only create basic distributions. You can also use distributions to serve "private" content. See CloudFront for more information. (blgr-10271)
You now have the ability to change the current bid price on a spot instance type Server. If you launch a Server that's a spot instance type and it is currently in the 'bidding' state (i.e. no instance has been provisioned), you can update your spot instance price by clicking the Rebid action button. The modified spot instance price only applies to the currently launched Server and is not propagated to the next Server launch.
Please see Server States (blgr-9815)
The create and update Server requests of the ApiComponentsController now supports Spot Instances as well. (Note: Additional documentation to follow on both rdoc and the API Guide in the Support Portal.)
RightScale now supports a new machine tag "rs_launch:type=auto" that can be used to automatically terminate auto-launched instances if they are not operational after 45 minutes. The use of this tag is designed to terminate instances that get stuck in booting and never become operational. By default, all newly created server arrays will have this tag. Therefore, any new instances that are launched into such an array will inherit the tag. You can also add the tag to existing Servers or Server Arrays.See Machine Tags: Servers. (az-10049, az-100676)
NOTE: This will not apply to instances that are already in stranded state.
Changes to the software are listed here. Changes usually refer to enhancements to existing features, minor UI changes, additional logging or messaging, etc.
Improvements have been made so that listing local RightScripts (Design -> RightScripts -> View Local) is more efficient. (blgr-6543w)
There is a new RightScript selector in the UI. It is similar in look and feel to other selector windows. For example, when running "Any Script" on an Instance, you will first select a Publisher (left pane of the window), then the RightScript name (middle pane), the Details (right pane) includes the RightScript Description and last commit message. As with other selector windows, you can apply a Filter to also assist in locating the correct component. The new selector is used elsewhere in the Dashboard as well, such as when adding a RightScript to a ServerTemplate.
The default user roles when sending out invitations (Settings -> Account -> Invitations tab -> send invitations action button) have been changed to be more sensible. The prior user roles were thought to be too powerful for default values. The defaults are now: server, actor and server_login. (The defaults use to include the following extensive privlieges as well: designer, library and admin.) See User Role Privileges for more information on roles.
Previously, you could only manually view ServerTemplate Usage Reports (Report -> ServerTemplate Usage) inside the Dashboard and/or download the report as a .csv file. In addition to the manual report, you can now set up periodic reports that are automatically generated on a daily/monthly basis. You can also set up optional email notifications when the reports become available. Note: The periodic report is the exact same data that is downloaded to a .csv file, but it is run periodically and uploaded to a S3 bucket you specify. See the ServerTemplates Usage Report to learn more. (blgr-10294)
The Customer Usage Report (Report -> Customer Usage) now allows you to specify either daily or monthly. Previously, the report timeframe was by month only. If you run the report by day, a convenient monthly display assists in picking the correct day. See the ISV Customer Usage Report to learn more.
Previously, you managed your Account Groups under Settings -> Sharing. The options under the Sharing submenu can now be found under Design -> Account Library -> Your Account Groups.
RightLink now uses Chef 0.8.16 and Ohai 0.5.4. For more information on these releases, please view the OpsCode blog.
Previously, you could launch a Server from a ServerTemplate's show page. Since Servers cannot exist outside of the context of a Deployment, Servers that were launched in this fashion were added to the "Default" Deployment. In order to promote best practices, you are now required to add a Server to a specific Deployment before the Server can be launched.
The following bugs have been resolved in this release.
Previously, users with 'designer' role privileges were not able to "Detect Changes with HEAD" or "Update to HEAD RightScripts" on a ServerTemplate's Scripts tab. Privileges have been changed such that users with 'designer' role privileges can perform such actions. (gr-6594w)
Modifications have been so that you can now delete a MultiCloud Image even if it's referenced by a deleted ServerTemplate. (gr-6622w)
Previously, the Usage Estimate Report (Report -> Usage Estimate) was not calculating correct estimations for spot instance types. The Usage Estimates will now properly take into account price fluctuations for spot instances over the full time period that it remains operational. The report will display each spot instance rate in a different row. (gr-6588w)
Recent modifications to support the new MultiCloud Marketplace resulted in long loading times for displaying all data under the Server's or ServerTemplate's Scripts tab. Changes were made to optimize the loading of the Scripts tab. (gr-6282w)
The Cloud display name is now editable for the Cloud owner. You must also possess 'admin' user role privileges. To edit, navigate to Settings -> Account -> Clouds tab. Select the appropriate CloudName (e.g. MyRackSpace, EucalypusTest, etc.). Use the Edit action button on the Info tab to make a change to your Cloud display name. (or-6729w)
Previously, you couldn't manually force instances to terminate that were stuck in either the 'shutting-down' or 'terminating' states inside the Dashboard (under the server Srray's Instances tab). You would receive the following error message: "There are no active unlocked instances to terminate." This problem was fixed. See the Server States diagram for more information. (or-6699w, or-6696w)
In rare instances, a race condition could occur causing a Spot Instance to fail while booting, getting stuck in the "booting" state. This was accompanied by a "no valid instance" error message. The race condition has been corrected. (blgr-6720w)
RightGrid allows you to scale based on the SQS queue size or the age of the item in the SQS queue. The documentation for the item age contained an error when it comes to specifying the "created_at" timestamp. The documentation has been corrected in the Dashboard Help Text, and the RightGrid Technical User Guide. (Note: Help Text changes are posted a few days after the software is released.) (blgr-6694w)
When using the RightScale API to set a tag for a Server, the tag was set correctly, however an incorrect response was returned. The proper successful response is a HTTP 204, the API was returning a "422 Unprocessable Entity" (even though the tag was getting set). (blgr-6681w)
A race condition resulted in decommission scripts not running for a Server that was relaunched. If the next Server was already launched when the previous Server attempted to look up how to decommission itself, the lookup would fail and it would not execute the decommission scripts. This race condition has resolved. (blgr-6680w)
When launching a new RDS instance you may specify an optional RDS Parameter Group. Parameter groups specify configuration settings pertaining to the MySQL Engine options. No matter what RDS Parameter Group you specified, the default MySQL 5.1 group settings were used. This has been resolved, so the settings from whatever parameter group you specify in the drop-down menu are used when launching an RDS instance. (blgr-6721w)
Previously, if you imported a public ServerTemplate from the MultiCloud Marketplace that contained a premium RightScript it appeared to be a no-operation. That is, the ServerTemplate was not imported, and you were left exactly where you were in the Dashboard when you issued the "import" request. Now, you will be presented with an informative message with any pertinent contact information. (blgr-6542w)
Previously, if the lineage of a MultiCloud Image (MCI) only involved deleted ServerTemplates, you were still not able to delete the MCI. This brought about some confusion if you viewed the cross reference (Xref) tab for the MCI, because it would report no ServerTemplates in the lineage. Now we only look at current (undeleted) ServerTemplates to build out the lineage. (blgr-6622w)
When filtering ServerTemplates or MCIs in the MultiCloud Marketplace by "Paid", some items in the result set are actually "Free". For example, if looking at MultiCloud Marketplace -> ServerTemplates -> All action link, filter by "Paid", the "RightScale LAMP v4 Trial" ServerTemplate was included in the display and should not have been. The filter has been fixed and only Paid items displayed in the result set. (blgr-6553w)
When viewing the local ServerTemplate show page (Design -> ServerTemplates -> View local -> ServerTemplateName) RightScripts tab, clicking the Detect Changes in Head action button would produce the following message:
You do not have permission to perform this action on this account.
Please confirm you are operating in the expected account.
Unless you had 'admin' privileges, in which case the operation was permitted. This action should be allowable to any user that has 'designer' privileges. The incorrect restriction based on 'admin' user role privileges has been resolved. (blgr-6594w)
The Usage Report (Report -> Usage Estimate, see Service column = "Spot Instance") use to only display a single price and calculate the total based on the single price. However, with Spot Instances, the rate could oscillate over time. This has been taken into account and a more accurate total for the Usage Report is calculated. (blgr-6588w)
Servers that were launched using an EBS based image and then stopped still showed as "operational" (e.g. green sphere) in two locations within the Dashboard: Dashboard Overview and Dashboard Deployments. This was a display bug only (usage estimates were not impacted ) and the issue has been resolved. (blgr-6605w)
The following scenario use to fail but has been resolved with this release: Importing a ServerTemplate that includes a RightScript with a "local" HEAD revision, and the version being imported is revision 1. An error would occur during the validation process and while trying to save the RightScript. (blgr-6526w)
An Internal Error would result when viewing the Info tab of a Server when the default MCI had no image for that Server's region. The following simple example illustrates when this internal error could occur:
This issue has been resolved. Now the following message is printed (in red) in the Info tab of the Server's "Image" field:
no matching image is available
v5 Spot Instance Servers that were previously rebooted could not be terminated. A termination request was posted and added to the Audit Entries, but not successfully executed. This issue has been resolved and they terminate properly now. (az-6792w)
This is actually more of a "known issue" than a "unresolved issue". If a user goes into a running Windows or Linux Server and changes the password or trusted key, the Dashboard has no way of knowing about it. See FAQ 159 for more information.
Please report issues to: firstname.lastname@example.org
© 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.