summaryrefslogtreecommitdiffstats
path: root/doc/source
diff options
context:
space:
mode:
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/runnova/vncconsole.rst7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/source/runnova/vncconsole.rst b/doc/source/runnova/vncconsole.rst
index f851e5372..d6bc16322 100644
--- a/doc/source/runnova/vncconsole.rst
+++ b/doc/source/runnova/vncconsole.rst
@@ -48,6 +48,9 @@ nova-consoleauth. This service must be running in order for for either proxy
to work. Many proxies of either type can be run against a single
nova-consoleauth service in a cluster configuration.
+nova-consoleauth should not be confused with nova-console, which is a xen-specific
+service that is not used by the most recent vnc proxy architecture.
+
Getting an Access Url
---------------------
Nova provides the ability to create access_urls through the os-consoles extension.
@@ -63,7 +66,7 @@ Accessing VNC Consoles with a Java client
To enable support for the OpenStack java vnc client in nova, nova provides the
nova-xvpvncproxy service, which you should run to enable this feature.
-* :option:`--xvpvncproxy_baseurl=[base url for client connections]` -
+* :option:`--xvpvncproxy_base_url=[base url for client connections]` -
this is the public base url to which clients will connect. "?token=abc"
will be added to this url for the purposes of auth.
* :option:`--xvpvncproxy_port=[port]` - port to bind (defaults to 6081)
@@ -109,7 +112,7 @@ server address and credentials.
By default, nova-novncproxy binds 0.0.0.0:6080. This can be configured with:
-* :option:`--novncproxy_baseurl=[base url for client connections]` -
+* :option:`--novncproxy_base_url=[base url for client connections]` -
this is the public base url to which clients will connect. "?token=abc"
will be added to this url for the purposes of auth.
* :option:`--novncproxy_port=[port]`