public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Mark Schouten <mark@tuxis.nl>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Create a ZFS filesystem upon datastore creation
Date: Mon, 27 Jun 2022 12:03:06 +0200	[thread overview]
Message-ID: <a6f4a43c-538b-3bf6-96ab-ad18be008403@proxmox.com> (raw)
In-Reply-To: <em22ccb14f-16b5-47c1-8104-2661ed46dcfe@96b102e8.com>

On 6/27/22 10:20, Mark Schouten wrote:
> Hi,
> 
> We run a few PBS servers with a lot of datastores, ZFS based. While PBS can create zpools, it 
> currently cannot create a ZFS datastore when you create a datastore via the API.
> 
> Currently we have a script to create users and datastores and with the corresponding ZFS filesystem:
> 1: Create PBS user
> 2: Create ZFS filesystem for this user (we set the quotum here)
> 3: Create a ZFS filesystem for this datastore, inside the users filesystem
> 4: Create the datastore
> 
> As we’re going to implement PBS-as-a-service into our portal, I would like to know if it’s feasable 
> to make the API create a filesystem when you create a datastore, or is the general feeling that this 
> should not be inside PBS’ scope?
> 
> Regards,
> 
> —
> Mark Schouten, CTO
> Tuxis B.V.
> mark@tuxis.nl
> 

Hi,

imo is that the wrong point for such things, since the datastore creation
only takes an (arbitrary) path, which has really nothing to do with
the underlying filesystem.

we already have a zpool creation in the api/gui, maybe we could extend that
to also be able to create (and destroy?) zfs fs?

i think we don't want pbs to become a fs/partition manager though ;)

kind regards






  reply	other threads:[~2022-06-27 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  8:20 Mark Schouten
2022-06-27 10:03 ` Dominik Csapak [this message]
2022-06-27 10:14   ` Mark Schouten
2022-06-30 15:13     ` Mark Schouten
2022-07-01  6:46       ` Dominik Csapak

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=a6f4a43c-538b-3bf6-96ab-ad18be008403@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=mark@tuxis.nl \
    --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