GoGrid’s solid state disk (SSD) Cloud Servers are the next evolution in cloud servers. With 10 Gbps public and private network connectivity, RAM allocations of up to 64 GB, 40 cores, up to 2,199 GB of persistent storage, plus the ability to provision up to 12 TB block volumes, these SSDs are designed to solve for most high I/O applications. You can find out more about our SSD Cloud Servers in a video we posted on YouTube.
In this post I’ll walk you through the basics of deploying an SSD Cloud Server on GoGrid. Like everything we deliver as a service, deploying SSD Cloud Servers through the GoGrid management console is simple and easy. Let’s get started.
Once in the management console I’ll select the +add button to begin setting up my server deployment. By selecting +add , I can deploy a variety of compute, network, and storage options.
Clicking on the +add button brings up the Add a New Object window. From here I select the data center location I’d like to use for this deployment. In this example, I’ll select “US-West-1” from the dropdown menu.
I then need to select whether or not I want to spin up a compute, network, or storage object. Each of these selections leads to their related resources. In addition to the compute options—Standard Cloud Servers, Dedicated Servers, and SSD Cloud Servers—I have the option of deploying network and storage options like Dynamic Load Balancers, Firewall Services, or Block Storage and even requesting additional managed services like Managed Security and Managed Monitoring.
For this demonstration however, I’ll simply be deploying an SSD Cloud Server. Once I’ve selected the data center, I simply click on the Compute button to see my options. From here, I’m prompted to select a server image. In this case, I want to select a Windows image, so I’ll select “Windows” as the OS type from the drop-down menu.
This action brings up a list of available Windows servers. At the bottom of the list is an option for a Windows 2012 Server (64-bit). I’ll go ahead and select that image and click Next to begin the deployment.
The Add Cloud Server window pops up where I can add server details. I’ll go ahead and fill out the server name, description, select an IP, and choose the “server flavor.” Flavors are related to the type of server; for example, I can filter by SSD or Standard Cloud Servers. For this example, I’ll select SSD and choose a large SSD server.
Clicking Next brings up the options for server payment terms. At GoGrid, customers have the option to pay by the hour, by the month, or by the year. Monthly charges are roughly 25% off what the typical hourly rate would be if you ran an hourly server for an entire month. Annual servers are about 50% off what the hourly rate would be if you ran an hourly server for an entire year. For this example, I’ll choose to pay for the server by the hour.
After making my selection, all I have to do is hit the Save button to launch the server. In the management console, I can now see that my server has been launched. As the server is building the icon will appear greyed out and the status/availability indicator (the vertical bar) will be yellow.
Once the server is active, the status indicator will turn green and the server icon will appear in full color.
Hovering over the server with your mouse lets you see the server details.
Right-clicking on the server or ctrl+click on a Mac brings up an action menu. I’ll select passwords to access the default password for the server I just created. Once I’ve retrieved my password, I’ll select the option to access my server through the console feature by bringing up the action menu again and selecting console.
This action brings up a “console” screen in your browser. I’ll need to hit the Ctrl-Alt-Del button in the right-hand corner to log in to the server.
Doing so lets me access the server and then I can see the desktop.
At this point, I can begin configuring my new server to suit my needs.
And that’s it. I now have an SSD Cloud Server up and running, and it took me less than 5 minutes to deploy. Be sure to check out all our server options and then imagine what you could do in just a few minutes.
Latest posts by Kole Hicks (see all)
- Selecting a Provider and Infrastructure for Running an In-Memory Database - August 19, 2014
- Architecting for High Availability in the Cloud - July 22, 2014
- Comparing Cloud Infrastructure Options for Running NoSQL Workloads - April 11, 2014