Proxmox Datacenter Manager - First Alpha Release

[batara.edward]

As stated in the initial release post, we require up-to-date Proxmox VE remotes. The metric export API endpoint was introduced in pve-manager 8.2.5, it seems like you are using a version older than that.

Hope this helps!

Hi thank you for the suggestion, after upgrading my PVE to 8.3.2 i can able to see the metric and the dashboard working as well

 

[Lukas Wagner]

Hi thank you for the suggestion, after upgrading my PVE to 8.3.2 i can able to see the metric and the dashboard working as well

Great, thanks for letting me know that everything works okay now

 

[bbgeek17]

Thank you for the great addition to PVE infrastructure.

We've installed PDM in our environment and connected it to two clusters, all nodes running:
pve-manager/8.3.2/3e76eec21c4a14a7 (running kernel: 6.8.12-1-pve)

When trying to migrate the VM between clusters we get the following error message in the Target Network field:

Error: api error (status = 400 Bad Request): api returned unexpected data - failed to parse api response

The storage portion is populated successfully.

Any suggestions?

Datacenter Manager 0.1.10

P.S. just realized that perhaps the fact that we are running PVE as instances in Openstack with Public/Private network may have something to do with it?

Public IP from PDM point of view: 172.22.1.142

Spoiler: ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether fa:16:3e:99:48:e2 brd ff:ff:ff:ff:ff:ff
altname enp0s3
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc noqueue state UP group default qlen 1000
link/ether fa:16:3e:99:48:e2 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.98/24 brd 10.0.0.255 scope global dynamic vmbr0
valid_lft 79339sec preferred_lft 79339sec
inet 192.168.100.11/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe99:48e2/64 scope link
valid_lft forever preferred_lft forever
4: ens7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc pfifo_fast state UP group default qlen 1000
link/ether fa:16:3e:b3:58:52 brd ff:ff:ff:ff:ff:ff
altname enp0s7
inet 10.1.0.216/24 brd 10.1.0.255 scope global dynamic ens7
valid_lft 79575sec preferred_lft 79575sec
inet6 fe80::f816:3eff:feb3:5852/64 scope link
valid_lft forever preferred_lft forever

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[tinduong1337]

It would be great if we have a centralised firewall for all Proxmox DCs in PDM.

 

[foxdeluxx_88]

Do you have set the permissions?

i think so...?! im connection with "root"

 

[RocketSam]

UPD: I've reinstalled DCM.

Upgrading proxmox-datacenter-manager:amd64 (0.1.8, 0.1.10), proxmox-datacenter-manager-client:amd64 (0.1.8, 0.1.10) made DCM non-functional due to:

systemctl list-units --failed
  UNIT                           LOAD   ACTIVE SUB    DESCRIPTION
● proxmox-datacenter-api.service loaded failed failed Proxmox Datacenter Manager API daemon

Reboot didn't change anything.

Unit log.

Jan 05 17:12:05 pm-dcm systemd[1]: Starting proxmox-datacenter-api.service - Proxmox Datacenter Manager API daemon...
Jan 05 17:12:05 pm-dcm proxmox-datacenter-api[797]: applied rrd journal (2 entries in 0.001 seconds)
Jan 05 17:12:05 pm-dcm proxmox-datacenter-api[797]: rrd journal successfully committed (0 files in 0.000 seconds)
Jan 05 17:12:05 pm-dcm proxmox-datacenter-api[797]: thread 'main' panicked at /usr/share/cargo/registry/proxmox-rest-server-0.8.5/src/connection.rs:154:38:
Jan 05 17:12:05 pm-dcm proxmox-datacenter-api[797]: called `Result::unwrap()` on an `Err` value: ErrorStack([Error { code: 167772350, library: "SSL routines", function: "SSL_CTX_check_private_key", reason: "no private key assigned", file:>Jan 05 17:12:05 pm-dcm proxmox-datacenter-api[797]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 05 17:12:05 pm-dcm systemd[1]: proxmox-datacenter-api.service: Main process exited, code=exited, status=101/n/a
Jan 05 17:12:05 pm-dcm systemd[1]: proxmox-datacenter-api.service: Failed with result 'exit-code'.
Jan 05 17:12:05 pm-dcm systemd[1]: Failed to start proxmox-datacenter-api.service - Proxmox Datacenter Manager API daemon.

 

[darthrater]

Whenever I click on the remote VM, it does not attach the suffix of the domain, causing a cert error. The search domain in defined.

 

[RocketSam]

I discovered DCM somehow gets a different serial for a host certificate. How is that possible?

Jan 05 18:56:29 pm-dcm proxmox-datacenter-api[1316]: bad fingerprint: 47:69:ef:da:f8:1d:9d:e9:ca:34:29:85:90:26:54:39:8e:6e:ad:7a:bc:b3:55:fe:a3:98:5a:6d:70:47:04:98
Jan 05 18:56:29 pm-dcm proxmox-datacenter-api[1316]: expected fingerprint: 0c:65:97:47:d1:c5:eb:02:54:e8:40:0f:09:1b:3d:bb:a7:ae:cc:9c:73:38:c5:06:8f:28:00:14:be:57:dd:75

None of the certificates has a serial 47:69:ef:da:f8:1d:9d:e9:ca:34:29:85:90:26:54:39:8e:6e:ad:7a:bc:b3:55:fe:a3:98:5a:6d:70:47:04:98