Open Stack

I just tried deleting .novaclient directory but didn't work. What i hadn't
tried before was rebooting the server, and that's what solved the problem.
I don't like this magic solutions hahaha, i'd like to what happened. It
could be something related with cache, but i remeber rebooting nova-*
hundreds of times. Thanks!


2013/5/9 Razique Mahroua <razique.mahroua at gmail.com>

> Maybe its cached somehow. Can you check the .nova directory within the
> user's home. Remove it and try again maybe
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahroua at gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 9 mai 2013 à 19:23, Juan José Pavlik Salles <jjpavlik at gmail.com> a
> écrit :
>
> Eventhough i've the same novncproxy_base_url on both compute nodes, when
> the instances are created on Node-1 i get a wrong URL. Now i remember that
> the first IP this compute node had was 172.19.136.170, but i changed that
> weeks ago, that's why i think it could be somewhere else.
>
>
> 2013/5/9 Juan José Pavlik Salles <jjpavlik at gmail.com>
>
>> Hi i double checked this morning, these are my compute nodes:
>>
>> Node-1
>>
>> # novnc #
>> novnc_enable=true
>> novncproxy_base_url=http://*172.16.16.170*:6080/vnc_auto.html
>> vncserver_proxyclient_address=*172.19.136.10*
>>
>> #Para que tenga migracion en vivo hay que usar la 0.0.0.0
>> vncserver_listen=0.0.0.0
>>
>> Node-2
>>
>> # novnc #
>> novnc_enable=true
>> novncproxy_base_url=http://*172.16.16.170*:6080/vnc_auto.html
>> vncserver_proxyclient_address=*172.19.136.11*
>> #Para que tenga migracion en vivo hay que usar la 0.0.0.0
>> vncserver_listen=0.0.0.0
>>
>> I just rebooted nova-api and nova-consoleauth on both of them and created
>> two new instaces, but the problem's still there. It's really confusing.
>>
>>
>> 2013/5/9 Razique Mahroua <razique.mahroua at gmail.com>
>>
>>> Hi,
>>> no this information is only within nova.conf
>>> Here are my settings :
>>>
>>> # NOVNC CONSOLE
>>>
>>> vncserver_proxyclient_address=192.168.2.20
>>>
>>> novnc_enabled=true
>>> novncproxy_port=6080
>>> novncproxy_base_url=http://*PUBLIC-IP*:6080/vnc_auto.html
>>> vncserver_listen=0.0.0.0
>>> root_helper=sudo nova-rootwrap
>>> verbose=True
>>>
>>>
>>> Make sure to update the proxy client_address so it matches every node
>>> IP, the rest should remain unchanged and restart the following services
>>> afterwards:
>>> nova-api
>>> nova-consoleauth
>>>
>>> *Razique Mahroua** - **Nuage & Co*
>>> razique.mahroua at gmail.com
>>> Tel : +33 9 72 37 94 15
>>>
>>> <NUAGECO-LOGO-Fblan_petit.jpg>
>>>
>>> Le 9 mai 2013 à 04:39, Juan José Pavlik Salles <jjpavlik at gmail.com> a
>>> écrit :
>>>
>>> I've two compute nodes, and both of them have this in nova.conf
>>>
>>> novncproxy_base_url=http://172.16.16.170:6080/vnc_auto.html
>>>
>>> Is this information saved somewhere else? maybe in the nova database?
>>>
>>> 2013/5/8 Razique Mahroua <razique.mahroua at gmail.com>
>>>
>>>> Hi,
>>>> looks for the /etc/nova/nova.conf file on your compute nodes :)
>>>> how many nodes do you have?
>>>>
>>>> *Razique Mahroua** - **Nuage & Co*
>>>> razique.mahroua at gmail.com
>>>> Tel : +33 9 72 37 94 15
>>>>
>>>> <NUAGECO-LOGO-Fblan_petit.jpg>
>>>>
>>>> Le 8 mai 2013 à 22:34, Juan José Pavlik Salles <jjpavlik at gmail.com> a
>>>> écrit :
>>>>
>>>> I've created 3 different instances and they have differents novnc URL
>>>> (two of them)
>>>>
>>>> root at locro:/etc/nova# nova --os-username=admin --os-tenant-name=admin
>>>> --os-password=XXX --os-auth-url=http://172.19.136.1:35357/v2.0get-vnc-console 68c770a7-2678-4c1e-8028-7c9401f5319d  novnc
>>>>
>>>> +-------+-------------------------------------------------------------------------------------+
>>>> | Type  | Url
>>>>                       |
>>>>
>>>> +-------+-------------------------------------------------------------------------------------+
>>>> | novnc |
>>>> http://172.19.136.170:6080/vnc_auto.html?token=4ac35743-3f06-4000-b039-706d82cb4dd4|
>>>>
>>>> +-------+-------------------------------------------------------------------------------------+
>>>> root at locro:/etc/nova# nova --os-username=admin --os-tenant-name=admin
>>>> --os-password=XXX --os-auth-url=http://172.19.136.1:35357/v2.0get-vnc-console 8014674a-6c5b-462c-abd2-eea82cd03dcd novnc
>>>>
>>>> +-------+------------------------------------------------------------------------------------+
>>>> | Type  | Url
>>>>                      |
>>>>
>>>> +-------+------------------------------------------------------------------------------------+
>>>> | novnc |
>>>> http://172.16.16.170:6080/vnc_auto.html?token=6b3629a2-1c0f-4410-93d9-da12931f2e30|
>>>>
>>>> +-------+------------------------------------------------------------------------------------+
>>>> root at locro:/etc/nova# nova --os-username=admin --os-tenant-name=admin
>>>> --os-password=XXX --os-auth-url=http://172.19.136.1:35357/v2.0get-vnc-console cd7f99be-a962-40e2-bc01-66f4274df736 novnc
>>>>
>>>> +-------+-------------------------------------------------------------------------------------+
>>>> | Type  | Url
>>>>                       |
>>>>
>>>> +-------+-------------------------------------------------------------------------------------+
>>>> | novnc |
>>>> http://172.19.136.170:6080/vnc_auto.html?token=4189f6a2-0905-49a4-a66f-2a4e6dc496ff|
>>>>
>>>> +-------+-------------------------------------------------------------------------------------+
>>>> root at locro:/etc/nova#
>>>>
>>>> Where dose this URL come from? Thankss
>>>>
>>>>
>>>> 2013/5/7 Juan José Pavlik Salles <jjpavlik at gmail.com>
>>>>
>>>>> Here i come with a new problem, this time with novnc and dashboard.
>>>>> When i try to connect to the vnc of a running instance from the dashboard i
>>>>> get a wrong url, but is the same one i get when i run nova get-vnc-console:
>>>>>
>>>>> root at locro:/etc# nova --os-username=admin --os-tenant-name=admin
>>>>> --os-password=XXX --os-auth-url=http://172.19.136.1:35357/v2.0get-vnc-console f0fc0fc6-e4c2-4518-a0e0-589ce4cc8903  novnc
>>>>>
>>>>> +-------+-------------------------------------------------------------------------------------+
>>>>> | Type  | Url
>>>>>                         |
>>>>>
>>>>> +-------+-------------------------------------------------------------------------------------+
>>>>> | novnc |
>>>>> http://172.19.136.170:6080/vnc_auto.html?token=c7921e91-a325-45d4-817d-e3f742d710bd|
>>>>>
>>>>> +-------+-------------------------------------------------------------------------------------+
>>>>>
>>>>> I don't have any host running on 172.19.136.170, this is my nova.conf:
>>>>>
>>>>> # novnc #
>>>>> novnc_enable=true
>>>>> novncproxy_base_url=http://172.16.16.170:6080/vnc_auto.html
>>>>> vncserver_proxyclient_address=172.19.136.11
>>>>> #Para que tenga migracion en vivo hay que usar la 0.0.0.0
>>>>> vncserver_listen=0.0.0.0
>>>>>
>>>>> Where 172.16.16.170 is my controller node, and 172.19.136.11 is a
>>>>> compute node. Does anybody know where this link come from? Because it's not
>>>>> taking novncproxy_base_url.
>>>>>
>>>>> --
>>>>> Pavlik Juan José
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Pavlik Salles Juan José
>>>>  _______________________________________________
>>>> OpenStack-operators mailing list
>>>> OpenStack-operators at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Pavlik Salles Juan José
>>>
>>>
>>>
>>
>>
>> --
>> Pavlik Salles Juan José
>>
>
>
>
> --
> Pavlik Salles Juan José
>
>
>


-- 
Pavlik Salles Juan José
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130509/878dd83b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NUAGECO-LOGO-Fblan_petit.jpg
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130509/878dd83b/attachment-0001.jpg>