213
edits
Changes
Jump to navigation
Jump to search
Line 52:
Line 52: − + Line 58:
Line 58: − + − + Line 107:
Line 107: − + Line 115:
Line 115: − + − + − + − + Line 139:
Line 139: − + Line 188:
Line 188: − + Line 216:
Line 216: − + Line 245:
Line 245: − + − −
no edit summary
Priorities for investment from the Application Modernization and Workload Migration funds are based upon identifying high business value applications that are impacted by at-risk technologies. These at risk technologies can include, amongst other things, end of life software, end of life infrastructure, outdated architectures, to be decommissioned facilities such as data centres, etc…
Priorities for investment from the Application Modernization and Workload Migration funds are based upon identifying high business value applications that are impacted by at-risk technologies. These at risk technologies can include, amongst other things, end of life software, end of life infrastructure, outdated architectures, to be decommissioned facilities such as data centres, etc…
1) To stabilize the IT landscape and ensure continuity of services to Canadians, TBS and SSC are working in collaboration with GC departments that demonstrate a readiness to modernize applications and migrate them to end state hosting platforms (cloud or enterprise data centres).
1) To stabilize the IT landscape and ensure continuity of services to Canadians, TBS and SSC are working in collaboration with GC departments that demonstrate a readiness to modernize applications and migrate them to end state hosting platforms ([https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] or enterprise data centres).
2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment. If endorsed by governance, those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program.
2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment. If endorsed by governance, those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program.
To facilitate the prioritization process, [https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr a GCEARB Gate1 (Prioritization) template] has been provided for departments to complete. This template, once completed, can be brought forward to your Departmental Architecture Review Board before being brought forward to request endorsement by governance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group], [[GC EARB]], ADM CEPP, and DM CEPP). The request for endorsement is a department’s opportunity to make a strong business case for investment to address at-risk technologies.
To facilitate the prioritization process, [https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr a GCEARB Gate1 (Prioritization) template] has been provided for departments to complete. This template, once completed, can be brought forward to your Departmental Architecture Review Board before being brought forward to request endorsement by governance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group], [[GC EARB]], ADM CEPP, and DM CEPP). The request for endorsement is a department’s opportunity to make a strong business case for investment to address at-risk technologies.
The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework (described on this page), and the strategy that will be used to modernize (rehost, replatform, refactor, replace and to which hosting platform; data centre or cloud services)
The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework (described on this page), and the strategy that will be used to modernize (rehost, replatform, refactor, replace and to which hosting platform; data centre or [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services)
In 2018, the following data centre facilities were identified as at-risk technologies to be decommissioned and the applications to be migrated or modernized to a new enterprise data centre or cloud services.
In 2018, the following data centre facilities were identified as at-risk technologies to be decommissioned and the applications to be migrated or modernized to a new enterprise data centre or [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services.
The first wave of workload migration projects began in 2018:
The first wave of workload migration projects began in 2018:
By the end of this step, you should have discussed with leadership how far you want to take your modernization journey. This will be the vision for your organization. Those who will be performing the subsequent portfolio analysis steps should understand that vision.
By the end of this step, you should have discussed with leadership how far you want to take your modernization journey. This will be the vision for your organization. Those who will be performing the subsequent portfolio analysis steps should understand that vision.
This is an opportunity to determine the direction for the organization; is it to largely sustain current operations and culture, or does the organization desire to modernize and be more transformative. Perhaps your organization has already begun a modernization journey. In today's IT environment cloud technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary
This is an opportunity to determine the direction for the organization; is it to largely sustain current operations and culture, or does the organization desire to modernize and be more transformative. Perhaps your organization has already begun a modernization journey. In today's IT environment [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary
* deliver IT faster
* deliver IT faster
This guide is meant to be a catalyst for establishing the vision. These changes can be wide sweeping impacting Roleroles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement.
This guide is meant to be a catalyst for establishing the vision. These changes can be wide sweeping impacting Roleroles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement.
While some organizations have started this journey years ago and are ready to go "all in" on cloud and the workforce are DevOps practitioners, others have not begun the journey.
While some organizations have started this journey years ago and are ready to go "all in" on [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] and the workforce are DevOps practitioners, others have not begun the journey.
For those who have not yet begun a modernization journey the choice may be take this opportunity to start that journey. For others, they may decide to simply sustain operations as-is. Here is a simple visual for plotting your cloud adoption .
For those who have not yet begun a modernization journey the choice may be take this opportunity to start that journey. For others, they may decide to simply sustain operations as-is. Here is a simple visual for plotting your [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] adoption .
[[Image:Cloud maturity map .png]]
[[Image:Cloud maturity map .png]]
Start small with a few low risk applications. A team of developers from within your existing workforce would lead an initative to migrate those low risk workloads to the cloud. The build from these experiences and learnings to train others to do the same. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. An organization should review the [https://gccollab.ca/file/view/3691530/engc-cloud-rr-matrixfr GC Cloud R&R Matrix] to ensure your organization is ready to undertake the required roles to support cloud services.
Start small with a few low risk applications. A team of developers from within your existing workforce would lead an initative to migrate those low risk workloads to the [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud]. The build from these experiences and learnings to train others to do the same. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. An organization should review the [https://gccollab.ca/file/view/3691530/engc-cloud-rr-matrixfr GC Cloud R&R Matrix] to ensure your organization is ready to undertake the required roles to support [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services.
See the [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple cloud fitness scorecard]] to assess low risk workloads for cloud migration. It provides you a short list to help with the decision as to where to start and to identify low risk and low effort migrations. Any application can be migrated to the cloud with enough time and effort.
See the [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple cloud fitness scorecard]] to assess low risk workloads for cloud migration. It provides you a short list to help with the decision as to where to start and to identify low risk and low effort migrations. Any application can be migrated to the [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] with enough time and effort.
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
==== <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 ( cloud or EDC ).
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 ).
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.
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.
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 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, 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.
====== '''Replatform (lift, shift, and tinker)''' ======
====== '''Replatform (lift, shift, and tinker)''' ======
''Enterprise Data Centre (EDC):'' a new data centre with low technical risks
''Enterprise Data Centre (EDC):'' a new data centre with low technical risks
''Cloud:'' a public cloud service provider available from the SSC Cloud Broker
''Cloud:'' a public cloud service provider available from the [https://cloud-broker.canada.ca/s/?language=en_CA SSC GC Cloud Brokering Service]
===== '''<u>Identify Data Centre</u>''' =====
===== '''<u>Identify Data Centre</u>''' =====
The [https://gccollab.ca/file/view/2650673/engeneric-wlm-app-mod-gcearb-gate2-executionfr generic template] for the presenting your discovery analysis and funding approval to move to execution.
The [https://gccollab.ca/file/view/2650673/engeneric-wlm-app-mod-gcearb-gate2-executionfr generic template] for the presenting your discovery analysis and funding approval to move to execution.
As part of the GC EARB a CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy requirement (requirement 6.4.2) and meeting requirement 6.1.1 of the Directive.
As part of the GC EARB a CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy (Cloud First 4.4.1.9 / Data Residency 4.4.1.10 / Non-Public Cloud GC EARB Assessments 4.1.1.2.4) of the [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital]. If and when endorsement is provided by GC EARB, approval will be requested from the GC CIO. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr Memorandum of Understanding] between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.
If and when endorsement is provided by GC EARB, approval will be requested from the GC CIO. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr Memorandum of Understanding] between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.
=== ''Reporting Requirements'' ===
=== ''Reporting Requirements'' ===
