Open Stack

Thats correct, i installed the nova-compute over a vm, and then configured
the nova.conf to point to the correct xenserver.

regards

On Wed, May 4, 2011 at 3:16 PM, Outback Dingo <outbackdingo at gmail.com>wrote:

>
>
> On Wed, May 4, 2011 at 2:05 PM, Leandro Reox <leandro.reox at gmail.com>wrote:
>
>> Ken, i fixed this earlier today, was like you just wrote, a db version
>> mismatch .
>> Now its all working, i configured glance as image repository and the
>> compute is interacting flawlessly with the xenapi .
>> Im going to test the massive deployment with chef this afternoon !
>>
>
> So you installed Openstack in a XCP virtual image like suggested? Did you
> do a separate storage node ?
>
>
>
>> Regards
>> Lele
>>
>>
>> On Wed, May 4, 2011 at 1:51 PM, Ken Pepple <ken.pepple at gmail.com> wrote:
>>
>>> On May 4, 2011, at 5:00 AM,
>>> openstack-operators-request at lists.openstack.org wrote:
>>> > I finally get a nova-controller and a separate nova-compute installed,
>>> but
>>> > the nova compute is not connecting to the controller, everything in the
>>> > nova.conf seems ok but when i restart the nova compute service i get a
>>> > CRITICAL error with this :
>>> >
>>> > 2011-05-03 10:19:56,420 CRITICAL nova [-] (OperationalError) (1054,
>>> "Unknown
>>> > column 'floating_ips_1.auto_assigned' in 'field list'")
>>> >
>>> > Somebody know why the compute node is not seeing this table on the
>>> > controller database ?
>>>
>>>
>>> If I had to guess, the compute node either (1) has an incorrectly
>>> configured sqlconnect flag (most likely) that is pointing the compute node
>>> to it's local sqlite db or (2) is not using the same version of Nova as the
>>> controller.
>>>
>>> To diagnose further:
>>>
>>> (1) sqlconnect flag
>>> Make sure that you have exactly the same nova.conf on both machines
>>> (especially the name:password part). You can also look in the
>>> nova-compute.log for something like
>>> "--sql_connection=mysql://root:nova@localhost/nova"
>>>
>>> (2) nova version / db mismatch
>>> Run these two commands on BOTH machines and make sure they match exactly
>>> to rule out the codebase version mismatch:
>>>
>>>        $ bin/nova-manage version list
>>>        2011.3-dev (2011.3-LOCALBRANCH:LOCALREVISION)
>>>        $ bin/nova-manage db version
>>>        15
>>>
>>> The missing column that is OperationalError-ing was introduced in the
>>> newest migration (15).
>>>
>>> regards
>>> /k
>>>
>>>
>>> ---
>>> Ken Pepple
>>> http://ken.pepple.info/
>>> +1 530 359 8384
>>>
>>>
>>
>> _______________________________________________
>> Openstack-operators mailing list
>> Openstack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20110504/e60af2ab/attachment-0002.html>