Commentary

John Foley
Editor, InformationWeek  

IBM Turns To Cloud Management

Want a clue on what's next from IBM in cloud computing? Then take note that Dennis Quan, the guy behind IBM's cloud computing partnership with Google, recently moved into IBM Tivoli's development group. His new assignment tells a lot about the challenges IBM sees ahead.

Want a clue on what's next from IBM in cloud computing? Then take note that Dennis Quan, the guy behind IBM's cloud computing partnership with Google, recently moved into IBM Tivoli's development group. His new assignment tells a lot about the challenges IBM sees ahead.Quan is director of development in IBM's Autonomic Computing division. Autonomic computing refers to highly adaptive, self-managing distributed computing systems. In other words, it's got a lot in common with cloud computing, and Quan tells me that one of the things he's working on is aligning IBM's work in these two areas.

In his 10 years with IBM, Quan has had a hand in the company's most important data center initiatives. He helped create Blue Cloud, an ongoing effort to adapt software, hardware, and services to support cloud computing, and he recently served as CTO of IBM's High Performance On-Demand Solutions group.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Cloud computing may look and feel simple, but behind that ease of use lies data center complexity, and Quan is one of the computer scientists grappling with it. I asked him about IBM's cloud computing development work for the year ahead, and he focused on three things in particular -- security, service management, and standards.

Security comes up "all the time" in discussions with customers about cloud computing, so it's clear that security will continue to be a major issue, Quan says. He didn't provide details on what IBM will do in this area, but he did say that financial services companies, public agencies, and other large users want some level of "control" over systems in their cloud environment. That's vague, but remember that Quan now works in IBM's Tivoli systems management division. Look to IBM Tivoli to develop new capabilities that address cloud security by giving IT departments more control over the systems that house their data and applications.

Service management, including the ability to manage workloads among virtual servers, will be a second area of development. Quan talks of helping IT departments manage cloud services in hybrid environments comprised of public Web services and cloud-like services within their own data centers. IBM will address this requirement, in part, by injecting new capabilities into existing products, including its Tivoli Service Request Manager, Provisioning Manager, and Monitoring platform.

Standards are a third area of focus. The challenge here is to give IT folks a way to establish interoperability among cloud services from a variety of sources. "We're spending a lot of time in research and development looking at different ways to enable this," Quan says. Some of the work under way is related to SOA specs already in place. "We've got the ability to have services talk to one another in standards-compliant ways," says Quan. The next, and bigger, task is to "transplant" services from one cloud to another. "Those standards are in their infancy now," he says.

What about new cloud services from IBM? The company opened several cloud computing data centers this year, bringing the total to 13 centers, from which it offers Lotus Connections, its Bluehouse collaboration service (in beta), and, on a limited basis, some infrastructure as a service. Quan says it's reasonable to expect more cloud services from IBM Services, but he stopped short of promising anything along the lines of Amazon's EC2 or S3 services or Google's App Engine, where customers can dial up servers and storage in a few minutes with a credit cards.

For more on IBM's cloud computing strategy, see InformationWeek's Guide To Cloud Computing.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links