--- Begin Message ---
Hi,
December 6, 2022 4:47 PM, "Aaron Lauterer" <a.laute...@proxmox.com> wrote:
> To get more details for a single OSD, we add two new endpoints:
> * nodes/{node}/ceph/osd/{osdid}/metadata
> * nodes/{node}/ceph/osd/{osdid}/lv-info
As an idea for a different name for lv-info,
`nodes/{node}/ceph/osd/{osdid}/volume`? :)
>
> The {osdid} endpoint itself gets a new GET handler to return the index.
>
> The metadata one provides various metadata regarding the OSD.
>
> Such as
> * process id
> * memory usage
> * info about devices used (bdev/block, db, wal)
> * size
> * disks used (sdX)
> ...
> * network addresses and ports used
> ...
>
> Memory usage and PID are retrieved from systemd while the rest can be
> retrieved from the metadata provided by Ceph.
>
> The second one (lv-info) returns the following infos for a logical
> volume:
> * creation time
> * lv name
> * lv path
> * lv size
> * lv uuid
> * vg name
>
> Possible volumes are:
> * block (default value if not provided)
> * db
> * wal
>
> 'ceph-volume' is used to gather the infos, except for the creation time
> of the LV which is retrieved via 'lvs'.
You could use lvs/vgs directly, the ceph osd relevant infos are in the lv_tags.
`lvs -o lv_all,vg_all --reportformat=json`
`vgs -o vg_all,pv_all --reportformat=json`
Why do you want to expose the lv-info?
Cheers,
Alwin
--- End Message ---
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
