The document summarizes a discussion on enterprise cloud computing that took place at the World Summit of Cloud Computing. It discusses three approaches that were proposed: [1] establishing a "standards body" to develop unified cloud interface standards, [2] adopting existing proven cloud technologies as standards, and [3] taking a "customer driven" approach where industry use cases define the standards. While each approach has benefits, a hybrid approach is suggested that incorporates elements of all three.

1. Enterprise Cloud Computing Session
at the
World Summit of Cloud Computing
KEVIN JACKSON
DIRECTOR, BUSINESS DEVELOPMENT

2. NCOIC-IGT quot;Enterprise Cloud Computing“ Session
 ~100 registered
 ~50 attendees
• Merrill Lynch, Ebay, Forrester, 451 Group, IBM, Amazon,
Gigaspaces, BMC, Open Group Forum
 Initial Topics
• Cloud Interoperability
• Cloud Standards
• Cloud Computing Reference Architecture (i.e. SOA-R)
• Forrester “Ultra Modular Computing”
• Cloud Computing Service Layers
• 2009 Events

3. www.Grid.org.il
The Clouds Space
SaaS
PaaS
IaaS
Cloud PC
(DaaS)
Enterprise External
IntraClouds InterClouds
Load Balancing of Cost/Performance
Cloud Computing: Pay-per-Use
for On-Demand Scalability

4. www.Grid.org.il
The Clouds Space
High Risk Data
Low Risk data
General Peak Time
R&D
Ad-hoc Projects
Enterprise External
IntraClouds InterClouds
Load Balancing of Cost/Performance
Cloud Computing: Pay-per-Use
for On-Demand Scalability

5. Ultra Modular Computing
• Like Cloud Computing, but deployed within the
Enterprise – and with some key differences
Applications
'Enterprise Enabling Software Layer(s)'
Commodit y hardware infrastructure
5 Entire contents © 2008 Forrester Research, Inc. All rights reserved.

6. UMC has potential to be hugely disruptive
• Possible combination of both Grid and Cloud Computing
technologies – but deployed within the Enterprise
• Exploits ultra low cost of commodity hardware
• Reduces cost to manage by 10x-100x
• Provides many of the business advantages of Cloud
Computing, but without several of the concerns
• Introduces an enterprise-specific asynchronous,
transaction-based, dynamic and scalable computing
environment
6 Entire contents © 2008 Forrester Research, Inc. All rights reserved.

7. How UMC will arrive …
• All Enterprises encounter ‘core decision events’ -when
an opportunity appears which provides the chance to
introduce major change
• UMC will exploit ‘thin end of the wedge’ adoption; can be
introduced gradually
• Main downside: most costs are up front in the initial
enterprise-specific software environment – but, once
done, scalability is there for the taking
7 Entire contents © 2008 Forrester Research, Inc. All rights reserved.

8. Key UMC decisions
• Should the UMC software environment:
» only look to the future (new application and
development models)
» enable existing application and development models,
and, possibly, operating systems
» both*
* This is the most expensive route
8 Entire contents © 2008 Forrester Research, Inc. All rights reserved.

9. “Standards Body” Approach
 Cloud Computing Interoperability Forum
 “Unified Cloud Interface” (aka broker)
 Implement as XMPP Extension Protocol (XEP)
 Address PaaS and IaaS
 Collaboration with OASIS, OMG, W3C, and OGF on Cloud Reference
Architecture
 “Global Socialization” through 2009 events
- NCOIC Enterprise Cloud Computing Working Groups
- Open Group 2009 Global Enterprise Cloud Computing Conferences
- CloudCamp
- ASD NII Cloud Computing Conference
- World Summit of Cloud Computing
 Internet Engineering Task Force (IETF) approval
 IEEE International Workshop on Cloud Computing

10. “Adopt Proven Technology” Approach
 General Disagreement with “Standards Body” approach
 External vs. Internal Cloud Competition
• Legacy applications to the cloud
o High value for Enterprise CIO
o Worst scenario for External cloud providers
• External cloud best practices (like EC2) result in Enterprise cloud implementation
and management applications and tools
• Internal metering vs. External implementation
o Lack of metering tools
o Lack of consistent metrics
o Inability to build Internal vs. External ROI
 Cloud Application definition
• Entire application in cloud,
• Single service in cloud
• Mashed-up services in cloud
• 3Tera Applogic “Automation Bundle”
 Adopt existing Cloud-VM standard
• Distributed Management Task Force - Open Virtualization Format (DMTF-OVF)
• Reservoir Project

11. “Customer Driven” Approach
 Technology doesn’t set standards. Industry use cases set the
standards
 Main Cloud Value = Reduced Cost
• Solid Cloud ROI model required
 Define Interoperability Requirements from Customer Viewpoint
• Disaster Recovery
o Between Enterprise and External Cloud
o Between External Clouds
 Customer Driven Standards & Interoperability
• Identify industry cloud needs via Web/Email Survey, Interviews, etc.
• Build Internal/External Cloud ROI models
• Large Industry Customers cooperatively drive cloud vendor standards
and interoperability through ability to deliver on Industry organization
cloud ROI models

12. Personal Observation
 Three distinct and valuable approaches
• Standards Body
• Adopt Proven Technology
• Customer Driven
 Issues
• Global agreement on standards could be a long process
• “Proven Technology” may mean “Proprietary Technology”
• Multiple industry customers could result in industry linked standards
for cloud
 Hybrid needed (Examples)
• Release “Proven Technology” to industry and adopt as basis for open
standard
• Multiple standards optimized for industry ROI models
• “Interoperability Rating “ issued after standards body technical review
 NCOIC engagement needed for any approach