New-PveClusterConfig
Generate new cluster configuration. If no links given, default to local IP address as link0.
API: POST /cluster/config, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveClusterConfig [-PveTicket <PveTicket>] -Clustername <string> [-LinkN <hashtable>] [-Nodeid <int>] [-TokenCoefficient <int>] [-Votes <int>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Clustername |
string |
Yes | The name of the cluster. |
-LinkN |
hashtable |
No | Address and priority information of a single corosync link. (up to 8 links supported; link0..link7) |
-Nodeid |
int |
No | Node id for this node. |
-TokenCoefficient |
int |
No | Coefficient used to determine Corosync’s token timeout. See the corosync.conf(5) manual for more details. |
-Votes |
int |
No | Number of votes for this node. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
