Proxmox Datacenter Manager - First Alpha Release
- Thread starter t.lamprecht
- Start date
Hi team,
It could be very useful to join from PVE/Cluster to PDM (on cloud for istance) instade of from PDM to PVE/Cluster, avoiding annoing IN firewall rules.
It could be very useful to join from PVE/Cluster to PDM (on cloud for istance) instade of from PDM to PVE/Cluster, avoiding annoing IN firewall rules.
Just installed it, as I manage many clusters, mine and my customers. I am connected with a permanent VPN to my customers, so the Proxmox servers are easy to reach. I currently keep open tabs in my browser to every cluster to be able to see them easily. So this datacenter seemed a good idea.
I proceed to add my first server (remote id), which sees all servers in the cluster and adds them as endpoints, but adds the probe remote itself too! I have to delete this server in double. It created properly the remote and now I see all the servers in the cluster, but what if the remote server is down? So I added a second remote ID, but it sees the same servers of the cluster and adds them in endpoints. Now all Proxmox servers are in double. So at this point I am unsure how to configure this properly.
I then tried to add a remote id with a customer's server, but on the last step it returns "api error (status = 400 Bad Request): parameter verification errors id: value does not match the regex pattern".
It's a fail for me, hope it could be easier to integrate a cluster and distant servers to it.
I proceed to add my first server (remote id), which sees all servers in the cluster and adds them as endpoints, but adds the probe remote itself too! I have to delete this server in double. It created properly the remote and now I see all the servers in the cluster, but what if the remote server is down? So I added a second remote ID, but it sees the same servers of the cluster and adds them in endpoints. Now all Proxmox servers are in double. So at this point I am unsure how to configure this properly.
I then tried to add a remote id with a customer's server, but on the last step it returns "api error (status = 400 Bad Request): parameter verification errors id: value does not match the regex pattern".
It's a fail for me, hope it could be easier to integrate a cluster and distant servers to it.
Last edited:
when i added a cluster it added the cluster overall, and each of the three nodes, one deletes the cluster node and renames the 3 nodes to the FQDN - it did not double add every node in the cluster for me - if you were adding one node clusters i could see how this would like double. its still a funky process - nut remember this is alpha!
would love an option where the node connects out to the datacenter manager - for remote notes that may not have access from the outside world
very nice start guys, thanks a lot
using proxmox for a long time for a small companies to virtualize windows servers with regular backups, its very convenient to have centralized remote logs for me.
PS: its a bit annoying to see THIS big warning about luck of subscription. I understand your concerns but it making interface pretty unusable indeed. I know for myself I'm using community edition, thanks
using proxmox for a long time for a small companies to virtualize windows servers with regular backups, its very convenient to have centralized remote logs for me.
PS: its a bit annoying to see THIS big warning about luck of subscription. I understand your concerns but it making interface pretty unusable indeed. I know for myself I'm using community edition, thanks
Even small companies should be able to afford a community subscription. But even if not: One click and the popup is closed so "unusable" is a bit of a stretch in my book.its a bit annoying to see THIS big warning about luck of subscription. I understand your concerns but it making interface pretty unusable indeed. I know for myself I'm using community edition, thanks
Last edited:
in pdm there is pretty big warning in the center of interface
and its not a popup. But generally I agree with youWell PDM is still an alpha version so why would you use it in mission-critical production environments?!?in pdm there is pretty big warning in the center of interface
because its not a mission-critical production of course its a near-hobby servers for small businesses with regular backing up so thats a nice playground to see how its looks like.
its a near-hobby servers for small businesses with regular backing up so thats a nice playground to see how its looks like.Most probably your pve-ssl.pem certificate has been renewed on the host, and you should update the configuration with the new fingerprint
Suggestion, add support for more fields on Certificates → Challenge Plugins:
PowerDNS Example:
My PowerDNS setup requires both a username/password in addition to the
The above is a sanitized version of my auth file for the standalone certbot powerdns plugin.
Having support for all these fields is necessary for setups like mine. Without it, we are forced to use the standalone certbot with for handling renewals with a --deploy-hook to handle to move the certificate into place and restart
Thanks for your time and effort on this tool. It has already helped us greatly with merging some of our data centers in cross datacenter migrations!
PowerDNS Example:
My PowerDNS setup requires both a username/password in addition to the
PDNS_Token which is called `dns_powerdns_api_url` in the certbot powerdns plugin auth file. e.g.:
INI:
# PowerDNS API URL
dns_powerdns_api_url = http://my.power.dns.server.com:8081
# PowerDNS API Key (from X-API-Key header)
dns_powerdns_api_key = MY_PDNS_API_KEY
# PowerDNS Basic Auth Username
dns_powerdns_username = WEB_AUTH_USERNAME
# PowerDNS Basic Auth Password
dns_powerdns_password = WEB_AUTH_PASSWORD
# Optional: Server ID (usually 'localhost' unless you have a specific setup)
dns_powerdns_server_id = SERVER_IDThe above is a sanitized version of my auth file for the standalone certbot powerdns plugin.
Having support for all these fields is necessary for setups like mine. Without it, we are forced to use the standalone certbot with for handling renewals with a --deploy-hook to handle to move the certificate into place and restart
proxmox-datacenter-api service. Thanks for your time and effort on this tool. It has already helped us greatly with merging some of our data centers in cross datacenter migrations!
Related to comment https://forum.proxmox.com/threads/proxmox-datacenter-manager-first-alpha-release.159323/post-731260 regarding qm remote-migrate and this bugzilla request https://bugzilla.proxmox.com/show_bug.cgi?id=4928
BR
Bjørn
I am trying to figure out how this works. Do you have an example for the qm remote-migrate command where I can specify that the remote-migration shouldn't migrate the storage (Ceph/RBD). Given I interpreted the comment correctly!
BR
Bjørn
Integrating something like this in PVE would \ should handle basic load balancing :https://github.com/cvk98/Proxmox-load-balancer but maybe it could be done via the API better?
I am trying to figure out how this works. Do you have an example for the qm remote-migrate command where I can specify that the remote-migration shouldn't migrate the storage (Ceph/RBD). Given I interpreted the comment correctly!
that's not yet implemented - it requires adding the "remote" part to our replication feature.
Hi everyone,
I just wanted to say a big thank you to the Proxmox team for the amazing work you’ve done with the Proxmox Datacenter Manager (PDM). I’ve been testing it recently and I honestly think it’s a fantastic step forward, we manage multiple remote Proxmox nodes across our clients via a mesh VPN and has never been easier!
I know it’s still in early alpha and development takes time, but I was wondering if there's any rough estimate on when we might see a new alpha or even a beta release? It’s been about six months since the last update, and I’m really eager to keep testing and following the progress.
Thanks again for all the hard work!
I just wanted to say a big thank you to the Proxmox team for the amazing work you’ve done with the Proxmox Datacenter Manager (PDM). I’ve been testing it recently and I honestly think it’s a fantastic step forward, we manage multiple remote Proxmox nodes across our clients via a mesh VPN and has never been easier!
I know it’s still in early alpha and development takes time, but I was wondering if there's any rough estimate on when we might see a new alpha or even a beta release? It’s been about six months since the last update, and I’m really eager to keep testing and following the progress.
Thanks again for all the hard work!
I thougt about a view/report to on the one hand side have a kind of Systemdokumentation and on the other side to have a current healt state report usable to compare states between changen and as an information source for tuning, troubleshooting etc.
like RVtools for VMware