Follow up Xen Toolstack new design proposal
Owner: anthony.perard
Time: Wed 11:00 AM 17 Sep -0700 (America/Los_Angeles) Final
Location: Turbo Room

Following up with my talk Xen toolstack: Past and Future, I’d like to have more discussion the proposed API design. The API I’ve proposed is for communication between an higher level toolstack (or a simpler command line tool) and a daemon. An API to describe a guest, with the daemon doing the translation to Xen hypercall and other resource creation.

  • Is this the right direction?
  • Other things to consider?
  • How many part of the toolstack to consider for design documents?