Cloud+ Mod03 - FINAL

Module 3
Migration to the Cloud
West, MindTap for CompTIA Cloud+ Guide to Cloud Computing, 1st Edition. © 2021 Cengage. All Rights
Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in
part.
Overview (1 of 3)
• In this module, you will learn how to:

• Describe the phases of cloud migration.
• Assess the characteristics of a cloud migration to determine
cloud fit.
• Analyze system requirements for a planned migration.
• Determine the appropriate migration strategy for a specific
workload.
• Evaluate environmental constraints that affect the timing of a
cloud migration.
• Analyze how documentation affects a cloud migration.
part.
Overview (2 of 3)
• In this module, you will learn how to: (cont’d)

• Employ change management procedures for migrating to the
cloud.
• Evaluate the options and benefits of automation during
migration.
• Evaluate data transfer options.
• Consider the specific requirements of storage migration.
• Analyze system requirements to develop a testing plan.
• Determine validation standards for a testing plan.
part.
Overview (3 of 3)
• In this module, you will learn how to: (cont’d)

• Anticipate and prepare for common deployment issues.
• Install and use cloud CLIs.
• Apply project management principles to cloud migration.
• Apply DevOps principles to managing a cloud deployment.
part.
Module 3 Scenario (1 of 2)
• Private school migrating VM services to cloud

• VM characteristics
• Machine within a physical machine
• Shares resources with other VMs
• Is its own system
• Requires right file type or conversion to migrate
• VMs require correct network settings and resource connections
• Resources must be accessible or in cloud
• Other environments exist: container and stand-alone service
• Migration process could take months or even years
part.
Module 3 Scenario (2 of 2)
• Action list questions

• How do we decide which cloud provider is the best fit for us?
• What should we move to the cloud first?
• What’s the cheapest way to move a large database to the
cloud?
• How will this migration affect applications we have and need?
part.
Migration Planning (1 of 17)
Figure 3-1 The five phases of cloud

migration.
West, MindTap for CompTIA Cloud+ Guide to Cloud Computing, 1st Edition. © 2021 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
• Cloud migration phases

• Performed in layers: simple to complex
• Reasons to revisit each migration phase repeatedly:
• Cloud provider no longer meets needs
• Choose to extend the scope of deployment
• Accelerating growth of cloud technologies
• Fluctuating prices for services
• Constant demand for quality improvement
part.
• Transition assessment
• Considerations
• Overall performance
• Legacy software compatibility
• Latency interference: most cited reason for return to company data
center
• Thorough research and testing required before migration
• Avoids moving workloads to the cloud that do not belong there
part.
• Transition assessment (cont’d)

• Decisions
• Which cloud is the best fit for your needs?
• What are the needs or the focus?
• Will existing applications and processes work well in the cloud?
• What new skills are needed?
• What are the costs (hidden and up-front)?
• Who will be the migration champion?
• Considering these questions takes time in the initial phase
• Guard against analysis paralysis
part.
• Migration plan
• Planning stage: most challenging cloud migration phase
• Well-laid-out plan ensures:
• Migration proceeds smoothly
• End result meets the organization’s goals
• Plan considerations:
• Type of migration being undertaken
• Whether data, databases, applications, or network function will be
moved
part.
• Migration plan (cont’d)

• Baseline
• Collect thorough baselines before beginning any transition
• Collect information on KPIs (key performance indicators)
• Business continuity
• Consider effects of any anticipated downtime
• Consider how to minimize or avoid downtime
• Consider user training that can be performed before migration occurs
• Consider temporarily increasing service desk staff hours immediately
following the transition
part.

• Existing systems
• Thoroughly understand and document existing systems affected by the
cloud migration.
• Use a dependency diagram to show which components rely on which
other components
• Include a discovery process to identify so-called shadow IT
• Target hosts
• Configure target host carefully to match needs and anticipated growth
of transitioned resources
part.

• Legal restrictions
• Countries and states have different laws for data protection
• Must be aware before signing a contract
• Limitations on what software can run on machines hosted in particular
countries exist
• Organization needs formal process for evaluating contracts before
signing them and ensuring that both legal and IT experts weigh in on
the terms of the agreement
part.

