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

Chapter 7. Understanding Automation in Microsoft Azure Stack

In the previous chapters, you have seen how to create cloud environments in Azure Stack and how to create one or more virtual machines in there. As you have recognized, this all is done with ARM templates and Azure Resource Manager. The ARM template defines the parameters for your resource, and Azure Resource Manager deploys them to the environment. The result of an ARM deployment is one or more virtual machines that are working in the same environment and define a solution in Azure Stack. As you have also already seen, there may be hybrid setups where parts of a solution are from another Azure based-cloud solution such as Azure public.

If we have a look at common solution design scenarios, a solution with various resources contains of default solutions (such as a VM template) and specifications dedicated to a customer environment. How could we set these specifications in the dedicated resources if a VM has been deployed? That is...