Single nodes question

[tdtmusic2]

Hello. This is not an issue, rather a question or a feature request, if possible. Can your app have one conection profile with multiple SINGLE nodes? As in not a cluster? It would be so easy to have an overall look at all nodes without having to create a connection profile for each one, since they're not in clusters.

Thank you!

[devnullvoid]

Hey, thanks for the question/feature request. Implementing a "multi-node" profile would be a bit complex. We'd need to handle multiple API clients alive at the same time, merged inventories, error handling per node, etc.

Does Proxmox Datacenter Manager work for your use case? I imagine it does. It may be a useful for me to reference in implementing this feature.

[tdtmusic2]

Hey, thanks for the question/feature request. Implementing a "multi-node" profile would be a bit complex. We'd need to handle multiple API clients alive at the same time, merged inventories, error handling per node, etc.

Does Proxmox Datacenter Manager work for your use case? I imagine it does. It may be a useful for me to reference in implementing this feature.

Hello. Thank you for your answer. Yes, PDM works fine in my scenario, there are about 13 single nodes added in it and no issues yet. But I would love to use your terminal instead, with all the nodes into a single configuration. At first, from the screenshots, I thought that's how it works, I missed the Cluster label :)
As a separate question, does the terminal have some sort of "read-only" mode? Where you can just view nodes & guests info but you are not allowed to do any potential damage?

[devnullvoid]

thanks for the details! For now, you can add multiple connection profiles and swap between as needed, but I will look into adding support for a multi-cluster/multi-node "overview" mode.

No "read-only" mode currently, but that is also a good idea. We should be able to use Proxmox's permissions/roles API to to do this -- enabling/disabling functionality depending on what permissions the user has.

[ocafebabe]

+1 for multiple single-node support.

[devnullvoid]

Since the Proxmox API considers even a standalone node as a "cluster" I'm thinking I'll implement this by adding an aggregate field to the connection profile, which can be used to group them together. Then we will need an API client for each profile and state tracking/routing to each one.

I'm working on a full implementation plan. I'll also need to spin up some nested nodes for testing.

[devnullvoid]

@tdtmusic2 and @ocafebabe would you be willing to assist with testing this feature? I can have something ready for testing very soon.

[tdtmusic2]

@tdtmusic2 and @ocafebabe would you be willing to assist with testing this feature? I can have something ready for testing very soon.

Sure, anytime. I can test on Windows and Alma 10 for now.

[ocafebabe]

@devnullvoid yes, of course. Very eager to test this!

[devnullvoid]

awesome! I've just pushed what I have so far to the develop branch. You can install with go install github.com/devnullvoid/pvetui/cmd/pvetui@develop

Then you should be able to add a group name in your config file to each profile you want to group together:

profiles:
    pve1:
        addr: https://192.168.99.201:8006
        user: root
        password: ""
        token_id: ""
        token_secret: ""
        realm: pam
        api_path: /api2/json
        insecure: true
        ssh_user: root
        vm_ssh_user: ""
        aggregate: test-group
    pve2:
        addr: https://192.168.99.202:8006
        user: root
        password: ""
        token_id: ""
        token_secret: ""
        realm: pam
        api_path: /api2/json
        insecure: true
        ssh_user: root
        vm_ssh_user: ""
        aggregate: test-group