• Cloud architecture
• Overall cloud architecture includes the interfaces between elements,
the networking architecture that manages the interfaces, and the
connections to your on-prem data center or users
• Provide appropriate structure in your target cloud for the resources
and workloads it will support
• Order of operations
• Start with easy application, simple and well defined without a lot of
interdependencies on other systems
• Start with low-priority resource
part.

• Continue to fine-tune migration plan as migration proceeds
• Revisit migration plan after migration is complete
• Document process
• Use information to create standard operating procedures (SOPs) for
workload migration
• SOPs
• Ensure consistent performance across multiple migrations and staff
members
• Used as a starting point for automating parts of the migration process
part.
• Migration strategies
• Organizations have unique approaches to cloud migration
• Rehost (lift-and-shift or forklift)
• Move application or data into the cloud as it is
• Disadvantage: weaknesses of resource retained
• Advantage: transition speed and cost savings
• Revise or replatform
• Make some relatively minor changes to application or data before
moving to the cloud
• Refactor, rearchitect, or rebuild
• Changes are more significant
part.
• Migration strategies (cont’d)

• Repurchase or replace
• Replacing product with an existing cloud-native product
• Can be a quick, easy, and inexpensive solution
• Retire
• Low-complexity strategy
• Organization stops using the application or data
• Retain (do-nothing option)
• Low-complexity strategy
• Organization keeps using an application or data as is
part.
Figure 3-2 Cloud migration strategies.
• Migration strategies (cont’d)

• Consider several factors from business and technical
perspective
• Does the application generate income?
• Justifies greater financial investment in adapting it for migration
• Does it support ongoing business processes?
• Is app compatible with a cloud environment?
• Can it easily be adapted to the cloud?
• Is it too old or does it have dependencies too complex to be moved?
• App may need to stay where it is or be replaced entirely
part.
• Timing
• Consider timing of actual workload migration
• Environmental constraints require careful scheduling
• Impact of downtime
• Downtime allowed might fluctuate in balance with other factors
• Work hour restrictions
• Schedule anticipated downtime to avoid normal user work hours
• Consider unique schedules kept by your organization
part.
• Timing (cont’d)
• Time zones
• Varying time zones impact planned migration schedule
• Follow the sun (FTS) – hand off work to others in another time zone
• FTS works in reverse when making major changes to an organization’s
data center resources
• Peak time frames and costs
• Time and money invested not constant from beginning to end
• Anticipate that demand will follow a bell-shaped curve
part.
Figure 3-3 Time and money

resources are most in demand in
the middle of the migration process.
Migration Execution (1 of 10)
• Migration documentation
• Easy to forget a small step that can fail the entire migration
• Refer to documentation frequently
• Follow standard operating procedures for your organization
• Factor in documentation and guidelines from the CSP
• Use commands and tools as needed
• Network connectivity commands, automation scripts, or migration tools
from CSPs or third-party vendors
• Document changes to network resources
• Follow formal, documented business processes
part.
• Change management
• Theoretical models guide change management process
• ITIL (IT Infrastructure Library)
• Collection of publications defining best practices in IT
• Models typically follow basic set of steps
• Define change, consider implications, implement change, evaluate
outcome
• Many models emphasize the human factor
• Invite user input
• Help affected users understand the need for change
• Ensure user acceptance before change is implemented
part.
• Change management (cont’d)

• Typical change management process highlights
• Change request
• Change assessment
• Change implementation
• Change review
• Change documentation
part.
• Deployment automation
• Workflow
• Steps of a process (typically an automated process)
• Automation
• Using technology to perform a process or procedure with minimal
human intervention
• Reduces overall migration time and cost and potential for mistakes
• Affects efficiency of sync between source and target hosts (delta)
• Orchestration
• Configuring automated processes ahead of time
• Design, development, and optimization of automation processes
part.
Figure 3-4 A simple workflow for

handling spam calls.
• Data transfer
• Methodology selected based on amount of data being migrated and
how quickly
• Public Internet
• Online transfers over the public Internet
• Support small or slow data migrations
• Private connection
• Online transfers over a private connection
• More dedicated bandwidth, cutting upload to a fraction of public Internet
• Requires long-term contract with an ISP and paying for direct connection into
CSP’s POP (Point of Presence)
• Can result in cloud platform lock-in
part.
• Data transfer (cont’d)

• Offline transfer
• Load encrypted data onto storage appliance
• Appliance physically shipped to CSP
• CSP uploads data to cloud
• Client configures data as needed
part.
Figure 3-5 Snowmobile can transfer up to 100 PB per trip.
• Storage migration
• Process of moving data blocks or volumes from one storage
medium to another
• Data itself typically not changed
• Streamlining
• Remove unneeded data before beginning any migration
• Capacity
• Provision sufficient space for existing data and anticipated growth
• Migration path
• Determine how to transfer data from old location to new one
part.
• Storage migration (cont’d)

• Security
• Protect data in transit to the new storage location
• Plan for data protection once it is in place
• Scheduling
• Make taking system offline during migration least disruptive to users
• Online migration keeps system running during migration
• Offline migration takes system down during migration
• Rollback plan
• Have plan ready before starting migration
part.
Deployment Testing and Validation (1 of 5)
• Testing types
• Performance testing
• Challenge system to determine its responsiveness and stability under
various conditions
• Checks for compatibility issues
• Load testing
• Push system beyond normal workload conditions
• Determine how system adapts to higher demands
• Done manually or automatically (often involves both methods)
• Data collected inform auto-scaling threshold configurations
part.
• Testing types (cont’d)

• Security testing
• Vulnerability testing identifies system’s security weaknesses
• Penetration testing attempts to take advantage of vulnerabilities
• CSPs offer testing tools optimized for their platforms
• User acceptance testing (UAT) or user acceptance training
• Testing requiring help from users most familiar with resources
• Coordinate testing so migration team members can process feedback
part.
• Testing considerations
• Components and characteristics to validate before going live
• Proper functionality
• Everything works as it should
• Data integrity
• Migrated data accurate
• Connectivity
• Quality of connections good
• Network latency: a big obstacle to a well-functioning cloud
part.
• Testing considerations (cont’d)

• Availability
• Test redundancies belonging to high availability (HA) plan
• Security
• Data adequately encrypted both at rest and in transit
• Virtual firewall configurations
• Authentication and access control mechanisms functioning properly
• Sizing
• Physical hardware supporting cloud sized appropriately
• Monitoring
• All services working as expected
part.
• Test analysis
• Anticipate how to analyze test plan results
• Compare results to various documents
• Change management documentation
• Service level agreement (SLA): identifies minimum performance
benchmarks and maximum downtimes for specific services
• Baselines collected before migration began containing KPIs
• Confirm auditing enabled so logs properly collected
• Use management tools to send live data feeds to a dashboard
part.
Troubleshooting the Deployment (1 of 9)
• Common deployment issues

• Resource contention
• Benchmark test before and during migration to minimize issue
• Template misconfiguration
• Use tools to monitor and audit server configurations
• Use regular configuration audits after migration
• CSP outage (rare)
• Implement redundancies across platforms
• Store backups in a separate location from the primary CSP
part.
• Common deployment issues (cont’d)

• Platform integration issue
• Reliance of cloud services on APIs helps open up communication between
platforms
• Ensure proper staff training
• Licensing outage
• Use software license management (SLM) to minimize expenses
• Use a central repository for license documents and receipts
• Set reminders to renew and pay
• Time synchronization issue
• Earth’s rate of rotation causes leap second to be added
• Offset with CSPs time service
part.
• Cloud CLIs
• Graphical user interface (GUI) console beginner tool
• Presents information from a system
• Accepts commands from a user
• Dashboard beginner tool
• Graphical layout of KPIs and command functions
• Allows for quick review of and response to a system’s state
• Command-line interface (CLI) advanced tool
• Offered by all major CSPs (AWS, Azure, and GCP)
• Can create scripts for automating deployments and other tasks
part.
• Cloud CLIs (cont’d)

• AWS CLI
• Interact with AWS services using local computer’s command-line shell
• Perform AWS Management Console tasks through a browser
• Interacts with AWS’s public APIs and account credentials stored on
computer
• Installed on Windows, Linux, macOS, and Unix computers
• Relies on TCP port 443
part.

• AWS CLI (cont’d)
• Download AWS CLI installation package
• Windows computer: MSI installation package
• Linux, macOS, and Unix: AWS CLI Bundled Installer
• Python: pip package manager
• Configure AWS CLI using configure command
• Use AWS CLI’s command syntax
part.

