-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/06/2016 03:26 PM, David Turner wrote:
> Best practices in general say to do them separate. If something
> doesn't work... Is it the new kernel, some package that are
> different on 16.04, Jewel, etc. The less things in that list the
> easier i
d Turner
Cc: ceph-us...@ceph.com
Subject: Re: [ceph-users] Best upgrade strategy
Hi David,
> Am 06.06.2016 um 15:26 schrieb David Turner :
>
> Best practices in general say to do them separate. If something doesn't
> work... Is it the new kernel, some package that are differ
Hi David,
> Am 06.06.2016 um 15:26 schrieb David Turner :
>
> Best practices in general say to do them separate. If something doesn't
> work... Is it the new kernel, some package that are different on 16.04,
> Jewel, etc. The less things in that list the easier it is to track down the
> issue
Best practices in general say to do them separate. If something doesn't work...
Is it the new kernel, some package that are different on 16.04, Jewel, etc. The
less things in that list the easier it is to track down the issue and fix it.
As far as order, hammer 0.94.5 wasn't built with 16.04 in
If your monitor nodes are separate from the osd nodes, I'd get ceph
upgraded to the latest point release of your current line (0.94.7).
Upgrade monitors, then osds, then other dependent services (mds, rgw,
qemu).
Once everything is happy again, I'd run OS and ceph upgrades together,
starting with m
Hi,
we are running a cluster with 6 storage nodes(72 osds) and 3 monitors.
The osds and and monitors are running on Ubuntu 14.04 and with ceph 0.94.5.
We want to upgrade the cluster to Jewel and at the same time the OS to
Ubuntu 16.04. What would be the best way to this? First to upgrade the
OS an