From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 574B4738CE for ; Wed, 7 Jul 2021 02:30:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 09D6728BB8 for ; Wed, 7 Jul 2021 02:30:09 +0200 (CEST) Received: from email.corp.tncrew.net.au (email.corp.tncrew.net.au [103.127.162.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3900928BA8 for ; Wed, 7 Jul 2021 02:30:05 +0200 (CEST) Received: from [180.150.12.121] (port=64264 helo=[192.168.20.3]) by email.corp.tncrew.net.au with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1m0vS1-003cZO-EY for pve-user@lists.proxmox.com; Wed, 07 Jul 2021 10:30:02 +1000 To: pve-user@lists.proxmox.com References: From: Luke Thompson Message-ID: <69792235-2ea3-24ed-2412-ad18b9260b6e@tncrew.com.au> Date: Wed, 7 Jul 2021 10:30:02 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - email.corp.tncrew.net.au X-AntiAbuse: Original Domain - lists.proxmox.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tncrew.com.au X-Get-Message-Sender-Via: email.corp.tncrew.net.au: authenticated_id: luke.t@tncrew.com.au X-Authenticated-Sender: email.corp.tncrew.net.au: luke.t@tncrew.com.au X-Source: X-Source-Args: X-Source-Dir: X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Proxmox VE 7.0 released! X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2021 00:30:39 -0000 I was surprised to see the stable release out so soon too. Debian 11 is tentatively due to be released EOM July [0]. For what it's worth, we upgraded to PVE 6.4 a fortnight ago and have enjoyed no problems thus far. With PVE 7.x, we'll probably wait for the release of PVE 7.1 which should be "truly stable". [0] https://lists.debian.org/debian-release/2021/06/msg00199.html Cheers, Luke T. On 7/7/21 6:50 am, Alain péan wrote: > Hi Martin, > > Already ? The beta is less than two weeks, and Debian 11 is not yet > released... > I have yet to upgrade to 6.4... > > Alain > > > Le 06/07/2021 à 13:47, Martin Maurer a écrit : >> Hi all, >> >> It's our pleasure to announce the stable version 7.0 of Proxmox >> Virtual Environment. It's based on the great Debian 11 "Bullseye" and >> comes with a 5.11 kernel, QEMU 6.0, LXC 4.0, OpenZFS 2.0.4. and >> countless enhancements and bugfixes. >> >> Here is a selection of the highlights >> >> -Debian 11 "Bullseye", but using a newer Linux kernel 5.11 >> - LXC 4.0, QEMU 6.0, OpenZFS 2.0.4 >> - Ceph Pacific 16.2 as new default; Ceph Octopus 15.2 remains supported. >> - Btrfs storage technology with subvolume snapshots, built-in RAID, >> and self-healing via checksumming for data and metadata. >> - New ‘Repositories’ Panel for easy management of the package >> repositories with the GUI. >> - Single Sign-On (SSO) with OpenID Connect >> - QEMU 6.0 with ‘io_uring’, a clean-up option for un-referenced VM disks >> - LXC 4.0 has full support for cgroups2 >> - Reworked Proxmox installer environment >> - ACME standalone plugin with improved support for dual-stacked (IPv4 >> and IPv6) environments >> - ifupdown2 as default for new installations >> - chrony as the default NTP daemon >> - and many more enhancements, bugfixes, etc. >> >> As always, we have included countless bugfixes and improvements on >> many places; see the release notes for all details. >> >> Release notes >> https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0 >> >> Press release >> https://www.proxmox.com/en/news/press-releases/proxmox-virtual-environment-7-0 >> >> >> Video tutorial >> https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-7-0 >> >> >> Download >> https://www.proxmox.com/en/downloads >> Alternate ISO download: >> http://download.proxmox.com/iso >> >> Documentation >> https://pve.proxmox.com/pve-docs >> >> Community Forum >> https://forum.proxmox.com >> >> Bugtracker >> https://bugzilla.proxmox.com >> >> Source code >> https://git.proxmox.com >> >> We want to shout out a big THANK YOU to our active community for all >> your intensive feedback, testing, bug reporting and patch submitting! >> >> FAQ >> Q: Can I upgrade Proxmox VE 6.4 to 7.0 with apt? >> A: Please follow the upgrade instructions on >> https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 >> >> Q: Can I upgrade a 7.0 beta installation to the stable 7.0 release >> via apt? >> A: Yes. >> >> Q: Can I install Proxmox VE 7.0 on top of Debian 11 "Bullseye"? >> A: Yes, see >> https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye >> >> Q: Why is Proxmox VE 7.0 released ahead of the stable Debian 11 release? >> A: The Debian project team postponed their plans for the May release >> mainly due to an unresolved issue in the Debian installer. Since we >> maintain our own Proxmox installer, we are not affected by this >> particular issue, therefore we have decided to release earlier. The >> core packages of Proxmox VE are either maintained by the Proxmox team >> or are already subject to the very strict Debian freeze policy for >> essential packages. >> >> Q: Can I upgrade my Proxmox VE 6.4 cluster with Ceph Octopus to 7.0 >> with Ceph Octopus or even Pacific? >> A: This is a two step process. First, you have to upgrade Proxmox VE >> from 6.4 to 7.0, and afterwards upgrade Ceph from Octopus to Pacific. >> There are a lot of improvements and changes, so please follow exactly >> the upgrade documentation: >> https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 >> https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific >> >> Q: Where can I get more information about feature updates? >> A: Check the roadmap, forum, the mailing list, and/or subscribe to >> our newsletter. >> >