Future Storage Systems: A pause in workflow

Since I started this article series, I’ve had the awesome opportunity to have my ideas (well, some of the early articles at least) reviewed by person(s) who deal with the actual infrastructure of storage systems day in, day out.  The benefit of such peer review is that you get to learn at the symbolic “feet” of the masters and discover flaws, omissions, and understated features that need to be understood and incorporated.  This post is dedicated to some of those discussions and, where applicable, my understanding of how the FSS either incorporates or misses the boat.

Future Storage Systems: Part 4: Operating System – Conceptual Overview

In the previous Future Storage System articles, we’ve covered the basic hardware foundation for what I envision to be a powerful future-oriented storage solution for the commercial midrange.  However, as you’re probably aware, hardware is meaningless without software to provide the operational capabilities that are needed to mange information.  In this article, I will focus on a general design for an extensible software layer (an OS) that will provide future-oriented capability expansion as well as robust analytics, capabilities, and integration with business continuity principles.  As always, please reference the diagram below.

Future Storage System - Operating System - Conceptual

Future Storage Systems: Part 3b – I/O Expansion Node

In Part 3a, we discussed the possibility of a purpose-driven Compute Node based on the Torrenza initiative for the Future Storage system.  This expansion node made use of Hypertransport as a “glue” between the base storage compute node and the expansion node (of computation or I/O flavours) that could be added.  The advantages of that topology were simple:  hot add support for additional processing power, additional I/O bandwidth within the system, and additional computing power for the array OS (which we’ll cover in a later article).  In this overview, we’ll take a look at another variation on an expansion node: an I/O expansion node that will add additional front-end ports and/or functionality to the base system.  We will be referencing the diagram below. (Apologies in advance for the image shearing off in the lower right hand corner).

Hypertransport I/O Expansion Topology

Future Storage Systems: Part 3a – Node Expansion Overview

In the previous two articles on the Future Storage System (FSS), I took a general look at a basic storage system architecture (Part 1) and then went a bit deeper into some of the more interesting bits of that system from a platform standpoint (Part 2).  In this article, I want to dive a bit deeper into how I envision nodes to be building blocks for additional capabilities and processing directives.  I will be referencing the image below as part of this article.

Hypertransport Node Expansion (detailed)

Future Storage Systems: Part 2 – Detailed Node View

So, in my article yesterday, I gave a global view of a very simple storage system for the future. Since I LOVE this type of conjecture and theoretics (is that a word?), I decided to take this a step further and flesh out some of the other intricacies of the design.  Check out the image below and then click through to read the rest.

Fleshing out the Hypertransport Storage System

Why wouldn’t the following work? (Future Storage System: Part 1)

So, I’ve been toying around with this in my mind for some time.  Essentially, I’ve tried to understand the basic “Storage Processor” limitation of current storage systems and propose an admittedly simplistic design to get around some of the difficulties.  The biggest hurdle, in my mind, is to have cache coherency, low latency memory access to other nodes in a “cluster,” and have a communications “bus” between nodes that is extensible (or at least will grow bandwidth with more devices on the signal chain).  Staring at that problem, then, look at the image below.

A case for Hypertransport connected nodes...

Scheduling blog entries…

One of my favourite blogs is done by the Oracle Storage Guy. His subject knowledge, post clarity, and humour lend themselves to an easy understanding of the subject matter that he is covering for a given post.  To that end, I’m going to lay out a consistent (I hope) weekly blog list of what I’d like to cover (at a high level) with deep-dives where necessary.  Note: this list isn’t exhaustive (as if it could be) and, like anyone else, I do have a life outside of EMC and technology (I’m a guitarist ). So, without further ado, here’s my subject lists:

1. CAS.  Content Addressed Storage overview. Hopefully will be able to tackle the “Why CAS?” question I hear a lot.
2. Centera.  Why Centera represents a “best fit” in the CAS market (as I see it).
3. Infiniband. Is there a resurgence of Infiniband?
4. Hypertransport. Focus on version 3.x revision of this system bus/interconnect topology.
5. Hypertransport, part 2.  How Hypertransport is shifting interconnect technology beyond the system bus.
6. Hypertransport, part 3.  Why Infiniband failed at becoming a system bus contender and forward thinking issues with CSI (common system interface; Intel bus)
7. OpenFabric Consortium. 
8. RDMA, IPoIB, etc.  Hey, I’m open to suggestions here. What do YOU want to know about?

I think this is about as forward-thinking as I get this go-around. Stay tuned. You won’t want to miss it.

Cheers,

Dave

Technorati Tags: EMC, CAS, Infiniband, Hypertransport, OpenFabric, RDMA, IPoIB, Centera

Powered by ScribeFire.

Joining the Fray…

Just thought I’d introduce myself as the latest blog persona to float into the Inter-ether. The name is Dave Graham and I’m an avid storage fan.  Coming from a background of business analytics, social psychology (more on that later), and IT consultancy, I’m glad to finally be “at home” with an employer who challenges my concepts of “good” storage and pushes me to become the best I can be.  Whew!  That was an exceptionally long-winded intro but, captures who I am.  Moving forward, I hope to be able to indulge you in two of my distinct passions:  high-speed, low latency interconnects for storage (Hypertransport/LDT, Infiniband, PCIe, et al.) and *drumroll please* CAS (especially as it relates to EMC Centera.  I welcome all feedback as I pursue these passions and, hopefully, along the way, we can have serious dialogue.

Cheers,

Dave

Technorati Tags: EMC, Centera, Infiniband, CAS, Hypertransport

Powered by ScribeFire.