Colin Smith takes you step-by-step through building a Windows Server in the Rackspace Cloud. Here are some of the problems he ran into and his overall rating of the service.
I am scheduled to do a presentation on Virtualization and Cloud Computing later this month at Microsoft Canada TechDays. As part of my presentation I will be demonstrating some cloud services. My plan is to demonstrate both a SaaS (software as a service) offering and an IaaS (infrastructure as a service) offering. I chose to use Microsoft Business Productivity Online (BPOS) and a Rackspacecloud.com Windows 2008 R2 Server.
In this post, I will take you through the steps to create a server in the Rackspace Cloud and give you my impressions of their offering.
The Rackspace Cloud is an IaaS cloud service that offers cloud hosted servers. I chose them over EC2 because they offer a Windows Server R2 x64 instance. EC2 does not have an AMI for Windows Server 2008 R2 yet (go figure?) and the on demand instances are less expensive by about $0.04 / hour. The sign-up was pretty straight forward and creating a cloud server was quite easy. Again my screen resolution made things a little awkward but it was definitely usable. The control panel where instances are created is much more intuitive than EC2 and much less cluttered. Creating a server was fairly easy. Overall, it took about 15 minutes. I have created three servers in the last few days and every time I encountered the same glitch. The control panel gave me a message that indicated that it couldn't update the status of my server. Both times when I renavigated to the control panel, my server was built and active.
Here are the steps that I followed to build my server:
1. Create an account at rackspacecloud.com and login to it.
2. Select Hosting.
3. Select Cloud Servers.
4. Click Add Server.
5. Select Windows.
6. Select the image that you want your server based on.
7. Give your server a name and select the server size then press Create Server.
8. The server will now be built. You will see a rotating progress icon as in Figure E.
Note: Every time I built a server I received the error pictured in Figure F.
If you refresh the page the error should disappear, as in Figure H.
9. Once your server is active (Figure I) you should receive an email from Rackspace giving you your server's IP address and the Administrator password. TIP: Since newer versions of the Microsoft Terminal Services Client do not permit pasting into the password field, you may prefer to give your server a short name as the auto-generated password will be your server name followed by a series of random characters. You can, always rename your server once you reset the password.
10. Connect to your new server using the Rackspace VNC client or an RDP client (Remote Administration is turned on by default).
11. Check for patches and harden your server as appropriate.
Although it was easy enough to create a server, I found the service is still a little rough around the edges. Some of my complaints are:
- The website was a little slow.
- The server status glitch I mentioned previously.
- Waiting for the password to arrive can be a pain. The first time I used it (a Sunday evening) it took about 30 minutes to arrive --TWICE as long as creating the server! This was not an issue for subsequent servers that I created.
- There isn't much documentation available compared to EC2 or MS BPOS.
- There is virtually no security on these servers. EC2 has an x.509 PKI infrastructure in place to help safeguard the admin console and security groups for firewalling and isolating servers while Rackspace has a single factor logon to get to the control panel. They claim that they have a new service being launched next month that has better security.
Overall I rate the product 7/10.
While I was waiting for the password to come through I decided to call Rackspace support and see how good they are. They claim that they have fanatical support. I explained the issue I was having and while I was on hold the emails came through. Overall I found the support quite good although I did have to wait in a hold queue for about 5 minutes before speaking with a human with a North American accent. I rate the telephone support 8.5/10.