For me that solved XCP platform specific issue: the address should be per
compute node (for now I manually edit the node to have this address). For
each compute node (domU), it's the address of the Xen server which runs the
compute node.

On Mon, Apr 8, 2013 at 7:31 PM, Justin Shepherd <notifications@github.com>wrote:

> In templates/default/folsom/nova.conf.erb:
>
> > @@ -84,7 +92,7 @@ novncproxy_host=<%= @novncproxy_bind_host %>
> >  novncproxy_port=<%= @novncproxy_bind_port %>
> >
> >  vncserver_listen=<%= @vncserver_listen %>
> > -vncserver_proxyclient_address=<%= @vncserver_proxyclient_address %>
> > +vncserver_proxyclient_address=<%= node["nova"]["compute"]["vncserver_proxyclient_address"] or @vncserver_proxyclient_address %>
>
> @ilyash <https://github.com/ilyash>: what is this change trying to solve?
> do we have an issue with the vncserver_proxyclient_address variable?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rcbops-cookbooks/nova/pull/258/files#r3697732>
> .
>



-- 

Ilya Sher, Coding-Knight LTD.
+972 54 8166121
http://coding-knight.com/