Cloud computing provides on-demand access to shared computing resources like networks, servers, storage, applications and services over the internet. It has evolved from earlier concepts like grid computing, web services, and virtualization. Key characteristics of cloud computing include shared resources that are scalable and elastic, self-service access, and pay-per-use metering. While cloud computing provides opportunities for cost savings and innovation, concerns around security, lock-in, and reliability must be addressed for widespread adoption. Standards and interoperability between cloud platforms are still developing.
2. What is Cloud Computing?
Some form of IT functionality on a service basis over the net
Clouds differ across two different axes
What services are offered, and in what form?
Where are the resources located, who else has access to them?
Essential characteristics
Shared resource, on-demand, elastic & scalable,
self-service, network access, usage-based metering
Your appraisal strongly depends on who you are
Startup vs. enterprise, application architect vs. business director, admin vs. user
On-demand IT, someone else’s equipment, self-service, pay-per-use
1 Copyright 2010 FUJITSU
3. Many Preceding Concepts [aka Evolution]
In 1960’s John McCarthy, a computer scientist,
brought up the idea that computation may
someday be organized as a public utility SaaS
Clouds
Virtualization
The idea faded by the mid-1970s as it became clear that the
Web services
technologies of the time were simply not ready
Grid
Since 2000, the idea has resurfaced in new forms
Grid computing enabled distributed computing and storage, using virtualized resources
Web services reduced data interchange costs between Internet-scale application services
Several concepts: on-demand computing, adaptive computing, dynamic data center, RTI
ASP, virtualization, Web 2.0 applications, mashups, Salesforce.com, Amazon
Some technologies behind clouds have existed in DCs over many years
2 Copyright 2010 FUJITSU
4. Value Propositions
Business delivery benefits come from the self-service
nature of cloud usage combined with improved resource
availability, efficiency & scalability
Infrastructure management benefits come from the added
efficiency of using shared resources, the opportunity to outsource
IT management tasks and the metered nature of cloud usage
Developer empowerment benefits come from the way
in which clouds empower developers to build and
experiment, speeding up IT cycle times
Benefits are greatly affected by the choice of cloud model
3 Copyright 2010 FUJITSU
5. Old Story, What’s new?
Evolution, not revolution Disruptive opportunities
Minimize costs, shared infra Do new things
Cooling Perform tasks not able to achieve otherwise
Electricity
Servers and storage New tools like Hadoop allows for amazing processing
Elasticity and scalability Speed up the organization
Massive scale Faster, cheaper innovation
Economies of scale Transform how one does business
Infrequent peaks
Capacity on demand Prototyping enablement
Ops cost reduction Publish databases
Flat data sets Reduce start-up
Streamlined data mgmt Work differently
Data availability
Real-time collaboration
DR cost reduction
Ubiquitous and unlimited computing power and
amount of storage
4 Copyright 2010 FUJITSU
6. Not a Technology Thing or an IT Issue Alone
Organizational changes
Sourcing and vendor management changes
Information governance concerns
Risk management and compliance issues
Business process and execution chances
Legal, HR, marketing & sales, R&D impacts
How an organization works with others
… and a technology, application, IT architecture thing as well
Getting into cloud computing requires some thinking to use it well
5 Copyright 2010 FUJITSU
7. Cloud Computing Approaches
Infrastructure services provide compute and storage building
blocks that can be molded to run different applications IaaS
Virtual machines User can choose how these resources are used
Platform services offer a ready built infrastructure and application
PaaS
frameworks that can be used for building and running applications
Programmable environment User writes his own applications to the given interface
Software services are applications or components that can be
SaaS
used as an end application or used as part of custom solution
No programmability User accesses and runs applications as provided
IT resources and/or application framework and/or applications
6 Copyright 2010 FUJITSU
8. Major Business Innovation Driver
Providers emerge from a broad set of market segments Innovate
“Your next competitor may not be born yet”
Enables entirely new business models
Opens access to new customer segments Differentiate
New application ventures are nearly always cloud-based
Makes companies partner across an ecosystem to expand their breadth
Cloud-based IT outsourcing and SaaS aggregators in partnership with business process
outsourcing and SaaS providers
Providers will deliver industry-specific business benefits through cloud
computing to help them innovate
Creates new services across almost all industries
7 Copyright 2010 FUJITSU
9. Models of Cloud Computing
The basic thre-layer model of
cloud computing
There are plenty of others
Opportunities exist at each
level of the stack
But none are necessarily right for
everyone
Data at every level of the stack
Becomes more important as the
stack commoditizes
Cloud help ease pain points, you need to know what yours are
8 Copyright 2010 FUJITSU
11. From Price Focused to Value Focused IaaS
Highly industrialized compute infrastructure service
Server capacity, storage capacity
Self-service, tiered SLAs, pay-per-use
Pre-defined catalog of infrastructure elements
Development server, live virtual server on shared/dedicated host
Block storage, file/IP storage, data protection/VTL, archive/ILM
Add-on and premium services
OS, application or DB provision and mgmt, additional firewalls
HA and DR options, LB, IPSEC VPN, MPLS mgmt, direct Internet
Application architecture services
Parallel database, content delivery network, messaging queues
10 Copyright 2010 FUJITSU
12. Next Generation IT Industry?
Machines or code?
Provider defined or Do-It-Yourself?
Next gen ISV?
On-demand applications
Next gen x86?
Machines on-demand
Next gen DCO?
Virtual datacenter on-demand
Next gen SI?
Building/integrating apps on-demand
11 Copyright 2010 FUJITSU
13. Cloud Computing Stack and Layers
Software as a Service
•Core collaboration, CRM/ERP/HR, industry application
User subscription administration
•Hosted custom applications, ecosystem applications,
business processes
•Multi-tenancy operating environment, data, metadata
Self-service catalogue
•Business process management
Security, role and access control
Platform as a Service
•Web 2.0 application runtime, application servers
Policy enforcement
•Development tooling, APIs, mashup center, forms
•Middleware, ESB, adaptors, directory
•Database, data model extensions
Metering, billing and charge-backs
•Queue service, integration layer (cloud/on-premise)
Usage reporting & auditing
Infrastructure as a Service
•Scalable computer farms, storage, networking Service-level dashboard
•Image catalog, management portal
•Llogical virtual systems, dynamic provisioning
•Resource pooling, shared, virtualized Consolidated license management
•Automation, monitoring, HA/DR
Implied hierarchy, however this is not always the model for deployment
12 Copyright 2010 FUJITSU
14. Emerging Trusted and Private Clouds
Public
Mega clouds
Trusted clouds
Private clouds
Known trust boundaries, qualified services and policies, SLAs,…
13 Copyright 2009 FUJITSU
15. Deployment Types
• Cloud-like service owned and managed (unless out-tasked) by single consuming enterprise
for its own internal use
Private cloud • Internal cloud if located on-premise, private/trusted if hosted off-premise
• Promoted by key virtualization and storage vendors
• Drives efficiency, standardization and best practice across an organization
• IT resources and services are owned and managed by an external provider, located off-
premise, sold to and made available as metered services to public
Public cloud • Deliver a standard set of business processes, applications, or infrastructure services
• Offer capital preservation, flexibility and rapid time to market for new applications
Hybrid cloud • A combination of two or more clouds, also with in-house systems
• IT resources and services are operated on behalf of a community of organizations
Community cloud • Options for a group of partners wanting to share IT costs and improve efficiency
• Access is restricted to specific community members
14 Copyright 2010 FUJITSU
16. Mixture and Composition of Enterprise IT
Capacity
Trusted cloud
Public (off-premise) Private cloud
cloud
(off-premise) Costs
Off-premise
On-premise
Sharing
Private cloud
Private cloud (on-premise)
(on-premise)
Flexibility
Federation of cloud services is an enterprise system integration job
15 Copyright 2009 FUJITSU
17. Required Capabilities
End-to-end architecture to gain strong economies of Cap/OpEx
16 Copyright 2009 FUJITSU
18. Causes of Concern
SECURITY:
Can I safely put corporate data outside my firewall?
BORDER CONTROLS:
How do I ensure my data stays where it needs to be?
LOCK-IN:
Will I be able to move my data and applications if I decide to move?
17 Copyright 2010 FUJITSU
19. Services are Important
79% want assistance
Based on interviews with senior management
of 35 major UK customers, September 2009
18 Copyright 2010 FUJITSU
20. Application and Workload with Interesting Fit
Test and pre-production systems
Non-business critical applications like collaboration
Software development environments
Batch processing jobs and highly parallelized workloads
Very large-scale data analytics, data sets and number crunching
Isolated workloads where latency between components is not an issue
Data intensive workloads when storage is tied to compute cloud
New web application architectures with minimal DB tiers
Modular mashups and web applications with loosely coupled services
A strong case for pilots, experiments, once in a while jobs, startups etc.
19 Copyright 2010 FUJITSU
21. Application and Workload with Challenges
Highly sensitive data workloads (e.g. employee and health care records)
Multiple, co-dependent services (e.g. high throughput OLTP)
Workloads requiring a high level of auditability or accountability (e.g. SOX)
3rd party software which does not have a
virtualization or cloud aware licensing strategy
Applications that require strong integration
with on-premise systems
These will await for clouds to become more trusted and mature
20 Copyright 2010 FUJITSU
22. Example of Cloud Usage
Amazon CapEx and OpEx savings
Fullfillment BPaaS
Business Web Service pale in comparison to the
users Salesforce.com potential agility and new
BPOS-D
SpringCM
SaaS capability benefits
enabled by cloud
Application Force.com
Appistry PaaS
developers Bungee Labs
IT admins Terremark Amazon EC2/S3 IaaS
Private Public
Different parts of an organization use clouds for different needs
21 Copyright 2010 FUJITSU
23. How to get into a cloud?
Port to VM/AMI: machine-centric
Run machines in the cloud with traditional config
Cost savings, but no network effects
Port the code: tweak few functions
Copy your code to the cloud, limited portability
Rewrite the code: build from scratch
Rearchitect the app, costly
Rewrite the process: workflow in cloud
Re-create the process
Copy the content: switch to their app
Just use their application, be sure you have SLAs & can leave
22 Copyright 2010 FUJITSU
24. Impact on Your Data Architecture
Proximity matters
Connect time to a single hosted site
increases with distance
Compared to the cost of moving bytes
around, everything else is effectively free
Global cloud providers are present in all continents
Several compute locations
Replication of (static) data
Apps duplication over a large distance
Local data security laws entail multilocation data centers
He who owns the storage, owns the computation
23 Copyright 2010 FUJITSU
25. 2010 is Still Era Before Interoperability
Multiple providers
Getting started in the cloud is fast,
cheap, and easy Dynamic federation
Workload mobility
Data retention
Application portability
Distributed storage
Service integration
Placement interoperability
Trust boundaries
The longer you're there, the Network model
harder it is to move
Switching costs
Cloud as of today = subscriber sandboxing
24 Copyright 2010 FUJITSU
26. Inhibitors to Cloud Computing
Security… sending data outside firewalls
Privacy… all identities are remote
Platform dependency… lock-in, lack of standards
Reliability… outages
Portability… migration and switching costs
Physical location… different jurisdictions
Speed.. application latency
Trustworthiness… of cloud service provider
Interoperability… data and application integration
Technology and business model inhibitors + legal and security issues
25 Copyright 2009 FUJITSU
27. Don’t Get Married to One Vendor’s Platform
Ability to move data, applications, and
Portability
virtual servers from one cloud ‘gotchas’
computing environment to another
Ability to mix & match cloud services,
depending on business need
Cloud provider might fail
Ability to blend public and private
cloud environments into hybrids
Ability to develop to and manage
cloud services via APIs
What if the cloud dumps you?
26 Copyright 2010 FUJITSU
28. Focus on Concrete Issues Before They Hit
How much of interoperability is standards and architecture, and how much
is throwing software engineers and months at the problem?
Do you need to port or rewrite them?
Platform war in the cloud
How do you integrate new sites into the fold? computing space
Can you load your DB into the cloud, or have to use Hadoop?
Off-the-shelf vs. Custom integration
Did you roll your own?
Do you regret it?
Migration of full application
configurations across clouds
Getting in the box is not same as getting out of the box
27 Copyright 2010 FUJITSU
29. Key Active Industry Groups
Distributed Management Task Force/Open Cloud Standards Incubator group Fujitsu is
"Interoperable Clouds - A White Paper from the Open Cloud Standards Incubator“ Nov. 11, 2009 Board Member of
Fujitsu and three other companies have submitted their own IaaS technologies for standardization work
Will create two working groups in June: Infrastructure + Security group & Use case + Data Artifact group
Open Grid Forum/Open Cloud Computing Interface Working Group Fujitsu is in
Board of Directors of
“Requirements and Use Cases for a Cloud API” as informational document on Jan. 14, 2010
Four other documents about IaaS interface entered public comment period until March 15, 2010
Storage Network Industry Association/Cloud Storage Technical Work Group
“Cloud Data Management Interface” published and entered public comment period on Feb. 9, 2010 Fujitsu is in
Combination of SNIA CDMI and OGF OCCi will be demonstrated at OGF29 on June 20-22 Board of Directors of
Cloud Security Alliance
2nd version of “Security Guidance for Critical Areas of Focus in Cloud Computing” Dec. 17, 2009
28 Copyright 2010 FUJITSU
30. DMTF
OVF: First Industry Standard Cloud Workload
September 2009 vCloud API Submitted
November 2009 Fujitsu Submits its Cloud API
VMware and Fujitsu both very active on developing standard APIs
29 Copyright 2010 FUJITSU
31. What Cloud Means to Fujitsu
Fujitsu defines a Cloud Service as the consumption of infrastructure,
an application, an activity or content where that consumption has three
distinct characteristics:
Pay per use
Elastic and Scalable
Self Service
A new set of choices for IT and business leaders
30 Copyright 2010 FUJITSU
32. Our Vision: Cloud at YOUR Pace
MODE 1 Infrastructure as a Service
Compute, storage and network move to a subscription model
MODE 2 Application as a Service
Applications move to a subscription model, reducing
technology footprint
MODE 3 Activity as a Service
Customers subscribe to business services, specified in
business not technology terms
MODE 4 Content as a Service
Customers subscribe to brokered business services
integrated by service suppliers at a price and quality
determined by business value
31 Copyright 2010 FUJITSU
33. Towards the Networked Society...
New ways of using IT and in areas where it has not been applied before
32 Copyright 2010 FUJITSU
34. Smart Clouds and New Markets
Infrastructure and Activity and content
application clouds are modes of clouds will
aimed at existing exploit new markets
enterprise markets
Linking people with information systems to create new value from IT
33 Copyright 2010 FUJITSU
35. Our Value Proposition
Evolution not revolution
A safe and low risk journey
Flexibility and responsiveness
Sense and respond is our key global value
Our experience and heritage
Telecoms, networks, computing and services
Low energy, low carbon Security
Leveraging our R&D investments Addressing the main concern of our customers
34 Copyright 2010 FUJITSU
38. Our Approach to Cloud Services
A single point of customer interaction for the provision and coordination of
any type of Cloud Service
A comprehensive range of enablement services to effectively prepare and
transition customers to any Cloud Service
A depth of capability and
services providing access
the vast range of
Cloud Services
37 Copyright 2010 FUJITSU
40. Target Markets
EXISTING MARKETS
Existing technology services, delivered from the Cloud
Traditional customer base – medium sized (>100 employees) and large
customers (>1,000 employees)
NEW MARKETS
New applications for technology – the networked society, the whole of society
Delivered in the context of new business models
39 Copyright 2010 FUJITSU
41. Summary
Clouds will over time change the way IT is bought and used
There will be many clouds, public and private
New business and commercial models
The enterprise will consume various services from the cloud
However for many years they will continue with the traditional model as well
Cloud creates new services integration opportunities
Customers will only use trusted suppliers for this work
For large customers the adoption of cloud services will be an evolution
In addition to CIOs, business leaders will become active in the procurement of services
40 Copyright 2010 FUJITSU