What if the upgrade fails, what is the rollback scenario?
On Wed, Jan 27, 2016 at 10:10 PM, <ceph@xxxxxxxxxxxxxx> wrote:
I just upgraded from firefly to infernalis (firefly to hammer to
infernalis) my cluster
All came like a charm
I upgraded mon first, then the osd, one by one, restarting the daemon
after each upgrade
Remember to change uid of your file, as the osd daemon now run under the
user ceph (and not root): can be pretty long operation .. do the chown,
then upgrade, then shut the daemon, rechown the remaining files, start
the daemon (use chown --from=0:0 ceph:ceph -R /var/lib/ceph/osd/ceph-2
to speed up the last chown)
To conclude, I upgraded the whole cluster without a single downtime
(pretty surprised, didn't expect the process to be "that" robust)
On 27/01/2016 15:00, Vlad Blando wrote:
> Hi,
>
> I have a production Ceph Cluster
> - 3 nodes
> - 3 mons on each nodes
> - 9 OSD @ 4TB per node
> - using ceph version 0.80.5 (38b73c67d375a2552d8ed67843c8a65c2c0feba6)
>
> Now I want to upgrade it to Hammer, I saw the documentation on upgrading,
> it looks straight forward, but I want to know to those who have tried
> upgrading a production environment, any precautions, caveats, preparation
> that I need to do before doing it?
>
> - Vlad
> ᐧ
>
>
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
ᐧ
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
