From: Victor Denisov <vdenisov@mirantis.com>
To: Jason Dillaman <dillaman@redhat.com>
Cc: Gregory Farnum <gfarnum@redhat.com>,
Mykola Golub <mgolub@mirantis.com>,
ceph-devel <ceph-devel@vger.kernel.org>,
Josh Durgin <jdurgin@redhat.com>
Subject: Re: blueprint: consistency groups
Date: Thu, 12 May 2016 19:45:03 -0700 [thread overview]
Message-ID: <CA+hcxJQAC7m5mRXhGfL0Fu8erWFb--GstHzOYO-swJNLWXPhHw@mail.gmail.com> (raw)
In-Reply-To: <CA+aFP1AchQD6b-gm7Z4zijQfW8OMZJrrE8S2nLde2CE+VUjZew@mail.gmail.com>
Jason,
Do you have any opinion regarding deleting images that are in a
consistency group?
Should we delete them as well as the references in the consistency
group they belong to or should we prohibit deleting images that are in
a consistency group?
V.
On Wed, May 11, 2016 at 1:24 PM, Jason Dillaman <jdillama@redhat.com> wrote:
> On Wed, May 11, 2016 at 2:44 PM, Victor Denisov <vdenisov@mirantis.com> wrote:
>> One more question. I see that remove operation for images can report
>> progress. Is it necessary for consistency groups?
>
> It shouldn't be necessary for consistency groups. The rationale for
> the progress callback for images is because it might require deleting
> tens of thousands of backing objects. When you remove a consistency
> groups, we should ensure that all associated images have already been
> removed -- so it should be a quick (algorithmically speaking)
> operation.
>
> --
> Jason
next prev parent reply other threads:[~2016-05-13 2:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 15:50 blueprint: consistency groups Victor Denisov
2016-03-24 22:38 ` Gregory Farnum
2016-03-25 7:19 ` Mykola Golub
2016-03-29 17:54 ` Gregory Farnum
2016-04-22 23:49 ` Victor Denisov
[not found] ` <CA+aFP1CnKvVJrWDmKhpziu5otOV73HC5gnUsgZ8+oDW+708Rag@mail.gmail.com>
2016-04-25 21:11 ` Victor Denisov
2016-04-26 16:09 ` Jason Dillaman
2016-04-26 23:33 ` Victor Denisov
2016-04-27 17:50 ` Jason Dillaman
2016-04-28 18:06 ` Victor Denisov
2016-05-03 0:26 ` Victor Denisov
2016-05-03 6:54 ` Mykola Golub
2016-05-03 12:05 ` Jason Dillaman
2016-05-03 21:48 ` Victor Denisov
2016-05-04 0:29 ` Jason Dillaman
2016-05-10 16:25 ` Victor Denisov
2016-05-11 15:12 ` Jason Dillaman
2016-05-11 18:44 ` Victor Denisov
2016-05-11 20:24 ` Jason Dillaman
2016-05-13 2:45 ` Victor Denisov [this message]
2016-05-16 15:48 ` Jason Dillaman
2016-05-23 15:32 ` Victor Denisov
2016-05-23 22:43 ` Victor Denisov
2016-05-24 2:39 ` Jason Dillaman
2016-05-24 22:42 ` Victor Denisov
2016-05-25 5:30 ` Jason Dillaman
2016-05-25 21:34 ` Victor Denisov
2016-05-26 0:53 ` Jason Dillaman
2016-05-26 1:01 ` Victor Denisov
2016-06-04 0:33 ` Victor Denisov
2016-06-09 23:23 ` Victor Denisov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+hcxJQAC7m5mRXhGfL0Fu8erWFb--GstHzOYO-swJNLWXPhHw@mail.gmail.com \
--to=vdenisov@mirantis.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=gfarnum@redhat.com \
--cc=jdurgin@redhat.com \
--cc=mgolub@mirantis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.