New-PveNodesCephInit

Create the initial Ceph default configuration and set up symlinks. Idempotent on re-call: if a [global] section already exists in ceph.conf, the existing fsid / auth / pool defaults are preserved and most parameters are silently ignored.

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

Syntax

New-PveNodesCephInit
    [-PveTicket <PveTicket>]
    [-ClusterNetwork <string>]
    [-DisableCephx <bool>]
    [-MinSize <int>]
    [-Network <string>]
    -Node <string>
    [-PgBits <int>]
    [-Size <int>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-ClusterNetwork	string	No	Declare a separate cluster network, OSDs will route heartbeat, object replication and recovery traffic over it.
-DisableCephx	bool	No	Disable cephx authentication. WARNING: cephx is a security feature protecting against man-in-the-middle attacks. Only consider disabling cephx if your network is private!
-MinSize	int	No	Minimum number of available replicas per object to allow I/O.
-Network	string	No	Use specific network for all ceph related traffic.
-Node	string	Yes	The cluster node name.
-PgBits	int	No	Placement group bits, used to specify the default number of placement groups. Depreacted. This setting was deprecated in recent Ceph versions.
-Size	int	No	Targeted number of replicas per object.

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.