From: Lindsay Mathieson <lindsay.mathieson@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Proxmox 6.3 - Upgrade Ceph Nautilus to Octopus
Date: Sat, 28 Nov 2020 13:17:02 +1000 [thread overview]
Message-ID: <d6a8c76f-0886-00af-6e01-4eec0874b98a@gmail.com> (raw)
Just performed this as per the instructions:
https://pve.proxmox.com/wiki/Ceph_Nautilus_to_Octopus
Went flawlessly, no problems. Small 5 node cluster, took about 30 min
with me obsessively checking ever step.
I did shut down all non-essential VM's first.
Because I like to live on the edge, I did it remotely :) With the router
and VPN (pfSense) virtualised on the promox cluster I was upgrading no
less :)
I also enabled the autoscaller - had proiblems with it in Nautilus, so
it was set to warn. Now its slowly decreasing my pool from 512 pgs to
128. Not having any problems with this so far.
--
Lindsay
reply other threads:[~2020-11-28 3:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d6a8c76f-0886-00af-6e01-4eec0874b98a@gmail.com \
--to=lindsay.mathieson@gmail.com \
--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