openstack/nova
Code Issues Proposed changes

fix doc to refer to nova-vncproxy

Browse Source
This commit is contained in:
Vishvananda Ishaya 2011-03-29 22:37:19 -07:00
parent 9513458c3e
commit 3e9bafd4f0
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/runnova/vncconsole.rst
View File

@ -34,17 +34,17 @@ A VNC Connection works like so:
Configuring the VNC Proxy
-------------------------
nova-vnc-proxy requires a websocket enabled html client to work properly. At
nova-vncproxy requires a websocket enabled html client to work properly. At
this time, the only tested client is a slightly modified fork of noVNC, which
you can at find http://github.com/openstack/noVNC.git
.. todo:: add instruction for installing from package
noVNC must be in the location specified by --vncproxy_wwwroot, which defaults
to /var/lib/nova/noVNC. nova-vnc-proxy will fail to launch until this code
to /var/lib/nova/noVNC. nova-vncproxy will fail to launch until this code
is properly installed.
By default, nova-vnc-proxy binds 0.0.0.0:6080. This can be configured with:
By default, nova-vncproxy binds 0.0.0.0:6080. This can be configured with:
* --vncproxy_port=[port]
* --vncproxy_host=[host]
@ -56,7 +56,7 @@ At the moment, VNC support is supported only when using libvirt. To enable VNC
Console, configure the following flags:
* --vnc_console_proxy_url=http://[proxy_host]:[proxy_port] - proxy_port
defaults to 6080. This url must point to nova-vnc-proxy
defaults to 6080. This url must point to nova-vncproxy
* --vnc_enabled=[True|False] - defaults to True. If this flag is not set your
instances will launch without vnc support.