Proxmox Datacenter Manager - First Alpha Release

Hi to the Proxmoxlers :)

Is the development still in progress or paused / canceled?
I ask because no updates come for a some weeks / one month I think and before there were coming updates almost weekly.
 
  • Like
Reactions: Taomyn
didn't read every page, but this is looking great. Can't wait to see the next milestone release.
 
m-electronics said:
Hi to the Proxmoxlers :)

Is the development still in progress or paused / canceled?
I ask because no updates come for a some weeks / one month I think and before there were coming updates almost weekly.
Click to expand...
neither paused nor canceled, just a bit slowed down as we cannot just focus on PDM ;)

see https://lore.proxmox.com/pdm-devel/ if you want to follow in-flight patches and discussions
 
  • Like
Reactions: BinaryCrash, m-electronics, syadnom and 1 other person
you'd need to apply them yourself and build the packages..
 
very cool tool.
Are there any plans to add a report function like RVTools for VMware?

f.e. an exportable view over
- VMs: Name, Datacenter, Cluster, PVENode, CPU, Mem, Disk, OS, Network, virtIO Tool, Snapshots, setc.
- Nodes: Name, CPU, Cores, Speed, RAM, local DISK capacity, Networkinterfaces, Info,PVE version, HW Vendor information (Type, Model, Serial number)
- VMStorage; Type (local, NAS, SAN, NFS), Size, LUN/WWN Info Available size and consumed size
- Health:
tbc.

Regards Rainer
 
  • Like
Reactions: mentalinc
t.lamprecht said:
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:
Code: 
openssl s_client -connect HOSTNAME-OR-IP:8006 < /dev/null 2>/dev/null | openssl x509 -fingerprint -sha256 -noout -in /dev/stdin
Click to expand...
Long ago and I wanted to give it try again. Today I stumbled over this again. The fingerprint I used is exactly the one of the openssl command. I get "api error (status = 400: error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1889:"

After installing the respective Root CA cert it works out of the box.

DCM 0.1.11
 
Adding a new PVE-Cluster doesn't work anymore for me. Whatever I do, I always get a:

Code: 
api error (status = 400: parameter verification errors id: value does not match the regex pattern)

I tried root, my LDAP User, my PVE User. With existing token, with token creation. It's always the same error. I don't know what I'm doing wrong. Any hints?
 
At the end of the day, you are going into the vCenter direction, or just creating your own "vision" of managing Proxmox clusters? Could you post your final PDM conception? Just in few words.
 
Very interesting.

One question - if you're running a single small cluster, i.e a typical homelab or SMB setup, is there much advantage to using Datacenter over the std cluster UI, or is it more aimed at large multiple cluster setups?
 
blackpaw said:
One question - if you're running a single small cluster, i.e a typical homelab or SMB setup, is there much advantage to using Datacenter over the std cluster UI, or is it more aimed at large multiple cluster setups?
Click to expand...
One advantage of the datacenter is that you don't need a cluster to have all in one ui, which avoids issues with broken clusters due to network latency issues.
 
  • Like
Reactions: blackpaw
Johannes S said:
One advantage of the datacenter is that you don't need a cluster to have all in one ui, which avoids issues with broken clusters due to network latency issues.
Click to expand...

Ah, so even if cluster quorum is broken, you can access individual nodes via the DC UI? That is useful.
 
blackpaw said:
Ah, so even if cluster quorum is broken, you can access individual nodes via the DC UI? That is useful.
Click to expand...
No! But if you have the datacenter, you don't need clusters just to have all pve hosts in one ui. So the idea is that instead of one cluster with two or three nodes you would have all three nodes as three single-node "clusters" together in the dc ui
 
  • Like
Reactions: blackpaw
You must log in or register to reply here.
Top Bottom