Added link to libvirt-qpid on front page, and docs on URI formats for each driver

This commit is contained in:
Daniel P. Berrange 2009-01-27 14:49:09 +00:00
parent f03d3439cd
commit 04b120e481
13 changed files with 134 additions and 5 deletions

View File

@ -1,3 +1,10 @@
Tue Jan 27 14:28:16 GMT 2009 Daniel P. Berrange <berrange@redhat.com>
* docs/index.html.in: Add link to libvirt-qpid & UML driver info
* docs/drvopenvz.html.in, docs/drvqemu.html.in, docs/drvtest.html.in,
docs/drvuml.html.in docs/drvxen.html.in: Add examples of local and
remote URI formats. Also re-generate equiv .html files
Tue Jan 27 13:25:16 +0100 2009 Jim Meyering <meyering@redhat.com> Tue Jan 27 13:25:16 +0100 2009 Jim Meyering <meyering@redhat.com>
virterror.c: don't read beyond end of buffer upon OOM virterror.c: don't read beyond end of buffer upon OOM

View File

@ -142,6 +142,7 @@
</p> </p>
<pre> <pre>
openvz:///system (local access) openvz:///system (local access)
openvz+unix:///system (local access)
openvz://example.com/system (remote access, TLS/x509) openvz://example.com/system (remote access, TLS/x509)
openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+tcp://example.com/system (remote access, SASl/Kerberos)
openvz+ssh://root@example.com/system (remote access, SSH tunnelled) openvz+ssh://root@example.com/system (remote access, SSH tunnelled)

View File

@ -21,6 +21,7 @@
<pre> <pre>
openvz:///system (local access) openvz:///system (local access)
openvz+unix:///system (local access)
openvz://example.com/system (remote access, TLS/x509) openvz://example.com/system (remote access, TLS/x509)
openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+tcp://example.com/system (remote access, SASl/Kerberos)
openvz+ssh://root@example.com/system (remote access, SSH tunnelled) openvz+ssh://root@example.com/system (remote access, SSH tunnelled)

View File

@ -149,6 +149,23 @@
node. If both are found, then Xen paravirtualized guests can be run using node. If both are found, then Xen paravirtualized guests can be run using
the KVM hardware acceleration. the KVM hardware acceleration.
</li></ul> </li></ul>
<h2>Connections to QEMU driver</h2>
<p>
The libvirt QEMU driver is a multi-instance driver, providing a single
system wide privileged driver (the "system" instance), and per-user
unprivileged drivers (the "session" instance). The of the driver protocol
is "qemu". Some example conection URIs for the libvirt driver are:
</p>
<pre>
qemu:///session (local access to per-user instance)
qemu+unix:///session (local access to per-user instance)
qemu:///system (local access to system instance)
qemu+unix:///system (local access to system instance)
qemu://example.com/system (remote access, TLS/x509)
qemu+tcp://example.com/system (remote access, SASl/Kerberos)
qemu+ssh://root@example.com/system (remote access, SSH tunnelled)
</pre>
<h2> <h2>
<a name="xmlconfig" id="xmlconfig">Example domain XML config</a> <a name="xmlconfig" id="xmlconfig">Example domain XML config</a>
</h2> </h2>

View File

@ -32,6 +32,26 @@
</li> </li>
</ul> </ul>
<h2>Connections to QEMU driver</h2>
<p>
The libvirt QEMU driver is a multi-instance driver, providing a single
system wide privileged driver (the "system" instance), and per-user
unprivileged drivers (the "session" instance). The of the driver protocol
is "qemu". Some example conection URIs for the libvirt driver are:
</p>
<pre>
qemu:///session (local access to per-user instance)
qemu+unix:///session (local access to per-user instance)
qemu:///system (local access to system instance)
qemu+unix:///system (local access to system instance)
qemu://example.com/system (remote access, TLS/x509)
qemu+tcp://example.com/system (remote access, SASl/Kerberos)
qemu+ssh://root@example.com/system (remote access, SSH tunnelled)
</pre>
<h2><a name="xmlconfig">Example domain XML config</a></h2> <h2><a name="xmlconfig">Example domain XML config</a></h2>
<h3>QEMU emulated guest on x86_64</h3> <h3>QEMU emulated guest on x86_64</h3>

