public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Luke Thompson <luke.t@tncrew.com.au>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Proxmox VE 7.0 released!
Date: Wed, 7 Jul 2021 10:30:02 +1000	[thread overview]
Message-ID: <69792235-2ea3-24ed-2412-ad18b9260b6e@tncrew.com.au> (raw)
In-Reply-To: <d984c3da-e738-eca4-2284-a1568c4b46e9@c2n.upsaclay.fr>

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.
>>
>



  reply	other threads:[~2021-07-07  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06 11:47 Martin Maurer
2021-07-06 20:50 ` Alain péan
2021-07-07  0:30   ` Luke Thompson [this message]
2021-07-06 23:50 ` Lindsay Mathieson
2021-07-07  0:22   ` Luke Thompson

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=69792235-2ea3-24ed-2412-ad18b9260b6e@tncrew.com.au \
    --to=luke.t@tncrew.com.au \
    --cc=pve-user@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal