Differences

This shows you the differences between two versions of the page.

--- nova-rdp [2013/12/23 02:09]
admin
+++ nova-rdp [2014/06/12 19:37] (current)
@@ Line 1: / Line 1: @@
-====== Nova RDP Support======
+====== Nova RDP Support Configuration======
-Nova currently provides support for [[http://en.wikipedia.org/wiki/Virtual_Network_Computing|VNC]] and [[http://en.wikipedia.org/wiki/SPICE_(protocol)|SPICE]] graphical consoles. VNC in particular is the protocol employed natively by most popular hypervisors supported by Nova. [[http://en.wikipedia.org/wiki/Hyper-V|Microsoft Hyper-V]] in this context is a remarkable exception, as it employs [[http://en.wikipedia.org/wiki/Remote_Desktop_Protocol|Remote Desktop Protocol (RDP)]] for graphical console access, based on [[http://msdn.microsoft.com/en-us/library/jj712081.aspx|Open Specifications]].
+Nova currently provides support for [[http://en.wikipedia.org/wiki/Virtual_Network_Computing|VNC]] and [[http://en.wikipedia.org/wiki/SPICE_(protocol)|SPICE]] graphical consoles. VNC in particular is the protocol employed natively by most popular hypervisors supported by Nova. [[http://en.wikipedia.org/wiki/Hyper-V|Microsoft Hyper-V]] in this context is a remarkable exception, as it employs the [[http://en.wikipedia.org/wiki/Remote_Desktop_Protocol|Remote Desktop Protocol (RDP)]] for graphical console access, based on [[http://msdn.microsoft.com/en-us/library/jj712081.aspx|Open Specifications]] and implemented by various open source projects.
-==== Getting console connection details ====
+[[http://www.youtube.com/watch?v=DhBa-IuTQAs|Here]]'s an example video showing an HTML5 RDP console based on [[https://github.com/FreeRDP/FreeRDP|FreeRDP]].
-Nova includes internally the required proxy solutions for VNC (novnc, xvpvnc) and SPICE, but this is not the case for RDP. Beside that, it's also desirable to leave third party the ability to choose a custom graphical console UI solution not necessarily included with Nova.
-In order to allow external tools to access graphical console protocol connection details, a public API has been provided.
+----
+===== Configuring Nova for RDP support =====
+RDP console configuration is quite straightforward. All you need to do is to add the following configuration settings in your Hyper-V compute node's **nova.conf**:
-==== Get console connection info: V2 API ====
+    [rdp]
+    enabled=True
+    html5_proxy_base_url=http://10.0.0.1:8000/
+Where the url specified in the **html5_proxy_base_url** setting is provided by the FreeRDP HTML5 proxy as detailed in the next section.
-^Verb	^URI			^Description						^
+===== Installing and configuring the FreeRDP HTML5 proxy =====
-|GET	|/servers/id/action	|gets the connection info for the specified server.	|
-==== Get console connection request: XML ====
+The FreeRDP HTML5 proxy can be installed on various Linux distributions (currently Ubuntu >= 12.04, RHEL 6.x / CentOS 6.x and Fedora >= 16) or on Microsoft Windows, including Hyper-V Server.
-<code xml>
+==== Ubuntu 12.04 and above ====
-<?xml version="1.0" encoding="UTF-8"?>
-<action>os-getConsoleConnectInfo<action/>
-</code>
-==== Get console connection request: JSON ====
+A shell script is provided to simplify the installation of the application and the dependencies, mostly available in source form only.
-<code javascript>
+    sudo apt-get install -y git
-{
+    git clone https://github.com/FreeRDP/FreeRDP-WebConnect.git
-    'action': 'os-getVNCConsole'
+    cd FreeRDP-WebConnect
-}
+    sudo ./setup_all.sh -f -i
-</code>
+At this point the proxy, called **wsgate** can be installed by running:
+    sudo make install
+==== wsgate configuration ====
+The default configuration file is located here:
+    /usr/local/etc/wsgate.ini
+Change the following options to match your environment configuration:
+    [global]
+    port = 8000
+Note: make sure to open the port in your operating system firewall.
+    [openstack]
+    authurl = http://10.0.0.1:5000/v2.0
+    username = admin
+    password = secret
+    tenantname = admin
+    [hyperv]
+    # Credentials used to connect to the Hyper-V hosts when accessing
+    # OpenStack instances consoles
+    hostusername = Administrator
+    hostpassword = secret
+It is also strongly recommended to encrypt the traffic using HTTPS. Here are the relevant parameters, including a PEM file containing both the certificate and the private key.
+    [ssl]
+    port = 4430
+    certfile = /usr/local/etc/wsgate/test.pem
+    certpass = verysecret
+HTML, CSS and Javascript files are available at the following location for further customization:
+    /usr/local/share/wsgate
+==== Running wsgate ====
+wsgate can be executed as a demon with the following instruction:
+    wsgate -c /usr/local/etc/wsgate.ini
+In case you should prefer to execute wsgate in a shell for debugging purposes, just set:
+    [global]
+    daemon = false

Cloudbase Solutions Wiki

User Tools

Site Tools

Differences

Page Tools