0

In order to connect Nova-compute to the controller, I would like to install it from source on Ubuntu 20.04. The controller is an all-in-one Devstack.

apt install nova-compute

You can see the configuration of this node below

stack@compute:~# cat /etc/nova/nova-cpu.conf
[DEFAULT]
transport_url = rabbit://stackrabbit:PASSWORD@172.17.0.3:5672/
my_ip = 172.17.0.4

[oslo_messaging_notifications]
transport_url = rabbit://stackrabbit:PASSWORD@172.17.0.3:5672/
driver = messagingv2

[api]
auth_strategy = keystone

[keystone_authtoken]
www_authenticate_uri = http://172.17.0.3/identity
auth_url = http://172.17.0.3/identity
memcached_servers = 172.17.0.3:11211
auth_type = password
project_domain_name = Default
user_domain_name = Default
project_name = service
username = nova
password = PASSWORD

[vnc]
enabled = true
server_listen = 0.0.0.0
server_proxyclient_address = $my_ip
novncproxy_base_url = http://172.17.0.3:6080/vnc_auto.html

[glance]
api_servers = http://172.17.0.3:9292

[oslo_concurrency]
lock_path = /opt/stack/data/nova

[placement]
region_name = RegionOne
project_domain_name = Default
project_name = service
auth_type = password
user_domain_name = Default
auth_url = http://172.17.0.3/identity
username = placement
password = PASSWORD

The controller does not recognize this compute node with the following command.

stack@controller:~$ ./devstack/tools/discover_hosts.sh
Found 0 unmapped computes in cell: 47b7379b-c66c-4d32-adec-xxxxxxxxxx
stack@cntr:~$

Is there a requirement for identifying this node in the controller?

It would be nice if I could configure and install nova-compute separately from devstack.

Saha Ahmadi
  • 3
  • 4
  • The message says „found 0 unmapped“, so I would assume that it was able to map the compute node. Do you see it in ‚openstack compute service list‘? And what about ‚nova-manage cell_v2 list_hosts‘? – eblock Nov 20 '22 at 12:23
  • @eblock I tried to install nova-compute from opendev.org and now I have no problem. Only when I build the instance in the compute node, I get the following error. Exhausted all hosts available for retrying build failures for instance eb67c76f-cd67-4de3-a5fe-91500ae17459. – Saha Ahmadi Nov 26 '22 at 11:17
  • Please read the comments and provide the requested information (add to your question, not in comments). Provide also all relevant nova logs (scheduler, conductor). – eblock Nov 28 '22 at 09:51
  • @eblock my problems solved. thank you (i will review my post and add the solution later) – Saha Ahmadi Nov 29 '22 at 12:38

0 Answers0