Adam is working on packaging novnc:

  http://lists.fedoraproject.org/pipermail/cloud/2012-April/001385.html
  http://lists.fedoraproject.org/pipermail/cloud/2012-April/001398.html
  http://lists.fedoraproject.org/pipermail/cloud/2012-May/001438.html

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?

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.

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

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.

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
29c29
< 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

/lib/systemd/system/openstack-nova-novncproxy.service
[Unit]
Description=OpenStack Nova NoVNC Proxy Server
After=syslog.target network.target

[Service]
Type=simple
User=nova
ExecStart=/usr/bin/nova-novncproxy --flagfile=/etc/nova/nova.conf --web /usr/share/novnc/

[Install]
WantedBy=multi-user.target

Packaging work is here for noVNC
https://bugzilla.redhat.com/show_bug.cgi?id=822187

Depends on Webscokify which has been completed.
https://bugzilla.redhat.com/show_bug.cgi?id=822182

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:

https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6179/novnc-0.3-10.el6
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6138/python-websockify-0.1.0-5.el6