Resizing a Rackspace Cloud Server Down to 256MB

by Mike Levin SEO & Datamaster, 03/07/2012

[caption id=”” align=”alignright” width=”177” caption=”The Rackspace Cloud (Photo credit: Laughing Squid)”]The Rackspace Cloud[/caption]

Well, yesterday was the sort of day I hope for. I now have a 3-server network in the Rackspace cloud: 2 Ubuntu servers and one loadbalancer. I have been putting this step off forever—a critical step—perhaps THE most critical in getting my work ready for the public. There was a piece of unsettled work yesterday because the internal network DNS at the office took forever to update. It’s updated now, and an nslookup against my app’s domain name returns the load-balancer’s IP. That means I can safely turn off the main server and resize it down to Rackspace’s $10/mo first tier, and not interrupt any one’s work…

Confirm that that’s true… Yep, only “bar” is appearing on my foo/bar test, ensuring that everyone is now working of the new (and smaller) instance of the server. It’s now safe to go into the Rackspace web control panel…

Hosting / Cloud Servers / server name / Resize / 256 / continue…

Queued for Resize Preparing for Resize

…performing a site crawl while this is going on to ensure server #2 is doing it’s thing… Done!

Server Resize Complete

It only took about 2 minutes to go down from 512MB to 256MB.

Confirm Resize.

Well, I’ve got both servers up and running at the el-cheap-o… or shall we say, loyalty… tier. You hear that, Amazon? I saw your new prices, and I’m not impressed. Anyway, it’s time to re-activate that node on the loadbalancer…

Hosting / Load Balancer / balancer name / Nodes / node name / Enabled / Save changes

…and now, confirm the alternation on my foo/bar test by visiting text.txt and refresh… Done! Two servers are live and being round-robin alternated. But round robin was only for testing. For actual use, I want Least Connections. I am passing on Weighted Least Connections, because my quick research indicates the weights are arbitrarily assigned by the administrator, and is not a reflection of the machine’s load or anything like that. And since both VMs are identical, whichever one has the least connections is in all likelihood the more available one.

Done, done and done. The best part of a project like this is that I get to say, yeah… on my cloud network… on my load balancer… blah, blah, blah. It’s a position of great strength.

Enhanced by Zemanta