Skip to main content

Synchronize Proxmox Virtual Environment (PVE) information to a NetBox instance

Project description

netbox-pve-sync

Synchronize Proxmox Virtual Environment (PVE) information to a NetBox instance. This allows automatic tracking of Virtual Machines, disks, IP addresses/prefixes, MAC addresses, VLANs, ...

How does it work?

This script work by pulling VMs information from the PVE API and create/update/delete resources on NetBox.

Installation

This package is available on PyPi. You can install it using pip.

$ pip install netbox-pve-sync

Configuration

On NetBox

You'll need to create a dedicated user (ex: netbox-pve-sync) on your NetBox instance and then create a write API token.

The following env variables will need to be set:

  • NB_API_URL: The URL to your NetBox instance. (ex: https://netbox.example.org)
  • NB_API_TOKEN: The token created previously. (ex: f74cb99cf552b7005fd1a616b53efba2ce0c9656)

You'll also need to perform a minimal configuration on NetBox:

  • Create the physical nodes hosting the cluster. (The name should match the one on Proxmox, so that the script can correctly link the VMs to the physical host)
  • Create the cluster.
  • Add the following Custom Fields:
Name Object types Label Type
autostart Virtual Machine Autostart Boolean
replicated Virtual Machine Replicated Boolean
ha Virtual Machine Failover Boolean
backup Virtual Disk Backup Boolean
dns_name Prefix DNS Name Text

On the PVE API

You'll need to create a dedicated user (ex: netsync) on your PVE cluster and then create an API token.

The user needs to have access to the VM.Monitor, Pool.Audit, VM.Audit, Sys.Audit permissions.

The following env variables will need to be set:

  • PVE_API_HOST: The DNS/IP to your PVE instance. (ex: 10.10.0.10)
  • PVE_API_USER: The username of the account created previously. (ex: netsync@pve)
  • PVE_API_TOKEN: The name of the API token created previously. (ex: test-token)
  • PVE_API_SECRET: The API token created previously (ex: 4d46dc0a-6363-47a2-98df-d5cdfefa33d2)

Executing the script

You can then execute the script using the following command:

PVE_API_HOST=xx PVE_API_USER=xx PVE_API_TOKEN=xx PVE_API_SECRET=xx NB_API_URL=xx NB_API_TOKEN=xx python3 -m netbox_pve_sync

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

netbox_pve_sync-0.2.1.tar.gz (18.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

netbox_pve_sync-0.2.1-py3-none-any.whl (18.8 kB view details)

Uploaded Python 3

File details

Details for the file netbox_pve_sync-0.2.1.tar.gz.

File metadata

  • Download URL: netbox_pve_sync-0.2.1.tar.gz
  • Upload date:
  • Size: 18.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.3

File hashes

Hashes for netbox_pve_sync-0.2.1.tar.gz
Algorithm Hash digest
SHA256 6337fc0726791d753f7cfa63199023cd772e0b4f80a598c81861b806594c6cd3
MD5 7d3da97a085da62cd0bd758066490caf
BLAKE2b-256 eb3d6859cffd4d873ab177682deb75881fd8e8ead6da144008b0d936b6a811bc

See more details on using hashes here.

File details

Details for the file netbox_pve_sync-0.2.1-py3-none-any.whl.

File metadata

File hashes

Hashes for netbox_pve_sync-0.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 ffcc174cc9e035f3adf0be757795c84e6c85b59b2f6f9472ac48f7d3f006f9ab
MD5 044ed4a58367a26b66402554acbda227
BLAKE2b-256 e5f0199a2240f12d27561d333f92a63b909ec9fc6d651bc7d70c33dd62e7f58d

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page