Storagebod Rotating Header Image

SRM – Stack Resource Management

2011 will see acquisitions continue to come as all of the major players try to position themselves as owners of the vertical stack; we will see acquisitions to enable the general compute stack but also acquisitions which enable specialised appliance based stacks. Obviously, we will also see the major players continue to announce home-grown stack products as well.

All of these stacks will blow up smog which might well look something akin to a Cloud; the question is whether this will be a toxic cloud or something more beneficent bringing the necessary components for business growth?

One of the biggest challenges will be that we will have different types of stacks; there will be the odd case where a data centre is homogeneous but it will be more usual for a data centre to have at least two vendors. This might be for either technical reasons or for purely commercial reasons; two vendors competing may well be more honest than a single dominant vendors. And of course, there is the ever present public Cloud option to be considered.

The question is going to be one of how to manage these stacks; both from a data centre point of view but also from a rack/server position. How do we manage both the data centre and from application to spindle? 

To this day we struggle to manage storage arrays from different vendors with a single pane of glass; we even struggle to get a common view let alone a common configuration tool. How much more complex will this become when we have several vertical stacks from a variety of vendors to manage?

Yes, we could struggle on and manage at the component level but how is this going to bring the reduced complexity and business benefit that these stacks could bring? We could even find ourselves using shell interfaces/APIs to produce our own consolidated tools; assuming that these shell interfaces/APIs are available. 

Storage Resource Management has been a big #FAIL in general; Stack Resource Management could have a similar future unless we see vendors and other interested parties begin to get a handle on this. I certainly expect to see acquisition in this space as vendors try to steal a march on each other but really, this might a place best served by co-opetition and standards.

Formal standards? Possibly not but two or three of the bigger players could do the market a huge service by beginning to think along the lines of an open standard. And if one emerges; they could do an even bigger service but not taking the approach of 'embrace and extend'.  

 


3 Comments

  1. Andrew Fidel says:

    Perhaps a marriage of Cloud Data Management Interface with SMI-S? I don’t think people are demanding standards compliance enough from the vendor and I don’t think enough end users are getting engaged with SNIA to push what they actually need into the standards.

  2. Martin G says:

    There’s a bit of chicken and egg going on at the moment; I completely agree that end-users are not engaged enough with SNIA but how end-users get the time and funding to get engaged with SNIA is another challenge.
    Yet without robust standards which are applicable and relevant to the end-user; standards compliance never becomes a decision factor for acquisition.

  3. Andrew Fidel says:

    I agree completely, and I’m a bit of a hypocrite on this as I’m not very engaged myself. I justify it to myself by saying that storage is just a very small part of my job (though an important one).
    One interesting thing is that most vendors have a Powershell API so you can at least write scripts that tie more than one system together even if a standardized interface would be preferred for modularity and reusability as well as the possibility of a rich 3rd party ecosystem.

Leave a Reply

Your email address will not be published. Required fields are marked *