Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

Deploy apps to an Azure VM scale set with a custom packer image III

0 (0 Likes / 0 Dislikes)
[Male:] Packer is an open source tool that enables a templated approach to creating custom Virtual Machine images. There are several benefits to adopting Packer in your Continuous Integration and Deployment tool chain, but for our purposes in this module, we are going to use Parker as a means of automating the customizations to our Virtual Machine and defining Azure Virtual Machine settings. This will allow us to automate our VM setup so that we can more easily scale the number of Virtual Machines in our 'scale set'. So, again, whenever you think of Packer, think of automating Virtual Machine customizations, all right? So, you create a Packer template, and a Packer template is simply a JSON, or a JavaScript Object Notation document. That document has two main sections; you can see the screenshot in the video right now. Those two main sections are where you create Provisioners and Builders. So, a Provisioner is something that actually carries out configuration tasks. So, you can set it up to update an Operating System, install Packages on the OS, you can configure applications, and so on. So, what's great about Packer is that these Provisioners are agnostic. In other words, they work regardless of the platform. You can create these Packer definitions on how you want the image to be configured and what you want to install in that image. And then, it works the same way, no matter which platform, which operating system, and which cloud environment you use like Azure, for example. So, that is a Provisioner. A Builder is really, kind of, the special sauce where you see Packer's magic come into play. It uses these Builders to work across different Cloud environments. So, there is a Builder for Azure. The Builder section of the template defines how to create that base Virtual Machine in Azure. So, it will define things like which subscription to use, which region, where we want to locate that Virtual Machine into, and we also get to define things that will support the Virtual Machine, like, you know, any temporary resources or supporting resources, things like the virtual network, things like storage, and so on. Okay. So, the Azure Builder for Packer uses that section and all the things that you define in it in Json, and then it takes care of the underlying components that are needed to push the VM into our Azure environment. So, Packer can even use Azure Marketplace images to quickly get a base Ubuntu or Red Hat VM created, and then just overlay the Provisioner definition to customize it just like you defined. So, if you take this approach, what you end up with is a mix of the Azure Marketplace - the Azure Marketplace image, with your own customizations on top of it, which lets you quickly get to actually deploying your applications in a clean, consistent manner. So, that's the beauty of Packer it allows you to follow one of the basic Azure administration principles to automate everything so that you only have to think through it one time. Okay?

Video Details

Duration: 3 minutes and 28 seconds
Language: English
License: Dotsub - Standard License
Genre: None
Views: 6
Posted by: csintl on Jul 5, 2018


Caption and Translate

    Sign In/Register for Dotsub to translate this video.