[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-28 Thread Thomas Bennett
A pleasure. Hope it helps :) Happy to share if you need any more information Zac. Cheers, Tom On Wed, 26 Apr 2023 at 18:14, Dan van der Ster wrote: > Thanks Tom, this is a very useful post! > I've added our docs guy Zac in cc: IMHO this would be useful in a > "Tips & Tricks" section of the

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-26 Thread Dan van der Ster
Thanks Tom, this is a very useful post! I've added our docs guy Zac in cc: IMHO this would be useful in a "Tips & Tricks" section of the docs. -- dan __ Clyso GmbH | https://www.clyso.com On Wed, Apr 26, 2023 at 7:46 AM Thomas Bennett wrote: > > I would second

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-26 Thread Thomas Bennett
I would second Joachim's suggestion - this is exactly what we're in the process of doing for a client, i.e migrating from Luminous to Quincy. However below would also work if you're moving to Nautilus. The only catch with this plan would be if you plan to reuse any hardware - i.e the hosts

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-25 Thread Marc
Maybe he is limited by the supported OS > > I would create a new cluster with Quincy and would migrate the data from > the old to the new cluster bucket by bucket. Nautilus is out of support > and > I would recommend at least to use a ceph version that is receiving > Backports. > >

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-25 Thread Joachim Kraftmayer
I would create a new cluster with Quincy and would migrate the data from the old to the new cluster bucket by bucket. Nautilus is out of support and I would recommend at least to use a ceph version that is receiving Backports. huxia...@horebdata.cn schrieb am Di., 25. Apr. 2023, 18:30: > Dear

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-25 Thread huxia...@horebdata.cn
Thanks a lot for the valuable input, Wesley, Josh, and Anthony. It seems the best practice would be upgrade first, and then expand, remove old nodes afterwards. best regards, Samuel huxia...@horebdata.cn From: Wesley Dillingham Date: 2023-04-25 19:55 To: huxia...@horebdata.cn CC:

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-25 Thread Wesley Dillingham
Get on nautilus first and (perhaps even go to pacific) before expansion. Primarily for the reason that starting in nautilus degraded data recovery will be prioritized over remapped data recovery. As you phase out old hardware and phase in new hardware you will have a very large amount of backfill

[ceph-users] Re: For suggestions and best practices on expanding Ceph cluster and removing old nodes

2023-04-25 Thread Josh Baergen
Hi Samuel, While the second method would probably work fine in the happy path, if something goes wrong I think you'll be happier having a uniform release installed. In general, we've found the backfill experience to be better on Nautilus than Luminous, so my vote would be for the first method.