Table of Contents
Release Date: December 18, 2014
Note: Archived release notes available here.
Support for multiple subnets - Allows user to launch instances and servers in any subnets defined in the account. This removes the previous limitation that required user to provide a single subnet at the time of cloud registration.
Support for multiple storage accounts - Allows user to distribute storage workload across multiple storage accounts for application that require high IOPS.. Due to Azure limitations, a single storage account can only support 2000 IOPS. For I/O performance sensitive applications, this feature will enable customers to spread the storage load across multiple storage accounts, thereby increasing the IOPS capacity available to the application.
Configurable port-forwarding rules and endpoints - Prior to this release, port forwarding rules were auto-configured, making it difficult to control the port numbers that were assigned in the port-forwarding rules. This features makes it easier to configure these rules as well as Azure endpoints for cloud services.
Volume Snapshot Support - This release introduces the ability to snapshot volumes in a vSphere environment (enabled via RCA-V). This also enables use of the Storage Toolbox template on vSphere.
For example, RackConnected network in Rackspace with a UUID of 56f30c3a-e12c-46e7-af59-f412cab61f85 can be used for server launches by passing the following info in the user-data field, at the time of server or instance launch.
You can launch the server or instance in multiple cloud networks by specifying UUIDs in a comma separated list in the following format.
The example below shows a RackConnected cloud network and Rackspace ServiceNet as the cloud networks:
Added capability to update existing users' SSO settings even when they aren't linked to your SAML provider, provided their email domain matches your company's. RightScale must link your account to an email domain before you can make use of this feature; talk to your account manager or our support team for details.
Support for Multiple Subnets - This removes the previous limitation that required a user to provide a single subnet at the time of cloud registration. Beginning with this release, a user can have as many subnets as they need for their cloud account per region. These subnets will be detected by RightScale, allowing instances and servers to be launched in these subnets.
Support for Multiple Storage Accounts - Removes the limitation where a single storage account had to be used for all storage needs. Due to Azure limitations, a single storage account can only support 2000 IOPS. For I/O performance sensitive applications, this feature will enable customers to spread the storage load across multiple storage accounts, thereby increasing the IOPS capacity available to the application.
Configurable Port-Forwarding Rules and Endpoints - Prior to this release, port forwarding rules were auto-configured, making it difficult to control the port numbers that were assigned in the port-forwarding rules. This features makes it easier to configure these rules as well as Azure endpoints for cloud services.
Fix to Allow Private-Only Networking Choice - This is achieved by supplying only the private network. There is no explicit flag to specify "private-only" selection. Essentially, you can provide public + private, only private, or cloud default (which will pick a public + private of cloud's choosing).
User-Supplied Hostnames Instead of Randomly Generated Hostnames Upon Server/Instance Creation - The previous implementation had a randomly-generated hostname instead of a user-supplied name. This made it difficult to co-relate servers in the RightScale dashboard with the ones listed on the SoftLayer dashboard. This fix will aid in keeping the hostnames the same on both the RightScale and SoftLayer dashboards. Note that the fix only helps newly-launched servers/instances starting with this release. Anything launched prior to this release will remain as is.
Timeout Value Changed to 1200 Seconds - On occasion, the SoftLayer API takes longer to respond to requests than the default timeout originally implemented (30 seconds). This value has been increased to 1200 seconds to avoid spurious errors that occur due to response time inconsistency on SoftLayer.
firstname.lastname@example.org - For questions about this release.
email@example.com - Report any perceived errors, omissions or suggestions to improve this document.
© 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.