From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-2?Q?S=B3awomir_Skowron?= Subject: Best practice - upgrade ceph cluster Date: Fri, 20 Apr 2012 21:00:12 +0200 Message-ID: <5934003767531706998@unknownmsgid> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-wi0-f172.google.com ([209.85.212.172]:50470 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755073Ab2DTTAO (ORCPT ); Fri, 20 Apr 2012 15:00:14 -0400 Received: by wibhj6 with SMTP id hj6so976690wib.1 for ; Fri, 20 Apr 2012 12:00:13 -0700 (PDT) Sender: ceph-devel-owner@vger.kernel.org List-ID: To: "ceph-devel@vger.kernel.org" Maybe it's a lame question, but is anybody knows simplest procedure, for most non-disrubtive upgrade of ceph cluster with real workload on it ?? It's most important if we want semi-automate this process with some tools. Maybe there is a cookbook for this operation ?? I know that automate this is not simple, and dangerous, but even in manual upgrade it's important to know what can we expect. Regards Slawomir Skowron