發行工作負載Release workloads

在收集工作負載並將及其支援資產部署至雲端後,必須先進行準備工作,才能發行工作負載。After a collection of workloads and their supporting assets have been deployed to the cloud, it must be prepared before it can be released. 在這個階段的移轉工作中,會對企業進行工作負載集合的負載測試和驗證。In this phase of the migration effort, the collection of workloads are load tested and validated with the business. 然後,會將其最佳化並記載。They're then optimized and documented. 當企業和 IT 小組檢閱並簽核工作負載部署後,這些工作負載就可發行,或遞交給控管、安全性和作業小組進行後續的作業。Once the business and IT teams have reviewed and signed off on workload deployments, those workloads can be released or handed off to governance, security, and operations teams for ongoing operations.

「發行工作負載」的目的是準備好已移轉的工作負載,以升級至生產環境用途。The objective of "release workloads" is to prepare migrated workloads for promotion to production usage.

對完成的定義Definition of done

當工作負載已正確設定、指定大小,並且部署至生產環境之中時,表示最佳化程序已完成。The optimization process is complete when a workload has been properly configured, sized, and deployed to production.

最佳化期間的責任Accountability during optimization

雲端採用小組必須負責處理整個最佳化程序。The cloud adoption team is accountable for the entire optimization process. 不過,雲端策略小組、雲端作業小組以及雲端治理小組的成員也應為此程序內的活動負責。However, members of the cloud strategy team, the cloud operations team, and the cloud governance team should also be responsible for activities within this process.

最佳化期間的職責Responsibilities during optimization

除了高層級的責任之外,還有個人或群組必須直接負責的動作。In addition to the high-level accountability, there are actions that an individual or group needs to be directly responsible for. 以下是需要指派給負責之合作對象的幾個活動:The following are a few activities that require assignments to responsible parties:

  • 業務測試。Business testing. 解決會防止工作負載順利移轉至雲端的任何相容性問題。Resolve any compatibility issues that prevent the workload from completing its migration to the cloud.
    • 企業內的進階使用者應深入參與對已移轉工作負載的測試。Power users from within the business should participate heavily in testing of the migrated workload. 視所嘗試的最佳化程度而定,可能需要進行多個測試循環。Depending on the degree of optimization attempted, multiple testing cycles may be required.
  • 業務變更方案。Business change plan. 基於移轉工作的結果而開發使用者採用方案、對業務程序進行變更,以及修改業務 KPI 及學習計量。Development of a plan for user adoption, changes to business processes, and modification to business KPIs or learning metrics as a result of the migration effort.
  • 建立基準並加以最佳化。Benchmark and optimize. 對業務測試和自動化測試進行研究,以建立效能基準。Study of the business testing and automated testing to benchmark performance. 雲端採用小組會根據使用方式調整已部署的資產大小,以依據預期的生產需求平衡成本與效能。Based on usage, the cloud adoption team refines sizing of the deployed assets to balance cost and performance against expected production requirements.
  • 針對生產環境進行準備。Ready for production. 針對工作負載持續的生產環境用途準備工作負載和環境。Prepare the workload and environment for the support of the workload's ongoing production usage.
  • 升級。Promote. 將生產環境流量重新導向至已移轉且已最佳化的工作負載。Redirect production traffic to the migrated and optimized workload. 此活動代表發行週期的完成。This activity represents the completion of a release cycle.

除了核心活動之外,還有幾個平行活動需要特定的指派和執行計畫:In addition to core activities, there are a few parallel activities that require specific assignments and execution plans:

  • 解除委任。Decommission. 一般而言,可以透過將先前的生產環境資產解除委任並正確處置,以實現透過移轉來節省成本的目的。Generally, cost savings can be realized from a migration, when the previous production assets are decommissioned and properly disposed of.
  • 追溯性。Retrospective. 每個發行都能提供進行深度學習,以及採納成長心態的機會。Every release creates an opportunity for deeper learning and adoption of a growth mindset. 當每個發行週期完成之後,雲端採用小組應評估在移轉期間所使用的程序,以找出可改善的區塊。When each release cycle is completed, the cloud adoption team should evaluate the processes used during migration to identify improvements.

後續步驟Next steps

在對最佳化程序取得基本認識之後,您便可以針對候選工作負載建立業務變更方案來開始該程序。With a general understanding of the optimization process, you're ready to begin the process by establishing a business change plan for the candidate workload.