From abd2214b44e23cfdcfd73fe30d3b7d853085ffa9 Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Sun, 22 Jan 2006 17:03:48 +0000 Subject: [PATCH] Updated and fixed a broken link, Daniel --- docs/intro.html | 11 ++++++++--- docs/libvir.html | 13 +++++++++---- docs/news.html | 2 +- 3 files changed, 18 insertions(+), 8 deletions(-) diff --git a/docs/intro.html b/docs/intro.html index 4b4cb8cb60..aa5e4539ff 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -1,7 +1,9 @@ -Introduction

Introduction

Libvir won't try to provide all possible interfaces for interacting with -the virtualization features of a set of Linux (or other OS) system.

To avoid ambiguity about the terms used here here are the definitions for +Introduction

Introduction

Libvir is a C toolkit to interract with the virtualization capabilities of +recent versions of Linux (and other OSes), but ibvir won't try to provide all +possible interfaces for interacting with the virtualization features of a set +of Linux (or other OS) system.

To avoid ambiguity about the terms used here here are the definitions for soem of the specific terms used in libvir documentation:

  • a node is a single physical machine
  • an hypervisor is a layer of software allowing to virtualize a node in a set of virtual machines with possibly different @@ -9,7 +11,7 @@ soem of the specific terms used in libvir documentation:

    • a no
    • a domain is an instance of an operating system running on a virtualized machine

    Now we can define the goal of libvir: to provide the lowest possible -generic layer to manage domains on a node.

    This implies the following:

    • the API should not be targetted to a single virtualization environment +generic and stable layer to manage domains on a node.

      This implies the following:

      • the API should not be targetted to a single virtualization environment though Xen is the current default, which also means that some very specific capabilities which are not generic enough may not be provided as libvir APIs
        • @@ -18,6 +20,9 @@ generic layer to manage domains on a node.

        This implies the following:

      • the API will not try to provide hight level multi-nodes management features like load balancing, though they could be implemented on top of libvir
        • +
      • stability of the API is a big concern, libvir should isolate + applications from the frequent changes expected at the lower level of the + virtualization framework

      So libvir should be a building block for higher level management tools or for applications focusing on virtualization on a single node (the only exception being domain migration between node capabilities which may need to diff --git a/docs/libvir.html b/docs/libvir.html index 48ef00d880..cdf2e6f826 100644 --- a/docs/libvir.html +++ b/docs/libvir.html @@ -30,7 +30,7 @@ virtualization mechanisms if needed.

      Here is the list of official releases, however since it is early on in the development of libvir, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list +href="downloads.html">CVS version or snapshot, contact the mailing list and check the ChangeLog to gauge progresses.

      0.0.1: Dec 19 2005

      @@ -42,8 +42,10 @@ and check the ChangeLog to gauge progresses.

      Introduction

      -

      Libvir won't try to provide all possible interfaces for interacting with -the virtualization features of a set of Linux (or other OS) system.

      +

      Libvir is a C toolkit to interract with the virtualization capabilities of +recent versions of Linux (and other OSes), but ibvir won't try to provide all +possible interfaces for interacting with the virtualization features of a set +of Linux (or other OS) system.

      To avoid ambiguity about the terms used here here are the definitions for soem of the specific terms used in libvir documentation:

      @@ -57,7 +59,7 @@ soem of the specific terms used in libvir documentation:

    Now we can define the goal of libvir: to provide the lowest possible -generic layer to manage domains on a node.

    +generic and stable layer to manage domains on a node.

    This implies the following:

      @@ -70,6 +72,9 @@ generic layer to manage domains on a node.

    • the API will not try to provide hight level multi-nodes management features like load balancing, though they could be implemented on top of libvir
      • +
    • stability of the API is a big concern, libvir should isolate + applications from the frequent changes expected at the lower level of the + virtualization framework

    So libvir should be a building block for higher level management tools or diff --git a/docs/news.html b/docs/news.html index a532da84cb..f45fa55943 100644 --- a/docs/news.html +++ b/docs/news.html @@ -1,7 +1,7 @@ Releases

    Releases

    Here is the list of official releases, however since it is early on in the -development of libvir, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list +development of libvir, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list and check the ChangeLog to gauge progresses.

    0.0.1: Dec 19 2005

    • First release
    • Basic management of existing Xen domains
    • Minimal autogenerated Python bindings