Blogs

RedMonk

Skip to content

Open Management Consortium: The Kids vs. The Stodgy in Systems Management

The Open Management Consortium, is finally public today. I’ve been talking with William “whurley” Hurley of Qlusters on and off about it for sometime, so it’s exciting to see it finally take shape.

What Is It?

The essence of the OMC’s mission is:

The Consortium will work to drive open standards for systems management within the industry, assisting IT managers and system administrators to custom-create solutions to best serve their business needs. One of the first projects will involve developing protocols for managing common IT infrastructure components, including information about servers, storage devices, configurations, networks models, middleware, applications and other relevant data, to create a unified approach to systems management for open source vendors and projects. The Consortium’s agenda also includes designing several integration paths for exchanging data with proprietary systems.

And the founding members are:

Nagios (sponsored by Ayamon), NetDirector (sponsored by Emu Software), openQRM (sponsored by Qlusters), openSIMS (sponsored by Symbiot), the Webmin project and the Zenoss project (sponsored by Zenoss, Inc.).

You can check out the rest of the site at www.open-management.com. Raven Zachary of 451 also has some commentary on the OMC.

How Real Is It?

I’ve spoken with several of the vendors involved, and they’re companies and software are very real. They have paying customers, roadmaps, and good systems management pedigree. I’ve also spoken extensively with some of the people involved, particularly, whurley, and I know he’s for real not only with his vision, but the execution of it.

As with any group, simply slapping up a web page, blog, and mailing list, snazzy as they may look, are simply the costs of doing business. The type and amount of activity on the mailing list over the next few months will be the best indicator — from afar — of how “real” the group is. The next mile-stone is developing some sort of interop mechanism — perhaps a standard — that each of the members support and ship. Once that’s accomplished, them the OMC will indeed, be very real.

And, by “real” I mean an active threat to The Big 4: BMC, IBM, CA, and HP…and, as we’ll see below, Microsoft.

The Zero Sum Game

The OMC’s goal to go up against The Big 4 is no big secret. Indeed, whurley said as much in an interview with Dan Farber last month:

Hurley described the coalition as a potential “800-pound gorilla alternative to IBM Tivoli” and other proprietary heavyweights, who he dissed as “old and stodgy” compared to the more fleet “user-driven innovations” that come from an open source ecosystem.

Along those lines, the first thing that’ll be fun to watch is the mailing list and the blog reaction. Getting open source systems management people talking on one mailing list is sure to be enjoyable. The OSS systems management people have a window open to cause some serious disruption in the systems management world, and ganging up together gives them a good shot at not only surviving, but thriving.

There’ll be a lot of excitement all around if Big 4 vs. OSS systems management goes zero-sum. Remember how much fun it was to think, talk, and write about Windows vs. Linux, and the watch Linux take out all the commercial Unixes?

Growing Instead of Killing

I’m not much for vendor sports, even when vendors are open source. In my ideal world, I’d prefer to see The Big 4 and the OMC partner up and work together. I’m pretty sure the “small” guys wouldn’t mind that at all, if it was genuine, but I’m somewhat pessimistic about the larger folks even smelling out the other camp: indeed, what’s the motivation. Of all The Big 4, CA has done something to make me think otherwise.

I’ve suggested that Microsoft team up with the likes of the OMC, and the same applies to The Big 4 as well. The great thing about “open thinking” is that everyone is welcome to the party as long as they’re not an ass. So if you’re one of BMC, IBM, CA, or HP, I’d suggest figuring out how to become part of the OMC, ideally by open sourcing something yourself, getting involved with standardization, or something as base as sponsoring them. There’s plenty of standardization work to be done that will be beneficial no matter who does it, and a body like the OMC could be a catalyst for actually getting a usable and ubiquitous systems management standard. Old King SNMP has sit on the throne for a long, long, long time, and the fracture between WS-Management and WSDM will just be a distraction from whatever the OMC or others might come up with.

The benefits for the OMC of Big 4 involvement would be, essentially, an instant victory in their mission: shaking up systems management both technologically and price-wise. As always, Sun is the wild-card with their yet to be open sourced systems management suite. Involvement from Sun would be fantastically exciting to see, perhaps we can arrange something if both parties are interested in smelling each other out.

Microsoft & the Mid-market

For the OMC, of course, I still believe that Microsoft is their biggest competition: the small to mid-market is going to be both Microsoft’s and the OMC member’s bread and butter for the next few years.

Indeed, assimilating or “winning” against Microsoft is probably the gate-keeper for even getting on the battle field with The Big 4. At the very least (and here I go sinking into military analogies again, apologies all around), the OMC will have a two front war to fight against Microsoft and The Big 4.

I have no doubt that the open source systems management crew has and will have the technology to do it: the real question is if they can change the culture of enterprise systems management to buy from them. Again, when it comes to smaller folks, working together is always the best shot at that kind of marketering.

Innovation

At the very least, I’m hoping that the energy and the passion of the OMC members will give the systems management a big shot in the arm: there’s plenty of innovation to be had outside of the mindset that’s existed for years. I’ve seen The Big 4 talking a good talk along those lines, but they haven’t had motivation to go into hyper-mode and deliver at a rapid pace. Those thick maintenance revenues are keeping the halls awfully quite. Hopefully, the OMC will live up to my expectations and light a big enough fire under the whole systems management market, themselves includes, to spice things up. These next few months will be telling

Disclaimer: Microsoft, BMC, IBM, and Sun are clients.

Technorati Tags: , , , , , , , , ,

Categories: Uncategorized.

Comment Feed

2 Responses

  1. Hey Cote – some great perspectives here on the OMC. With respect to their mission and your suggestion that Microsoft should be looking to collaborate, one question that springs to mind concerns WS-Management.

    It seems to me at least the the OMC is setting to solve some of the problems which Microsoft is addressing with WS-Management. Is that your sense? Microsoft is closely linking WS-Management and the System Definition Model, which might pose a stumbling block for collaboration with OMC given that it is Microsoft-only at the moment (in contrast to WS-Management which at least is being addressed through DMTF).

    Also, given the convergence that is planned for WS-Management and WSDM (see http://www.mwdadvisors.com/blog/2006/03/web-services-management-standards.html) what could that mean for any interop standards developed by OMC?

    Interesting times indeed.

  2. Neil: thanks for the comment ;>
    Yeah, WSMan and WSDM, along with whatever their merger ends up looking like, have long left the stables, as it were. It’d be a big deal if they were scuttled, or changed, because of OMC involvement. Effectively, that means the OMC would have to piggy-back on that “locked down” standards.
    To me, accomplishing the goal of SDM is the real value. The fact that that’s not open is a chance for someone to make an equivalent that gets deployed and used before SDM has a chance to take hold…if it’s ever to have a chance out of the MSFT silo.
    Now, I should also point out that the OMC’s approach to their standardization goals, in true OSS fashion, don’t take exactly the same form as large vendors do. See this little thread on their list. The notion of establishing standard URLs isn’t something you’d expect to see from an XML-centric committee, and it’s a great first step.
    In that sense, even if there’s little chance for something beyond rubber-stamp collaboration between the OMC and Microsoft (and/or other vendors), there’re plenty of other green fields to work on.