public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Christian Ebner <c.ebner@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] api: add dedicated datastore disk schema
Date: Wed, 29 Nov 2023 09:56:24 +0100	[thread overview]
Message-ID: <c6b4ce5b-cb56-46bd-aea6-b16e79e44ba7@proxmox.com> (raw)
In-Reply-To: <665749042.845.1701246279052@webmail.proxmox.com>

Am 29/11/2023 um 09:24 schrieb Christian Ebner:
>> On 28.11.2023 18:49 CET Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
>> this is not really helping me, while that might be because its late, I also think
>> that this needs a different name, as what is a datastore-disk here actually?
> 
> The intention was to distinguish between the datastore itself and the disk, on which the datastore might be created upon, as these are 2 independent entities. Most of the time they will be referred to by the same name, as e.g. created by `proxmox-backup-manager disk fs create foo --disk sdd --add-datastore true`.
> 

The base intention I get, and I think too that this could/should be
improved.

> I choose to refer to this as `datastore disk` as that is what the API methods in src/api2/node/disks/directory.rs are called.
> 
> Unfortunately, that does not really match up with ZFS, as there the name refers to the zpool.
> 

Why not STORAGE_NAME_SCHEMA then? As this is used as datastore name
is only for convenience and might not happen if one doesn't ticks the
"add as datastore" checkbox.
So having this naming hardwired to datastore or disk, while it isn't
necessarily related to either type, is IMO just not that ideal.

As description you could then use something like:

"Name of the Storage. Will be also used for any datastore name, if part of an transaction."

(not really ideal as it's worded a bit overly generic, but just to convey
the base idea).




  reply	other threads:[~2023-11-29  8:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 15:25 Christian Ebner
2023-11-28 17:49 ` Thomas Lamprecht
2023-11-29  8:24   ` Christian Ebner
2023-11-29  8:56     ` Thomas Lamprecht [this message]
2023-11-29  9:13       ` Christian Ebner
2023-11-29  9:21         ` Thomas Lamprecht

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=c6b4ce5b-cb56-46bd-aea6-b16e79e44ba7@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=c.ebner@proxmox.com \
    --cc=pbs-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