• Azure CLI
• Run in the Azure Cloud Shell in a browser or download and install the
Azure CLI for use through a computer’s CLI
• Launch Cloud Shell from the portal
• Choose a subscription to associate the session with
• Start all Azure CLI commands with the base call az
part.
Figure 3-6 Use the Azure Cloud Shell directly in your browser.

• GCP CLIs
• gcloud – Allows interaction with GCP services through local computer’s
command-line shell
• gsutil – Manages Google Cloud Storage
• bq – Manages Google BigQuery, a data analytics service operating in
conjunction with Google Storage
• kubectl – Managing Kubernetes container clusters
• Accessed using Google Cloud SDK (software development kit) or
Google Cloud Shell in the GCP console
part.
Figure 3-7 Use the Google Cloud Shell directly in your browser.
Increasing Agility (1 of 11)
• Project management
• Skill required for cloud migration
• Project
• Effort with clearly defined beginning and ending
• Project categories
• Initiating, planning, executing, monitoring and controlling, and closing
• Project management defined
• Application of specific skills, tools, and techniques to manage
processes so desired outcome is achieved
part.
Figure 3-8 The five project

management process groups.
• Project management (cont’d)

• Certifications
• PMP (Project Management Professional) by PMI
• Certified Six Sigma Black Belt (CSSBB) by ASQ
• CSM (Certified ScrumMaster) by the Scrum Alliance
• Project+ by CompTIA (entry level)
part.
• Project management (cont’d)

• Key project management skills
• Communication: highly desired “soft” skill
• Negotiation: successfully writing RFPs (requests for proposals)
• Task and time management: scheduling successful project phases
• Cost and quality management: managing costs and quality standards
• Risk management: choosing risk wisely
• Leadership: inspiring and guiding others
part.
• Application life cycle

• Application life cycle management (ALM)
• Oversight of an application
• Through development, maintenance, and retirement
• Software development phase: most active
• Called software development life cycle (SDLC)
part.
Figure 3-9 The application progresses from one end to the other.
• Application life cycle (cont’d)

• Waterfall SDLC
• Older
• Linear path: too slow for today’s demand
• Clearly defined beginning and ending
• Continuous or cyclical SDLC
• Efficient and faster response time
• Increased agility to adapt quickly to market demands
part.
Figure 3-10 A linear progression

of software development.
Figure 3-11 A cyclical approach to

software development.
• Application life cycle (cont’d)

• DevOps (development and operations)
• Continuous collaboration between development and operations teams
• Results in highly responsive application updates
• Emphasizes agility
• Continuous integration/continuous delivery (CI/CD)
• Merging all code changes from all developers working on a project
• Deploying changes in small increments on a short time schedule
• Provides highly responsive adaptations to application updates
part.
Figure 3-12 DevOps teams blur the lines between development and operations functions.

Cloud+ Mod03 - FINAL

Uploaded by

Copyright:

Available Formats

You might also like

Cloud+ Mod03 - FINAL

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cloud+ Mod03 - FINAL

Uploaded by

Copyright:

Available Formats

Module 3

Migration to the Cloud

• In this module, you will learn how to:

• In this module, you will learn how to: (cont’d)

• In this module, you will learn how to: (cont’d)

• Private school migrating VM services to cloud

• Action list questions

Figure 3-1 The five phases of cloud

• Cloud migration phases

• Transition assessment (cont’d)

• Migration plan (cont’d)

• Migration plan (cont’d)

• Migration plan (cont’d)

• Migration plan (cont’d)

• Migration plan (cont’d)

• Migration strategies (cont’d)

Figure 3-2 Cloud migration strategies.

• Migration strategies (cont’d)

Figure 3-3 Time and money

• Change management (cont’d)

Figure 3-4 A simple workflow for

• Data transfer (cont’d)

Figure 3-5 Snowmobile can transfer up to 100 PB per trip.

• Storage migration (cont’d)

• Testing types (cont’d)

• Testing considerations (cont’d)

• Common deployment issues

• Common deployment issues (cont’d)

• Cloud CLIs (cont’d)

• Cloud CLIs (cont’d)

• Cloud CLIs (cont’d)

• Cloud CLIs (cont’d)

Figure 3-8 The five project

• Project management (cont’d)

• Project management (cont’d)

• Application life cycle

• Application life cycle (cont’d)

Figure 3-10 A linear progression

Figure 3-11 A cyclical approach to

• Application life cycle (cont’d)

You might also like