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)

Further reading

My first steps into the performance and troubleshooting world, already many years ago, were started by documents written by Sander van Vugt. Many of this information and more survived in a video course: Red Hat Performance Troubleshooting and Optimization (https://www.sandervanvugt.com/).

Another big source of information is the website of Brendan D Gregg (http://www.brendangregg.com), where he shares an unbelievably big list of his documentation, slides, videos and so on. On top of that, there are some some nice utilities! He was the one who taught me in 2015 that it is important how to identify the problem:

  • What makes you think that there is a problem?
  • Was there a time that there wasn't a problem?
  • Has something changed recently?
  • Try to find technical descriptions: such as latency, run-time error and so on.
  • Is it only the application, or are other resources...