All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Ewan Mellor <ewan@xensource.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen Management API Draft, version 0.4
Date: Fri, 07 Jul 2006 13:18:37 +0100	[thread overview]
Message-ID: <1152274717.7717.35.camel@localhost.localdomain> (raw)
In-Reply-To: <1152014143.7716.131.camel@localhost.localdomain>

A site-wide emergency power outage happens during any of the use-cases.
The user wants the use-case to roll back to the start or proceed to
completion when power is restored.
User wants to run a text-only interactive application on a virtual
machine.
User wants to run a 2-D graphical interactive application on a virtual
machine.
User wants to run a 3-D graphical interactive application on a virtual
machine.
User wants to configure networking between virtual machines.
User wants to configure networking between virtual machines and the
outside world.
User wants to change storage provision allocated to a virtual machine.
User wants to connect a USB device to a virtual machine :-(
User wants to clone a virtual machine.
User wants to run synthesis on a cloned virtual machine (to make it
slightly different from the original) before connecting it to the
outside world.
User wants to replay virtual machine operation to analyse a security
breach or intermittent problem.
User wants to configure a fault-tolerant virtual machine for a high
availability application.
User wants to configure virtual machines to operate in lock-step to
evaluate whether a change to internal implementation has affected the
external interface (n-version programming).
User wants to single-step a consistent set of virtual machines in
virtual time to debug a cluster application.
User wants to restore a consistent set of virtual machines from a backup
(this one normally gets forgotten).
User wants to test an application designed for large SMP on cheaper
small SMP hardware.
User wants to repeatedly test an application against multiple versions
of a VM, resetting the VMs between each test run.

There must be lots of other use cases.  Yes, there's a bit of a gap
between the level of these use cases and the API proposal.  Which is why
it's important to have a sketch in the document about the software
that's going to be there to fill the gap, roughly how it's going to go
about doing it and how the low-level API operations are sequenced to
operate on the model to achieve these user-level use-cases.

People rarely comment on the notes I write.  I'm continually wondering
whether I'm managing to convey anything useful at all.

Harry.

  reply	other threads:[~2006-07-07 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 15:53 Xen Management API Draft, version 0.4 Ewan Mellor
2006-07-04 11:55 ` Harry Butterworth
2006-07-07 12:18   ` Harry Butterworth [this message]
2006-07-07 13:22     ` Ewan Mellor
2006-07-07 14:32       ` Harry Butterworth
2006-07-07 13:16 ` Harry Butterworth
2006-07-07 13:19   ` Ewan Mellor
2006-07-07 13:49     ` Harry Butterworth
2006-07-07 14:31       ` Ewan Mellor
2006-07-07 14:57         ` Harry Butterworth
2006-07-07 15:10           ` Harry Butterworth

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=1152274717.7717.35.camel@localhost.localdomain \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=ewan@xensource.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.