Difference between revisions of "ProxCP Admin - Manage Nodes"
From ProxCP Documentation
| Line 3: | Line 3: | ||
This ProxCP admin feature allows you to add Proxmox nodes to ProxCP. Even if your Proxmox nodes are in a cluster, you must add each individual node here that you want to run VPS services on. | This ProxCP admin feature allows you to add Proxmox nodes to ProxCP. Even if your Proxmox nodes are in a cluster, you must add each individual node here that you want to run VPS services on. | ||
| − | This page allows you to add, view, and delete nodes. If you want to edit node details, you | + | This page allows you to add, view, and delete nodes. If you want to edit node details, you can click on the node's hostname in the table and edit the associated values. The table also shows whether a node is SSH-enabled or NAT-enabled. |
| + | |||
| + | A node cannot be deleted from ProxCP if it has active LXC/KVM/Public Cloud services on it. | ||
== Feature Overview == | == Feature Overview == | ||
| − | * '''Hostname:''' the FQDN of the Proxmox node | + | * '''Hostname:''' the FQDN of the Proxmox node, must be an actual DNS A record |
* '''Name:''' the name of the Proxmox node. This must match the node name within the Proxmox interface (upper left corner of the Proxmox GUI) | * '''Name:''' the name of the Proxmox node. This must match the node name within the Proxmox interface (upper left corner of the Proxmox GUI) | ||
* '''API Username:''' the username for the Proxmox user that ProxCP uses for API functions | * '''API Username:''' the username for the Proxmox user that ProxCP uses for API functions | ||
| Line 14: | Line 16: | ||
* '''Port:''' the port of the Proxmox GUI | * '''Port:''' the port of the Proxmox GUI | ||
* '''Location:''' the location of the Proxmox node. Currently, this is only used on the /nodes (Status) page | * '''Location:''' the location of the Proxmox node. Currently, this is only used on the /nodes (Status) page | ||
| − | |||
* '''CPU:''' the CPU model of the Proxmox node. Currently, this is only used on the /nodes (Status) page | * '''CPU:''' the CPU model of the Proxmox node. Currently, this is only used on the /nodes (Status) page | ||
| − | |||
* '''Backup Store:''' where should VPS backups be stored on this Proxmox node? The storage name here must match a storage name in Proxmox. | * '''Backup Store:''' where should VPS backups be stored on this Proxmox node? The storage name here must match a storage name in Proxmox. | ||
Note: the Proxmox node must have a valid, signed SSL certificate to work with ProxCP. A self-signed certificate will not work. | Note: the Proxmox node must have a valid, signed SSL certificate to work with ProxCP. A self-signed certificate will not work. | ||
Latest revision as of 16:29, 22 July 2020
Manage Nodes
This ProxCP admin feature allows you to add Proxmox nodes to ProxCP. Even if your Proxmox nodes are in a cluster, you must add each individual node here that you want to run VPS services on.
This page allows you to add, view, and delete nodes. If you want to edit node details, you can click on the node's hostname in the table and edit the associated values. The table also shows whether a node is SSH-enabled or NAT-enabled.
A node cannot be deleted from ProxCP if it has active LXC/KVM/Public Cloud services on it.
Feature Overview
- Hostname: the FQDN of the Proxmox node, must be an actual DNS A record
- Name: the name of the Proxmox node. This must match the node name within the Proxmox interface (upper left corner of the Proxmox GUI)
- API Username: the username for the Proxmox user that ProxCP uses for API functions
- API Password: the password for the Proxmox user that ProxCP uses for API functions
- Realm: the realm for the Proxmox user that ProxCP uses for API functions
- Port: the port of the Proxmox GUI
- Location: the location of the Proxmox node. Currently, this is only used on the /nodes (Status) page
- CPU: the CPU model of the Proxmox node. Currently, this is only used on the /nodes (Status) page
- Backup Store: where should VPS backups be stored on this Proxmox node? The storage name here must match a storage name in Proxmox.
Note: the Proxmox node must have a valid, signed SSL certificate to work with ProxCP. A self-signed certificate will not work.