Table of Contents
RightScale's new version of the Dashboard and API is known as "Unified Cloud Platform" (or simply UCP) while the old platform is known as "Legacy Cloud Platform." You can see if your account is a UCP account by logging into my.rightscale.com and if you are redirected to us-3.rightscale.com or us-4.rightscale.com, your account is a UCP account. If your account is not redirected and you remain on my.rightscale.com, you are on a LCP account. All LCP accounts will be migrated over to UCP accounts in the future.
The primary difference between platforms is the unification of the API into API 1.5. On the Legacy Cloud Platform, RightScale API 1.0 supports AWS, whereas API 1.5 supports all other clouds. Additionally, all RightScale functionality is now developed for Unified Cloud Platforms exclusively. A UCP account provides a faster, more powerful Dashboard with new UIs, new integrated cloud services, more API calls, new multi-cloud tools, and performance boosts.
A UCP account on the RightScale platform allows you to utilize the API and Dashboard as a true single pane of glass to manage all your cloud resources. There are also many new features in the pipeline that will only be available in the new Unified Cloud Platform environment. As we see more sophisticated architectures and environments in cloud development, we are building a platform to allow for this growth and the many iterations we will see in the future. In a Unified Cloud Platform account, you will see features such as Cloud Workflow, our orchestration language equipped with its own UI, currently in private beta. And your favorite cloud services such as ELB will be integrated with the Dashboard. The purpose of this new direction is to allow for a unison of API, Dashboard, public clouds, and private clouds.
We are continuing development for these features exclusively in the Unified Cloud Platform:
To determine if your account is currently in a UCP environment, simply login to the Rightscale dashboard and view or switch to that account. The address bar of your browser will display a RightScale sub-domain, which can be mapped to either the Legacy Cloud Platform or the Unified Cloud Platform:
|Legacy Cloud Platform (LCP)|
|Unified Cloud Platform (UCP)||https://us-3.rightscale.com |
If your account is a Legacy account and you wish to migrate to the Unified Cloud Platform, please see the Migration section below for details on migrating your account. Once migrated, the URL in your browser will be changed accordingly when viewing your Rightscale account in the Dashboard.
The Legacy Cloud Platform is built on both API 1.0 and API 1.5, with API 1.0 supporting only AWS while API 1.5 supports all other clouds. With the Unified Cloud Platform, the majority of API 1.0 (AWS) functionality was carried over to API 1.5.
Also, see recent release notes to avoid post-migration backup issues.
The Unified Cloud Platform has some substantial navigational differences from the Legacy Cloud Platform. These changes apply for AWS only and are described in detail below.
AWS Cloud selected in the Clouds Menu in Legacy Cloud Platform
AWS Cloud selected in the Clouds Menu in Unified Cloud Platform
Notice a few differences.
Network functionality (for both Security Groups and VPC functionality) can be found in the Manage menu under the link 'Networks'
AWS VPC is supported in UCP within Network Manager. As we built up Network Manager, we created some differences with AWS VPC when comparing LCP and UCP. This is temporary. We will reach parity between UCP and LCP as it pertains to VPC. Below is a table that lists the actions that can be performed through the both the Dashboard or API depending on the platform at this time.
Note: that these differences in the table below only apply to AWS.
X - Supported feature
Ø - Not supported
|VPC Feature||Legacy Cloud Platform||Unified Cloud Platform|
|Security Group|| |
|IP Addresses (Public or EIP)|| |
|Network Interfaces (ENI)||Ø||Ø||Ø||Ø||Ø||Ø||Ø||Ø|
|Route Table|| |
|Internet Gateway|| |
|Customer Gateways|| |
|VPN Gateways|| |
|VPN Connections|| |
|NAT Instances|| |
|DHCP Options Sets|| |
|Network ACLs|| |
|Support for provisioning EC2 in VPC (In general)|| |
|Support for provisioning EC2 in VPC with non-elastic public IP|| |
|Support for provisioning EC2 in VPC with static private IP|| |
|Support for provisioning in ELB in VPC|| |
|Support for provisioning RDS in VPC|| |
With a UCP account, RightScale ServerArrays support scaling across multiple subnets which may span one or more Availability Zones in a given VPC.
The most substantial change for Rightscale API users who are using a UCP account will be the change of the API endpoint to match the Rightscale UCP environment that your account is hosted in.
For example, you may have used an API endpoint to login to Rightscale and set a cookie with your legacy Rightscale account:
When your account is hosted in or migrated to a UCP environment, the endpoint URL will need changing for the same login call. As an example, 'us-3' is a Rightscale UCP environment, so the updated endpoint would be as follows:
You can determine the endpoint that you are supposed to use by simply logging into the Rightscale dashboard, viewing or switching to your UCP account and observing the address bar for your browser. It should reflect a URL with the appropriate sub-domain, which in turn will be the endpoint you are supposed to use for that particular account.
It's important to note that if you do forget to change your endpoint, and are still using the legacy 'my.rightscale.com' API endpoint with a UCP account, then the API will return an HTTP 302 redirect. Along with this redirect, we also return a <Location> header that points you to the appropriate endpoint, however we DO NOT make the updated call to the new endpoint for you.
For example, if I were to issue the following Curl command (which uses my.rightscale.com) to establish an API 1.5 login/session for a UCP account, it will return an HTTP 302 and a <Location> header with the updated API endpoint/URL, like so:
curl -v -H 'X-API-VERSION:1.5' -c myCookie -d "email@example.com&password=<user password>&account_href=/api/accounts/<UCP account ID>" https://my.rightscale.com/api/session
And the subsequent output (shortened for brevity):
< Status: 302 Found < X-Runtime: 21 < Location: https://us-3.rightscale.com/api/session
So, in this case, the API endpoint should be updated to us-3.rightscale.com instead of my.rightscale.com for this particular account.
We HIGHLY recommend updating your scripts, code or libraries to the newer UCP compatible API endpoint as soon as possible. If you wish to continue using the my.rightscale.com endpoint, then it is your responsibility to ensure that your scripts, code or libraries that are using our API can take advantage of this <Location> header as needed.
It is also important to understand that you can continue to perform an API 1.0 call against an account in a UCP environment. The only requirement is that the endpoint must be changed to match the account environment (as mentioned previously). The API 1.0 call will be translated to its API 1.5 counterpart and will be automatically ran.
For example, the following Curl command uses API 1.0 and will login, create an API session and set a login cookie. Notice the X-API-VERSION header is set to 1.0 still, and the endpoint is set to us-3 for a UCP account. This call will be translated to it's corresponding 1.5 call and will be successfully executed:
curl -v -H 'X-API-VERSION:1.0' -c myCookie -u firstname.lastname@example.org:<user password> https://us-3.rightscale.com/api/acct/<UCP account ID>/login
Here is the Curl output showing the HTTP 204 response code, which is a success for this call:
< HTTP/1.1 204 No Content * Server nginx/1.0.14 is not blacklisted < Server: nginx/1.0.14 < Date: Thu, 31 Oct 2013 19:18:28 GMT < Connection: keep-alive < Status: 204 No Content
Important! Most API 1.0 calls can be translated to API 1.5 calls, however there may be certain calls that fail or are not supported. For this reason, we recommend updating any scripts, code or libraries that utilize API 1.0 to utilize API 1.5 instead.
The Unified Cloud Platform does not support the following capabilities on AWS today, however, many will be supported (as indicated) soon:
Customers can sign up to migrate their existing account(s) to a UCP. Contact your account manager to get started. Moving from an existing Legacy account to a desired cluster involves a minimal migration process. During the migration from Legacy to Unified, your RightScale account will be unavailable for about two hours. Similar to our release maintenance windows, all cloud resources in the RightScale account will continue to function normally, except you will not be able to manage them from the RightScale Dashboard.
Once the account is migrated, you will automatically redirect to the correct Unified Cloud URLs when accessing RightScale. For disaster recovery, RightScale will provide you with specific URLs to the new Unified Cloud so if the Dashboard goes down, you will still have access to your account by going to the specific Unified Cloud Platform URL.
Note: There is no graceful migration back to Legacy Cloud Platform once your account is migrated to Unified Cloud Platform.
Your questions, concerns and feedback are welcome. Please contact email@example.com for assistance.
|Glossary | 用語 | 용어||Site Map | Site Help||Community||Corporate Site||Get Support||Dashboard Login|
|Doc Feedback||Product Feedback||Resources||MultiCloud Marketplace||Forums|
© 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.