Filed in Cloud Industry Insights by The Rackspace Cloud Solutions Engineering Team | June 6, 2013 3:00 pm
There are many solutions to consider as you migrate to the cloud. Here are a few key points that are invaluable when integrating Rackspace services into your application. Our goal is to ensure your move to the Rackspace Cloud is a smooth and successful transition.
The relationship between customers and Rackers is at the very core of the Fanatical Support experience. By working together to build a resilient and scalable Open Cloud architecture from the beginning, we’re actively redefining how to best leverage cloud. Let’s collaborate from day one on a solution that makes the most sense for your applications instead of relying on last-minute heroics when your business can least afford it.
This guide will familiarize you with everything you need to know as you start to use The Rackspace Open Cloud. The entry point is our Control Panel; please feel free to check out the Control Panel documentation or watch the demo video. If you prefer to use the RESTful API or language-specific SDKs to interface with the cloud directly, you can find more information at the developer portal.
If you are hungry for more please feel free to explore the guides for:
Since Rackspace guaranties that our data center network will be available 100% of the time in any given monthly billing period, excluding scheduled maintenance, you don’t need to use Availability Zones to maintain a high uptime. We do, however, split our host servers into groups called cells. Each cell is on its own L2 network for both the public and ServiceNet networks. This separation helps prevent certain types of network interruptions from affecting all servers in a given data center.
We have multiple geographically separated regions in which you can build Cloud Servers. These include Dallas, Chicago, London, and soon Sydney. By mirroring your infrastructure between datacenters, you can achieve higher availability of your application. You can also store backups of your data to Cloud Files in a remote region to enable availability of your data as part of your disaster recovery plan.
Our Cloud Server instances, provisioned on RAID10-backed hosts, have persistent storage which only goes away if the instance is deleted. Additionally we offer persistent Cloud Block Storage which is independent of the server instances and can be detached and reattached to a different server instance if needed. Public and ServiceNet IP addresses are yours for the life of the instance, however if you delete the instance an IP is assigned to, that IP is returned to the pool for other customers to use. Regardless of what storage methods you’re using, we recommend setting up backups and clustering your instances for greater redundancy and uptime.
SSH key pairs are not used by default, however you can inject files into your Cloud Server instance during the build process to distribute your keys, configuration files, or make any other small deviations from the image. This is useful if you’re spinning up servers programmatically and need to pass unique configuration parameters to each of them at build time. You can also simply add your key pair to a server and take an image of the server, then every new server built from that image will be easily accessible using your SSH key.
Firewalling is done at the Cloud Server instance level by utilizing a software firewall such as iptables or Windows Firewall. We also offer hardware firewall options via our RackConnect® solution as well as third party security vendors like CloudPassage, Dome9, CloudSMS, and CloudFlare. As an additional layer of security, isolated networks can be created to allow for secure network communication among Rackspace Cloud instances.
Rackspace has a much simpler billing structure for our services. We do not bill you based on the number of IO operations you make or the number of API calls made. Cloud Files, for example, is simply billed based on your monthly storage usage and outbound bandwidth and has the unique benefit of tiered pricing. Cloud Load Balancers are billed based on the average number of concurrent users throughout the month. You’ll also want to be aware that our RedHat Linux distributions have an additional monthly fee for the licensing. We also sell additional IPv4 addresses for SSL usage.
We have simple flavors that scale disk, memory, CPU, and network throughput together as the flavor size increases. Should you want to increase your disk size without increasing other resources, we would recommend attaching a Cloud Block Storage volume (either SATA or SSD) to your instance. Additionally, if your application has specific performance or security requirements that demand dedicated gear, we would suggest leveraging RackConnect. As a powerful hybrid solution, RackConnect allows you to blend your highly customizable bare metal configuration with Rackspace’s elastic cloud infrastructure.
Message queuing services are available from Rackspace solution partners, such as Iron.io and their IronMQ product. Porting is generally straightforward, and IronMQ offers performance and consistency at least equivalent to SQS. Iron.io offers SDKs for major languages, such as Ruby, Python, PHP, Java, Clojure, and Go. You may also opt to use your own message broker, such as RabbitMQ, which can run on your own Cloud Servers.
Autoscaling, like disaster recovery, is not currently innate to the Cloud Servers product. To build an environment that scales resources up and down based on load, we recommend using a third party solution such as RightScale, Scalr, or ScaleXtreme available through our Rackspace Cloud Tools Marketplace. Alternatively, you can work with Cloud Monitoring, Service Registry, and Chef or Puppet to configure a similar self-aware environment that reacts to the demands of your application. Regardless of your scaling solution, it will be imperative that you’re architecting for horizontal growth.
It is very important to test all configurations before using them as a production environment. If you have a preferred method for testing, please use what you are comfortable with. If not, there are a number of great third-party tools available for you to use such as Blitz IO, LoadStorm, and Soasta.
Now you’re ready to get going on the Rackspace Open Cloud. As always, we’re here to help you if you need it. Happy migrating!
ANY USE OR CHANGES TO THIRD PARTY PRODUCTS AND/OR CONFIGURATIONS SHOULD BE MADE AT THE DISCRETION OF YOUR ADMINISTRATORS AND SUBJECT TO THE APPLICABLE TERMS AND CONDITIONS OF SUCH THIRD PARTY. EVEN THOUGH RACKSPACE PROVIDES THIS INFORMATION FOR HOW YOU MAY DEPLOY THIRD PARTY PRODUCTS OR SERVICES ON THE RACKSPACE CLOUD, RACKSPACE DOES NOT PROVIDE TECHNICAL SUPPORT FOR THIRD PARTY PRODUCTS, OTHER THAN SPECIFIED IN YOUR HOSTING SERVICES AGREEMENT YOU HAVE SIGNED WITH RACKSPACE AND RACKSPACE ACCEPTS NO RESPONSIBILITY FOR THIRD-PARTY PRODUCTS.
Third-party trademarks and trade names appearing on this page are the property of their respective owners. Such third-party trademarks have been printed in caps or initial caps and are used for referential purposes only. We do not intend our use or display of other companies’ tradenames, trademarks, or service marks to imply a relationship with, or endorsement or sponsorship of us by, these other companies.
Source URL: https://blog.rackspace.com/migrating-to-the-rackspace-open-cloud/
Copyright ©2016 The Official Rackspace Blog unless otherwise noted.