All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Coffing" <ccoffing@novell.com>
To: christian.limpach@gmail.com
Cc: xen-devel@lists.xensource.com
Subject: Re: Control tools work
Date: Tue, 31 May 2005 15:29:45 -0600	[thread overview]
Message-ID: <s29c82f6.031@sinclair.provo.novell.com> (raw)

Christian,

I've done a pull and now see the functionality in XendCheckpoint.py; thanks for the heads-up.

But how do you see things outside of xm & xend accessing this functionality?  In particular, I'm thinking of a CIMOM provider written in C++.  Forking/exec-ing an "xm migrate" command is less than ideal, for several reasons (progress reporting, error reporting without having to grok text, overhead on a busy server, ...)  In my ideal world, this level of functionality would be in C or C++ libraries, so you can put whatever you want on top of it, be it Python commands or C++ CIMOM code or anything else.

I don't necessarily want to revive the old Python debate, but this does complicate things.

Thanks,
Charles


>>>christian.limpach@gmail.com 05/31/05 3:07 pm >>> 
On 5/31/05, Charles Coffing <ccoffing@novell.com> wrote: 
 
>1.  Providing a higher-level consistent API for domain actions 
>(create, save, migrate, restore, pause, etc). 
 
I'm no longer convinced there is a much higher API to have.  Except 
for create and migrate, all the actions you list are already single 
functions in libxc, migrate is save | restore.  It might be useful to 
group several functions together for create, but it's not quite clear 
how/where device configuration fits in there. 
 
>I'm refactoring / rewriting / writing code in xutil, libxc, and xfrd 
>(although it wouldn't be hard to slip libxen in there instead of libxc 
>if that is the ultimate direction).  I hope to have something to show 
>in a week or two. 
 
Please note that xfrd does no longer exist in -unstable.  Also we 
don't use libxutil anymore. 
Xend handles the first half of a relocation itself and then runs the 
xc_save or xc_restore helper programs to do the second part. During 
the first part of a relocation, the xend domain configuration is 
exchanged and the format of this part is specific to xend.  The 
xc_save and xc_restore helpers are merely wrappers for the 
xc_linux_save and xc_linux_restore functions and use pipes to 
communicate with xend and write/read the virtual machine image to/from 
a file handle or socket. 
 
   christian 
 
 
Xen-devel mailing list 
Xen-devel@lists.xensource.com 
http://lists.xensource.com/xen-devel 

             reply	other threads:[~2005-05-31 21:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 21:29 Charles Coffing [this message]
2005-05-31 21:48 ` Control tools work Daniel Stekloff
2005-05-31 22:25 ` Steven Hand
2005-06-01  0:25   ` Christian Limpach
2005-06-03  1:01 ` Anthony Liguori
     [not found] <s29d6a51.010@sinclair.provo.novell.com>
2005-06-01 20:13 ` Christian Limpach
  -- strict thread matches above, loose matches on Subject: below --
2005-06-01 13:56 Charles Coffing
     [not found] <s29c82f6.030@sinclair.provo.novell.com>
2005-06-01  0:15 ` Christian Limpach
2005-05-31 17:57 Charles Coffing
2005-05-31 21:07 ` Christian Limpach
2005-05-31 23:33 ` Jacob Gorm Hansen
2005-06-01 10:28   ` Grzegorz Milos

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=s29c82f6.031@sinclair.provo.novell.com \
    --to=ccoffing@novell.com \
    --cc=christian.limpach@gmail.com \
    --cc=xen-devel@lists.xensource.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.