From: mj <lists@merit.unu.edu>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] asking for 5->6 upgrade feedback (meshed ceph network)
Date: Tue, 8 Sep 2020 13:18:33 +0200 [thread overview]
Message-ID: <0f278b38-a74f-efe7-606e-41d25cac34a9@merit.unu.edu> (raw)
Hi,
We're still on (latest) pve5/ceph, with the three-host 'mesh network'
type. (https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server)
Of course we want to upgrade to 6, and I would like to ask here:
anything special to watch out for? Is it considered a dangerous upgrade,
or should it normally work out fine?
We have of course studied the upgrading wiki page
(https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0)
Just looking for some feedback of those who have done it, preferably
someone also using the full_mesh_network type for ceph.
Was it an easy upgrade..? Anything in particular to watch out for?
Thanks!
MJ
next reply other threads:[~2020-09-08 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 11:18 mj [this message]
[not found] ` <mailman.12.1599647596.452.pve-user@lists.proxmox.com>
2020-09-09 11:38 ` mj
2020-09-14 6:34 ` Harald Leithner
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=0f278b38-a74f-efe7-606e-41d25cac34a9@merit.unu.edu \
--to=lists@merit.unu.edu \
--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