From: "Mark Schouten" <mark@tuxis.nl>
To: "Dominik Csapak" <d.csapak@proxmox.com>,
"Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Create a ZFS filesystem upon datastore creation
Date: Thu, 30 Jun 2022 15:13:43 +0000 [thread overview]
Message-ID: <embc48af17-572f-4d3b-b30e-5cf5a590bc7e@154f42ee.com> (raw)
In-Reply-To: <em8c2e4d93-375d-4f0a-8f36-381ca369a6c5@96b102e8.com>
Hi,
>>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?
>That would be a big win. What I’m trying to prevent is that we need to create a second API-tool on PBS-servers to handle the ZFS interaction.
I’ve taken a look at the code, but implementing this is way above my
coding skills :)
Should I create a bugreport for this to let it show up on a todo-list
somewhere? (Or that people can say, ‘WONT-FIX’, in which case I’ll have
to think of another fix)
Thanks,
—
Mark Schouten, CTO
Tuxis B.V.
mark@tuxis.nl
next prev parent reply other threads:[~2022-06-30 15:13 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
2022-06-27 10:14 ` Mark Schouten
2022-06-30 15:13 ` Mark Schouten [this message]
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=embc48af17-572f-4d3b-b30e-5cf5a590bc7e@154f42ee.com \
--to=mark@tuxis.nl \
--cc=d.csapak@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