View
605
Download
1
Category
Preview:
DESCRIPTION
This lecture was given by Professor June Sung Park at Korea Advanced Institute of Science and Technology in the 2012 Cloud Conference held in August 2012 by Electronic Times in Korea.
Citation preview
Prof. June Sung Park
KAIST
Agenda
Cloud Computing: Disruptive or Sustaining?
Supplier
Diversification of Architecture and Delivery Model
Supplier
Competency-Based, Agile / Lean Process for Cloud Business Development
Supplier
Options for Cloud Migration
Consumer
Cloud Adoption Process Standardization
Consumer
3
IaaS: Disruptive Business Model / Fusion of State-of-Art Technologies
Infrastructure as a Service Web Services Automated ITSM over Virtualization 1 to Global, “Swipe and Start”,
“Pay as You Go” Service Built-In Monetization Functions
Infrastructure Utility Service Sharing Virtualized Infrastructure Fully-Implemented ITIL 1 to 1 Contract
4
Infrastructure Outsourcing Service
Externalization SLA
Software as a Service Single Code Base in Multitenant
Architecture Frequent Upgrade Automated ITSM over Virtualization Usage Fee Built-In Monetization Functions 1 to Global
Vendor-Managed Software Packaged App Hosted by Vendor License Fee +
Maintenance/Hosting Fee
SaaS: Disruptive Business Model / Disruptive Technology
5
Packaged Software
Single Code Base (Grey-Box) Single Tenant Upgrade and Distribution
ASP
Packaged App Hosted by a 3rd Party
Usage Fee
Architectures and Delivery Models – IaaS
6
Architectures and Delivery Models - SaaS
7
How to Avoid Cloud Com Crash? Extend your Current Capability and Asset
Cloud Service/Product Providers
P
I I I
P
A
I
P
A
I
P
A
I
P
IaaS PaaS SaaS
I
IU
A
VMS
Cloud Service Brokerage
Cloud Service Aggregation
Cloud Service Intermediation
Managed Cloud Service Cloud Consulting
Cloud Service Marketplace
Cloud Service Implementation
Cloud Service Management Platform
BSS OSS
Cloud Service Consumers
P A C
A A C C
SAP Oracle
IBM AT&T
Amazon Rackspace IBM eVapt
BMC CloudSwitch
Google Salesforce
Microsoft CloudFoundry
Accenture Appirio
8
How to Avoid Cloud Com Crash? Understand the whole Value Chain Build the Positive Feedback effect in collaboration with upstream
Platform vendors and downstream Complementors
Cloud Service Infrastructure &
Offering
Cloud Service Marketing and
Sales
Cloud Service Assurance &
Billing
Cloud Acquisition and Implementation
Cloud Operation
Cloud Architecture
Cloud Service Value Chain
Cloud Service Strategy
Provider
Cloud Requirement
Consumer
9
How to Avoid Cloud Com Crash? Build New Skills
Cloud Service Strategy
Cloud Requirement
Business/IT Strategy Planning BPM
Cloud Service Infrastructure &
Offering
Cloud Architecture
Virtualization App Platform Agile Process / XP SOA / WOA Multitenant Architecture WAN optimization
EA SOA/WOA MDM
Cloud Service Marketing and Sales
Cloud Acquisition and Implementation
Service Packaging/ Pricing/SLA Web Marketing Self-Service Portal Real-Time Provisioning
Cloud Acquisition Policy Fit/Gap Analysis Cost/Benefit Analysis App Composition Eng.
Cloud Service Assurance & Billing
Cloud Operation
Monitoring Metering Billing & Payment ITIL Security
ITIL Performance Monitoring
10
How to Avoid Cloud Com Crash? Adopt Iterative Customer Development Process
Customer Discovery
Customer Validation
Customer Creation
Company Building
Founded in April 2004. Now has the world’s largest virtual
goods catalog of 100M+ items created by 50M+ members.
Followed customer development process
Leveraged cloud services; no press release at launch; charged from Day 1.
Using agile process and XP, shipped in 6 months and ships 20 times a day.
11
Cloud-in-a-box, providing prepackaged Integrated cloud stacks, available from several vendors.
An optimal approach is to decide what apps or user groups are appropriate for a private cloud, and what for a public cloud, considering security, compliance, accountability, availability, etc.
Both internal and external cloud services should support the basic properties of cloud, i.e., virtualization, multitenancy, service catalog, service portal, automated provisioning, elasticity, metering and billing, etc.
12
Cloud Migration Options – Hyper-Hybrid Approach
Refactor
Replace
How to Migrate Apps to Cloud?
Rehost
Revise Rebuild Apps Redesigned for PaaS EA / SOA transformation followed by Rehost or Refactor
Apps Rebuilt on PaaS Abandon code, Keep functionality, Standardize silos
Apps Moved to PaaS Adapt code
Replace Apps by SaaS Standardize silos, Adapt to better functionality
Apps Moved to IaaS Keep code, Re-platform from Unix to Linux, Choose an optimal IaaS architecture
13
Cloud Adoption Process
Describe As-Is Enterprise
Architecture
Select Architectural Components
Develop Business
Case
Create Req’t Spec and Test Plan and
Move to Cloud
Define business process, data and se
rvice models
Scan and catalog cloud services;
Match candidate components with candidate clouds;
Do fit/gap analysis
Define project scope; Estimate cost/benefit of cloud adoption
Develop use cases, test cases and NFQ
requirements; Construct a pilot system; Roll out
14
Questions
june.park@kaist.ac.kr
15
Recommended