Rackspace Raising Prices 100% - WTF? Cloud File Migration to Linode

Summary

This video chronicles the real-world experience of migrating critical cloud file infrastructure from Rackspace to Linode due to an unexpected 100% price hike. The video highlights the challenges of unclear communication from Rackspace, the steps involved in a seamless migration process, and the technical adjustments required for system stability. The speaker emphasizes the importance of planning ahead, manual configuration, and testing for a successful migration without downtime or revenue loss. It’s a must-watch for businesses facing similar challenges in cloud infrastructure management.

Takeaways

• 😀 Rackspace unexpectedly raised its pricing by 100%, forcing the business to consider alternative cloud storage solutions.
• 💾 Migrating critical cloud file infrastructure requires careful planning to ensure zero downtime for production systems.
• 🔄 A custom script was used to migrate over 1TB of data, ensuring the process was smooth and automated.
• ⚙️ Metadata such as headers, caching behavior, and access rules must be properly handled during a cloud file migration to avoid breaking the system.
• 🔍 Hard-coded URLs in code, databases, emails, or media can break the system if not properly audited before migration.
• 💰 The business was able to reduce the Rackspace bill to $250/month, but the price hike made continuing with them financially unfeasible.
• 🌐 Linode Object Storage was chosen as the new platform, with careful consideration of storage regions to minimize transfer times and latency.
• 🛠️ Manual configuration of granular settings is needed when moving to Linode, unlike the more automated options offered by Rackspace.
• 📡 Integration with a CDN (e.g., Cloudflare) was implemented to optimize file delivery and ensure smooth user experience post-migration.
• 🔒 After migration, the system was thoroughly tested for integrity, with zero differences found between the transferred files and the originals.

Q & A

Why did the business decide to migrate from Rackspace to Linode?

The business migrated from Rackspace to Linode after Rackspace unexpectedly doubled their pricing with less than 30 days' notice. The pricing change was a significant increase that would impact the business's operating margins, prompting the decision to find a more cost-effective solution.

How much data was involved in the migration?

The migration involved approximately 1 terabyte of data, consisting of over 36,000 files.

What was the main challenge faced during the migration process?

The main challenge was ensuring the migration was done seamlessly without downtime, while also managing complex details such as metadata (headers, caching behavior, access rules) and ensuring all hard-coded URLs were correctly updated to avoid broken assets.

What role did metadata play in the migration?

Metadata, including headers, caching behavior, and access rules, played a crucial role in ensuring that the migrated data worked just as it did on the original Rackspace setup. Any mistakes with metadata could lead to performance issues or broken assets.

Why was it important to check for hard-coded URLs during the migration?

Hard-coded URLs could exist in code, databases, emails, or media. If these URLs weren’t updated to reflect the new storage location on Linode, it would result in broken assets, disrupting the functionality of the business's production environment.

What was the cost impact of Rackspace’s price increase?

The price increase from Rackspace would effectively double the business's storage and bandwidth costs. This was not just a storage problem but also impacted the performance and operating margins, making it a critical factor in the decision to migrate.

How did Linode’s pricing and features compare to Rackspace?

Linode's pricing was more affordable and offered S3-compatible object storage, making it a viable alternative to Rackspace. However, Linode required more manual configuration, including granular control over file headers and caching settings, which was a key difference compared to Rackspace's more automated setup.

What was the significance of using the 'RC clone' command in the migration?

The 'RC clone' command was used to copy files from Rackspace to Linode. It allowed for efficient transfer of data, moving over 36,000 files in just 11 minutes. The command also helped with ensuring the integrity of the transfer by providing data about the transfer status.

How did the business ensure no downtime during the migration?

The business implemented a fallback system where the code would first look for files on Linode. If a file was not found, it would fall back to Rackspace to fetch the file. This allowed the site to continue functioning normally while the migration was in progress.

What were the final results of the migration?

The migration was successful with no downtime. The business fully switched to Linode, and all files were being served through Linode’s object storage and Cloudflare CDN. The migration process involved some manual adjustments but ultimately improved the infrastructure's stability and cost-effectiveness.