Entries in IBM (2)


IBM v. AWS: Who 'wins' at the Cloud Game?

This morning, I encountered an article by Rob Enderle of CIO.com entitled: Why IBM Will Win the War with Amazon Web Services.

While I don't believe Enderle takes the time to play this out, there's reason for giving this notion some real, serious consideration.  The unstated, but important premise on which Enderle's story depends is: IBM has used the past three years to watch the cloud industry, sees where it's going, and has bought into the 'open technology' aspects of the cloud industry (in a way analogous to the way it embraced TCP/IP-oriented networking and the Linux operating system). 

Having recognized this, my key take-aways are:

  • Premise: IBM's offerings under the SmartCloud Enterprise umbrella have been placeholders and holding actions, which permits IBM to assess the winning technical directions and offerings, assess their maturity, throw significant resources into development and acqisitions, and emerge with a formidable, contemporary and commercially mature set of cloud offerings. 
  • First, IBM has and knows how to establish credibility with those parts of the organization that make technology purchasing decisions.  Few organizations have EVER out-marketed IBM. And, while we've become accustomed to paying the price for IBM's customization and customer-centric support, those aspects of their products DO impact the purchasing and operating decisions of Enterprise and even SMB IT.
  • Second, so long as IBM fields cloud infrastructure and platform that is performant, compliant and adheres to the standards on which the developer and operations communities rely, the battle's outcome is likely to depend most heavily on credibility, positioning, packaging and attendance to the 'customer facing' aspects.

The Unstated Premise.  Unlike CIO.com, I would have made the premise much more concrete and factual: IBM's initial push to respond to the rapid (... ok, the explosive) growth of cloud infrastructure services was a 'holding action.'  It has been, in great measure, a means by which a large (and entrenched) IT company responds to a market demand that AWS has both created and then served so well.  In this regard, I view IBM's recent activities in revising their cloud computing lineup with a perspective quite different from those who interpret these moves as commercial failure (like Nirvanix), customer abandonment (at worst) or perhaps bait-and-switch. Like Ben Kepes in his post on IBM, I note and am more heartily in alignment with Holger Mueller on the SCE announcements.

IBM is now selectively phasing out their initial offers (offered up under the SmartCloud Enterprise moniker), to be replaced by a 'composed' offering that relies on open cloud infrastructure (both CloudStack and OpenStack) delivered by Softlayer; storage solutions that are in lockstep with the maturity of OpenStack object storage as well as older forms more familiar to those with private SAN or NAS appliances; platform services built on Pivotal's Cloud Foundry and a stated reliance on BOSH as a general purpose utility for deployment of complex, composed applications; and… the list goes on.  

IBM's cloud thought leaders are incredibly active in their support of and contribution to open source cloud.  And, it's not just a marketing and sloganeering effort.  There is a real presence by the IBM cloud technology strategists like Angel Diaz at the Cloud Foundry Conference or Mac Devine's Keynote address recently the LinuxCon + CloudOpen conference. (Check here for the post-keynote panel discussion.)

Disparagement and Derision about Marketing and Packaging.  

As I started to read Enderle's article, I wondered at the likely reaction from the Clouderati who are now mostly engaged in word-wars about mindshare between AWS and OpenStack (with Open CloudStack making a guest appearance), the PaaS competitions which have emerged, and the various flavors of "software defined everything."  I tweeted the CIO.com link and predicted that the Cloud commentary would be generally negative, derisive reaction.

I'm now going to ask for Clouderati restraint.  (… and if any of you comment about the oxymoronic nature of that concept, bear with me.)  Before throwing brickbats at IBM or at one another, take a moment to consider:

  • If this article were about ANY other major systems or services provider, would you have made the same comments?
  • In the face of a company that has signed up to embrace open source cloud and enhance it with specific added value options for their EXISTING as well as new customers, would you not have lauded the transition as being true to the open source software credo?
  • When you consider companies that have dominated their sectors of the technology market in the recent past - including IBM, Microsoft, Oracle, BEA, Red Hat - to what degree HAS marketing, positioning and attendance to the purchasing customer and the end-user been a major pillar of their strategy and ultimate commercial success?

Now re-read the Enderle article, and drop me a line (or a tweet at @rhm2k).  



IBM's embrace of OpenStack and 'open source': OSLC, TOSCA and ...?

David Lindquist’s post in IBM’s Thoughts on Cloud blog (made in conjunction with the IBM OpenStack announcement), is an excellent high-level explanation of the rationale behind IBM’s decisions.  It is telling for at least two reasons, and notable for what might be construed as missing pieces.

Along with the whole-hearted endorsement and embrace of OpenStack, IBM has called attention to two open initiatives.  Open Services Lifecycle Collaboration(OSLC) is an initiative of which I personally was unaware until Sunday’s presentations at the IBM Pulse Open Cloud Summit. The objective of the initiative is to standardize the way that software lifecycle tools can share data.  Not just an admirable goal, but one of the necessary preconditions of a truly open, multi-vendor approach to operations, administration, management and provisioning of cloud components.

Lindquist calls out the IBM support of OASIS Topology and Orchestration Specification for Cloud Applications (aka TOSCA).  IBM has started (and will no doubt continue) to make a strong case for the use of LinkedData and OSLC in combination with TOSCA to ease the job of integration and federation within the cloud ecosystems.   Again, it’s nothing less than what one would expect from IBM, a company with a long history that values systems management.  

From David Lindquist, For cloud computing, open means agile

Together with the OpenStack FoundationOpen Services Lifecycle Collaboration (OSLC) and OASIS, we are helping to lead open cloud standards and open source initiatives. Creating an industry rallying point to drive interoperability is accelerating delivery and lowering costs, while optimizing the infrastructure layers and enabling management of the entire lifecycle to support agility with integrity. Further, workload portability and optimization supports scale, security, recovery, resiliency and agility in the development and delivery of new business applications and business models.

Further, to support the interoperability and portability of workloads across clouds we are contributing and supporting the OASIS Topology and Orchestration Specification for Cloud Applications known asTOSCA. To drive the full lifecycle of design, development, and delivery we architect our cloud solutions with Linked Data and OSLC. By leveraging OSLC we are creating an open environment to easily integrate and federate our capabilities as well as third-party tools to support DevOps, Continuous Delivery pipelines, orchestration and automation.

By opening access to data though OSLC, we can quickly pull together solutions that span the complete lifecycle, provide dashboards with insights driven by analytics, and link information across applications and infrastructures to support subject matter experts, all with a compelling user experience. With OSLC we have been able to leverage the extensive capabilities and data across our products to provide consumable interfaces. These examples include storage management, application and infrastructure monitoring, and control desk solutions. With this architecture and these interfaces, users can easily access information across systems, using mobile access, and compose dashboards with the insights their businesses need.

What seems to be missing, however, is a less well-known, but arguably vital initiative known as the OASIS Cloud Application Management for Platforms (CAMP).  As expressed in its charter, 

CAMP defines interfaces for self-service provisioning, monitoring, and control. Based on REST, CAMP is expected to foster an ecosystem of common tools, plugins, libraries and frameworks, which will allow vendors to offer greater value-add.

That seems to be a logical addition to the effort by IBM. As important, perhaps, is the adoption and recognition of the LinkedData and OSLC work within the CAMP TC.  I know, after a number of informal conversations with participants in both OASIS TCs that the IBM emphasis has created new energy around OSLC for CAMP, and increased interest in seeing IBM attend to the work of CAMP.  

(Truth in advertising:  I am a participant in the CAMP Technical Committee and an observer in the TOSCA TC.)