CLOUD COMPUTING
The Business, Human and Technology Transformation
Kevin BackeRajan Palat
PAETEC
Changing the acquisition paradigm
• Traditional path of acquiring services/technology
– Driven by IT/IS Contributor or Organization
• Evaluate, Vendor Meet, Proposal, Justification, Business case, etc.
– To C Level
– To Board
• Cloud Computing
– Not just in trade rags, but Fortune, Wall Street Journal, New York Times, Business Week, etc
– More or as much defined by business benefits as technical capabilites
– Often topic initiated at Board/C/Senior Level and driven down
– Unique acquistion and adaption of technology– certain expectations have been set
• Turns paradigm on its head
– Asked to change something that has been built and layered on often times over years and iterations of employees
The Business Case
• Agility – speed to market
• Economies of scale
• Utility Pricing - Elasticity
• Storage and archiving
• Disaster Recover/Business Continuity
• Quickly adapt to client, vendor and business demand
• Operational Expense vs. Capitol Expense
• Need for Capital
• Green
• Focus on strategic enterprise expertise and growth
• Improved Utilization of resources - less underutilization
The Human Case
• Expectations
– Immediate Gratification
• On Demand, iTunes, Apps, Devices….storage and access
– Time is now clicks and buttons
– Get it now or somewhere else• Ease of finding options
• Need to meet
– Clients
– Vendors
– Employees
– They will no know other way
Cloud Questions
• Completeness of solution
• SLA’s for all aspects
• Billing and Disputes
• Flexibility and ease of transition if need be
– Could you be cut off from services?
• Controls and Parameters
– Utility billing could spiral
– Process to overide/expand
– Designed for efficiency and utilization
IT Challenges Driving Cloud
Discussions
Technology Business
Storage Growth
Continuous Availability
Mobility
Backup & Retention
Cost
Agility
Data Center Evolution
Centralized Decentralized Virtualized
Mainframe Client-Server and
Distributed computingService Oriented
InfrastructureOutsourcing
ManagedServices
VirtualizationPrivateCloud
PublicCloud
OutsourcingArrangements
Build It/ DIY IT
Cloud Computing(Infrastructure)
Current Hype SpectrumThe Past
IT Sourcing Model
IncreasingAgility
IncreasingAgility
TechnologyDisruption
Typical Cloud Options
Virtualized Data Center
(On-Premise)
Private Cloud
(On-Premise)
Public Cloud
(Off-Premise)
Cloud ServicesTraditional IT
• Single tenant • IT designed & operated • No delegation • No service catalog • Traditional IT delivery model • Very customizable • Lots of capex• Limited scalability
• Single tenant • IT designed & operated• Delegation• Service catalog • Internal SP model• Fairly customizable • Even more capex• Bounded scalability up, no
scalability down
• Multi tenant• SP designed & operated• Delegation through billing• Public service catalog only• New sourcing model• Not customizable • No capex• Dynamic scalability, at a
cost
The Gap
Private Cloud
On-Premise
Public Cloud
Off-Premise
Cloud Gap
• Complex to architect• Limited solution maturity• Expensive• Requires a DR solution• Requires culture of
standardization, automation, metering
• Doesn’t sound cloudy to business
• Complex to re-architect• Can’t replicate current
capabilities • Security • No service catalog • Forces culture of
standardization, automation, metering
• Sounds very cloudy to business
Support existing architectures
Enable new, dynamic model
Immediately available,
purchased as a service
Hybrid Cloud
Infrastructure
User Experience
Service
Catalog
Integration
with existing
assets
Extensibility
End to End
SLAs
Managed
Services GovernanceManagement
Storage Compute Backup Network
SecurityDMZs
Private WAN DLP
DPI
Private Line
VLANs
IDS/ IPS
Ethernet Private Line
Replication
Capabilities
LAN-like
Experience
WAN Acceleration
/ Optimization
APM
Monitoring
Tiering
Physical
VirtualFlash/ SSD
De-duplication
Local
Local
MPLS
Layer 2 Ext
Enterprise Capabilities
Policy Conformance
Performance
Most Data Centers are like a diamond…
Examine every facet
Network
Compute resourcesDisaster Recovery
StaffingSecurity
Storage
Environmental
Infrastructure
Applications
Considerations for a Cloud Migration
Application Mapping
- Avoid the „Hardware Trap‟
- Application Requirements
- Dependencies
- Storage
- Security
- Application Virtualization
Network Requirements
- Shift of bandwidth allocation
- VPN or MPLS requirements
- Redundant Connectivity
Business Continuity / Disaster Recovery
- Backups
- Geographic Diversity
- “Warm” or “Hot” Failover Site
- Virtualized Desktop Environments
Reclaim your budget
- Savings to be found in productivity
- Environmental Infrastructure
support
- Hardware maintenance
- Expansion no longer requires
CAPEX expenditure
- Resources can be rescaled and
re-cycled
Considerations for a Cloud Migration
Evaluate your cloud deployment strategy
- Public, Private, or Hybrid?
- Stay away from “One Cloud Fits All”
- Prepare your Disaster Recovery strategy at the outset
Evaluate Cloud Hosting Partners
- Do they meet your regulatory compliance requirements?
- What are their SLAs?
- Can they provide Network services in addition to compute
and storage resources?
- Do they have other services that can benefit your organization?
Identification and deprecation of unsupported applications
Deploy „low hanging fruit‟
Migration of complex applications
Make it a one-way street - Don‟t Look Back!
Thank You
The Business, Human and Technology Transformation
Kevin BackeRajan Palat
PAETEC