On Mon, Oct 6, 2014 at 10:57 AM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote:
Add documentation for these options even though they are mainly meant to
be set by the oVirt portal when it generates the .vv file.
---
man/remote-viewer.pod | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/man/remote-viewer.pod b/man/remote-viewer.pod
index 2526675..7e8718b 100644
--- a/man/remote-viewer.pod
+++ b/man/remote-viewer.pod
@@ -270,6 +270,37 @@ port 8080, use the value "http://foobar:8080".
=back
+=head2 oVirt Support
+
+The connection file can also carry some oVirt-specific options when oVirt
+support is compiled in. These options are used to interact with oVirt REST API.
+This is currently only used in order to show a menu allowing to change the CD
+image being used by the virtual machine from remote-viewer user interface.
+These options go in an optional [ovirt] group.
+
+=over 4
+
+=item C<host> (string, mandatory)
+
+The oVirt instance to connect to. This corresponds to the hostname one would
+connect to to access the oVirt user or admin portal.
+
+=item C<vm-guid> (string, mandatory)
Is the vm-guid really mandatory? Even after Pavel's patches to open a dialog showing which VMs you can connect from an oVirt domain?
Fabiano Fidêncio
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
