Data centres don't move to the cloud, applications do. In presentation, we use common sense, commercial triggers to move to the cloud and ask when does a move to cloud make sense and when it doesn't.
Following on, we will discuss in detail how an application CAN move to the cloud and when it should be shot to be put out of its misery.
We'll also talk about money - a LOT since someone has to pay for something. How does cost and complexity relate to cloud adoption planning? etc.
4. Principles
• Cloud is a methodology, not a destination
• Workplace Maturity and Operational Readiness are cloud
principle driven
• Cloud principles include elasticity and obfuscation of
service
• Change is required to adopt the new technology curve
• The required change can be measured and managed
• Continuous integration is a constant when adopting cloud
services
• There must be a higher benefit for being in cloud than
staying on-premises
5. Industry trends are creating new opportunities
New
apps
Device
proliferation
Data
explosion
Cloud
computing
Cyber threat
detection
6. Business events trigger opportunities to modernize
Reduce or eliminate expensive
datacenters, lower costs, and
explore new possibilities with
modernization.
Datacentre
consolidation
With the rise of modern threats, it is critical today to
apply the right level of security on your critical assets
and on the underlying infrastructure they are using.
Protect critical business assets
Out of capacity or contending with Shadow IT?
Remain relevant to business units by delivering new
cloud capabilities and value with speed and agility.
Business need for new capabilities
Without software updates, your
business can become vulnerable to
cybersecurity threats, might not
meet regulatory requirements, and
might be out of compliance.
Software end of
support
Rather than just renewing current
outsourcing contracts or on-
premises licenses, consider how
you can leap forward through
modernization.
Contracts, licenses
up for renewal
7. Datacenter consolidation
The desire to reduce or eliminate datacenters can be driven by
changing organizational goals or significant corporate events.
Reduce operational
expenses
Minimize your infrastructure
footprint through datacenter
closures or divestitures
Streamline business
processes
Integrate heterogeneous
infrastructure resulting
from acquisitions or
mergers
Gain efficiencies
Reduce application
redundancies and
minimize server
management
8. Cloud Services - Economics
• Capex vs Opex
• Elasticity and capacity on
demand
• Overflow on Demand
• Compute
• Storage
• Services
9. Business need for new capabilities
• Prepare for the pivotal moment when you need to react to
business demands or market conditions in days, not months.
12. Hybrid Cloud Services - Economics
•Capex vs Opex
•Elasticity and capacity on demand
•Overflow on Demand
• Compute
• Storage
• Services
•Transparent
• Shouldn’t need to know where on-
premises ends and cloud starts
14. Cloud Strategy Team
Microsoft Example:
•equivalent structure
to be documented
•Result
• Best Practices
• Dogfood adoption
• Feedback to business
15. Choosing a Framework
• What happens to existing EA frameworks? Zachman, Et
Al
• Open Datacentre Alliance (see image) vs Gartner vs
Other
16. SAAS before PAAS before IAAS
Base Principle:
• Application Migration
• Service Adoption
• Exception apply
• Exception Management
• If bad PAAS fit – build on
IAAS
17. Application Migration Friction
• Rated by RISK vs TIME TO DEPLOY
• Average weighting - Average Application adoption to
new platform
18. Basics for Datacenter migration newbies
• Requires Datacentre planning Disciplines
• Networking
• Subnet Planning
• Gateway Planning
• EXPRESSROUTE vs IPSEC
• Client Networking Considerations (browsing vs cloud
• Storage Planning
• Managed vs unmanaged storage
• Max # of VMs per storage account
• Licensing – BYO vs Metered
• DC vCPU core Limits
• VM Placements – DC locations
19. Example: IAAS Areas of Consideration
1. network, security and nxgen (load balancers, ip's,
ids, ip/subnet and routing, name resolution et al)
2. structure or microsegmentation
3. workload and class of service sizing, rto/rpo
criteria/selection/rules
4. crypto/encryption/certificates
5. management and reporting
6. maintenance and ops
7. onboarding/off boarding/decom and succession
8. development ops life cycle
9. content and data management, classification,
protection
10. SIEM /privacy /pci
management/control/enforcement
20. Tier 3 Application – MS reference Architecture
• HA within Region
• DR between Regions using
replication methods
• DR Test: Failover –
Depending on workload
22. Application Taxonomy
• Application Taxonomy derived from CMDB and other sources
• Application Taxonomy drives Migration:
• Start Here
• Quick Wins
• Long Term
• Pursue Later
• Retire!