View File

@ -126,6 +126,22 @@
</div> </div>
<div id="content"> <div id="content">
<h1>Test "mock" driver</h1> <h1>Test "mock" driver</h1>
<h2>Connections to Test driver</h2>
<p>
The libvirt Test driver is a per-process fake hypervisor driver,
with a driver name of 'test'. The driver maintains all its state
in memory. It can start with a pre-configured default config, or
be given a path to a alternate config. Some example conection URIs
for the libvirt driver are:
</p>
<pre>
test:///default (local access, default config)
test:///path/to/driver/config.xml (local access, custom config)
test+unix:///default (local access, default config, via daemon)
test://example.com/default (remote access, TLS/x509)
test+tcp://example.com/default (remote access, SASl/Kerberos)
test+ssh://root@example.com/default (remote access, SSH tunnelled)
</pre>
</div> </div>
</div> </div>
<div id="footer"> <div id="footer">

View File

@ -1,5 +1,25 @@
<html> <html>
<body> <body>
<h1>Test "mock" driver</h1> <h1>Test "mock" driver</h1>
<h2>Connections to Test driver</h2>
<p>
The libvirt Test driver is a per-process fake hypervisor driver,
with a driver name of 'test'. The driver maintains all its state
in memory. It can start with a pre-configured default config, or
be given a path to a alternate config. Some example conection URIs
for the libvirt driver are:
</p>
<pre>
test:///default (local access, default config)
test:///path/to/driver/config.xml (local access, custom config)
test+unix:///default (local access, default config, via daemon)
test://example.com/default (remote access, TLS/x509)
test+tcp://example.com/default (remote access, SASl/Kerberos)
test+ssh://root@example.com/default (remote access, SSH tunnelled)
</pre>
</body> </body>
</html> </html>

View File

@ -146,8 +146,11 @@
URIs are URIs are
</p> </p>
<pre> <pre>
uml:///system (local access, system instance) uml:///session (local access to per-user instance)
uml:///session (local access, session instance) uml+unix:///session (local access to per-user instance)
uml:///system (local access to system instance)
uml+unix:///system (local access to system instance)
uml://example.com/system (remote access, TLS/x509) uml://example.com/system (remote access, TLS/x509)
uml+tcp://example.com/system (remote access, SASl/Kerberos) uml+tcp://example.com/system (remote access, SASl/Kerberos)
uml+ssh://root@example.com/system (remote access, SSH tunnelled) uml+ssh://root@example.com/system (remote access, SSH tunnelled)

View File

@ -25,8 +25,11 @@
</p> </p>
<pre> <pre>
uml:///system (local access, system instance) uml:///session (local access to per-user instance)
uml:///session (local access, session instance) uml+unix:///session (local access to per-user instance)
uml:///system (local access to system instance)
uml+unix:///system (local access to system instance)
uml://example.com/system (remote access, TLS/x509) uml://example.com/system (remote access, TLS/x509)
uml+tcp://example.com/system (remote access, SASl/Kerberos) uml+tcp://example.com/system (remote access, SASl/Kerberos)
uml+ssh://root@example.com/system (remote access, SSH tunnelled) uml+ssh://root@example.com/system (remote access, SSH tunnelled)

View File

@ -159,6 +159,19 @@
the <code>/etc/xen</code> directory. It is important not to place the <code>/etc/xen</code> directory. It is important not to place
any other non-config files in this directory. any other non-config files in this directory.
</li></ul> </li></ul>
<h2>Connections to Xen driver</h2>
<p>
The libvirt Xen driver is a single-instance privileged driver,
with a driver name of 'xen'. Some example conection URIs for
the libvirt driver are:
</p>
<pre>
xen:/// (local access, direct)
xen+unix:/// (local access, via daemon)
xen://example.com/ (remote access, TLS/x509)
xen+tcp://example.com/ (remote access, SASl/Kerberos)
xen+ssh://root@example.com/ (remote access, SSH tunnelled)
</pre>
<h2> <h2>
<a name="xmlconfig" id="xmlconfig">Example domain XML config</a> <a name="xmlconfig" id="xmlconfig">Example domain XML config</a>
</h2> </h2>

