Next-Generation Cloud Migration Considerations and Options
If you're moving your application from our First Generation Cloud platform to the Next Generation Cloud Servers platform, consider any pros and cons of the new platform before the cloud migration.
Our Next Generation Cloud platform offers several benefits over the original.
The OpenStack API used by our Next Generation cloud is responsive and flexible, with room to grow. New features include management of server metadata.
Next Generation Cloud Servers have assigned IPv6 addresses, though at this time we only support one assigned IPv6 address per server.
You can choose the region that will house a created cloud server in our Next Generation cloud environment.
Regional control helps you manage back-end availability between your servers and connectivity to services such as Cloud Databases and Cloud Load Balancers. You can also ensure that you have copies of your application in multiple regions to aid with disaster recovery.
Disk management is more flexible and with it you can repartition your Cloud Server's virtual disk and switch file systems if desired.
The Next Generation cloud's OpenStack underpinnings provide the potential for interoperability with OpenStack-based tools like python-novaclient, as well as compatibility with private and third-party clouds running OpenStack.
General Purpose and Optimized servers
Our Next Generation platform includes multipurpose General Purpose server flavors as well as server flavors optimized for computing power, memory, and network and disk throughput. These server flavors offer dramatic improvements over First Generation and Standard servers in disk and network speed. For more information, see our article, New features in General Purpose and optimized Cloud Servers.
No shared IP groups
Unlike First Generation Cloud Servers, our Next Generation environment does not offer the ability to create shared IP groups via the API.
No 256 MB instances
Instances with 256 MB of memory are not available for Next Generation Cloud Servers - server sizes start at 512 MB RAM.
IP address change
All migration options involve moving data to a new server, and the new server will have a different IP address from the original instance. After a migration you will likely need to make DNS changes and application configuration changes to account for the new IP address.
Virtual CPU allocation
Our First Generation servers are less strict about allocating CPU time on the host to instances than our Next Generation servers. If your application relies on frequent CPU bursts, you may see a reduction in performance on a Next Generation Cloud Server. Conversely, if you rely on consistent CPU power (without being affected by bursts from other instances on the host), Next Generation Cloud Servers are more reliable in that respect.
Note that in some cases our virtual cloud server packages can offer more virtual CPUs than our First Generation platform. Further, our Compute optimized Cloud Servers flavors offer the ability to emphasize CPU power in your server loadout. See the Cloud Servers pricing page for more information on virtual cloud server vCPU allocation.
We offer some articles describing how to manually migrate your data to a Next Generation server.
Remember to take the size of the original server into account, as well as other considerations like the region of connected Cloud Database instances, Cloud Load Balancers, and Cloud Block Storage volumes when creating a new server for a migration.
Our article series on migrating a Linux server provides instructions for migrating your data via rsync, either with a manual process or with the assistance of a python script.
For advice on taking the system disks and data disks on General Purpose and I/O optimized servers into account when migrating, see our article, Migrating to a General Purpose or I/O Server.
Web Farm Framework on Windows 2008
To migrate IIS and MSSQL data on Windows 2008, you can use Microsoft's Web Farm Framework per the instructions in this article.
Web Deploy on Windows 2012
To migrate IIS and MSSQL data on Windows 2012, you can use Microsoft's Web Deploy tool per the instructions in this Rackspace Community post.
After a migration
After migrating to a new Cloud Server remember to make any necessary changes to DNS information or load balancers for your application.
Also bear in mind that existing First Generation snapshots can't be used to create Next Generation servers. Don't forget to make back-up arrangements for the new server.
© 2014 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER