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

Creating cloud images


Creating images has been at the core of infrastructure automation. I am sure we have all created or at least used virtual machine images. It is one of the major reasons for the rise of the adoption of virtualization: its ease of management. 

The cloud also uses images, as one of the underlying technologies is virtualization. Now, for the most important question, "how different is the image created for the cloud from one created for virtualization?" The answer is, "Not much!" 

The cloud uses known (sometimes modified/tweaked) versions of the virtualization platforms that we have already worked on. As an example, AWS uses a modified version of Xen. OpenStack can technically work with any hypervisor, but the choice is normally KVM. Azure would work with Hyper-V. 

This means that creating cloud images will not be very different from what we have been doing so far in order to create the corresponding virtualization images. We may need to change the format of the image (similar...