summaryrefslogtreecommitdiffstats
path: root/meta-openstack
diff options
context:
space:
mode:
authorAmy Fong <amy.fong@windriver.com>2014-03-25 13:31:26 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2014-03-26 09:31:46 -0400
commit7ea966f082b35ff541a377456d833c8b6b43229d (patch)
tree9483ac7e98ed381d8ba0c1819e815fa0778a1777 /meta-openstack
parent681c9eca5f48333d6afd28f31909b89abf8aee05 (diff)
downloadmeta-cloud-services-7ea966f082b35ff541a377456d833c8b6b43229d.tar.gz
docs: Add README.spice
Create a README.spice and document and special consideration, usage.... Signed-off-by: Amy Fong <amy.fong@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta-openstack')
-rw-r--r--meta-openstack/README.spice82
1 files changed, 82 insertions, 0 deletions
diff --git a/meta-openstack/README.spice b/meta-openstack/README.spice
new file mode 100644
index 0000000..a6b93b2
--- /dev/null
+++ b/meta-openstack/README.spice
@@ -0,0 +1,82 @@
1OpenStack offers two types of console support, VNC support and SPICE.
2The VNC protocol is fairly limited, lacking support for multiple monitors,
3bi-directional audio, reliable cut+paste, video streaming and more.
4SPICE is a new protocol which aims to address all the limitations in VNC,
5to provide good remote desktop support.
6
7The Controller will have both the proxy for vnc and for spice html5
8running. The nova-spicehtml5proxy service communicates directly with
9the hypervisor process using SPICE.
10
11OpenStack's Dashboard uses a SPICE HTML5 widget in its console tab
12to communicate with the nova-spicehtml5proxy service. Since both proxies
13are running, the Dashboard will automatically attempt to connect to
14whichever console is provided by the compute node.
15
16Another way to access the spice console is from the controller,
17run the following command:
18
19 nova get-spice-console myinstance spice-html5
20
21This will give you an URL which will directly give you access to the console
22(instead of from Horizon).
23
24The enable or disable VNC/SPICE, on the compute node, modify
25/etc/nova/nova.conf.
26
27Options for configuring SPICE as the console for OpenStack Compute can be
28 found below.
29
30---------------------------------------------------------------------------------
31 Configuration option=Default value (Type) Description
32
33 agent_enabled=True (BoolOpt)enable spice guest agent support
34
35 enabled=False (BoolOpt)enable spice related features
36
37 html5proxy_base_url=http://127.0.0.1:6080/spice_auto.html
38 (StrOpt)location of spice html5
39 console proxy, in the form
40 "http://127.0.0.1:6080/spice_auto.html"
41
42 keymap=en-us (StrOpt)keymap for spice
43
44 server_listen=127.0.0.1 (StrOpt)IP address on which instance
45 spice
46 server should listen
47
48 server_proxyclient_address=127.0.0.1 (StrOpt)the address to which proxy
49 clients (like nova-spicehtml5proxy)
50 should connect
51---------------------------------------------------------------------------------
52
53Combinations/behaviour from Compute:
54
551. VNC will be provided
56
57vnc_enabled=True
58enabled=True
59agent_enabled=True
60
612. SPICE will be provided
62
63vnc_enabled=False
64enabled=True
65agent_enabled=True
66
673. VNC will be provided
68
69vnc_enabled=True
70enabled=False
71agent_enabled=False
72
734. No console will be provided
74
75vnc_enabled=False
76enabled=False
77agent_enabled=False
78
79After nova.conf is changed on the compute node, restart nova-compute
80service. If an instance was running beforehand, it will be necessary to
81restart (reboot, soft or hard) the instance to get the new console.
82