Gain insights into DevOps in Azure, delve into configuration management, CI/CD, and Infrastructure as Code. Explore tools like GitHub and Kubernetes through hands-on projects to become a DevOps professional.

admintodevops.tar.gz

Username

Password

AZURE_SUBSCRIPTION_ID

AZURE_CLIENT_ID

AZURE_SECRET

AZURE_TENANT

Git_Email

Git_Name

Azure

Ansible

Chrome

vscode 

Azure-VM

Terraform

az-boards

azure-instances

azure-pipelines

Docker

This course is for anyone in IT or software engineering who wants to learn more about DevOps and, specifically, how to follow DevOps practices in Azure. Whether you’re a system administrator, engineer, developer, or IT manager, this course will help you understand what it takes to deliver more value to customers with DevOps.

You will dive into concepts like configuration management, continuous integration/continuous delivery, and Infrastructure as Code. You will learn the key tools used by DevOps professionals such as: the command line, Visual Studio Code, GitHub, Kubernetes, and more.

You will complete various projects throughout the course where each chapter’s project is designed in a step-by-step manner to walk you through using the tool just as you would in your daily life.

By the time you finish, you will have the foundations in place to become a DevOps professional.

The Complete Guide to DevOps in Azure

# Need for availability sets
When building an Azure VM, it can be difficult to keep your VMs in separate vaults and update domains. You can't simply to say, “I want this VM here  and the datacenter B on that server there". Instead, you have to assign VMs to *availability sets*.

> *You can specify where a server is  in Azure if you have Microsoft provision physical servers, but we’re not going to go into that in this chapter.*

Availability sets are Azure’s way of automatically distributing a set of VMs across various fault and update domains and ensures your VMs inherit Azure’s [99.5% VM SLA](https://azure.microsoft.com/en-us/support/legal/sla/virtual-machines/v1_9/). Even though you can’t explicitly define an update or fault domain that you’d like VMs to be in, you can define a VM’s availability set.

When you create a VM in Azure, you have the option of defining an availability set. You can be sure all VMs you add to a single availability set will be spread across three faults and up to 20 update domains. 

Availability sets are free. You only pay for the VM resources that you assign to the availability set.

# Availability set design

Perhaps you have an application with a front end (web) tier and a backend (data) tier with a load balancer controlling each tier. In that case, you'd want to create an availability set based on each tier. Doing so will ensure each web server and database server is in a different fault domain.

Learn how Azure distributes a set of VMs across various fault and update domains.
