Thanks for the feedback, but I am assuming that this by itself is not enough.
I guess I should have created the DB before.....
Any other actions that must be done before that?

Best,

George


To add cells you need to issue the following command after nova
service-list lists all your compute nodes as up state!

nova-manage cell_v2 simple_cell_setup --transport-url $transport_url

Where

$transport_url=rabbit://{rabbit_user}:{rabbit_pass}@{rabbit_host}:{rabbit_port}

This command will populate the db and add a transport_url option in
nova.conf on the controller.

Again, you need to issue this command after all computes node show as
up state in nova service-list, otherwise you will still be unable to
spawn instances.

I might have written the command wrong from the top of my head, but
issue a nova-manage help cell_v2 to see the appropiate option.

I am mailing you directly because for some reason i am unable to send
to thr mailing list.

When you reply to the mailing list olease put this mail in it so
others can see it too if they have the same problem.

Thanks,
Mihai

On 2 Mar 2017 20:00, "Georgios Dimitrakakis"  wrote:

It seems that I wont 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 [17]

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 didnt add the [placement] section in nova.conf on the
controller but adding it only on the compute node brought it
online.

I dont 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 havent
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
[6]

[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/ [1] [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 [2] [3]

Best regards,

George

_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[3] [4]
Post to     : openstack@lists.openstack.org [4] [5]
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[5] [6]

Links:
------
[1]





https://docs.openstack.org/ocata/install-guide-rdo/nova-compute-install.html
[7]
[2] https://review.openstack.org/#/c/440140/ [8]
[3] http://controller:35357/v3 [9]
[4]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[10]
[5] mailto:openstack@lists.openstack.org [11]
[6]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[12]
[7] mailto:gior...@acmac.uoc.gr [13]

_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [14]
Post to     : openstack@lists.openstack.org [15]
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [16]

_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [18]
Post to     : openstack@lists.openstack.org [19]
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [20]


Links:
------
[1] https://review.openstack.org/#/c/440140/
[2] http://controller:35357/v3
[3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[4] mailto:openstack@lists.openstack.org
[5] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[6]

https://docs.openstack.org/ocata/install-guide-rdo/nova-compute-install.html
[7]

https://docs.openstack.org/ocata/install-guide-rdo/nova-compute-install.html
[8] https://review.openstack.org/#/c/440140/
[9] http://controller:35357/v3
[10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[11] mailto:openstack@lists.openstack.org
[12] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[13] mailto:gior...@acmac.uoc.gr
[14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[15] mailto:openstack@lists.openstack.org
[16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[17] https://bugs.launchpad.net/openstack-manuals/+bug/1663485
[18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[19] mailto:openstack@lists.openstack.org
[20] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[21] mailto:gior...@acmac.uoc.gr


_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to