WZ-IT supports PDM introduction and multi-cluster management: installation, connections and agreed operational processes. Arrange a discussion.
This guide adds installation, remote connections and acceptance to the PDM fundamentals article. Reference: PDM documentation 1.1.7, October 2026. Steps are derived from vendor sources.
Contents
- Requirements and deployment model
- Install with ISO or on Debian
- Connect a remote and check connectivity
- Limit roles and access
- Repositories and updates
- Acceptance and operations
- Sources
Requirements and deployment model
The installation documentation distinguishes evaluation and recommended server specifications:
| Purpose | CPU | RAM | OS storage |
|---|---|---|---|
| Evaluation | x86-64, at least one core | 1 GiB | More than 10 GB |
| Recommended | Modern AMD/Intel 64-bit CPU, at least two cores | At least 4 GiB for the OS | 40 GB or more |
For production, the vendor also lists redundant storage and redundant multi-GBit/s network interfaces. Evaluation minimums are not production sizing. Our recommendation: record the number of remotes, intended functions and recovery path before provisioning.
For this procedure, we choose a separate management instance as a VM or dedicated host with access to remote management networks. LXC or Docker are not presented as equivalent standard methods: the documented proxmox-datacenter-manager-container-meta retains the existing kernel; that does not validate every community image and its operating model.
Install with ISO or on Debian
The vendor's recommended path is the official installation medium. Download the ISO, compare its checksum with the download listing and boot it on the intended system. Explicitly choose the target disk, network, hostname and administrative credentials. Before confirming, establish that the selected disk may be overwritten.
Alternatively, the vendor documents installation on Debian. After configuring matching Debian and PDM package sources, the regular meta-package also installs the Proxmox kernel:
apt update
apt install proxmox-datacenter-manager-meta
Do not copy sources and keys from instructions for another Debian release. The web interface is available at https://<pdm-address>:8443. Restrict access to the administration network.
Connect a remote and check connectivity
PDM manages PVE nodes, clusters and PBS instances as remotes. For the initial connection, we recommend an inventory and a limited evaluation scope:
- Record remote type, unique identifier, reachable API endpoint and responsible operator.
- Check API connectivity from the PDM instance. PVE typically uses 8006 and PBS 8007; allow the specific network path in the firewall.
- Enter the endpoint and appropriate credentials or API token in the remote dialog. Do not copy secrets into project records. The PDM CLI manual documents available options.
- Check TLS trust. For certificates without public trust, verify the fingerprint through an independent channel instead of accepting it without review.
- Compare inventory and metrics; only then check explicitly approved actions.
According to the remote documentation, PDM validates certificates against the system certificate store. Self-signed or privately issued certificates alternatively require a fingerprint. Certificate replacement may require updating that fingerprint.
Limit roles and access
PDM permissions are based on roles and paths. New users and tokens initially have no permissions. Auditor permits reading, while Administrator permits administrative actions on the assigned path. Tokens require their own ACL entries and cannot exceed their user's permissions.
Our recommendation: verify read-only access to the intended remote scope first, then grant only required actions. Document PDM permissions and remote API permissions separately. Resource visibility does not automatically establish eligibility for migration or changes.
Repositories and updates
PDM package sources distinguish enterprise, no-subscription and test. Enterprise is the recommended production channel with its own access requirements; no-subscription is accessible without a key but not recommended for production. Test is for evaluation.
The PDM FAQ specifies Administration > Updates or apt update and apt full-upgrade for minor updates. PDM has no dedicated subscription; enterprise access follows the subscription requirements of its remotes. The product page identifies AGPLv3 as its license. Before an update, we recommend reviewing the package plan and release notes and documenting configuration and recovery. Separately, PDM offers update management for PVE remotes. Cluster maintenance still requires its own procedure and acceptance.
Acceptance and operations
Recommended acceptance points: expected inventory, verified certificates, appropriate read and change permissions, traceable token management and documented recovery of the PDM instance. PDM replaces neither individual cluster quorum nor a backup. Cross-cluster migration is not automatic cross-site HA failover. Approve cross-cluster migration only after separately checking its prerequisites; a central overview alone does not establish migration eligibility.
Discuss PDM introduction: define remotes, permissions and operational scope.
