From: Stefan Hrdlicka <s.hrdlicka@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH V3 SERIES storage/manager/docs 0/3] add ZFS dRAID creation
Date: Mon, 13 Jun 2022 16:55:56 +0200 [thread overview]
Message-ID: <20220613145559.1021205-1-s.hrdlicka@proxmox.com> (raw)
V1 -> V2:
# pve-storage
* formating change
* fixing typos & wording
* added check if dRAID options draidspares & draiddata are used for something
else then setting up a dRAID
# pve-manager
* add a viewModel and use a binding for visiblity
* remove controller
# pve-docs
* fix many typos
* reword last paragraph to make it (hopefully :)) more helpful
V2 -> V3:
# pve-storage
* use a draid-config format
# pve-manager
* change due to draid config format (submit text field all with draid config values)
* add hidden field for submitting values --> added addtional binding
* the data & spares fields are now required to be selected in the GUI
** via the API the two config params are not required for now
# pve-docs
* openZFS replaced with OpenZFS
Stefan Hrdlicka (1):
fix #3967: enable ZFS dRAID creation via API
PVE/API2/Disks/ZFS.pm | 55 ++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 54 insertions(+), 1 deletion(-)
---
www/manager6/node/ZFS.js | 69 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
---
local-zfs.adoc | 41 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 40 insertions(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2022-06-13 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 14:55 Stefan Hrdlicka [this message]
2022-06-13 14:55 ` [pve-devel] [PATCH V3 storage 1/3] fix #3967: enable ZFS dRAID creation via API Stefan Hrdlicka
2022-06-13 14:55 ` [pve-devel] [PATCH V3 manager 2/3] fix #3967: enable ZFS dRAID creation in WebGUI Stefan Hrdlicka
2022-06-13 14:55 ` [pve-devel] [PATCH V3 docs 3/3] fix #3967: add ZFS dRAID documentation Stefan Hrdlicka
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=20220613145559.1021205-1-s.hrdlicka@proxmox.com \
--to=s.hrdlicka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.