Book Image

Hands-On Linux Administration on Azure

By : Frederik Vos
Book Image

Hands-On Linux Administration on Azure

By: Frederik Vos

Overview of this book

Azure’s market share has increased massively and enterprises are adopting it rapidly, while Linux is a widely-used operating system and has proven to be one of the most popular workloads on Azure. It has thus become crucial for Linux administrators and Microsoft professionals to be well versed with managing Linux workloads in an Azure environment. With this guide, system administrators will be able to deploy, automate, and orchestrate containers in Linux on Azure. The book follows a hands-on approach to help you understand DevOps, monitor Linux workloads on Azure and perform advanced system administration. Complete with systematic explanations of concepts, examples and self-assessment questions, the chapters will give you useful insights into Linux and Azure. You’ll explore some of Linux’s advanced features for managing multiple workloads and learn to deploy virtual machines (VMs) in Azure. Dedicated sections will also guide you with managing and extending Azure VMs’ capabilities and understanding automation and orchestration with Ansible and PowerShell DSC. In later chapters, you’ll cover useful Linux troubleshooting and monitoring techniques that will enable you to maintain your workload on Azure. By the end of this book, you’ll be able to make the most out of Azure’s services to efficiently deploy and manage your Linux workloads.
Table of Contents (14 chapters)

SaltStack

Salt started as a tool to provide a method to execute remote commands. Nowadays, it's a complete open source solution for infrastructure management maintained by the company SaltStack. It's often referred to as SaltStack Platform.

Salt is easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds.

Salt is different from Ansible in terms of architecture. It is a client-server model; communication between the master and the slave is secured by the ZeroMQ transport method using keys for authentication. If you want to use SSH (agentless), it's possible, but the client-server model is chosen because that scales much better than working with many SSH clients at the same time. It is also different in the way you provide the configuration. You can push the configuration to...