Hardware

Storage, storage STORAGE!

SInce last month, our Nexenta based storage cluster has been deployed and I have now moved production data onto it.

A bump and bruise occurred last weekend (I had done an announcement already) and yesterday things burped again.

The problem? Looks like an issue with the 2 mirrored boot drives of the first head unit (each head manages its own volumes and HA is used to make sure a single head failure doesn’t cause an outage) are … bad.

One drive has full on SMART failure via the BIOS. Interesting…so replace that drive with another from the shelf…and the other drive is showing something ‘odd’. Yank it out, replace it, and move it another machine for testing.

And it is failing as well! Four hard disks, 2 per head unit, and 2 fail in one head unit, what are the chances of that? (the second head unit does not exhibit any of the same symptoms)

More >

A storage cluster is born

It is time to add space to our VMware cluster for storage of VMs for our customers.

We started initially using Compellent SAN storage. Worked well, had a lot of space, but the performance was not what I was looking for (it is all SATA based), using F/C is far more complicated than we need for this project, and just plain expensive to upgrade (adding a shelf of 16 450GB SAS disks is more expensive than the solution presented here).

Spin forward a few months, I took one of our older NetApp FAS270c systems and ripped out the 73GB 10K disks, went to eBay and purchased 2 shelves of 300GB 10K F/C disks and after an afternoon of shuffling we had ourselves a cluster for storage. Performance is absolutely great (and predictable). Expanding it? Expensive, just like the Compellent, and I also wanted to investigate some of the new things that can be done with storage, like inline (and synchronous) compression and data deduplication.

History lesson: Years and years ago I did a lot with Solaris and I have kept my feet wet playing with OpenSolaris and ZFS. I won’t bore you with the great details of why ZFS is the shit (links at the bottom of the post) or why Solaris needs to live on forever (because no one can thread at the kernel level like Solaris), but I will tell you that using Solaris (or OpenSolaris) with ZFS is a combination that is very tough to beat. So last year I used the Sun Try-and-Buy program to test out a 7110 and I absolutely loved the interface, and the price drop that occurred while I had it! But someone within Sun decided that no, as a TaB customer the new pricing is not available. I was floored by this. I shipped back the 7110, and anyway, I really wanted a cluster, not a single head, single JBOD enclosure.

In the end I wanted a cluster!

That’s 2 heads, automatic failover, etherchannel/trunk/IPMP/LACP oh hell, I just wanted multiple ethernets bound together if possible, basic reporting (I can SNMP for the real stuff), and finally, a price tag that I can feel good about for storage of our customer data.

This is where NexentaStor comes in! They have the pieces all put together so I don’t have to self-engineer something. I have a vendor I can harass or ask questions of. I can focus on what makes my business work instead of working to make my business stable.

More >

HOW-TO: Carpet your data center

Earlier today we announced the changes to our data center – you can read about that here.

Now we are getting some feedback:

How did you do it?

Why did you do it?

Why not shag?

Those purple stripes clash with my servers, wtf?

So, onward we go, with help from an office mate who wishes to remain anonymous; let’s call him Nick.

More >

Example cost: Virtual Private Cloud (updated)

Back in September, 2009, I had written a post with a quick overview of what a private cloud (or infrastructure) looks like and some basic costs and information, including why it is a great product (I am biased).

Since then, Dell has retired the PE2900III model server and items change, this is an update for the basic configuration.

Reminder graphic:

wpid-wpid-2-esx-with-a-mic.L9hFggu7HJmt.953Enl6Tm7vT.jpg

2 Servers, 1 firewall

So, originally, the physical servers were configured as:

  • Dell PE2900III (reasonably priced, very reliable, I have spares on the shelf)
  • 4 ethernet ports (2 built in, 2 port card installed, more can be added)
  • 2 73GB SAS drives mirrored together for booting VMware vSphere 4
  • 32GB RAM (48GB is max for this hardware platform)

New servers look like:

  • Dell PET610 (reasonable price, very reliable, spares to go onto the shelf)
  • 4 ethernet ports (all built in)
  • 2 80GB SATA drives mirrored together for booting VMware vSphere 4
  • 48GB RAM (192GB max available – very expensive)

The reason for the RAM change is that I am seeing a 2:1 (or higher) ratio of RAM to CPU usage in terms of percentage, and 48GB is a good place for this sized system. Also, the newer Xeon 55xx series processors uses RAM sticks in 3s instead of 2 or 4 at a time. 48GB is 12 4GB sticks of RAM. The newer 55xx series of processors also has working hyper-threading (or H/T) and I am seeing very nice performance on servers deployed using this processor family in our network.

Cost difference? The original posting listed had estimated the cost at $1,600.00 per month (see previous post), and I estimate this to be very close, inching up to approximately $1,700.00 per month, and this number should be high. (for accurate pricing, please contact ipHouse sales people, they can run up a quote based on real numbers)

The new iPad hype

What’s the issue really?

Oh noes, no camera? That’ll change I bet.

No flash? Win in my book!

No multitasking? Really, you wanna run more things, buy a computer.

Now, the speculation about version 2 makes me laugh, but really, aren’t we at version 3? In my office common area, I have version 1, and I’ll include a picture.

Back to the iPad – just sit back and see what really happens. We are 60-90 days out (minimum) before it hits the shelves, maybe a surprise will come. Like tether-ability! That’d be win.

And as promised…and yes, it still works, and is not for sale.

The Original iPad

For those about to write..

  • ipHouse Blog
  • an ipHouse production.