This article attempts to point out the process of migrating from the Rackspace legacy (First Generation) cloud to the Rackspace Open cloud, as well as any caveats or other things to watch out for when moving over. The Rackspace legacy cloud will be deprecated and will not have support from RightScale soon, so moving over it the best option at this point.
First, we'll need to add the Rackspace Open Cloud (Dallas, Chicago and/or UK) to your RightScale account.
To do this, follow the directions on this page to add one of the Dallas or Chicago clouds, or the UK cloud (if you are using a legacy Rackspace UK account and have Rackspace UK credentials).
Once completed, you are now setup and ready to go! You can now start adding and launching Rackspace Open Cloud servers from various ServerTemplates and images.
Caveats and Differences
The following are important differences between Rackspace legacy (first generation) and Rackspace Open Cloud -
1. The same cloud credentials are used in FirstGen as well as in Open Cloud.
As you may have noticed, Rackspace legacy credentials are going to be the same for the Rackspace Open Cloud. When registering the Rackspace Open Cloud, the only credentials you will need from the legacy cloud are your username and password to login to the Rackspace management console (in addition to your tenant ID, which isn't required by the legacy cloud).
2. The FirstGen 256 size instance type does not exist in Open Cloud.
If you have any servers or instances running on the '256' instance type in the Rackspace legacy cloud, then you will need to select a different instance type in the Open Cloud. The closest thing is the '512MB Standard Instance' type, doubling your RAM to 512MB.
3. Static IP's (IP Addresses that can be mapped to different servers dynamically) are not supported in Open Cloud at this time. They are not currently on the roadmap for future development.
This is self-explanatory, but there will be no public static IP support in the Open Cloud at this time. If this type of functionality is required for your application, there are other options, such as using Dynamic DNS registration scripts to register a DNS hostname to the public/private IP of the instance.
4. Older RightImages will not exist in Open Cloud. Customer ServerTemplates will need to upgraded to use the latest RightImages prior to these instances being migrated to OpenCloud.
This one is also fairly self-explanatory, but since we are deprecating support for the legacy cloud, it will not receive any ServerTemplate or image updates that the Open Clouds will receive. Thus, if you are using an older image that is available in the legacy cloud, but is not available in the open cloud, you will want to update your ServerTemplate and/or images to use a newer revision of the ServerTemplate or image that is compatible with the open cloud.
In general, there should be good parity between the legacy and open clouds for image and template availability, but as time goes on only certain images and templates will be available in the open cloud only, so updating your templates to the latest revisions is highly recommended.
If you have any specific questions about image or template availability, you are welcome to contact our support team by opening a request in the dashboard and we will be happy to assist.
5. That's it! There are no other preventative or disabling changes between the two clouds. The Rackspace Open Cloud does add many more features that the legacy cloud doesn't offer, so it is highly recommended that you update as soon as you can.