Hardwhere? - Part Deux: Softwhere (as in soft, fluffy clouds)

September 21, 2009

I won’t pretend to know the ins and outs of the cloud software we use (okay, maybe a little :),) but I know the gist of it as far as hardware is concerned- redundancy. Entire servers were the last piece of the puzzle needed to complete entire hardware redundancy. In my original article, Hardwhere?, (http://theinnerlayer.softlayer.com/2008/hardwhere/) I talked about using load balancers to spread the load to multiple servers (a service we already had at the time) and eluded to cloud computing.

Now cloud services are a reality.

This is a dream come true for me as the hardware manager. Hardware will always have failures and living in the cloud eliminates customer impact. Words cannot describe what it means to the customer. Never again will a downed server impact service.

Simply put, when you use a SoftLayer CloudLayer Computing Instance, your software is running on one or more servers. If one of these should fail, the load of your software is shifted to another server in the “cloud” seamlessly. We call this HA or High Availability.

If there is a sad part to all of this, it would be that I have spent considerable effort optimizing the hardware department to minimize customer downtime in the even on hardware failures. But I have a rather odd way of looking at my job. I believe the end game of any job I do is complete automation and/or elimination of the task altogether. (Can you say the opposite of job security?) I have a going joke where I say: “Until I have automated and/or proceduralized everything down to perfection with one big red button, there is still work to be done!”

Cloud computing eliminates the customer impact of hardware failures. Bam! Even though this has nothing to do with my hardware department planning, policies and procedures, I have no ego in the matter. If it solves the problem, I don’t care who did the work and was the genius behind it all, as long as it moves us forward with the best products and optimal customer satisfaction!

We have taken the worry out of hosting- no more deciding what RAID is best. No more worrying about how to keep your data available in the event of a hardware failure. CloudLayer does it for you and has all the same service options as a dedicated server and more! One more step to a big red button for the customer!

Now back to working on the DC patrol sharks (they keep eating the techs!) New project- tech redundancy!

Leave a Reply

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <pre>, <blockcode>, <bash>, <c>, <cpp>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>, <ruby>. The supported tag styles are: <foo>, [foo].
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.

Leave a Reply

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <pre>, <blockcode>, <bash>, <c>, <cpp>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>, <ruby>. The supported tag styles are: <foo>, [foo].
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.