Proxmox Datacenter Manager - First Alpha Release

[nettacompany]

root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui

 

[t.lamprecht]

- I couldn't connect to the PVE Cluster even with the cert fingerprint. I had to add the RootCA-cert to the trusted certificates in linux (update-ca-certificates). Then it worked.

And just to be sure, you really used the fingerprint of the certificate that the main API daemon from that PVE node uses?

I.e. what you see when you execute the following from a host in your network, with the HOSTNAME-OR-IP part being replaced with the respective value:

openssl s_client -connect HOSTNAME-OR-IP:8006 < /dev/null 2>/dev/null | openssl x509 -fingerprint -sha256 -noout -in /dev/stdin

 

[t.lamprecht]

that's the ID of the remote you give in the wizard, maybe we have to make that part more clear (it's the 'Remote ID' field)

Showing the cluster name somewhere in that view could be nice nonetheless.

 

[t.lamprecht]

root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui

Did you add the PDM repo and executed apt update ?

1. Add the PDM apt repository to your host:
   deb http://download.proxmox.com/debian/pdm bookworm pdm-test
2. Refresh the package index:
   apt update
3. Install the main packages:
   apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui

 

[nettacompany]

Yes repo add and update command

root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui

 

[KevinS]

Yes repo add and update command

root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui

Please also post your apt update output

 

[nettacompany]

Please also post your apt update output

root@datacenter:~# apt update
Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B]
Get:4 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B]
Get:7 http://download.proxmox.com/debian/pdm bookworm InRelease [1951 B]
Hit:2 https://deb.debian.org/debian bookworm InRelease
Hit:3 https://deb.debian.org/debian bookworm-updates InRelease
Err:7 http://download.proxmox.com/debian/pdm bookworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1140AF8F639E0C39
Hit:5 https://deb.debian.org/debian bookworm-backports InRelease
Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease
Reading package lists... Done
W: GPG error: http://download.proxmox.com/debian/pdm bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1140AF8F639E0C39
E: The repository 'http://download.proxmox.com/debian/pdm bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui
root@datacenter:~# dpkg --configure -a
root@datacenter:~# nano /etc/apt/sources.list
root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui
root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager
root@datacenter:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proxmox-datacenter-manager
E: Unable to locate package proxmox-datacenter-manager-ui
root@datacenter:~#

 

[JensF]

I quickly added another SSD to my second PVE with an additional ZFS storage to test the migration, but with some manual changes in the VM config like -acpitable I got following error:

2024-12-19 16:12:22 ERROR: error - tunnel command '{"firewall-config":null,"conf":"agent: 1\nargs: -acpitable file=/PM1735/w11slic_table\nbios: ovmf\nboot: order=scsi0;sata0\ncores: 4\ncpu: host\nefidisk0: ZFS:vm-106-disk-0,efitype=4m,pre-enrolled-keys=1,size=528K\nlock: migrate\nmachine: pc-q35-9.0\nmemory: 4096\nmeta: creation-qemu=8.0.2,ctime=1698242142\nname: W11-Test\nnet0: virtio=46:2D:82:23:64:29,bridge=vmbr0,firewall=1\nnuma: 0\nostype: win11\nrng0: source=/dev/urandom\nsata0: none,media=cdrom\nscsi0: ZFS:vm-106-disk-1,cache=writeback,discard=on,iothread=1,size=120G,ssd=1\nscsihw: virtio-scsi-single\nsmbios1: uuid=<<ID>>,manufacturer=<<SFA>>,product=<<Product ID>>==,serial=<<SN>>==,sku=<<SKU>>=,family=<<Fam.>>,base64=1\nsockets: 1\nstartup: order=5\ntpmstate0: ZFS:vm-106-disk-2,size=4M,version=v2.0\nvmgenid: 70599aa7-080c-450e-89ff-81a3c8d42f7f\n","cmd":"config"}' failed - failed to handle 'config' command - only root can set 'rng0' config

Edit: In that case above that random device was making trouble but after removing it came up with this:

