public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>,
	Lorenz Stechauner <l.stechauner@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 storage 1/2] fix #3633: pvesm: use print_api_result
Date: Wed, 27 Oct 2021 11:55:52 +0200	[thread overview]
Message-ID: <d785103a-5cac-0a2f-236b-9d8fa014287b@proxmox.com> (raw)
In-Reply-To: <6e865af1-9a82-4ca6-c0b8-2c32141bf4e9@proxmox.com>

On 25/10/2021 16:17, Dominik Csapak wrote:
> both patches LGTM, commit message could have used some more info
> (like which fields were added, etc.) but no big problem

yeah, mentioning that instead of three or so selected columns all are now
dumped and some reasoning for doing that (after all #3633 did not asked for that)
would be good ;)

Would be nice to reduce that a bit for the default output, ideally the content
list would made dependent of the content type passed, as `used`, `vmid`, `parent`,
`encrypted` and `verification` do not make much sense for `--content vztmpl`.

The headers are now all the internal property, `used_fraction` does not read
to nicely for a CLI tool human readable output IMO (would be naturally Ok for
the machine readable JSON one).

There's also ctime in content list that isn't printed more human friendly, which
would be the point of #3633,

And we really need to reverse the default for (no)border, as the content list
for vztmpl on the same storage here produced 72 lines previously (easily fitting
on one console page here) and now spews out 145 lines (which needs scrolling),
without adding really any value and making copying not exactly easier, but at
least that part isn't the job of this patch series.

> Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
> Tested-by: Dominik Csapak<d.csapak@proxmox.com>

thanks, it works as in breaks not something, but cannot say as advertised as it
does quite a bit more than the report requested, which can be fine but would need
some commit message to state at least some reasoning or thoughts on it.

I'm open to take it in now with at least the columns being the same as previously,
fancy auto-column selection and the border stuff can be done later/independent of
this.




      reply	other threads:[~2021-10-27  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 12:49 Lorenz Stechauner
2021-10-21 12:49 ` [pve-devel] [PATCH v3 storage 2/2] pvesm: using $API instead of PVE::API2::Storage Lorenz Stechauner
2021-10-21 12:50 ` [pve-devel] [PATCH v3 storage 1/2] fix #3633: pvesm: use print_api_result Lorenz Stechauner
2021-10-25 14:17 ` Dominik Csapak
2021-10-27  9:55   ` Thomas Lamprecht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d785103a-5cac-0a2f-236b-9d8fa014287b@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=l.stechauner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal