b2235bf3fb
Execluded all XML files in the directory doc/common/tables because they are autogenerated. The XML root element of Docbook XML files should match the following format: <ELEMENT xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="THE_XML_ID_OF_THE_ELEMENT"> Change-Id: If12091be81ec8b2e6e53bfcb4c3a883a65e24736
26 lines
1.4 KiB
XML
26 lines
1.4 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="spice-console">
|
|
<title>SPICE console</title>
|
|
<para>OpenStack Compute supports VNC consoles to guests. The VNC
|
|
protocol is fairly limited, lacking support for multiple monitors,
|
|
bi-directional audio, reliable cut-and-paste, video streaming and
|
|
more. SPICE is a new protocol that aims to address the limitations
|
|
in VNC and provide good remote desktop support.</para>
|
|
<para>SPICE support in OpenStack Compute shares a similar
|
|
architecture to the VNC implementation. The OpenStack dashboard
|
|
uses a SPICE-HTML5 widget in its console tab that communicates to
|
|
the <systemitem class="service">nova-spicehtml5proxy</systemitem>
|
|
service by using SPICE-over-websockets. The <systemitem
|
|
class="service">nova-spicehtml5proxy</systemitem> service
|
|
communicates directly with the hypervisor process by using SPICE.</para>
|
|
<para>VNC must be explicitly disabled to get access to the SPICE console.
|
|
Set the <option>vnc_enabled</option> option to <literal>False</literal> in
|
|
the <literal>[DEFAULT]</literal> section to disable the VNC console.</para>
|
|
<para>Use the following options to configure SPICE as the console for OpenStack Compute:</para>
|
|
<xi:include href="../common/tables/nova-spice.xml"/>
|
|
</section>
|