From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id C8D481FF15C for ; Fri, 11 Jul 2025 14:23:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DD728FB18; Fri, 11 Jul 2025 14:24:16 +0200 (CEST) From: "Max R. Carrara" To: pve-devel@lists.proxmox.com Date: Fri, 11 Jul 2025 14:23:42 +0200 Message-Id: <20250711122342.262727-1-m.carrara@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.297 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_INFOUSMEBIZ 0.75 Prevalent use of .info|.us|.me|.me.uk|.biz|xyz|id|rocks|life domains in spam/malware KAM_SHORT 0.001 Use of a URL Shortener for very short URL RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [pve8to9.pm, marc.info, proxmox.com] Subject: [pve-devel] [PATCH v1 pve-manager] pve8to9: check for usage of GlusterFS storages X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Starting with PVE 9, we will drop support for GlusterFS entirely [1] as it is no longer properly maintained upstream [2]. Therefore, scan the storage config and suggest either moving to different storages or using one's GlusterFS instances as directory storage if a 'glusterfs' storage is found. [1]: https://git.proxmox.com/?p=pve-storage.git;a=commit;h=7669a99e97f3fd35cca95d1d1ab8a377f593dccb [2]: https://marc.info/?l=fedora-devel-list&m=171934833215726 Signed-off-by: Max R. Carrara --- NOTE: I tested this briefly on a development VM by configuring a dummy 'glusterfs' storage with 'disabled' set to '1'. PVE/CLI/pve8to9.pm | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/PVE/CLI/pve8to9.pm b/PVE/CLI/pve8to9.pm index 91b50cd9..14810301 100644 --- a/PVE/CLI/pve8to9.pm +++ b/PVE/CLI/pve8to9.pm @@ -1581,6 +1581,38 @@ sub check_lvm_autoactivation { return undef; } +sub check_glusterfs_storage_usage { + my $cfg = PVE::Storage::config(); + my $storage_info = PVE::Storage::storage_info($cfg); + + log_info("Check for usage of GlusterFS storages..."); + + my $has_glusterfs_storage = 0; + + for my $storeid (sort keys $storage_info->%*) { + my $scfg = PVE::Storage::storage_config($cfg, $storeid); + + next if $scfg->{type} ne 'glusterfs'; + + $has_glusterfs_storage = 1; + log_fail("found 'glusterfs' storage '$storeid'"); + } + + if ($has_glusterfs_storage) { + log_fail("Starting with PVE 9, GlusterFS will not be supported anymore." + . " GlusterFS storages will therefore cease to work." + . "\nThis is due to the GlusterFS project not being properly maintained anymore." + . "\n\nThis means that you will have to move all volumes on GlusterFS storages to" + . " different storages and then remove any GlusterFS storage that you have configured." + . "\n\nAlternatively, you can mount your GlusterFS instances manually " + . " via the 'glusterfs' commandline and use them as directory storage."); + } else { + log_pass("No GlusterFS storage found."); + } + + return undef; +} + sub check_misc { print_header("MISCELLANEOUS CHECKS"); my $ssh_config = eval { PVE::Tools::file_get_contents('/root/.ssh/config') }; @@ -1693,6 +1725,7 @@ sub check_misc { check_legacy_notification_sections(); check_legacy_backup_job_options(); check_lvm_autoactivation(); + check_glusterfs_storage_usage(); } my sub colored_if { -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel