From: Ian Campbell <Ian.Campbell@citrix.com>
To: Chun Yan Liu <cyliu@suse.com>
Cc: ian.jackson@eu.citrix.com, Jim Fehlig <JFEHLIG@suse.com>,
wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: [RFC V9 3/4] domain snapshot design: xl
Date: Thu, 8 Jan 2015 11:59:54 +0000 [thread overview]
Message-ID: <1420718394.19787.47.camel@citrix.com> (raw)
In-Reply-To: <54984C360200006600087396@soto.provo.novell.com>
On Mon, 2014-12-22 at 01:52 -0700, Chun Yan Liu wrote:
>
> >>> On 12/19/2014 at 06:27 PM, in message <1418984856.20028.17.camel@citrix.com>,
> Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > On Fri, 2014-12-19 at 00:03 -0700, Chun Yan Liu wrote:
> >
> > > '--name' meant to give a meaningful name (like: newinstall. Used as the
> > > memory snapshot name and disk snapshot name).
> >
> > Where is this name stored and when and where would it be presented to
> > the user?
> e.g. For qcow2 internal disk snapshot, this name is stored within the disk.
> When user wants to delete internal disk snapshot, it will be:
> #qemu-img snapshot -d name disk
Makes sense, thanks. Can you clarify in the doc with something like
"name is used as an identifier in the underlying storage backend".
Does it have to be unique? Sounds like it does.
> > > That's good. Then we need to add some description to tell users about
> > > the auto-generated domain snapshot name, disk snapshot name,
> > > memory state file and external disk snapshot files, etc.
> >
> > We will need user docs and manpage updates, yes.
> >
> > > > > #e.g. to specify exernal disk snapshot, like this:
> > > > > #disks=['/tmp/hda_snapshot.qcow2,qcow2,hda',
> > > > > '/tmp/hdb_snapshot.qcow2,qcow2,hdb',]
> > > > >
> > > > > #e.g. to specify internal disk snapshot, like this:
> > > > > disks=[',,hda',',,hdb',]
> > > >
> > > > Ideally one or the other of these behaviours would be possible without
> > > > needing to be quite so explicit.
> > >
> > > OK, I'll delete one.
> >
> > I don't object to having this more capable syntax as an option, so the
> > user can override things if they wish, all I was suggesting is that the
> > default ought to be something useful so the user doesn't need to say
> > anything if they just want the toolstack to "do something sensible".
>
> I see. By default user doesn't need to specify 'disks' at all, then xl
> will do internal disk snapshot to each domain disk.
Right, or it could do an external snapshot to the directory it has been
told the snapshot should live in.
Ian.
next prev parent reply other threads:[~2015-01-08 11:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 6:32 [RFC V9 0/4] domain snapshot document Chunyan Liu
2014-12-16 6:32 ` [RFC V9 1/4] domain snapshot terms Chunyan Liu
2014-12-18 15:05 ` Ian Campbell
2014-12-19 2:46 ` Chun Yan Liu
2014-12-16 6:32 ` [RFC V9 2/4] domain snapshot overview Chunyan Liu
2014-12-17 12:17 ` Wei Liu
2014-12-18 3:34 ` Chun Yan Liu
2014-12-18 10:57 ` Wei Liu
2014-12-18 15:10 ` Ian Campbell
2014-12-19 5:45 ` Chun Yan Liu
2014-12-19 10:25 ` Ian Campbell
2014-12-23 3:42 ` Chun Yan Liu
2015-01-08 12:26 ` Ian Campbell
2015-01-12 7:01 ` Chun Yan Liu
2015-01-12 13:54 ` Ian Campbell
2015-01-14 3:12 ` Chun Yan Liu
2014-12-16 6:32 ` [RFC V9 3/4] domain snapshot design: xl Chunyan Liu
2014-12-17 12:28 ` Wei Liu
2014-12-18 3:23 ` Chun Yan Liu
2014-12-18 11:02 ` Wei Liu
2014-12-18 15:15 ` Ian Campbell
2014-12-19 7:03 ` Chun Yan Liu
2014-12-19 10:27 ` Ian Campbell
2014-12-22 8:52 ` Chun Yan Liu
2015-01-08 11:59 ` Ian Campbell [this message]
2014-12-16 6:32 ` [RFC V9 4/4] domain snapshot design: libxl/libxlu Chunyan Liu
2014-12-17 14:09 ` Wei Liu
2014-12-18 3:01 ` Chun Yan Liu
2014-12-18 15:27 ` Ian Campbell
2014-12-19 6:58 ` Chun Yan Liu
2014-12-19 10:38 ` Ian Campbell
2014-12-22 9:36 ` Chun Yan Liu
2014-12-22 9:36 ` [Qemu-devel] " Chun Yan Liu
2015-01-08 12:11 ` Ian Campbell
2015-01-09 9:59 ` Chun Yan Liu
2015-01-09 9:59 ` Chun Yan Liu
2015-01-08 12:11 ` Ian Campbell
2014-12-22 9:53 ` Chun Yan Liu
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=1420718394.19787.47.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JFEHLIG@suse.com \
--cc=cyliu@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.