2024-12-19 17:06:09 ERROR: error - tunnel command '{"cmd":"config","conf":"agent: 1\nargs: -acpitable file=/PM1735/w11slic_table\nbios: ovmf\nboot: order=scsi0;sata0\ncores: 4\ncpu: host\nefidisk0: ZFS:vm-106-disk-0,efitype=4m,pre-enrolled-keys=1,size=528K\nlock: migrate\nmachine: pc-q35-9.0\nmemory: 4096\nmeta: creation-qemu=8.0.2,ctime=1698242142\nname: W11-Test\nnet0: virtio=46:2D:82:23:64:29,bridge=vmbr0,firewall=1\nnuma: 0\nostype: win11\nsata0: none,media=cdrom\nscsi0: ZFS:vm-106-disk-1,cache=writeback,discard=on,iothread=1,size=120G,ssd=1\nscsihw: virtio-scsi-single\nsmbios1: uuid=<<ID>>,manufacturer=SFA=,product=<<Product>>,serial=<<SN>>,sku=<<SKU>>,family=<<Family>>,base64=1\nsockets: 1\nstartup: order=5\ntpmstate0: ZFS:vm-106-disk-2,size=4M,version=v2.0\nvmgenid: 70599aa7-080c-450e-89ff-81a3c8d42f7f\n","firewall-config":null}' failed - failed to handle 'config' command - only root can set 'args' config

 

[eXtremeSHOk]

via the gui, unable to add the domain to acme. button does not activate.

as a workaround, use acme.sh, the cert/key files are:
fullchain-file /etc/proxmox-datacenter-manager/auth/api.pem
key-file /etc/proxmox-datacenter-manager/auth/api.key

 

[t.lamprecht]

Reading package lists... Done
W: GPG error: http://download.proxmox.com/debian/pdm bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1140AF8F639E0C39

You also need to download our release key if this is a plain Debian installation and not a Proxmox based system already:
wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg

I clarified that in the initial post.

 

[nettacompany]

You also need to download our release key if this is a plain Debian installation and not a Proxmox based system already:
wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg

I remove it and test it.

You also need to download our release key if this is a plain Debian installation and not a Proxmox based system already:
wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg

I clarified that in the initial post.

I remove it and test it.

 

[jknight-ns]

This looks great, just starting to play around with it and so far so good. The announcement states that remotes should be running Proxmox VE 8.3. Are there any plans to support older VE releases, even if it's a limited set of features or even read only? Or do you plan to keep a minimum VE version requirement upon release of 1.0?

 

[t.lamprecht]

This looks great, just starting to play around with it and so far so good. The announcement states that remotes should be running Proxmox VE 8.3. Are there any plans to support older VE releases, even if it's a limited set of features or even read only? Or do you plan to keep a minimum VE version requirement upon release of 1.0?

The Proxmox VE 8 series is currently the only one with active support, all older series are end of life:
https://pve.proxmox.com/pve-docs/chapter-pve-faq.html#faq-support-table

The PDM requires some PVE API features that are relatively new, so older than latest 8.3 will probably not happen.
We did not make a final decision for how to handle supported releases yet, but I think it's safe to say that there will be some backward compatibility, but all outside of the currently supported release series might be only supported at a best-effort basis.
As we do not have a lot of churn in the API and do not actively break things this could be pretty tolerating w.r.t. older releases that are newer than 8.3 in practice.

 

[pneubert]

Good work! I'm just testing what is already working and what isn't. I tried to secure the Manager with Let's Encrypt SSL, but unfortunately, it doesn't seem to work yet because I can't add the ACME domain. The button, unfortunately, doesn't become active.

 

[nettacompany]

add button inactive

 

[ceelight]

New one: If I add a cluster, it shows the cluster nodes without FQDN. And one is double with FQDN. Adding it like this is impossible (DNS fails). So I have to add FQDN to all nodes and delete the double entry.

 

[t.lamprecht]

Good work! I'm just testing what is already working and what isn't. I tried to secure the Manager with Let's Encrypt SSL, but unfortunately, it doesn't seem to work yet because I can't add the ACME domain. The button, unfortunately, doesn't become active.
View attachment 79444

I could reproduce this, it's broken for the http-challenge mode. I pushed a fix into git, should work with the next package bumps (Soon™).

Fix should be available with proxmox-datacenter-manager-ui version 0.1.9

 

[t.lamprecht]

New one: If I add a cluster, it shows the cluster nodes without FQDN. And one is double with FQDN. Adding it like this is impossible (DNS fails). So I have to add FQDN to all nodes and delete the double entry.

View attachment 79448
View attachment 79449

Yeah, this is not yet ideal and a known pain point – we'll try to improve the experience here over the next weeks; albeit, holiday season is coming up, so maybe you need to hit delete for a little but more – it's "only" once per remote addition.

 

[roo82]

VM migrations between two standalone servers (not in a cluster) with the same shared storage mounted (an NFS mount backed by a ZFS dataset on a TrueNAS server) appear to duplicate the VM disk and copy all the data into the duplicate. It would be nice if migrations with the same shared storage could just migrate the active state of the VM, as in RAM and CPU exection, and then reattach the existing disk on the migrated to node since the underlying storage is the same.

Overall though this is a really cool development, thanks for all the work on this!

 

[egrueda]

Christmas came one week earlier this year
This is gonna be a great, grat software.
Thank you very much!