Proxmox Datacenter Manager - First Alpha Release

@jpass022
it can happen, check the file /etc/proxmox-datacenter-manager/remotes.cfg on your PDM and remove it there manually, after that you can readd the token.
another way: (not clean) on your pve you generate a new token with a different name.

on the short hand i cant find the actual bug-report, but IIRC i found one, when i had the same error a few weeks ago. feel free to file a new bug report.
 
Last edited:
  • Like
Reactions: jpass022
@jpass022
it can happen, check the file /etc/proxmox-datacenter-manager/remotes.cfg on your PDM and remove it there manually, after that you can readd the token.
another way: (not clean) on your pve you generate a new token with a different name.

on the short hand i cant find the actual bug-report, but IIRC i found one, when i had the same error a few weeks ago. feel free to file a new bug report.
Opened the file /etc/proxmox-datacenter-manager/remotes.cfg. There was no entry present for the node that I removed and I'm trying to reconnect.
Changing the "API Token Name" allowed me to reconnect the node to PDM. So I imagine when a remote is removed, the entry wherever the "API Token Name" is stored is not removed...
 
When I navigate to the "Shell" page in PDM, there is no prompt; After approximately 18 seconds, the prompt appears. PVE Shell doesn't behave the same, prompt appears in less than a second.
 
Opened the file /etc/proxmox-datacenter-manager/remotes.cfg. There was no entry present for the node that I removed and I'm trying to reconnect.
Changing the "API Token Name" allowed me to reconnect the node to PDM. So I imagine when a remote is removed, the entry wherever the "API Token Name" is stored is not removed...
the api token is stored on the cluster itself and does not get removed it seems when you remove a node.
you can find it under Datacenter -> Permissions -> API-Tokens
 
the api token is stored on the cluster itself and does not get removed it seems when you remove a node.
you can find it under Datacenter -> Permissions -> API-Tokens
Thats right, but on the PDM the remote is stored and when the remote is removed via gui, it is sometimes not cleaned from the config files, so you can't readd it again. For me it was the above file.
Can we eventually add Proxmox Backup Server to PDM?
it will be added in future. this is an alpha version of PDM, a technical preview.
here is the roadmap: https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap
 
Tried it today. Looks really good. Added some v8 and v7 single proxmox boxes.

I still have 2 v6.2 & 6.4 proxmox too, there i get an error 400 on login. Though I can easily migrate them with it

moving VMs between non cluster members is cool.
 
Last edited:
I added some nodes and 2 clusters. When trying to migrate a vm from 8.3.0 single node to 8.3.2 cluster i can select the cluster, but not the target node of it and on clicking migrate i get

api error (status = 400 Bad Request): api error (status = 501 Not Implemented):
 
I've installed the last version, and after successful login, I'm back to login screen. Can't do any action. Always back to login screen. Any idea?
 
I added some nodes and 2 clusters. When trying to migrate a vm from 8.3.0 single node to 8.3.2 cluster i can select the cluster, but not the target node of it and on clicking migrate i get

api error (status = 400 Bad Request): api error (status = 501 Not Implemented):
Got that one fixed. I needed to add the fingerprint of the pveproxy-ssl-pem . using a letsencrypt there.
Also I missed updating to 0.1.11 which is done now.
 
Last edited:
I've installed the last version, and after successful login, I'm back to login screen. Can't do any action. Always back to login screen. Any idea?
Datetime on server was incorrect. Now I can login & play with my servers in my homelab. #proxmox
 
There is a small bug when migrating a vm and not deleting the source. It stays locked: migrate and one must manually remove the line from the VM's config on the source node
 
  • Like
Reactions: KMJ
Hi all. I'm trying to modify the code of the Datacenter Manager to add a new functionality like order the nodes and clusters in custom folders, to have it more organised. How can I modify the code to get this feature?
 
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
In general i wish all the proxmox products would move to using/displaying the full fqdn and not just hostname.

we have a naming convention of pveXX.clustername.sitecode.domain.tld

so we have lots of duplicate pveXX node names but if they show the full fqdn it makes perfect sense.
 
I concur that space for scrolling through VMs/containers is kind of limited. Another option might be allow to scroll some of the "Remote" and "Allocation" information out of view. Or make the different parts of them fold-able. I probably do not need generic cluster information in view when migrating VMs. I think having those parts fold-able would be a good first step to increase usability of the VM list a lot.
+1 on this.
when using a laptop without a lot of vertical space the view is extremely limited.
being able to fold up the section above would help
 
We have added a large cluster to our PDM test instance. were planning to add two more nodes to the PVE cluster next week.
What steps need to be performed to make PDM aware of / support additional new nodes in an existing cluster in PDM
 
Not totally related to this but adding tags to the nodes would be a nice feature. We have several nodes and the color codes would be helpful
 
  • Like
Reactions: JoelPmm
I'm looking for an answer to this question, too. Did you find one?
you need to use the CLI (proxmox-datacenter-manager-client) - but see my response way earlier in the thread - those are neither guaranteed to be fully implemented yet, nor to stay as they are!
 
  • Like
Reactions: A Hettinger