Archive for the ‘GoGrid’ Category

 

Are These Really Mysteries? Solving Forbes’ “7 Great Unsolved Mysteries of Cloud Computing”

Wednesday, February 6th, 2013 by Michael Sheehan

From time to time, I come across an article that I feel compelled to respond to. Yesterday, I read “7 Great Unsolved Mysteries of Cloud Computing” written by Joe McKendrick (an author and independent researcher covering IT trends and markets) in Forbes.com. Although McKendrick definitely offers some thought-provoking questions in the form of “cloud mysteries,” part of me feels these mysteries were already solved a long time ago.

Forbes-article

What follows are the questions that McKendrick asks, my interpretation of his descriptions, and my responses to these mysteries. I’d love to hear your feedback on these mysteries and my responses, so be sure to leave a comment.

7 Great “Unsolved” Mysteries of Cloud Computing

McKendrick alludes to the 2010s as a “cloud computing migration.” A “migration” connotes a feeling of evolution, and I do believe that cloud computing is evolving through a natural progression (see “Riding the Gartner Hype Cycle Roller Coaster: Hang on to your Magic Quadrants!”) toward mainstream adoption.

But let’s take a look at the “unsolved” mysteries.

(more…) «Are These Really Mysteries? Solving Forbes’ “7 Great Unsolved Mysteries of Cloud Computing”»

High Availability with Dynamic Load Balancers

Monday, February 4th, 2013 by Rupert Tagnipes

Building out a highly available website means that it is fault-tolerant and reliable. A best practice is to put your web servers behind a load balancer not only to distribute load, but also to mitigate the risk of an end user accessing a failing web server. However, traditional load balancing funnels traffic into a single-tenant environment—a single point of failure. A better practice is to have a distributed load balancer that takes advantage of the features of the cloud and increases the fault-tolerance abilities on the load balancer. GoGrid’s Dynamic Load Balancer service is designed around a software-defined networking (SDN) architecture that turns the data center into one big load balancer.

traffic_light_2

GoGrid’s Dynamic Load Balancer offers many features, but one of its core features is high availability (HA). It is HA in two ways.

First, on the real server side, deploying multiple clones of your real servers is a standard load-balancing practice. That way, if one of your servers goes down, the load balancer will use the remaining servers in the pool to continue to serve up content. In addition, each GoGrid cloud server that you deploy as a web server (in the real server pool) is most likely on a different physical node. This setup provides additional protection in the case of hardware failure.

Second, on the Dynamic Load Balancer side, the load balancers are designed to be self-healing. In case of a hardware failure, Dynamic Load Balancing is designed to immediately recover to a functioning node. The Virtual IP address of the Dynamic Load Balancer (the VIP) is maintained as well as all the configurations, with all the changes happening on the back end. This approach ensures the Dynamic Load Balancer will continue to function with minimal interruption, preventing the Dynamic Load Balancer from being a single point of failure. Because the load balancer is the public-facing side of a web server, whenever it goes down the website goes down. Having a self-healing load balancer therefore makes the web application more resilient.

Users with websites or applications that need to always be available would benefit from including GoGrid’s Dynamic Load Balancing in their infrastructure. The load balancer is important for ensuring the public side of a service is always available; however, including easily scalable cloud servers, the ability to store images of those servers in persistent storage, and the option to replicate infrastructure between data centers with CloudLink are all important elements of a successful HA setup.

(more…) «High Availability with Dynamic Load Balancers»

How to Create a GoGrid Cloud Server Image for Rapid Scalability

Thursday, January 31st, 2013 by Michael Sheehan

Let’s say that you have fully configured a Cloud Server running on GoGrid. You’re so proud of your achievement that you want to share your configuration with your team or perhaps even with the GoGrid community. And let’s imagine that you or your company has developed a software solution that you’d like to monetize within a Public Cloud. Well, the process of creating and sharing a GoGrid Cloud Server Image (GSI) is easy and literally takes just a few minutes.

image

Similar to our previous “How To” article and video (“How to Select, Configure, & Deploy a GoGrid Cloud Server in Minutes”), the process of creating a GSI is straightforward and can be simplified into 3 easy steps:

1. Select
2. Save
3. Share

Before I show you how easy it is to create a GoGrid Cloud Server Image, here are some ways you might use it:

  • To reduce setup and configuration times for new servers
  • To enable rapid horizontal scaling of servers
  • To create a back-up repository of your GoGrid servers
  • To share your server configuration with your team for future cloud deployments
  • To monetize a software solution

(more…) «How to Create a GoGrid Cloud Server Image for Rapid Scalability»

Leverage Automation for your Private Network

Tuesday, January 29th, 2013 by Rupert Tagnipes

GoGrid has recently released some new features that improve on the customer experience using our private network.  Private Network Automation (PNA) is currently available in all our data centers. As of this most recent release, these new features will be exposed if you enable PNA by contacting support:

  • All servers will have a private IP assigned upon creation (both virtual and dedicated)
  • Any private IPs that are used will be marked as assigned on the portal
  • Cloud Storage no longer requires static routes. It is now accessible via your favorite protocol (Samba, SCP, etc.)

The assignment of private IPs happen automatically at the time a new server is deployed. GoGrid has enabled this for all new customers. If you are an existing customer, this is feature IS NOT enabled in data centers where you have servers deployed. You will need to file a support ticket to request this feature. Note that once enabled, this will be active for all new servers only – existing servers will keep their existing settings.

As you can see from the screenshot below, once you create the server, you will have a public IP and a private IP assigned. Note that this feature is enabled for both virtual and dedicated servers.

AMS_private_IP

This is also visible in the Networking tab so that you can monitor private IPs that have been assigned from your block.

PNA_List

(more…) «Leverage Automation for your Private Network»

How to Recover from a Linux Security Breach – Recovery & Hardening (Part 2)

Tuesday, January 29th, 2013 by Mario Duarte

This is Part 2 of a GoGrid security blog series on identifying and recovering from a Linux security breach. Part 1 provided general guidelines for conducting a security analysis on a compromised Linux server and forming strategic teams to address and resolve the breach.

In this article, we’ll review some recommended steps for recovering from a breach.

Recovering from the Breach

Lock the doors

Now that you’ve confirmed that there are no intruders logged in and you’ve identified the established connections, it’s time to “lock the doors.” Locking the doors largely depends on who is managing your firewall. Contact GoGrid in the event that we’re managing your firewall or perform the following actions if you manage your firewall:

  • Modify your system’s iptables configuration to restrict all remote console connections such as SSH to your office network
  • Modify your system’s iptables configuration to block all previously identified suspicious connections from and to your system.
  • Modify your system’s iptables to block all other services from the public Internet to your server. Doing so will effectively bring down your website or services, but you want to avoid compromising your customers or web site visitors.

Install and run a rootkit analyzer

(more…) «How to Recover from a Linux Security Breach – Recovery & Hardening (Part 2)»