Changes

==== <big>Document Migration Strategy and Targets</big> ====

==== <big>Document Migration Strategy and Targets</big> ====

By the end of this step you will have analyzed your portfolio of applications, updated key data in APM, chose the migrations strategy for each application ( one of the 5 Rs ), and the target for each application ( [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] or EDC ).

By the end of this step you will have analyzed your portfolio of applications, updated key data in APM, chose the migration strategy for each application (one of the 5 Rs), and the target for each application ([https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] or EDC).

 

During the Determine Modernization Vision for the Organization step you would have determine how far your organization wants to take its modernization journey. Part of that step was the Cloud Fit Scorecard. You should have already narrowed the target options for each application.  

===== '''<u>Choose the Appropriate Migration Strategy</u>''' =====

===== '''<u>Choose the Appropriate Migration Strategy</u>''' =====

With a rehost migration strategy, the application undergoes no changes and is migrated as-is to a new data centre or cloud. This is the simplest and least effort migration strategy.  

With a rehost migration strategy, the application undergoes no changes and is migrated as-is to a new data centre or cloud. This is the simplest and least effort migration strategy.  

For workloads migrating to [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud], it is strongly advised that, at the very least, the resources (network, compute, storage) be optimized and reduced to the smallest size possible. Additionally using reserved instances for production workloads and turning off unused servers during off-hours will help ensure a lower monthly bill from your cloud provider.  

For workloads migrating to [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud], it is strongly advised that the resources (network, compute, storage) be optimized and reduced to the smallest size possible. Additionally using reserved instances for production workloads and turning off unused servers during off-hours will help ensure a lower monthly bill from your cloud provider.  

====== '''Replatform (lift, shift, and tinker)''' ======

====== '''Replatform (lift, shift, and tinker)''' ======

With a replatform strategy, the application undergoes minor changes as it is migrated to a new data centre or cloud. Replatforming strategies may include, but as not limited to:

With a replatform strategy, the application undergoes minor changes as it is migrated to a new data centre or cloud. Replatforming strategies may include, but as not limited to:

Addressing end of life (EOL) software such as those deprecated by IT Policy Implementation Notice [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology/policy-implementation-notices.html ITPINs]

* Addressing end of life (EOL) software such as those deprecated by IT Policy Implementation Notice [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology/policy-implementation-notices.html ITPINs]

 

* Moving to Platform-as-a-Service (PaaS) for commoditized services such as databases, web servers, file servers, container orchestration, moving to a PaaS allows for a serverless architecture.  

Move to Platform-as-a-Service (PaaS). For commoditized services such as databases, web servers, file servers, container orchestration, moving to a PaaS allows for a serverless architecture. A serverless architecture negates the need to manage and patch operating systems, middleware and manage server instances. This also reduces an organization's IT Lifecycle Management burden. Users sometimes worry that using PaaS will cause vendor lock-in. By using PaaS that have alternatives elsewhere in the market will avoid lock-in. Being able to extract your business data and business rules from a PaaS is key to avoiding lock-in. Most cloud providers offer database, web server, and file server platforms. While migrating from one to another may not be completely painless, migration tools and APIs exist to allow for this possibility.

A serverless architecture negates the need to manage and patch operating systems, middleware and manage server instances. This also reduces an organization's IT Lifecycle Management burden. Users sometimes worry that using PaaS will cause vendor lock-in. By using PaaS that have alternatives elsewhere in the market will avoid lock-in. Being able to extract your business data and business rules from a PaaS is key to avoiding lock-in. Most cloud providers offer database, web server, and file server platforms. While migrating from one to another may not be completely painless, migration tools and APIs exist to allow for this possibility.

Containers is an increasingly popular method to deploy applications. If your application is stateless, moving it to a container will not only help portability, but also help with your organization's adoption of DevOps practices.

Containers is an increasingly popular method to deploy applications. If your application is stateless, moving it to a container will not only help portability, but also help with your organization's adoption of DevOps practices.