Set-PveNodesCephPool

Change POOL settings

API: PUT /nodes/{node}/ceph/pool/{name}, Proxmox VE API viewer

Syntax

Set-PveNodesCephPool
    [-PveTicket <PveTicket>]
    [-Application <string>]
    [-CrushRule <string>]
    [-MinSize <int>]
    -Name <string>
    -Node <string>
    [-PgAutoscaleMode <string>]
    [-PgNum <int>]
    [-PgNumMin <int>]
    [-Size <int>]
    [-TargetSize <string>]
    [-TargetSizeRatio <float>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Application	string	No	The application of the pool. Values: rbd, cephfs, rgw.
-CrushRule	string	No	The rule to use for mapping object placement in the cluster.
-MinSize	int	No	Minimum number of replicas per object.
-Name	string	Yes	The name of the pool. It must be unique.
-Node	string	Yes	The cluster node name.
-PgAutoscaleMode	string	No	The automatic PG scaling mode of the pool. Values: on, off, warn.
-PgNum	int	No	Number of placement groups.
-PgNumMin	int	No	Minimal number of placement groups.
-Size	int	No	Number of replicas per object.
-TargetSize	string	No	The estimated target size of the pool for the PG autoscaler.
-TargetSizeRatio	float	No	The estimated target ratio of the pool for the PG autoscaler.

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

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.