I just want the latest minor version before upgrading to the next major version
:) This practice isn't recommended elsewhere, but I want to make sure and limit
errors as much as possible.
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe
I have upgraded dozens of clusters 14 -> 16 using the methods described in
the docs, and when followed precisely no issues have arisen. I would
suggest moving to a release that is receiving backports still (pacific or
quincy). The important aspects are only doing one system at a time. In the
case
why are you still not on 14.2.22?
>
> Yes, the documents show an example of upgrading from Nautilus to
> Pacific. But I'm not really 100% trusting the Ceph documents, and I'm
> also afraid of what if Nautilus is not compatible with Pacific in some
> operations of monitor or osd =)
Yes, the documents show an example of upgrading from Nautilus to Pacific. But
I'm not really 100% trusting the Ceph documents, and I'm also afraid of what if
Nautilus is not compatible with Pacific in some operations of monitor or osd =)
___
ceph-users
Because pacific has performance issues
>
> Curious, why not go to Pacific? You can upgrade up to 2 major releases
> in a go.
>
>
> The upgrade process to pacific is here:
> https://docs.ceph.com/en/latest/releases/pacific/#upgrading-non-cephadm-
> clusters
> The upgrade to Octopus is here:
>
Curious, why not go to Pacific? You can upgrade up to 2 major releases in a
go.
The upgrade process to pacific is here:
https://docs.ceph.com/en/latest/releases/pacific/#upgrading-non-cephadm-clusters
The upgrade to Octopus is here:
>
> Hi, I want to upgrade my old Ceph cluster + Radosgw from v14 to v15. But
> I'm not using cephadm and I'm not sure how to limit errors as much as
> possible during the upgrade process?
Maybe check the changelog, check upgrading notes, and continuosly monitor the
mailing list?
I have to do