View File

@ -44,6 +44,23 @@
</li> </li>
</ul> </ul>
<h2>Connections to Xen driver</h2>
<p>
The libvirt Xen driver is a single-instance privileged driver,
with a driver name of 'xen'. Some example conection URIs for
the libvirt driver are:
</p>
<pre>
xen:/// (local access, direct)
xen+unix:/// (local access, via daemon)
xen://example.com/ (remote access, TLS/x509)
xen+tcp://example.com/ (remote access, SASl/Kerberos)
xen+ssh://root@example.com/ (remote access, SSH tunnelled)
</pre>
<h2><a name="xmlconfig">Example domain XML config</a></h2> <h2><a name="xmlconfig">Example domain XML config</a></h2>
<p> <p>

View File

@ -82,6 +82,8 @@
A set of bindings for common languages A set of bindings for common languages
</li><li> </li><li>
A <a href="CIM/">CIM provider</a> for the DMTF virtualization schema A <a href="CIM/">CIM provider</a> for the DMTF virtualization schema
</li><li>
A <a href="/qpid/">QMF agent</a> for the AMQP/QPid messaging system
</li></ul> </li></ul>
<h2>libvirt supports:</h2> <h2>libvirt supports:</h2>
<ul><li> <ul><li>
@ -95,11 +97,13 @@
The <a href="http://lxc.sourceforge.net/">LXC</a> Linux container system The <a href="http://lxc.sourceforge.net/">LXC</a> Linux container system
</li><li> </li><li>
The <a href="http://openvz.org/">OpenVZ</a> Linux container system The <a href="http://openvz.org/">OpenVZ</a> Linux container system
</li><li>
The <a href="http://user-mode-linux.sourceforge.net/">User Mode Linux</a> paravirtualized kernel
</li><li> </li><li>
Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
</li></ul> </li></ul>
<h2>libvirt provides:</h2> <h2>libvirt provides:</h2>
<ul><li>Remote management using TLS encryption and x509 certificates</li><li>Remote management authenticating with Kerberos and SASL</li><li>Local access control using PolicyKit</li><li>Zero-conf discovery using Avahi multicast-DNS</li><li>Management of virtual machines, virtual networks and storage</li></ul> <ul><li>Remote management using TLS encryption and x509 certificates</li><li>Remote management authenticating with Kerberos and SASL</li><li>Local access control using PolicyKit</li><li>Zero-conf discovery using Avahi multicast-DNS</li><li>Management of virtual machines, virtual networks and storage</li><li>Portable client API for Linux, Solaris and Windows</li></ul>
<p class="image"> <p class="image">
<img src="libvirtLogo.png" alt="libvirt Logo" /></p> <img src="libvirtLogo.png" alt="libvirt Logo" /></p>
</div> </div>

View File

@ -25,6 +25,9 @@
<li> <li>
A <a href="CIM/">CIM provider</a> for the DMTF virtualization schema A <a href="CIM/">CIM provider</a> for the DMTF virtualization schema
</li> </li>
<li>
A <a href="/qpid/">QMF agent</a> for the AMQP/QPid messaging system
</li>
</ul> </ul>
<h2>libvirt supports:</h2> <h2>libvirt supports:</h2>
@ -46,6 +49,9 @@
<li> <li>
The <a href="http://openvz.org/">OpenVZ</a> Linux container system The <a href="http://openvz.org/">OpenVZ</a> Linux container system
</li> </li>
<li>
The <a href="http://user-mode-linux.sourceforge.net/">User Mode Linux</a> paravirtualized kernel
</li>
<li> <li>
Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
</li> </li>
@ -59,6 +65,7 @@
<li>Local access control using PolicyKit</li> <li>Local access control using PolicyKit</li>
<li>Zero-conf discovery using Avahi multicast-DNS</li> <li>Zero-conf discovery using Avahi multicast-DNS</li>
<li>Management of virtual machines, virtual networks and storage</li> <li>Management of virtual machines, virtual networks and storage</li>
<li>Portable client API for Linux, Solaris and Windows</li>
</ul> </ul>
<p class="image"> <p class="image">