packstack multi node installation - impossible to launch instances, no availability zones to select

asked 2020-05-20 09:38:06 -0500

gusto gravatar image

updated 2020-05-20 10:26:38 -0500

Hi, as part of my finals this year I need to do a multi node openstack deployment.

The deployment is done on 3 HPE proliant dl360 gen 10 servers, I've installed centOS 7 minimal installation on each of them.

The formation I do take place between secondary school and engineering school so I'm not quite qualified to understand in detail how this product work yet (The project is quite hard compared to others, I'll be principaly evaluated on my documentation and methodology but I of course would be quite happy if I can make it work). So sorry in advance if I'm asking questions that seem obvious for you.

To do the multi node installation I used packstack with openstack stein and I've followed this guide :

First part : (link text)

Second part : (link text)

There was some difference mainly due to deprecated commands and gui changes between the kilo and stein versions of openstack but it went smoothly in general. However I'm stuck at the create instances part (pt. 8 link 2) because when I need to launch an instance there is no AZ available to select and after lots of research I'm quite stuck.

Beside that I have an identical gui in my test environnment as in the guide.

I'm pretty sure that the problem is that my compute node as some sort of bad configuration since I can't see my compute host in the "nova managed services" when using "openstack-status" on the controller and that "openstack hypervisor list" nor "nova service-list --binary nova-compute" return anything when run on the controller node.

If you need me to provide any informations just ask and I'll post it as soon as I can.

I hope you can help me, sorry for my english it is not my first language

openstack-status on controller node :

[root@openstack11 ~(keystone_admin)]# openstack-status 
== Nova services ==
openstack-nova-api:                     active
openstack-nova-compute:                 inactive  (disabled on boot)
openstack-nova-network:                 inactive  (disabled on boot)
openstack-nova-scheduler:               active
openstack-nova-conductor:               active
openstack-nova-console:                 inactive  (disabled on boot)
openstack-nova-consoleauth:             active
openstack-nova-xvpvncproxy:             inactive  (disabled on boot)
== Glance services ==
openstack-glance-api:                   active
openstack-glance-registry:              active
== Keystone service ==
openstack-keystone:                     inactive  (disabled on boot)
== Horizon service ==
openstack-dashboard:                    active
== neutron services ==
neutron-server:                         active
neutron-dhcp-agent:                     inactive  (disabled on boot)
neutron-l3-agent:                       inactive  (disabled on boot)
neutron-metadata-agent:                 inactive  (disabled on boot)
== Cinder services ==
openstack-cinder-api:                   active
openstack-cinder-scheduler:             active
openstack-cinder-volume:                active
openstack-cinder-backup:                active
== Support services ==
openvswitch:                            inactive  (disabled on boot)
dbus:                                   active
target:                                 active
rabbitmq-server:                        active
memcached:                              active
== Keystone users ==
| ID                               | Name      |
| 2ae187417bd749e9bc5d80229201940a | cinder    |
| 386b921494944291851ad10aebfa76f4 | placement |
| 6e2b537efcab4d53b0426210204de528 | swift     |
| 70a73ee1ee0c474db55f1b973e7bfcfd | glance    |
| 8f6b1385b46046358e2c959d59ff9a67 | nova      |
| 91d09db8d0e84be3ace6c36b82e391bc | neutron   |
| f7a225ce951f4f8296871d9c256f9731 | tpi_test  |
| f7fe6d555c3a4c7faaad6480eb7f483d | admin     |
== Glance images ==
| ID                                   | Name         |
| fc4d98dd-46f4-420a-9045-e0ee04b0dd97 | cirros_0.5.1 |
| 486bed16-3a6f-4ecd-a8a1-8c90704baf69 | cirros_0.5.1 |
== Nova managed services ==
| Id                                   | Binary           | Host                    | Zone     | Status  | State | Updated_at                 | Disabled Reason | Forced down |
| b4c84559-f286-428d-8105-2cf157587752 | nova-conductor   | openstack11.localdomain | internal | enabled | up    | 2020-05-20T14:15:46.000000 | -               | False       |
| dc5d2dde-caed-4428-b6b9-973e206ad7e5 | nova-scheduler   | openstack11.localdomain | internal | enabled | up    | 2020-05-20T14:15:46.000000 | -               | False       |
| 5032a3af-b0de-4be1-9465-ad1d08957eea | nova-consoleauth | openstack11.localdomain | internal | enabled | up    | 2020-05-20T14:15:44.000000 | -               | False       |
== Nova ...
edit retag flag offensive close merge delete


Kilo is very old, you should look into the manual deployment guide how to enable the compute service. More specifically, check if your cells configuration is valid. Something like nova-manage cell_v2 list_cells

eblock gravatar imageeblock ( 2020-05-20 10:48:21 -0500 )edit

Especially setting configuration values from an old guide for later releases can cause you trouble and prevent services from starting, although it looks as if you managed to get the controller services running.

eblock gravatar imageeblock ( 2020-05-20 10:50:17 -0500 )edit

Thank you for the response

I knew that the difference in version would be problematic but with the little knowledge I have this guide was the best I could find.

It's public holiday in my country, my teacher is setting up remote access I'll look into it tommorow and post my results/questions!

gusto gravatar imagegusto ( 2020-05-20 10:59:16 -0500 )edit

Is the official documentation so hard to understand?

Bernd Bausch gravatar imageBernd Bausch ( 2020-05-20 18:00:57 -0500 )edit