Book Image

Proxmox Cookbook

By : Wasim Ahmed, Ravi K Jangid
Book Image

Proxmox Cookbook

By: Wasim Ahmed, Ravi K Jangid

Overview of this book

Proxmox VE's intuitive interface, high availability, and unique central management system puts it on par with the world’s best virtualization platforms. Its simplicity and high quality of service is what makes it the foremost choice for most system administrators. Starting with a step-by-step installation of Proxmox nodes along with an illustrated tour of Proxmox graphical user interface where you will spend most of your time managing a cluster, this book will get you up and running with the mechanisms of Proxmox VE. Various entities such as Cluster, Storage, and Firewall are also covered in an easy to understand format. You will then explore various backup solutions and restore mechanisms, thus learning to keep your applications and servers safe. Next, you will see how to upgrade a Proxmox node with a new release and apply update patches through GUI or CLI. Monitoring resources and virtual machines is required on an enterprise level, to maintain performance and uptime; to achieve this, we learn how to monitor host machine resources and troubleshoot common issues in the setup. Finally, we will walk through some advanced configurations for VM followed by a list of commands used for Proxmox and Ceph cluster through CLI. With this focused and detailed guide you will learn to work your way around with Proxmox VE quickly and add to your skillset.
Table of Contents (18 chapters)
Proxmox Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Rebooting dilemmas after an update


After any update or upgrade, all administrators face the question of whether or not the node should be rebooted and whether or not virtual machines need to be power-cycled. A Proxmox upgrade process is usually very informative, letting us know whether the node really needs a reboot. Most updates do not require any reboot. They are simply package updates. However, some upgrades, such as kernel releases, newer grubs, and others, will require a node reboot to apply the new changes. The exact method of rebooting depends on each environment and the number and nature of the VMs that are stored per node. In this section, we are going to look at the most widely used method, which is by no means the only method.

How to do it…

For a minimal virtual machine downtime, we can live-migrate all the VMs from one node to another, then migrate them back to the original node. As of Proxmox VE 3.4, there is a nice GUI feature addition to instruct all VM migrations with a menu...