You - vendor. Pin your ears back, I've got some things to tell you

No, there is no coffee and you may not sit down. Notebooks out

La Puerta (The Door) by Mauricio García Vega

Storagebod The problem with many discussions in IT is that they rapidly descend into ones that look and feel like religious debate; whereas reality is much more complex and the good IT specialist will develop their own syncretic religion and pinch bits that work from everywhere.

One of the things that many of us working in Enterprise IT tend to find is that our houses have many rooms and must host many differing belief systems. The one true way is not a reality. And any organisation more than fifteen years old has probably built up a fair amount of incompatible dogmas.

For all the pronouncements of the clouderatti, we are simply not in the position to move whole-scale to the Cloud in any of its many forms. We have applications that are simply not designed for scale-out; they are certainly not infrastructure aware and none of them are built for failure. But we also have a developer community who might be wanting to push ahead, to use the language du jour and who want to utilise cloud-like infrastructure, dev-ops and software defined everything.

So what do we in the infrastructure teams do? Well, we're going to have to implement multiple infrastructure patterns to cater for the demands of all our communities. But we really don’t want to bespoke everything and we certainly don’t want to lock ourselves into anything.

Many of the hyper-converged plays lock us into one technology or another; hence we are starting to look at building our own rack-converged blocks to give us lowest common denominator infrastructure that can be managed with standard tools.

Vendors with unique features are sent packing. We want to know why you are better at the 90 per cent. Features will not sell; if I can’t source a feature/function from more than one vendor, I probably will not do it. Vendors who won't play nice with other vendors, or vendors who insist on doing it all and make that their lock-in are not where it’s at.

On top of this infrastructure we will start to layer on the environment to support the applications. For some applications this will be cloudy and fluffy. We will allow a lot more developer interaction with the infrastructure and it will feel a lot closer to dev-ops.

But everything does need to sit on a common, reusable infrastructure that will allow us to meet the demands of the business. This infrastructure needs to be able to be quickly deployed but also quickly removed and moved away from; it will not require us to train our infrastructure teams in depth to take advantage of some unique feature.

Remember, vendors - partner well with us but also with your competitors. Yes, it sometimes makes for an amusing conversation about how rubbish the other guy is but we’ll also have exactly that same conversation about you.

Don’t just play lip-service to openness, be prepared to show us evidence, my friend. ®


Biting the hand that feeds IT © 1998–2017