Book Image

Building Hybrid Clouds with Azure Stack

Book Image

Building Hybrid Clouds with Azure Stack

Overview of this book

Azure Stack is all about creating fewer gaps between on-premise and public cloud application deployment. Azure Stack is the logical progression of Microsoft Cloud Services to create a true hybrid cloud-ready application. This book provides an introduction to Azure Stack and the cloud-first approach. Starting with an introduction to the architecture of Azure Stack, the book will help you plan and deploy your Azure Stack. Next, you will learn about the network and storage options in Azure Stack and you'll create your own private cloud solution. Finally, you will understand how to integrate public cloud using the third-party resource provider. After reading the book, you will have a good understanding of the end-to-end process of designing, offering, and supporting cloud solutions for enterprises or service providers.
Table of Contents (19 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Azure Container Services


If you are willing to consume containers for Linux/Windows as a PaaS solution, Azure Container Services (ACS) could be a solution. The generic design of ACS is described here:

Source: https://docs.microsoft.com/de-de/azure/container-service/media/acs-intro/dcos.png

A good question is now how to design a container solution with Azure and Azure Stack in a hybrid way since—as of today—there is no PaaS solution with Azure Stack, but there are IaaS machines that support Windows containers or Linux Docker.

The answer is quite easy: as Azure and Azure Stack support site-to-site VPNs between each other, there is network connectivity enabled already.

So, we could set up containers in both solutions (with Azure- and Azure Stack-only IaaS based container images) and manage them with a dedicated orchestration solution such as Kubernetes. This means that you could just move workloads from Azure to Azure Stack and vice versa. As you can manage the location of a container/docker image...