Book Image

Hybrid Cloud for Architects

By : Alok Shrivastwa
Book Image

Hybrid Cloud for Architects

By: Alok Shrivastwa

Overview of this book

Hybrid cloud is currently the buzz word in the cloud world. Organizations are planning to adopt hybrid cloud strategy due to its advantages such as untested workloads, cloud-bursting, cloud service brokering and so on. This book will help you understand the dynamics, design principles, and deployment strategies of a Hybrid Cloud. You will start by understanding the concepts of hybrid cloud and the problems it solves as compared to a stand-alone public and private cloud. You will be delving into the different architecture and design of hybrid cloud. The book will then cover advanced concepts such as building a deployment pipeline, containerization strategy, and data storage mechanism. Next up, you will be able to deploy an external CMP to run a Hybrid cloud and integrate it with your OpenStack and AWS environments. You will also understand the strategy for designing a Hybrid Cloud using containerization and work with pre-built solutions like vCloud Air, VMware for AWS, and Azure Stack. Finally, the book will cover security and monitoring related best practices that will help you secure your cloud infrastructure. By the end of the book, you will be in a position to build a hybrid cloud strategy for your organization.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Software Hardware List
Packt Upsell
Contributors
Preface
Index

Monitoring the hybrid cloud


Armed with the knowledge about monitoring, let's look at how this changes in the hybrid cloud world or even just the cloud world. Can we not use the same systems that we were using in the traditional environment to monitor the new one? 

The answer is yes, for the systems that it was made for monitoring, we can. This means there is no difference in whether we monitored a virtual or physical machine on premises or on the cloud; we can use the same mechanism.

However, is this recommended? The answer is, not really. If you ask why, let's take a look at the main reasons behind it, which are listed as follows:

  • The cloud platform already monitors some of the resources (for the sake of autoscaling and the like); the old system of monitoring doesn't support these
  • There are new services that are being used and the old system doesn't know how to monitor these systems (as an example of containers) 
  • There have been several improvements in the new tools to be more optimized, and...