{"id":377902,"date":"2024-10-31T10:10:06","date_gmt":"2024-10-31T10:10:06","guid":{"rendered":"https:\/\/www.ninjaone.com\/?post_type=script_hub&p=377902"},"modified":"2024-10-31T10:10:06","modified_gmt":"2024-10-31T10:10:06","slug":"proxmox-vm-informationserfassung-automatisieren","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/de\/script-hub\/proxmox-vm-informationserfassung-automatisieren\/","title":{"rendered":"Linux-Skript-Guide: Automatisierung der Proxmox VM-Informationserfassung"},"content":{"rendered":"

In der heutigen IT-Welt sind die effiziente Verwaltung und \u00dcberwachung virtueller Umgebungen f\u00fcr Systemadministratoren und Managed Service Provider (MSPs<\/a>) ausschlaggebend. Virtuelle Umgebungen, wie die durch Proxmox verwalteten, m\u00fcssen regelm\u00e4\u00dfig \u00fcberwacht werden, um einen reibungslosen Betrieb und optimale Leistung zu gew\u00e4hrleisten.<\/p>\n

Die automatisierte Erfassung von Status- und Basisinformationen zu virtuellen Maschinen (VM)<\/a> spart nicht nur Zeit, sondern verringert auch das Risiko menschlichen Versagens. Vielleicht fragen Sie sich nun, wie Sie die Proxmox-VM-Informationserfassung automatisieren k\u00f6nnen. In diesem Blogbeitrag wird ein Bash-Skript vorgestellt, das den Status und die Details von Proxmox-G\u00e4sten automatisch abruft und anzeigt. Es wird dargelegt, wie es den IT-Betrieb durch seine N\u00fctzlichkeit optimieren kann.<\/p>\n

Kontext<\/h2>\n

Proxmox ist eine beliebte Open-Source-Virtualisierungs-Verwaltungsl\u00f6sung, die KVM und Container-basierte Virtualisierung auf einer einzigen Plattform vereint. F\u00fcr IT-Experten und MSPs ist die \u00dcberwachung des Zustands von VM und Containern eine routinem\u00e4\u00dfige, aber essenzielle Aufgabe. Dieses Skript erf\u00fcllt den Bedarf an einer automatisierten, konsistenten Methode zur Sammlung und Darstellung von VM-Informationen in einem benutzerfreundlichen Format, das leicht zug\u00e4nglich und interpretierbar ist.<\/p>\n

Das Skript<\/h2>\n
#!\/usr\/bin\/env bash\r\n\r\n# Description: This script gets the status and basic info of all Proxmox guests on a host and saves it to a WYSIWYG custom field.\r\n#\r\n# Release Notes: Initial Release\r\n# By using this script, you indicate your acceptance of the following legal terms as well as our Terms of Use at https:\/\/www.ninjaone.com\/terms-of-use.\r\n# Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms. \r\n# Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party. \r\n# Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library or website belonging to or under the control of any other software provider. \r\n# Warranty Disclaimer: The script is provided \u201cas is\u201d and \u201cas available\u201d, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations. \r\n# Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks. \r\n# Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script. \r\n# EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).\r\n#\r\n# Below are all the (case sensitive) valid parameters for this script.\r\n# Only the custom field name is required!\r\n# Preset Parameter: \"Custom_Field_Name\"\r\n#   Custom_Field_Name: The name of the WYSIWYG custom field to save the VM info to.\r\n\r\nCustom_Field_Name=$1\r\n\r\nif [[ -n \"${customFieldName}\" ]]; then\r\n    Custom_Field_Name=\"${customFieldName}\"\r\nfi\r\n\r\nif [[ -z \"${Custom_Field_Name}\" || \"${Custom_Field_Name}\" == \"null\" ]]; then\r\n    echo \"The custom field name is required.\"\r\n    echo \" Example: guests\"\r\n    exit 1\r\nfi\r\n\r\n# Check that we have the required tools\r\nif ! command -v pvesh &> \/dev\/null; then\r\n    echo \"The Proxmox VE API tool 'pvesh' is required.\"\r\n    exit 1\r\nfi\r\nif ! command -v python3 &> \/dev\/null; then\r\n    echo \"The python3 is required. Should already be installed.\"\r\n    exit 1\r\nfi\r\n\r\n# Check that we are running as root\r\nif [[ $EUID -ne 0 ]]; then\r\n    echo \"This script must be run as root.\"\r\n    exit 1\r\nfi\r\n\r\nfunction SetCustomField() {\r\n    \/opt\/NinjaRMMAgent\/programdata\/ninjarmm-cli \"$@\"\r\n}\r\n\r\n# Get the status and basic info of all Proxmox VMs on a host\r\nqemu_guests=$(pvesh get \/nodes\/localhost\/qemu --output-format=json)\r\n\r\n# Create a table to store the VM info with the headers: Name, Status, Memory, CPUs, Disk Sizes\r\nvm_table=\"<table><tr><th>Status<\/th><th>ID<\/th><th>Name<\/th><th>Memory<\/th><th>CPUs<\/th><th>Disk Sizes Combined<\/th><\/tr>\"\r\n\r\n# Loop through each VM and add the info to the table\r\nqemu_table=$(echo \"$qemu_guests\" | python3 -c '\r\nimport sys, json\r\n\r\n# Function to convert bytes to human readable format\r\ndef human_readable_size(size):\r\n    for unit in [\"B\", \"KB\", \"MB\", \"GB\", \"TB\", \"PB\", \"EB\", \"ZB\"]:\r\n        if size < 1024:\r\n            return f\"{size:.2f} {unit}\"\r\n        size \/= 1024\r\n\r\nqemu_guests = json.load(sys.stdin)\r\nvm_table = \"\"\r\n\r\nfor qemu in qemu_guests:\r\n    qemu_id = qemu[\"vmid\"]\r\n    qemu_name = qemu[\"name\"]\r\n    qemu_status = qemu[\"status\"]\r\n    # Convert the memory from bytes to GB\r\n    qemu_mem = human_readable_size(qemu[\"maxmem\"])\r\n    qemu_cpus = qemu[\"cpus\"]\r\n    # Convert the disk size from bytes to GB\r\n    qemu_disk = human_readable_size(qemu[\"maxdisk\"])\r\n\r\n    # Add HTML blank space if values are empty\r\n    qemu_id = qemu_id if qemu_id else \"&nbsp;\"\r\n    qemu_name = qemu_name if qemu_name else \"&nbsp;\"\r\n    qemu_mem = qemu_mem if qemu_mem else \"&nbsp;\"\r\n    qemu_cpus = qemu_cpus if qemu_cpus else \"&nbsp;\"\r\n    qemu_disk = qemu_disk if qemu_disk else \"&nbsp;\"\r\n\r\n    if \"running\" in qemu_status:\r\n        status_text = \"<tr class='\"'success'\"'><td>Running<\/td>\"\r\n    elif \"stopped\" in qemu_status:\r\n        status_text = \"<tr class='\"'danger'\"'><td>Stopped<\/td>\"\r\n    else:\r\n        status_text = \"<tr class='\"'other'\"'><td>{}<\/td>\".format(qemu_status)\r\n\r\n    vm_table += \"{}<td>{}<\/td><td>{}<\/td><td>{}<\/td><td>{}<\/td><td>{}<\/td><\/tr>\".format(\r\n        status_text, qemu_id, qemu_name, qemu_mem, qemu_cpus, qemu_disk\r\n    )\r\n\r\nprint(vm_table)\r\n')\r\nvm_table=\"$vm_table$qemu_table\"\r\n\r\n# Loop through each lxc and add the info to the table\r\nlxc_guests=$(pvesh get \/nodes\/localhost\/lxc --output-format=json)\r\n# Loop through each lxc and add the info to the table\r\nlxc_table=$(echo \"$lxc_guests\" | python3 -c '\r\nimport sys, json\r\n\r\n# Function to convert bytes to human readable format\r\ndef human_readable_size(size):\r\n    for unit in [\"B\", \"KB\", \"MB\", \"GB\", \"TB\", \"PB\", \"EB\", \"ZB\"]:\r\n        if size < 1024:\r\n            return f\"{size:.2f} {unit}\"\r\n        size \/= 1024\r\n\r\nlxc_guests = json.load(sys.stdin)\r\nvm_table = \"\"\r\n\r\nfor lxc in lxc_guests:\r\n    lxc_id = lxc[\"vmid\"]\r\n    lxc_name = lxc[\"name\"]\r\n    lxc_status = lxc[\"status\"]\r\n    # Convert the memory from bytes to GB\r\n    lxc_mem = human_readable_size(lxc[\"maxmem\"])\r\n    lxc_cpus = lxc[\"cpus\"]\r\n    # Convert the disk size from bytes to GB\r\n    lxc_disk = human_readable_size(lxc[\"maxdisk\"])\r\n\r\n    # Add HTML blank space if values are empty\r\n    lxc_id = lxc_id if lxc_id else \"&nbsp;\"\r\n    lxc_name = lxc_name if lxc_name else \"&nbsp;\"\r\n    lxc_mem = lxc_mem if lxc_mem else \"&nbsp;\"\r\n    lxc_cpus = lxc_cpus if lxc_cpus else \"&nbsp;\"\r\n    lxc_disk = lxc_disk if lxc_disk else \"&nbsp;\"\r\n\r\n    if \"running\" in lxc_status:\r\n        status_text = \"<tr class='\"'success'\"'><td>Running<\/td>\"\r\n    elif \"stopped\" in lxc_status:\r\n        status_text = \"<tr class='\"'danger'\"'><td>Stopped<\/td>\"\r\n    else:\r\n        status_text = \"<tr class='\"'other'\"'><td>{}<\/td>\".format(lxc_status)\r\n\r\n    vm_table += \"{}<td>{}<\/td><td>{}<\/td><td>{}<\/td><td>{}<\/td><td>{}<\/td><\/tr>\".format(\r\n        status_text, lxc_id, lxc_name, lxc_mem, lxc_cpus, lxc_disk\r\n    )\r\n\r\nprint(vm_table)\r\n')\r\nvm_table=\"$vm_table$lxc_table\"\r\n\r\n# Close the table\r\nvm_table=\"$vm_table<\/table>\"\r\n\r\n# Highlight the running and stopped VMs\r\nvm_table=$(echo \"$vm_table\" | sed 's\/<tr><td>running<\\\/td>\/<tr class=\"success\"><td>Running<\\\/td>\/')\r\nvm_table=$(echo \"$vm_table\" | sed 's\/<tr><td>stopped<\\\/td>\/<tr class=\"danger\"><td>Stopped<\\\/td>\/')\r\n\r\n# Save the table to the custom field\r\nif ! SetCustomField set \"$Custom_Field_Name\" \"$vm_table\"; then\r\n    echo \"Failed to save the Proxmox VM info to the custom field: $Custom_Field_Name\"\r\n    exit 1\r\nfi\r\necho \"The Proxmox VM info has been saved to the custom field: $Custom_Field_Name\"<\/pre>\n
 <\/p>\n\n
Greifen Sie auf \u00fcber 300 Skripte im NinjaOne Dojo zu.<\/p>\n
Zugang erhalten<\/a><\/p>\n<\/div>\n
Detailansicht<\/h2>\n
Das mitgelieferte Bash-Skript, mit dem Sie die Proxmox-VM-Informationserfassung automatisieren k\u00f6nnen, ruft den Status und wesentliche Informationen aller Proxmox-G\u00e4ste auf einem Host ab und speichert diese Daten in einem benutzerdefinierten Feld. Dies ist besonders n\u00fctzlich f\u00fcr Umgebungen mit zahlreichen VM, in denen manuelle Pr\u00fcfungen zeitaufw\u00e4ndig und fehleranf\u00e4llig sein k\u00f6nnen.<\/p>\n
Schritt-f\u00fcr-Schritt-Erl\u00e4uterung<\/h3>\n
1. Skriptinitialisierung und Parameterbehandlung:<\/h4>\n