[Starlingx-discuss] Openstack application can not be deployed on some compute nodes.

Zvonar, Bill Bill.Zvonar at windriver.com
Wed Dec 16 15:46:34 UTC 2020


Hi there – please note that StarlingX 2.0 is End of Life, and no longer supported.

Please try with the latest released version, StarlingX 4.0.

Bill…

From: parkeryan(闫志杰) <parkeryan at tencent.com>
Sent: Wednesday, December 16, 2020 2:53 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Openstack application can not be deployed on some compute nodes.

[Please note this e-mail is from an EXTERNAL e-mail address]
Hello, all.

I deployed StarlingX 2.0 on bare metal standard with controller storage, and got some problems while applying stx-openstack application. Here is the details.

[sysadmin at controller-0 log(keystone_admin)]$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+
| id | hostname     | personality | administrative | operational | availability |
+----+--------------+-------------+----------------+-------------+--------------+
| 1  | controller-0 | controller  | unlocked       | enabled     | available    |
| 18 | controller-1 | controller  | unlocked       | enabled     | available    |
| 19 | compute-0    | worker      | unlocked       | enabled     | available    |
| 20 | compute-1    | worker      | unlocked       | enabled     | available    |
| 21 | compute-2    | worker      | unlocked       | enabled     | available    |
| 22 | compute-3    | worker      | unlocked       | enabled     | available    |
| 23 | compute-4    | worker      | unlocked       | enabled     | available    |
| 24 | compute-5    | worker      | unlocked       | enabled     | available    |
| 25 | compute-6    | worker      | unlocked       | enabled     | available    |
| 26 | compute-7    | worker      | unlocked       | enabled     | available    |
| 27 | compute-8    | worker      | unlocked       | enabled     | available    |
| 29 | compute-10   | worker      | unlocked       | enabled     | available    |
| 30 | compute-11   | worker      | unlocked       | enabled     | available    |
| 32 | compute-12   | worker      | unlocked       | enabled     | available    |
| 33 | compute-13   | worker      | unlocked       | enabled     | available    |
+----+--------------+-------------+----------------+-------------+--------------+

And I labed all compute nodes to support openstack application.

[sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-0
+-----------+------------------------+-------------+
| hostname  | label key              | label value |
+-----------+------------------------+-------------+
| compute-0 | openstack-compute-node | enabled     |
| compute-0 | openvswitch            | enabled     |
| compute-0 | sriov                  | enabled     |
| compute-0 | sriovdp                | enabled     |
+-----------+------------------------+-------------+
[sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-1
+-----------+------------------------+-------------+
| hostname  | label key              | label value |
+-----------+------------------------+-------------+
| compute-1 | openstack-compute-node | enabled     |
| compute-1 | openvswitch            | enabled     |
| compute-1 | sriov                  | enabled     |
| compute-1 | sriovdp                | enabled     |
+-----------+------------------------+-------------+
[sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-2
+-----------+------------------------+-------------+
| hostname  | label key              | label value |
+-----------+------------------------+-------------+
| compute-2 | openstack-compute-node | enabled     |
| compute-2 | openvswitch            | enabled     |
| compute-2 | sriov                  | enabled     |
| compute-2 | sriovdp                | enabled     |
+-----------+------------------------+-------------+
[sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-3
+-----------+------------------------+-------------+
| hostname  | label key              | label value |
+-----------+------------------------+-------------+
| compute-3 | openstack-compute-node | enabled     |
| compute-3 | openvswitch            | enabled     |
| compute-3 | sriov                  | enabled     |
| compute-3 | sriovdp                | enabled     |
+-----------+------------------------+-------------+
[sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-12
+------------+------------------------+-------------+
| hostname   | label key              | label value |
+------------+------------------------+-------------+
| compute-12 | openstack-compute-node | enabled     |
| compute-12 | openvswitch            | enabled     |
| compute-12 | sriov                  | enabled     |
| compute-12 | sriovdp                | enabled     |
+------------+------------------------+-------------+
[sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-13
+------------+------------------------+-------------+
| hostname   | label key              | label value |
+------------+------------------------+-------------+
| compute-13 | openstack-compute-node | enabled     |
| compute-13 | openvswitch            | enabled     |
| compute-13 | sriov                  | enabled     |
| compute-13 | sriovdp                | enabled     |
+------------+------------------------+-------------+

However, I found some of them didn’t take effect by openstack host list command.

controller-0:~$ openstack host list
+----------------------------------+-------------+----------+
| Host Name                        | Service     | Zone     |
+----------------------------------+-------------+----------+
| nova-consoleauth-d54b6864c-r78q8 | consoleauth | internal |
| nova-conductor-855dff79f-rltf4   | conductor   | internal |
| nova-consoleauth-d54b6864c-78nkh | consoleauth | internal |
| nova-conductor-855dff79f-9kn2j   | conductor   | internal |
| nova-scheduler-6554b9c6bb-hqmw2  | scheduler   | internal |
| nova-scheduler-6554b9c6bb-nzjfl  | scheduler   | internal |
| compute-5                        | compute     | nova     |
| compute-8                        | compute     | nova     |
| compute-4                        | compute     | nova     |
| compute-11                       | compute     | nova     |
| compute-7                        | compute     | nova     |
| compute-1                        | compute     | nova     |
| compute-6                        | compute     | nova     |
| compute-0                        | compute     | nova     |
| compute-10                       | compute     | nova     |
+----------------------------------+-------------+----------+

From which I found compute-2, compute-3, compute-12 and compute-13 is nod displayed in openstack host.

I wonder how to solve the problem, and is there some logs can help to determine what happedn to these compute nodes.

Thanks in advance.


Best regards
parkeryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20201216/0ba17fcc/attachment-0001.html>


More information about the Starlingx-discuss mailing list