From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mykola Golub Subject: Re: blueprint: consistency groups Date: Fri, 25 Mar 2016 09:19:34 +0200 Message-ID: <20160325071933.GA14634@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-lf0-f44.google.com ([209.85.215.44]:35886 "EHLO mail-lf0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751993AbcCYHTh (ORCPT ); Fri, 25 Mar 2016 03:19:37 -0400 Received: by mail-lf0-f44.google.com with SMTP id d82so50313112lfe.3 for ; Fri, 25 Mar 2016 00:19:37 -0700 (PDT) Content-Disposition: inline In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Gregory Farnum Cc: Victor Denisov , ceph-devel , Josh Durgin , Jason Dillaman On Thu, Mar 24, 2016 at 03:38:25PM -0700, Gregory Farnum wrote: > Just to be clear, you know that you can use the same snapid for all > the images, right? (...although not if you're trying to allow CGs > across pools. Those will be a little harder.) I think not allowing CGs across pools would be annoying limitation for users. If a VM has several volumes for different purposes (e.g. small but fast volume for applicatin data, and large but slow one for backups) it is logical to have different pools for those. -- Mykola Golub