cloud-migration-wave-plan.pdf

Wave Planning

Document Life-cycle Status

TEMPLATE DRAFT IN REVIEW BASELINE

This Application Lifecycle defines each phase of the Application Migration Lifecycle. These common definitions will serve as a guide for reporting status and communicating clearly. This framework identifies key requirements and artifacts that are linked to further expand on the sub-tasks within these various phases, which will detail exactly what needs to be achieved to advance the application. The objective of the Application Lifecycle is to establish a shared understanding of all FEC’s individual application migration status to AWS. Following this process provides FEC the information needed to make informed decisions around migration costing and application migration planning. It replaces manual estimates and guesswork with true migration level of effort and right sizing of on-premises workloads and AWS transformation options - giving your customers a data-backed business case to accelerate their migration to AWS.

Exercise best practice migration criteria to baseline migration events/waves such as migrating dev before test before prod and lower workload criticality before high workload criticality.

On-premise workload migration to AWS, assessment and results including Source to target AWS workload mapping, level of efforts and cost

Right-sizing based on actual utilization

Over provisioned to optimized workload sizing

Other criteria can include high priority datacenter, aggressive application business units/owners

Stage Responsibilities

0 Planning Application Migration Lifecycle kick-off. Typically involves Long Range Planning (LRP).

1 Pre-Discovery Migration team initiates communication with application teams.

2 Application Discovery Cloud Engineers and AWS Pro-Serv team members conduct Application Discovery by holding working sessions with the Application Owners and POCs to learn and document the critical information using the Application Discovery Template.

3 Operations Discovery Validate status of agents prior to cutover (e.g. Big Fix) and ensure the AHE team has received all inputs and templates that are required prior to provisioning a server to a customer. Requirements include: SAARs, Hosting Sheets, etc.

4 Pre-Deployment For Replatform, prepare the cloud infrastructure for cutting over the application once team has completed their installations on the on-prem server(s) prior to cutover.

For Rehost, install the CloudEndure application on the server(s).

5 AWS Handoff to Ops For Replatform Only, deploy cloud infrastructure and ensure all Ops Discovery requirements have been met. In this phase, upgrade the applications OS and install the required tools on the server(s).

6 Ops Handoff to Apps For Replatform Only, the applications team must login into their machines, complete application installs and perform initial testing.

7 Cutover For Rehost, start Cutover in CloudEndure. , Power off the old servers For Replatform and power on the new servers, ensuring that the new machines are pointing to new IPs and supporting DBs.

8 Post-Cutover The steps to validate the application is successfully running, being monitored, and on-track to be decommissioned.

9 Ops Transition Checklist is carried out between Migration team and operations team.

8 Closed Confirm the application is successfully migrated and/or decommissioned on-prem.

Scope

Analysis of identified applications

Determination of each server's baseline disposition Can change during MRP and future planning phases

"Accurate, yet ballpark" server migration for entire portfolio cost and cost per server

Support to entire AWS account team in understanding MPA variables and assumptions

Migration event/waves are sized appropriately to customer expectations

Migration event/wave start dates are staggered appropriately to customer expectations and timelines

Migration event/wave complexity is created appropriately to customer expectations

Baseline criteria of dev before test before prod and lowest to highest application criticality is applied throughout all of the migration events /waves

Application to server persistent connections are factored

Application to application connections are factored when available

Educate customer teams on AWS migration best practices

Out Of Scope

Full regression testing on applications. More specifically, the migration phase supports cutover, startup, smoke testing, and if possible server shutdown (pending time table made by FEC).

Application and database deep dive discovery workshops. To be performed during MRP or later phases of migration planning

Database migration strategy. Migration events/waves will be impacted by whether the database servers are migrating at the server/host level or to RDS or other

Detailed project plan and customer resource allocation

Wave Planning