Book Image

Hybrid Cloud Infrastructure and Operations Explained

By : Mansura Habiba
Book Image

Hybrid Cloud Infrastructure and Operations Explained

By: Mansura Habiba

Overview of this book

Most organizations are now either moving to the cloud through modernization or building their apps in the cloud. Hybrid cloud is one of the best approaches for cloud migration and the modernization journey for any enterprise. This is why, along with coding skills, developers need to know the big picture of cloud footprint and be aware of the integration models between apps in a hybrid and multi-cloud infrastructure. This book represents an overview of your end-to-end journey to the cloud. To be future agnostic, the journey starts with a hybrid cloud. You'll gain an overall understanding of how to approach migration to the cloud using hybrid cloud technologies from IBM and Red Hat. Next, you’ll be able to explore the challenges, requirements (both functional and non-functional), and the process of app modernization for enterprises by analyzing various use cases. The book then provides you with insights into the different reference solutions for app modernization on the cloud, which will help you to learn how to design and implement patterns and best practices in your job. By the end of this book, you’ll be able to successfully modernize applications and cloud infrastructure in hyperscaler public clouds such as IBM and hybrid clouds using Red Hat technologies as well as develop secure applications for cloud environments.
Table of Contents (16 chapters)
1
Part 1: Moving to Hybrid Cloud
5
Part 2: Cloud-Native Methods, Practices, and Technology
8
Part 3: Elements of Embedded Linux

Understanding KPIs for the platform service

For hybrid cloud operations, we need to define a set of KPIs to measure the efficiency of the underlying cloud platform. Here is a set of KPIs for cloud platform evaluation:

  • Total downtime indicates the aggregate number of hours within the scheduled operational hours in the reporting period when the infrastructure elements and applications were unavailable for use by the designated end users.
  • Planned downtime refers to the aggregate number of hours out of the scheduled hours in any reporting period when the supported infrastructure elements and applications were unavailable for use by the designated users due to planned preventive maintenance, upgrades, or changes.
  • Response time refers to the time the first resolver group(s) takes to accept a ticket for resolution. For example, this would be the time difference between an incident (ticket) being created to the time the resolver acknowledges the incident (ticket) for action...