Hi, here are some changes to apply at the ONE Documentation, Thanks Abel Miguez Rodriguez ---- Distributed System Architecture Group (http://dsa-research.org) GridWay, http://www.gridway.org OpenNEbula, http://www.opennebula.org
--- drvone.html.in.bak 2009-07-01 20:01:45.000000000 +0200 +++ drvone.html.in 2009-07-01 19:59:59.000000000 +0200 @@ -10,11 +10,8 @@ <body lang="en-US" dir="LTR"> <h1>OpenNebula Virtual Infrastructure Manager driver</h1> <p><a name="toc"></a><a href="http://opennebula.org/">OpenNebula</a> -is a Virtual Infrastructure Engine -that manages Virtual Machines (VM) in a pool of distributed resources -by orchestrating network, storage and virtualization technologies. -The OpenNebula driver lets you manage your private cloud using a -standard libvirt interface, including the API as well as the related +is a Virtual Infrastructure Manager that controls Virtual Machines (VM) in a pool of distributed resources +by orchestrating network, storage and virtualization technologies. The OpenNebula driver lets you manage your private or hybrid (<a href="http://aws.amazon.com/ec2/">Amazon EC2</a> or <a href="http://www.elastichosts.com/">Elastic Hosts</a> based) cloud using a standard libvirt interface, including the API as well as the related tools and VM description files.</p> <h2> <a name="prereq"></a>Deployment pre-requisites</h2> @@ -24,10 +21,6 @@ tools and VM description files.</p> version 1.2 or higher. </p> </li> -<li> -<p>"libxmlrpc-c3" >= 1.06.27-1 development package. - </p> -</li> </ul> <h2> <a name="uris"></a>Connections to OpenNebula driver</h2> @@ -45,8 +38,8 @@ connection Uris for the driver are: <p>There are some limitations on the XML attributes that may be specified when interfacing OpenNebula. The following xml example details the attributes and options supported by the OpenNebula -driver: -</p> +driver:</p> + <h3>Paravirtualized guest direct kernel boot </h3> <pre> <domain type='one'> @@ -97,7 +90,20 @@ driver: <p> <b>Note:</b> The "<interface type='network'>" will attach the interface to a previously configured network (named -<tt>onenetwork</tt>) within the OpenNebula system, typically with the +<tt>onenetwork</tt>) within the <a name="toc"></a><a href="http://opennebula.org/">OpenNebula</a> system, typically with the <tt>onevnet</tt> CLI command.</p> +<p> + +<p><b>Note</b>: OpenNebula supports the simultaneous use of different hypervisors, so you can specify any os type (linux or hvm) supported by your cluster. +</p> + +<h2>Links</h2> +<ul> +<li> <a name="toc"></a><a href="http://www.opennebula.org/doku.php?id=documentation">OpenNebula Documentation</a> +</li> +<li><a name="toc"></a><a href="http://www.opennebula.org/doku.php?id=documentation:rel1.2:ug">OpenNebula User Guide</a> +</li> +</ul> +</p> </body> </html>
-- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list