Transcript Cloud Adoption Framework - Applied Information Sciences

Cloud Adoption Framework
Cloud Adoption Framework
2 | © 2016 Applied Information Sciences, Inc.
www.AISTeam.com
Step 1: Education & Training
• Know why you are moving to the cloud
• Starting with a deeper understanding of the benefits of the cloud (IaaS, PaaS, SaaS)
• Agility, cost, time to value, data growth, capacity, security
• Deep dive training
Day 1
Day 2
Day 3
Day 4
Sample agenda 
Azure Platform Overview (IaaS, PaaS, SaaS)
“Azure Networking Deep Dive”
Azure AD
Topology
Introduction to Azure IaaS w/ key concepts
Endpoints and Endpoint based ACLs
AD Federation
Subscription Management
VNET, Subnets
AD Security protocols
Network design
VNET - V2
StorSimple
Automation strategy
NSG
RBAC
Egress
HA/ DR – Site
Recovery
3 | © 2017 Applied Information Sciences, Inc.
Azure Portal
Compute and Storage
Licensing, Pricing
VMs (available images)
VHDs, Disks and Images
Virtual Networks (VNET)
Availability Sets
Express Route
Power Shell / REST API / Cross-plat CLI
Site to Site / Point to Site VPN
Azure Automation Service
Forced Tunneling
(VMs, storage)
Security Appliances
VM Extensions
VIPs DIPs
Monitoring
ILB
Resource Groups & ARM
Floating IP Address
www.AISTeam.com
Step 2: Azure Architecture & Governance
Develop a cloud architecture and governance strategy
• Network & Network Security
• Firewalls, Load Balancing, NSGs, User Defined Routing
• Subscription Topology
• Azure Regions, Security Zoning, Billing and Chargeback, Naming Conventions
• Automation
• Templates, Process, Scripts, Resource Catalog
• System Health
• Monitoring, Logging, Auditing
• Access & Resources
• RBAC, Resource Manager Policies, Resource Locking, Resource Management Roles and
Responsibilities
• Security Monitoring, Health Detection
• Support, Escalation and Incident Management
4 | © 2017 Applied Information Sciences, Inc.
www.AISTeam.com
Step 3: Base Infrastructure Build
• Express Route
• VNet Setup
• Configure Edge Firewall
• Set up Peering (Public/Private)
• Configure Load Balancing
• Setup RBAC
• Automate Build
• Deploy Subscription Topology
• Documentation
5 | © 2017 Applied Information Sciences, Inc.
www.AISTeam.com
Step 4: Application Portfolio Assessment
Conduct an Application Portfolio Assessment
• Which applications make sense to move to the cloud?
• Develop a long term roadmap that is aligned with the cloud
provider’s roadmap
• Start with a small app
• Startup /agile mindset
6 | © 2017 Applied Information Sciences, Inc.
www.AISTeam.com
Step 5: Application Migration Assessment
• Requirements Gathering
• Inventory of the components and services
• Assessment of migration strategy (what Azure resources are
appropriate?)
• Create and Deliver Migration Design Document
7 | © 2017 Applied Information Sciences, Inc.
www.AISTeam.com
Step 6: Application Onboarding
• Involvement from multiple teams
• Project to migrate each application
• Initiate / Plan / Execute / Close
• Cloud Service Provisioning team executes
requirements to migrate application
• Redesign and rebuild as necessary
•
Client
AIS
Key Stakeholders
Cloud Service
Provisioning Team
Application
Support Team
Operations and
Support Team
Cyber Security
Team
Core Cloud
Infrastructure and
Network Team
Performance, scalability, security
• Perform migration and optimize for cloud
• Operations & Support Handoff
• Provide documentation, training, monitoring
metrics to Operations & Support Team
• Support Staffing adjusted as needed
8 | © 2017 Applied Information Sciences, Inc.
www.AISTeam.com
Step 7: AIS Cloud Support Services
Cloud Support Teams
• Operations and Maintenance
• Monitor system health and performance
Application
Migration
• Respond to incident requests
• Core Cloud Infrastructure and
Networking
• Infrastructure build-out and support
• Networking architecture
• Cloud Service Provisioning Team
• Migrate applications
Infrastructure
and
Networking
Monitoring and
Support
• Manage Service Catalog
9 | © 2017 Applied Information Sciences, Inc.
www.AISTeam.com
Step 7: AIS Cloud Support Services (continued)
Support Process
Team becomes aware of
needed support
• Two options for support:
• Business Hours + On Call
• 365 x 24 hr
Acknowledge and triage
Escalate and handoff to
appropriate support team(s)
L2 Support
L3 Support
Core Cloud Infrastructure
and Network Team
• SLA – defined priority and
response time
Metrics tracking and
reporting
• Team size and makeup
based on need; scales up or
down accordingly
10 | © 2017 Applied Information Sciences, Inc.
Continuous process
improvement
L2 Support
L3 Support
Cloud Service Provisioning
Team
Operations and
Maintenance Team
www.AISTeam.com