Bug 801685 - horizon: no VNC console
Summary: horizon: no VNC console
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-django-horizon
Version: el6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Pádraig Brady
QA Contact: Fedora Extras Quality Assurance
Depends On: 822182 822187
TreeView+ depends on / blocked
Reported: 2012-03-09 06:57 UTC by Mark McLoughlin
Modified: 2016-01-04 14:45 UTC (History)
8 users (show)

Clone Of:
Last Closed: 2013-09-19 09:03:53 UTC

Attachments (Terms of Use)

Description Mark McLoughlin 2012-03-09 06:57:08 UTC
In the "Instance Detail" page, the VNC tab doesn't work

There's more to this than horizon work, so we should break down what's needed into individual bugs and turn this into a tracker bug

Comment 1 Mark McLoughlin 2012-05-11 09:33:14 UTC
Adam is working on packaging novnc:


I'm not clear whether just packaging novnc is all that's needed, or whether more will be required?

Adam - could you summarise the plan/status for this bug?

Comment 2 Adam Young 2012-05-11 12:57:17 UTC
There will be two Source RPMS and three RPMS in the final product.  They all come from the same upstream developer.

From https://github.com/kanaka/websockify  there will be python-websockify
From https://github.com/kanaka/noVNC  there will be python-novnc-server and novnc-common.  The server will have Python code and will depend on the other two packages.  novnc-common will have the Javascript client and should be deployable with other webservers.

Short term we ship this.  I'm trying to get the files reorganized upstream to a configuration compatable with the Fedora packaging standards,  but if it takes too long,  I will apply  patches to restructure the code.

There might need to be a change to the init script to start the server as well, as the current one,  in the nova-novnc package, does not map to how novnc is started.  Either I will get it to work by patching python-novnc-server,  or I'll submit a new init script to the nova package. 

Long term,  websockets should be run out of the Apache server just like the rest of the code,  but that is beyond the Folsom timeframe.

I should have something runnable/reviewable next week.

Comment 3 Jan van Eldik 2012-05-11 13:12:49 UTC
Hi Adam,

Do you think the "short term packages" will work on RHEL6 and F16 as well?
Should I open separate BZ's for that?

     thanks for your efforts, cheers, Jan

Comment 4 Adam Young 2012-05-11 13:31:49 UTC
I think the SPEC file will be identical for both.  Keep it as one BZ for now, and we can clone if it proves to be necessary.

Comment 5 Jose Castro Leon 2012-06-01 13:36:58 UTC
I am not sure it should be here or on BZ#822187

I installed the package in a cloud controller and it seems that there is a issue when using websockify rpm. It fails to start because a missing dependency. I found that needs wsproxy python module. Solved if you modify it like this

diff /usr/bin/nova-novncproxy.nopatch /usr/bin/nova-novncproxy
< import wsproxy
> import websockify as wsproxy

BTW in the RPM, I think that it need a way to start this service as it is on openstack in other distributions

Description=OpenStack Nova NoVNC Proxy Server
After=syslog.target network.target

ExecStart=/usr/bin/nova-novncproxy --flagfile=/etc/nova/nova.conf --web /usr/share/novnc/


Comment 6 Adam Young 2012-06-11 14:09:13 UTC
Packaging work is here for noVNC

Depends on Webscokify which has been completed.

Comment 7 Pádraig Brady 2012-06-18 21:34:39 UTC
Reassigning to EPEL as this is where the testing is mainly taken place.
Should have the same Essex logic as Fedora 17

Karma on these would be appreciated:


Note You need to log in before you can comment on or make changes to this bug.