Open Stack

Hi Jacob, you were right, i had a problem in the nova.conf of the new
compute node. The vncserver_proxyclient_address  was pointing to the wrong
IP, i changed it, restarted nova in the compute-node and novncproxy in the
controller and everything worked fine! Thanks!!


2013/4/8 Jacob Liberman <jliberma at redhat.com>

>  what is the vnc server listen address in /etc/nova/nova.conf  should be
> unique to each compute node
>
> the vnc proxy should be the same across all the compute nodes
>
> [root at rhos0 ~(keystone_admin)]$ for i in 2 3 4 5; do ssh rhos$i grep vnc
> /etc/nova/nova.conf; done | grep -v \#
> novncproxy_base_url=http://10.16.137.100:6080/vnc_auto.html
> vncserver_listen=10.16.137.102
> vncserver_proxyclient_address=10.16.137.102
> vnc_enabled=true
> novncproxy_base_url=http://10.16.137.100:6080/vnc_auto.html
> vncserver_listen=10.16.137.103
> vncserver_proxyclient_address=10.16.137.103
> vnc_enabled=true
> novncproxy_base_url=http://10.16.137.100:6080/vnc_auto.html
> vncserver_listen=10.16.137.104
> vncserver_proxyclient_address=10.16.137.104
> vnc_enabled=true
> novncproxy_base_url=http://10.16.137.100:6080/vnc_auto.html
> vncserver_listen=10.16.137.105
> vncserver_proxyclient_address=10.16.137.105
> vnc_enabled=true
>
>
> thanks, jacob
>
>
>
> On 04/08/2013 05:03 PM, Juan José Pavlik Salles wrote:
>
> Hi guys, today i added my second compute-node to my folsom deploy. After
> configuring everything i launched 2 VMs. One of the VMs is running on the
> new node, awesome i said!, but when i tried to open VNC (from the
> dashboard) i always get just the console of the VM running on the first
> compute-node i added.
>
>  What i see is on the first compute node is 2 tcp connections to KVM:
>
>  tcp        0      0 172.19.136.20:5900      172.19.136.1:53082
>  ESTABLECIDO 37988/kvm
> tcp        0      0 172.19.136.20:5900      172.19.136.1:53107
>  ESTABLECIDO 37988/kvm
>
>  But i don't see any on the new compute node. So i assume that somehow,
> the VNC from dashboard is connecting to the same console instead of the one
> in the VM running in the new compute-node.
>
>  I may have forgotten something in this new compute-node, but i can't
> figure it out.
>
>  The new VM is running on 172.19.136.21 (my new compute-node) so i should
> see one connection on this host to 5900 TCP, but instead of this, both
> connections go to 172.19.136.20.
>
>  I ran nova-novncproxy and i saw that no matter what VM i choose it
> always connects to:
>
>   21: connecting to: 172.19.136.20:5900
>
>  Any ideas?? Thanks!
>
>  --
> Pavlik Juan José
>
>
> _______________________________________________
> OpenStack-operators mailing listOpenStack-operators at lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Pavlik Juan José
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130409/f8868aa7/attachment.html>