New-PveNodesCephOsd

Create OSD

API: POST /nodes/{node}/ceph/osd, Proxmox VE API viewer

Syntax

New-PveNodesCephOsd
    [-PveTicket <PveTicket>]
    [-CrushDeviceClass <string>]
    [-DbDev <string>]
    [-DbDevSize <float>]
    -Dev <string>
    [-Encrypted <bool>]
    -Node <string>
    [-OsdsPerDevice <int>]
    [-WalDev <string>]
    [-WalDevSize <float>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-CrushDeviceClass	string	No	Set the device class of the OSD in crush.
-DbDev	string	No	Block device name for block.db.
-DbDevSize	float	No	Size in GiB for block.db.
-Dev	string	Yes	Block device name.
-Encrypted	bool	No	Enables encryption of the OSD.
-Node	string	Yes	The cluster node name.
-OsdsPerDevice	int	No	OSD services per physical device. Only useful for fast NVMe devices to utilize their performance better. Mutually exclusive with ‘db_dev’ and ‘wal_dev’.
-WalDev	string	No	Block device name for block.wal.
-WalDevSize	float	No	Size in GiB for block.wal.

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.