Hi, Daniel
It looks good for me.
Thanks
Atsushi SAKAI
"Daniel P. Berrange" <berrange(a)redhat.com> wrote:
On Tue, Jan 27, 2009 at 12:51:57PM +0900, Atsushi SAKAI wrote:
> Hi,
>
> I have a question about libvirt-qpid.
> The libvirt-qpid is working for QPID broker?
> If so, it should be added in "livirt is" section of following pages.
>
http://libvirt.org/
> How do you think?
Yes, it should be listed - here is an updated front page, also added
the User Mode Linux driver, and mentioning the Windows client support.
I also added details of URI format to all the per-driver pages, since
people often seem to ask about this
Daniel
diff -r f787e41fb699 docs/drvopenvz.html
--- a/docs/drvopenvz.html Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvopenvz.html Tue Jan 27 11:39:31 2009 +0000
@@ -142,6 +142,7 @@
</p>
<pre>
openvz:///system (local access)
+ openvz+unix:///system (local access)
openvz://example.com/system (remote access, TLS/x509)
openvz+tcp://example.com/system (remote access, SASl/Kerberos)
openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
diff -r f787e41fb699 docs/drvopenvz.html.in
--- a/docs/drvopenvz.html.in Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvopenvz.html.in Tue Jan 27 11:39:31 2009 +0000
@@ -21,6 +21,7 @@
<pre>
openvz:///system (local access)
+ openvz+unix:///system (local access)
openvz://example.com/system (remote access, TLS/x509)
openvz+tcp://example.com/system (remote access, SASl/Kerberos)
openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
diff -r f787e41fb699 docs/drvqemu.html
--- a/docs/drvqemu.html Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvqemu.html Tue Jan 27 11:39:31 2009 +0000
@@ -149,6 +149,23 @@
node. If both are found, then Xen paravirtualized guests can be run using
the KVM hardware acceleration.
</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>
<a name="xmlconfig" id="xmlconfig">Example domain
XML config</a>
</h2>
diff -r f787e41fb699 docs/drvqemu.html.in
--- a/docs/drvqemu.html.in Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvqemu.html.in Tue Jan 27 11:39:31 2009 +0000
@@ -32,6 +32,26 @@
</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><a name="xmlconfig">Example domain XML
config</a></h2>
<h3>QEMU emulated guest on x86_64</h3>
diff -r f787e41fb699 docs/drvtest.html
--- a/docs/drvtest.html Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvtest.html Tue Jan 27 11:39:31 2009 +0000
@@ -126,6 +126,22 @@
</div>
<div id="content">
<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 id="footer">
diff -r f787e41fb699 docs/drvtest.html.in
--- a/docs/drvtest.html.in Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvtest.html.in Tue Jan 27 11:39:31 2009 +0000
@@ -1,5 +1,25 @@
<html>
<body>
<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>
</html>
diff -r f787e41fb699 docs/drvuml.html
--- a/docs/drvuml.html Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvuml.html Tue Jan 27 11:39:31 2009 +0000
@@ -146,8 +146,11 @@
URIs are
</p>
<pre>
- uml:///system (local access, system instance)
- uml:///session (local access, session instance)
+ uml:///session (local access to per-user 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+tcp://example.com/system (remote access, SASl/Kerberos)
uml+ssh://root@example.com/system (remote access, SSH tunnelled)
diff -r f787e41fb699 docs/drvuml.html.in
--- a/docs/drvuml.html.in Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvuml.html.in Tue Jan 27 11:39:31 2009 +0000
@@ -25,8 +25,11 @@
</p>
<pre>
- uml:///system (local access, system instance)
- uml:///session (local access, session instance)
+ uml:///session (local access to per-user 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+tcp://example.com/system (remote access, SASl/Kerberos)
uml+ssh://root@example.com/system (remote access, SSH tunnelled)
diff -r f787e41fb699 docs/drvxen.html
--- a/docs/drvxen.html Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvxen.html Tue Jan 27 11:39:31 2009 +0000
@@ -159,6 +159,19 @@
the <code>/etc/xen</code> directory. It is important not to place
any other non-config files in this directory.
</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>
<a name="xmlconfig" id="xmlconfig">Example domain
XML config</a>
</h2>
diff -r f787e41fb699 docs/drvxen.html.in
--- a/docs/drvxen.html.in Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/drvxen.html.in Tue Jan 27 11:39:31 2009 +0000
@@ -44,6 +44,23 @@
</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><a name="xmlconfig">Example domain XML
config</a></h2>
<p>
diff -r f787e41fb699 docs/index.html
--- a/docs/index.html Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/index.html Tue Jan 27 11:39:31 2009 +0000
@@ -82,6 +82,8 @@
A set of bindings for common languages
</li><li>
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>
<h2>libvirt supports:</h2>
<ul><li>
@@ -96,10 +98,12 @@
</li><li>
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>
Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
</li></ul>
<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">
<img src="libvirtLogo.png" alt="libvirt Logo"
/></p>
</div>
diff -r f787e41fb699 docs/index.html.in
--- a/docs/index.html.in Tue Jan 27 11:15:48 2009 +0000
+++ b/docs/index.html.in Tue Jan 27 11:39:31 2009 +0000
@@ -25,6 +25,9 @@
<li>
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>
<h2>libvirt supports:</h2>
@@ -47,6 +50,9 @@
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>
Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
</li>
</ul>
@@ -59,6 +65,7 @@
<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">
--
|: Red Hat, Engineering, London -o-
http://people.redhat.com/berrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org -o-
http://ovirt.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|