Open Stack

 It seems that I won't be able to spawn an image even if this is working 
 for now...

 As you have pointed out there is also this bug: 
 https://bugs.launchpad.net/openstack-manuals/+bug/1663485

 that will not allow me to spawn an image until the Cells have been 
 configured properly.

 So I am looking for a permanent solution...

 Best,

 G.

 On Thu, 02 Mar 2017 10:56:19 +0200, Georgios Dimitrakakis wrote:
> Mihai, I am putting the list here as well...
>
> No I didn't add the [placement] section in nova.conf on the
> controller but adding it only on the compute node brought it online.
>
> I don't know yet if I can spawn an instance and if what you are
> saying is mandatory in Ocata in order to spawn one since I haven't
> reached that part of the installation guide. The verification though
> of the compute services went OK as supposed to by the installation
> guide.
>
> Best,
>
> George
>
>> Hi, 
>>
>> Did you also add the [placement] section in nova.conf on the
>> controller?
>>
>> Also in Ocata AFAIK you also need to create cell_v2 with nova-manage
>> or else you wont be able to spawn instances.
>>
>> But first add the placement section on the controller too in 
>> nova.conf
>> and the computes shoukd come online.
>>
>> On 2 Mar 2017 09:27, "Georgios Dimitrakakis"  wrote:
>>
>>>> On 03/01/2017 05:13 PM, Georgios Dimitrakakis wrote:
>>>>
>>>>> All,
>>>>>
>>>>> I am trying to deploy OpenStack Ocata on bare metal servers
>>>>> using the official
>>>>> guide from here:
>>>>>
>>>>>
>>>>
>>>
>> 
>> https://docs.openstack.org/ocata/install-guide-rdo/nova-compute-install.html
>>>>> [1]
>>>>>
>>>>> Unfortunately I have stuck at deploying the Compute Node due to
>>>>> the following
>>>>> error in the logs when I try to start nova-compute service:
>>>>>
>>>>> 2017-03-02 00:27:16.052 4236 INFO nova.service [-] Starting
>>>>> compute node
>>>>> (version 15.0.0-1.el7)
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service [-]
>>>>> Error starting thread.
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service
>>>>> Traceback (most recent
>>>>> call last):
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service 
>>>>>  File
>>>>> "/usr/lib/python2.7/site-packages/oslo_service/service.py",
>>>>> line 722, in
>>>>> run_service
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service
>>>>> service.start()
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service 
>>>>>  File
>>>>> "/usr/lib/python2.7/site-packages/nova/service.py", line 144,
>>>>> in start
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service
>>>>> self.manager.init_host()
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service 
>>>>>  File
>>>>> "/usr/lib/python2.7/site-packages/nova/compute/manager.py",
>>>>> line 1136, in init_host
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service   
>>>>>  raise
>>>>> exception.PlacementNotConfigured()
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service
>>>>> PlacementNotConfigured:
>>>>> This compute is not configured to talk to the placement
>>>>> service. Configure the
>>>>> [placement] section of nova.conf and restart the service.
>>>>> 2017-03-02 00:27:16.053 4236 ERROR oslo_service.service
>>>>
>>>> Did it actually kill the nova-compute service or just complain in
>>>> the
>>>> logs?  The release notes for nova in Ocata say:
>>>>
>>>>     The nova-compute worker now communicates with the new
>>>> placement API
>>>>     service. Nova determines the placement API service by
>>>> querying the
>>>>     OpenStack service catalog for the service with a service
>>>> type of
>>>>     placement. If there is no placement entry in the service
>>>> catalog,
>>>>     nova-compute will log a warning and no longer try to
>>>> reconnect to the
>>>>     placement API until the nova-worker process is restarted.
>>>>
>>>> Chris
>>>
>>> Hi Chris,
>>>
>>> it is constantly printing this output in the log and also prevents
>>> the openstack-nova-compute.service
>>> from being shown as Active (running) when doing a "systemctl status
>>> openstack-nova-compute.service"
>>>
>>> There is already a proposed bug fix
>>> https://review.openstack.org/#/c/440140/ [2] which seems to solve
>>> this problem
>>>
>>> For reference I ve added the following in the "placement" section
>>> of nova.conf in the compute node
>>>
>>>         [placement]
>>>         # ...
>>>         os_region_name = RegionOne
>>>         project_domain_name = Default
>>>         user_domain_name = Default
>>>         project_name = service
>>>         auth_type = password
>>>         username = nova
>>>         password = NOVA_PASS
>>>         auth_url = http://controller:35357/v3 [3]
>>>
>>> Best regards,
>>>
>>> George
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [4]
>>> Post to     : openstack at lists.openstack.org [5]
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [6]
>>
>>
>> Links:
>> ------
>> [1]
>> 
>> https://docs.openstack.org/ocata/install-guide-rdo/nova-compute-install.html
>> [2] https://review.openstack.org/#/c/440140/
>> [3] http://controller:35357/v3
>> [4] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> [5] mailto:openstack at lists.openstack.org
>> [6] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> [7] mailto:giorgis at acmac.uoc.gr
>
>
> _______________________________________________
> Mailing list: 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack