Manage Cloud Adoption | Digitalokta
Cloud management in the Cloud Adoption Framework
The guidance in the last phase of the Cloud Adoption Framework serves two purposes. On the one hand it helps you to develop the business and technical approaches needed to provide cloud management that powers ongoing operations and provides examples of actionable operations management approaches that represent common experiences often encountered by customers. On the other hand, it helps you create personalized management solutions based on business commitments. Delivering on a cloud strategy requires solid planning, readiness, and adoption. But it’s the ongoing operation of the digital assets that delivers tangible business outcomes. Without a plan for reliable, well-managed operations of the cloud solutions, those efforts will yield little value.
A section of the management phase is the Azure management guide. The Azure Management Guide helps Azure customers create a management baseline to establish resource consistency across Azure. This guide outlines the basic tools needed for any Azure production environments, especially environments that host sensitive data. This guide teaches you how to establish tooling for a management baseline. It also outlines ways to extend the baseline or build resiliency beyond the baseline. Inventory and visibility, Operational compliance, Protect and recover or Enhanced baseline options amongst others are covered in this guide.
Inventory and visibility is the first of three disciplines in a cloud management baseline. This discipline comes first because collecting proper operational data is vital when you make decisions about operations. Cloud management teams must understand what is managed and how well those assets are operated. In the Inventory and Visibility article different tools like Azure Service Health or Log Analytics that provide both an inventory and visibility into the inventory’s run state are described. Azure Service Health provides a personalized view of the health of your Azure services and regions.
Workload specialization too consists of a disciplined execution of the four processes in an iterative approach.
- Improve system design: Improve the design of a specific workload to effectively minimize interruptions.
- Automate remediation: Some improvements aren’t cost effective. In such cases, it might make more sense to automate remediation and reduce the effect of interruptions.
- Scale the solution: As systems design and automated remediation are improved, those changes can be scaled across the environment through the service catalog.
- Continuous improvement: You can use different monitoring tools to discover incremental improvements. These improvements can be addressed in the next pass of system design, automation, and scale.
Workload specialization often triggers a cultural change in traditional IT build processes that focus on delivering a management baseline, enhanced baselines, and platform operations. Those types of offerings can be scaled across the environment. Workload specialization is similar in execution to platform specialization. But unlike common platforms, the specialization required by individual workloads often doesn’t scale. When workload specialization is required, operational management commonly evolves beyond a central IT perspective.