Re: [pve-devel] [PATCH manager] report: filter comments in VM/CT configs

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Am 28/12/2022 um 15:18 schrieb Stefan Sterz:
> maybe somewhat off-topic for the patch at hand, but it might be nice to
> modularize the pve report. so that `pvereport` gives you a default set
> of information, but you could also use `pvereport ha` to give you more
> information specifically about the state of the ha manager or `pvereport
> ceph` for information about ceph etc.
> 
> maybe paired with a verbose flag so that you could request more detailed
> info. e.g. `pvereport zfs` gives the zfs information currently in the
> report, but `pvereport zfs -v` could also include `arc_summary` and `cat
> /sys/module/zfs/parameters/zfs_arc_max` and other less often needed but
> sometimes useful information.
> 
> this might be handy especially in cases where you need information that
> spans several files/commands that aren't always needed. it might make
> the `pvereport` more useful in the forum too, where we currently can't
> use it at all because it discloses too much information.
> 
I'd rather keep it simple and not blow it up too much with a massive amount of
switches, lots of topics are very intertwined, e.g., ha issues often need most
information to have a full picture, i.e., it never hurts to have more
information. Also note that the forum is the community one and so IMO the wrong
place for any generic enterprise support report request, publicly readable for
all compared to the subscription contract and private enterprise support portal.

If, a generic (public) IP hashing might be sensible, and if that's done such
that it's still relatively easy to trace the different used one (i.e., a more
human readable/comparable hash than md5/SHA/...) it can be just always turned
on too.