From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES v2 manager/storage] Some breaking API changes/cleanups
Date: Wed, 16 Jun 2021 13:51:16 +0200 [thread overview]
Message-ID: <1623844171.l7bb5nkxie.astroid@nora.none> (raw)
In-Reply-To: <20210616072700.54289-1-f.ebner@proxmox.com>
with two follow-ups:
- pve-storage postinst: handle read-only postinst (warn, but don't fail
the upgrade)
- pve-manager: wrap vzdump.cron check in eval {} and warn on error
On June 16, 2021 9:26 am, Fabian Ebner wrote:
> Improved version of the not-yet applied patches and follow-ups, regarding backup
> retention and CIFS credentials, and path+RFC for CephFS at the end.
>
>
> Changes from v1:
> * improve CIFS credential renaming
> * mention that maxfiles is deprecated
> * add checks for pve6to7
> * add patch+RFC for CephFS
>
>
> manager stable(+master):
>
> Fabian Ebner (2):
> pve6to7: add checks for backup retention options
> pve6to7: add check for CIFS credentials
>
> PVE/CLI/pve6to7.pm | 85 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 85 insertions(+)
>
>
> manager master:
>
> Fabian Ebner (1):
> ui: storage: update hint about prune-backups default
>
> www/manager6/storage/Base.js | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
>
> storage master:
>
> Fabian Ebner (5):
> postinst: move cifs credential files into subdirectory upon update
> config: mention that maxfiles is deprecated
> config: add backup content type to default local storage
> cephfs: revert safe-guard check for Luminous
> cephfs: update reminder for removal
>
> PVE/Storage.pm | 2 +-
> PVE/Storage/CIFSPlugin.pm | 3 ---
> PVE/Storage/CephFSPlugin.pm | 8 ++------
> PVE/Storage/Plugin.pm | 14 +++++++++++---
> debian/postinst | 33 +++++++++++++++++++++++++++++++++
> 5 files changed, 47 insertions(+), 13 deletions(-)
> create mode 100644 debian/postinst
>
> --
> 2.30.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
prev parent reply other threads:[~2021-06-16 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 7:26 [pve-devel] " Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 manager 1/3] pve6to7: add checks for backup retention options Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 manager 2/3] pve6to7: add check for CIFS credentials Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 manager 3/3] ui: storage: update hint about prune-backups default Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 storage 1/5] postinst: move cifs credential files into subdirectory upon update Fabian Ebner
2021-06-16 13:11 ` Thomas Lamprecht
2021-06-17 8:09 ` Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 storage 2/5] config: mention that maxfiles is deprecated Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 storage 3/5] config: add backup content type to default local storage Fabian Ebner
2021-06-16 7:26 ` [pve-devel] [PATCH v2 storage 4/5] cephfs: revert safe-guard check for Luminous Fabian Ebner
2021-06-16 7:27 ` [pve-devel] [RFC v2 storage 5/5] cephfs: update reminder for systemd_netmount removal Fabian Ebner
2021-06-16 11:51 ` Fabian Grünbichler [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=1623844171.l7bb5nkxie.astroid@nora.none \
--to=f.gruenbichler@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.