Hey folks -
I'm at a conference and the internet here is... well... not very
internetty. There are a number of folks here as well (Andy, Russell,
David) who won't be attending either.
That said, if anyone has stuff they want to do/talk about, go for it :)
It looks like a couple of projects are interested in using the noVNC
viewer as a way of talking to machines from a web browser. I've made a
first stab at packageing them, and, in doing so, learned a little bit.
The noVNC code is designed around a proxy that, under the Debian deploy,
lives in /usr/share/noVNC/utils/. This directory contains shell
scripts, a shared object complete with Makefile, and lots of python
code. Needless to say, it does not match Fedora packaging standards.
It uses the Websocket protocol, which is not quite HTTP. Apache HTTPD
does not support Websocket natively, although there is apparently a
path to do so via http://code.google.com/p/pywebsocket/. However, the
noVNC approach is to bundle a simple web server and websocket
implementation. In addition, a python script called websockify handles
When deployed, the web proxy does not lock down browsing of sub dirs.
When run from an init script that did not set cwd, it exposes the
entire directory tree underneath. The normal usage is better: devstack
runs $ cd /opt/stack/noVNC && ./utils/nova-novncproxy --config-file
/etc/nova/nova.conf --web . Run this way, it only exposes the
/usr/share/noVNC directory as read only, but really should not allow
directory indexing. However, our current init script runs:
daemon --user nova --pidfile $pidfile "$exec --flagfile $config
--logfile $logfile &>/dev/null & echo \$! > $pidfile"
where $exec is
In my spec file, in order to match this, I moved the executables from
/opt/stack/noVNC/utils to /usr/bin, but that does not seem like a good
long term solution: they are generically named and should have novnc as
part of their name as well.
I've also and renamed /opt/stack/noVNC/utils/nova-novncproxy to
/usr/bin/nova-vncproxy which seems like it should not be necessary.
Currently, the Openstack specific code is in the upstream git repo for
noVNC, but it really should be moved to the Nova git repository. I'll
talk to the original author to find out his rationale, and to see if we
can get it moved over.
I've posted my current work here
But would not suggest that people use it yet. I am certainly willing to
take feed back on the spec file:
Dan B suggested a few things that I'd like to record here:
1. Is there a need to create a novnc user with an empty home dir to run in?
2. The python code should be made into a site-package.
First off, thanks for getting something together.
I think you have a bug in your spec file at line 1. After that I got it to build after renaming some directories. I am in the process of testing this out now in a devstack install.
I will give you feedback when I get it.
----- Original Message -----
From: "Joshua Harlow" <harlowja(a)yahoo-inc.com>
To: "Jason Ford" <jason(a)chatinara.com>
Cc: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org>, "Andy Grimm" <agrimm(a)gmail.com>, "openstack" <openstack(a)lists.launchpad.net>, "Pádraig Brady" <P(a)draigBrady.com>
Sent: Thursday, May 24, 2012 9:18:06 PM
Subject: Re: [Openstack] centos 6 images
Starting this @ https://github.com/yahoo/Openstack-Condense/wiki/How-To-Use-This
I’ll try to finish it up soon :-P
On 5/22/12 6:33 PM, "Joshua Harlow" < harlowja(a)yahoo-inc.com > wrote:
Let me write something up that should explain this. Its not that hard.
On 5/22/12 6:31 PM, "Jason Ford" < jason(a)chatinara.com > wrote:
Do you have some basic instructions on how to push this into an image and configure it? Any information about what you have here would be great!
----- Original Message -----
From: "Joshua Harlow" < harlowja(a)yahoo-inc.com >
To: "Jason" < jason(a)chatinara.com >, "Pádraig Brady" < P(a)draigBrady.com >
Cc: "Fedora Cloud SIG" < cloud(a)lists.fedoraproject.org >, "Andy Grimm" < agrimm(a)gmail.com >, "openstack" < openstack(a)lists.launchpad.net >
Sent: Tuesday, May 22, 2012 1:49:06 PM
Subject: Re: [Openstack] centos 6 images
U might want to check out,
Its a stripped down/cleaned up/... version of cloud-init that I know works on RHEL6.
I tried to improve the following:
1. Code cleanliness (constants being uppercase, paths using os.path.join and so-on)
2. Stripping out some of the odd handlers (byobu, right-scale and such)
3. Improving logging by a lot (so that u can debug this thing)
4. Making what handlers I left work on RH and ubuntu...
Might be useful if u want to try it.
I know just from doing the above work that the cloud-init for ubuntu, requires some work to get it to work on RH, but not tons, eventually I hope that I can merge this back, but for now its forked so that I could focus on getting it working and cleaned up, rather than pushing code through some review process via launchpad and such (ie the slow as molasses approach).
On 5/22/12 10:05 AM, "Jason" < jason(a)chatinara.com > wrote:
I will give these a shot later today and reply with feedback.
Thanks for looking into this!
On May 22, 2012, at 11:44 AM, Pádraig Brady < P(a)draigBrady.com > wrote:
> On 05/22/2012 03:39 PM, Andy Grimm wrote:
>> On Tue, May 22, 2012 at 9:38 AM, Pádraig Brady < P(a)draigbrady.com > wrote:
>>> On 05/22/2012 04:07 AM, Jason Ford wrote:
>>>> I am trying to put together an image for centos 6 that works like cloud-init on ubuntu does. Currently I have ssh keys getting imported but having some problems getting the disk to dynamically resize to the flavor template as well as the hostname set in horizon to be pushed into the image. Does anyone have any howtos or suggestions on how to get this done? Is there cloud-init for centos just like ubuntu? I would also be interested in how to do this with debian as well.
>>> Well I notice there is no cloud-init package for EPEL.
>>> I took a quick stab at it here:
>> I've already responded in IRC, but it wouldn't hurt to have a response
>> in the mail archive. In short, the reason there isn't already a
>> cloud-init for EL6 (or EL5, for that matter) is that upstream has been
>> using python 2.7-only calls for a while now. In particular, a couple
>> of calls to subprocess.check_output need to be replaced, and I think
>> there are a few other issues as well. I don't think it's a huge
>> amount of work to make it functional, but it hasn't been high on
>> anyone's list. It would be cool if you have time to fix / test it,
> Ok I've fixed the check_output calls at the above URL.
Mailing list: https://launchpad.net/~openstack
Post to : openstack(a)lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
When: 1900 UTC (3pm US Eastern, 12pm US Pacific)
Where: #fedora-meeting on irc.freenode.net
* F18 plans! Who's got some?
* Checking in with various projects - OpenStack, OpenShift, Cloudstack,
Eucalyptus, OpenNebula, Gluster
Other agenda items welcome. See you soon :)