Adventures in systems land

One of the things I pushed for when I first joined Power Systems(then System p) was for the IBM redbooks to focus more on software stacks, and to relate how the Power Systems hardware can be exploited to deliver a more extensive, and easier to use and more efficient hardware stack than many scale out solutions.

Scott Vetter, ITSO Austin project lead, who I first worked with back in probably 1992 in Poughkeepsie, and the Austin based ITSO team, including Monte Poppe from our System Test team, who has recently been focusing on SAP configurations, have just published a new IBM Redbook.

The Redbook, Power Systems and SOA Synergy, SG24-7607, is available free for download from the redbooks abstract page here.

The book was written by systems people, and will be useful to systems people. It contains as useful summary and overview of SOA applications, ESB’s, WebSphere etc. as well as some examples of how and what you can use Power Systems for, including things like WPARs in AIX.

There’s an excellent analysis by Frank Dzubeck over on Network World today about the new Enterprise Data Center and that hoary old chestnut latency. I don’t know who briefed Frank, it wasn’t me, Jeff and I talked this afternoon and I asked, it wasn’t him, since the article covered also the z10 announcement, I have a good idea though

Frank covers ensembles, data center utilization and the some of the new data center fabric issues extremely well. He also makes the point, that I’d like folks to be clear about, that this isn’t the resurgance of the mainframe, or everthing back to a central server.

We’ve grown use to indefinite waits, or unbelievably fast response times from certain popular websites, but the emerging problem is around latency in the data center. How to deliver service levels and response times in an increasingly rich and complex systems environment. It’s OK to build a data center or server subsystem focussed around a single business model, something like Amazons EC2 or S3, or Googles search and query engines; it’s another to integrate a vast array of different vendors IT equipment bought at different times for different business applications and services and integrate them all together and orchestrate them as business services. While MapReduce may or may not be as good as, or better than a database, not everything is going to be run in this fashion.

Fibre channel over ethernet is a going to happen, 10Gb ethernet opens up some real options in terms of both integrating systems, and distributing services. It will be almost as fast to connect to another server as it is to talk between cores and processors within the same server. This disclosure from IBM Research today shows the way to the next generation of interconnected infrastructure, working at 300-Gbit/second, the bus goes optical making the integration of rich data systems video, VOIP, total encryption of data, secure key based secure infrastructure services, integrated with more traditional transactional systems a real possibility.

The opportunity isn’t to take the same old stuff and distribute it because the fabric is faster, it’s about better integrating systems, exploiting new ways of doing things. Introducing a common event infrastructure, being more intelligent about WAN and Application routing, having a publish/subscribe/consume model for the infrastructure and genuinely opening it up and simplifying it.

Of course, there a re lots of blanks to be filled in, but the new Enterprise Data Center is taking shape.

IBM announced today our new Enterprise Data Center vision. There are lots of links from the new ibm.com/datacenter web page which split out into their various constituencies Virtualization, Energy Efficiency, Security, Business resiliency and IT service delivery.

To net it out from my perspective though, there is a lot of good technology behind this, and an interesting direction summarized nicely starting on page-10 on the POV paper linked from the new data center page or here.

What it lays out are the three main stages of adoption for the new data center, simplified, shared and dynamic. The Clabby analytics paper, also linked from the new data center page or here, puts the three stages in a more consumable practical tabular format.

They are really not new, many of our customers will have discussed these with us many times before. In fact, there’s no coincidence that the new Enterprise Data Center vision was launched the same day as the new IBM Z10 mainframe. We started discussing and talking about these these when I worked for Enterprise Systems in 1999, and we formally laid the groundwork in the on demand strategy in 2003. In fact, I see the Clabby paper has used the on demand operating environment block architecture to illustrate the service patterns. Who’d have guessed.

Simplify: reduce costs for infrastructure, operations and management

Share: for rapid deployment of infrastructure, at any scale

Dynamic: respond to new business requests across the company and beyond

However, the new Enterprise Data Center isn’t based on a mainframe, Z10 or otherwise. It’s about a style of computing, how to build, migrate and exploit a modern data center. Power Systems has some unique functions in both the Share and Dynamic stages, like partition mobility, with lots more to come.

For some further insight into the new data center vision, take a look at the presentation linked off my On a Clear day post from December.

It’s not very often these days I get to escape my bunker in IBM Austin. On December the 6th I was asked to speak at the NCOIC Conference and work group in St Petersburg, Florida.

The invitation came in a roundabout way, via Massimo Re Ferre from IBM Italy, and Bob Marcus at SRI. The agenda and speakers looked interesting, and so I decided to take the opportunity and go run some of the current thinking by an influential audience. Speaking right before me was Roger Smith, CTO of the US Army PEO STRI division, and he gave a fascinating talk on warefare simulation and training.

I decided to talk about the evolution of Grid, On Demand, SOA and the Blue Cloud implementation of a Service Oriented Infrastructure. We had a useful discussion on what could be done now, net answer, pretty much all of it. You can’t buy it as a product or solution, but you can build it from either IBM or open standards/source parts now.

What’s made the difference is the ability to build around a common, composite infrastructure for management. Previously we’d tried to build and deliver this everywhere, now it’s much more focussed on platform by platform based implementation. Get it right in one place, move it to another.

I’ve posted the slides on slideshare.net here and I’ve also put the PDF on wordpress for download, here.

RedNun’s report on Open Source ESBs is published and it has some useful updates and additional information from her earlier web piece which elicited my “I’m a centrprise architect” response.

In her intro, Anne says “Lightweight open source enterprise service bus (ESB) implementations offer a low cost, scalable, and practical approach to enterprise application integration.” - I’m so with that, but as always with a spin on it. Actually an ESB would make the perfect vehicle(bus geddit?) for system infrastructure integration.

Still much to do on standards, implementations, h/w runtimes etc. but I still firmly believe this is the direction we should be going to implement genuinely interoperable hardware based components. Common messages formats, industry schema, common messaging protocols and one or more buses to intermediate for the components and manage pub/sub etc.. Dynamic, autonomic, vendor neutral hardware, we’ll get there.