[Starlingx-discuss] Stx-openstack application doesn't take effect on extra compute nodes.
Dear all, After deploying StarlingX 2.0 with stx-openstack in 2+2 mode, I added some more compute nodes, and labeled them with system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled system host-label-assign $NODE sriov=enabled After unlocking these extra compute nodes, I found the stx-openstack application didn’t deploy on them, even if I reapplied the stx-openstack application. Was there some action I should take to trigger the deploying? Here is the detailed log: [sysadmin@controller-0 ~(keystone_admin)]$ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-17-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ [sysadmin@controller-0 ~(keystone_admin)]$ [sysadmin@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | unlocked | enabled | available | | 3 | compute-0 | worker | unlocked | enabled | available | | 4 | compute-1 | worker | unlocked | enabled | available | | 5 | compute-2 | worker | unlocked | enabled | available | | 6 | compute-3 | worker | unlocked | enabled | available | | 7 | compute-4 | worker | unlocked | enabled | available | | 8 | compute-5 | worker | unlocked | enabled | available | | 9 | compute-6 | worker | unlocked | enabled | available | | 10 | compute-7 | worker | unlocked | enabled | available | | 11 | compute-8 | worker | unlocked | enabled | available | | 12 | compute-9 | worker | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ [sysadmin@controller-0 ~(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@controller-0 ~(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@controller-0 ~(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@controller-0 ~(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@controller-0 ~(keystone_admin)]$ system host-label-list compute-4 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-4 | openstack-compute-node | enabled | | compute-4 | openvswitch | enabled | | compute-4 | sriov | enabled | | compute-4 | sriovdp | enabled | +-----------+------------------------+-------------+ controller-0:~/sow$ openstack host list +-----------------------------------+-------------+----------+ | Host Name | Service | Zone | +-----------------------------------+-------------+----------+ | nova-consoleauth-67b4db556b-z6s6c | consoleauth | internal | | nova-consoleauth-67b4db556b-w7ztm | consoleauth | internal | | nova-conductor-76d979ff86-6l8ht | conductor | internal | | nova-scheduler-cd946798c-wkjpn | scheduler | internal | | nova-conductor-76d979ff86-l8s94 | conductor | internal | | nova-scheduler-cd946798c-vdmvb | scheduler | internal | | compute-1 | compute | nova | | compute-0 | compute | nova | +-----------------------------------+-------------+----------+
Are there any errors in your armada log in /var/log/armada? I ever encountered an issue. The system showed my application had been applied. But in fact, armada ran into some errors. From: parkeryan(闫志杰) <parkeryan@tencent.com> Sent: Tuesday, December 10, 2019 7:43 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Stx-openstack application doesn't take effect on extra compute nodes. Dear all, After deploying StarlingX 2.0 with stx-openstack in 2+2 mode, I added some more compute nodes, and labeled them with system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled system host-label-assign $NODE sriov=enabled After unlocking these extra compute nodes, I found the stx-openstack application didn’t deploy on them, even if I reapplied the stx-openstack application. Was there some action I should take to trigger the deploying? Here is the detailed log: [sysadmin@controller-0 ~(keystone_admin)]$ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-17-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ [sysadmin@controller-0 ~(keystone_admin)]$ [sysadmin@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | unlocked | enabled | available | | 3 | compute-0 | worker | unlocked | enabled | available | | 4 | compute-1 | worker | unlocked | enabled | available | | 5 | compute-2 | worker | unlocked | enabled | available | | 6 | compute-3 | worker | unlocked | enabled | available | | 7 | compute-4 | worker | unlocked | enabled | available | | 8 | compute-5 | worker | unlocked | enabled | available | | 9 | compute-6 | worker | unlocked | enabled | available | | 10 | compute-7 | worker | unlocked | enabled | available | | 11 | compute-8 | worker | unlocked | enabled | available | | 12 | compute-9 | worker | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ [sysadmin@controller-0 ~(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@controller-0 ~(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@controller-0 ~(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@controller-0 ~(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@controller-0 ~(keystone_admin)]$ system host-label-list compute-4 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-4 | openstack-compute-node | enabled | | compute-4 | openvswitch | enabled | | compute-4 | sriov | enabled | | compute-4 | sriovdp | enabled | +-----------+------------------------+-------------+ controller-0:~/sow$ openstack host list +-----------------------------------+-------------+----------+ | Host Name | Service | Zone | +-----------------------------------+-------------+----------+ | nova-consoleauth-67b4db556b-z6s6c | consoleauth | internal | | nova-consoleauth-67b4db556b-w7ztm | consoleauth | internal | | nova-conductor-76d979ff86-6l8ht | conductor | internal | | nova-scheduler-cd946798c-wkjpn | scheduler | internal | | nova-conductor-76d979ff86-l8s94 | conductor | internal | | nova-scheduler-cd946798c-vdmvb | scheduler | internal | | compute-1 | compute | nova | | compute-0 | compute | nova | +-----------------------------------+-------------+----------+
I am sorry to disturb you, and I think maybe it is due to lacking of patience. After one night, it became okay, and each compute node can be identified by openstack application, and VMs can also be deployed, it works, I think. controller-0:~$ openstack host list +-----------------------------------+-------------+----------+ | Host Name | Service | Zone | +-----------------------------------+-------------+----------+ | nova-consoleauth-67b4db556b-z6s6c | consoleauth | internal | | nova-consoleauth-67b4db556b-w7ztm | consoleauth | internal | | nova-conductor-76d979ff86-6l8ht | conductor | internal | | nova-scheduler-cd946798c-wkjpn | scheduler | internal | | nova-conductor-76d979ff86-l8s94 | conductor | internal | | nova-scheduler-cd946798c-vdmvb | scheduler | internal | | compute-1 | compute | nova | | compute-0 | compute | nova | | compute-3 | compute | nova | | compute-2 | compute | nova | | compute-7 | compute | nova | | compute-5 | compute | nova | | compute-4 | compute | nova | | compute-9 | compute | nova | | compute-6 | compute | nova | | compute-8 | compute | nova | +-----------------------------------+-------------+----------+ controller-0:~$ openstack server list +--------------------------------------+----------------+--------+-----------------------------+--------+--------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+----------------+--------+-----------------------------+--------+--------+ | e817723f-2a87-41cd-b877-2245c921e6da | leo-plane2-sw2 | ACTIVE | leo-mgmt-net=192.168.10.232 | leo_v2 | sim | | b17d9bca-34ae-4695-aa02-8972ba751774 | leo-plane2-sw1 | ACTIVE | leo-mgmt-net=192.168.10.240 | leo_v2 | sim | | 71a449e5-9bbd-42d8-96a4-5c8655d4680a | leo-plane1-sw2 | ACTIVE | leo-mgmt-net=192.168.10.98 | leo_v2 | sim | | 76d15983-8f91-4fe1-b45e-2551cd67089d | leo-plane1-sw1 | ACTIVE | leo-mgmt-net=192.168.10.178 | leo_v2 | sim | | 185bb3e9-c86c-4022-b752-4fbf03a816e6 | leo-pod2-tor4 | ACTIVE | leo-mgmt-net=192.168.10.238 | leo_v2 | sim | | ba54f234-2f7d-4fd5-bec5-6fe98dcbf934 | leo-pod2-tor3 | ACTIVE | leo-mgmt-net=192.168.10.63 | leo_v2 | sim | | ab8c7f87-4bca-47f7-ba55-99761f49f379 | leo-pod2-tor2 | ACTIVE | leo-mgmt-net=192.168.10.135 | leo_v2 | sim | | f1db761e-48d3-4727-93b1-2bdaf802fd49 | leo-pod2-tor1 | ACTIVE | leo-mgmt-net=192.168.10.16 | leo_v2 | sim | | 6ad274b4-fd33-45e4-ad62-d7e402b23e8a | leo-pod2-fab2 | ACTIVE | leo-mgmt-net=192.168.10.220 | leo_v2 | sim | | e5d34e60-930c-4ca2-b48f-5c1069e001f6 | leo-pod2-fab1 | ACTIVE | leo-mgmt-net=192.168.10.162 | leo_v2 | sim | | 1b40b14e-fd9a-4b51-8f5f-4f97c2f3d5e9 | leo-pod1-tor4 | ACTIVE | leo-mgmt-net=192.168.10.208 | leo_v2 | sim | | dedaf9d8-1064-4637-929a-235f272846fe | leo-pod1-tor3 | ACTIVE | leo-mgmt-net=192.168.10.247 | leo_v2 | sim | | c1279e60-3abd-46dc-9084-7f93673f4e30 | leo-pod1-tor2 | ACTIVE | leo-mgmt-net=192.168.10.105 | leo_v2 | sim | | ed14a773-496c-4b03-a900-c54e44596fcd | leo-pod1-tor1 | ACTIVE | leo-mgmt-net=192.168.10.221 | leo_v2 | sim | | 45b08f00-974a-4bc3-b7ba-f0d954660da2 | leo-pod1-fab2 | ACTIVE | leo-mgmt-net=192.168.10.139 | leo_v2 | sim | | dbc4873f-f946-441b-bf22-7c93a2052f41 | leo-pod1-fab1 | ACTIVE | leo-mgmt-net=192.168.10.43 | leo_v2 | sim | +--------------------------------------+----------------+--------+-----------------------------+--------+--------+ Sorry again, and thanks for your reply. 发件人: "Wang, Yi C" <yi.c.wang@intel.com> 日期: 2019年12月11日 星期三 08:34 收件人: "parkeryan(闫志杰)" <parkeryan@tencent.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> 主题: RE: [Starlingx-discuss] Stx-openstack application doesn't take effect on extra compute nodes.(Internet mail) Are there any errors in your armada log in /var/log/armada? I ever encountered an issue. The system showed my application had been applied. But in fact, armada ran into some errors. From: parkeryan(闫志杰) <parkeryan@tencent.com> Sent: Tuesday, December 10, 2019 7:43 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Stx-openstack application doesn't take effect on extra compute nodes. Dear all, After deploying StarlingX 2.0 with stx-openstack in 2+2 mode, I added some more compute nodes, and labeled them with system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled system host-label-assign $NODE sriov=enabled After unlocking these extra compute nodes, I found the stx-openstack application didn’t deploy on them, even if I reapplied the stx-openstack application. Was there some action I should take to trigger the deploying? Here is the detailed log: [sysadmin@controller-0 ~(keystone_admin)]$ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-17-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | +---------------------+-----------------------------+-------------------------------+--------------------+---------+-----------+ [sysadmin@controller-0 ~(keystone_admin)]$ [sysadmin@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | unlocked | enabled | available | | 3 | compute-0 | worker | unlocked | enabled | available | | 4 | compute-1 | worker | unlocked | enabled | available | | 5 | compute-2 | worker | unlocked | enabled | available | | 6 | compute-3 | worker | unlocked | enabled | available | | 7 | compute-4 | worker | unlocked | enabled | available | | 8 | compute-5 | worker | unlocked | enabled | available | | 9 | compute-6 | worker | unlocked | enabled | available | | 10 | compute-7 | worker | unlocked | enabled | available | | 11 | compute-8 | worker | unlocked | enabled | available | | 12 | compute-9 | worker | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ [sysadmin@controller-0 ~(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@controller-0 ~(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@controller-0 ~(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@controller-0 ~(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@controller-0 ~(keystone_admin)]$ system host-label-list compute-4 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-4 | openstack-compute-node | enabled | | compute-4 | openvswitch | enabled | | compute-4 | sriov | enabled | | compute-4 | sriovdp | enabled | +-----------+------------------------+-------------+ controller-0:~/sow$ openstack host list +-----------------------------------+-------------+----------+ | Host Name | Service | Zone | +-----------------------------------+-------------+----------+ | nova-consoleauth-67b4db556b-z6s6c | consoleauth | internal | | nova-consoleauth-67b4db556b-w7ztm | consoleauth | internal | | nova-conductor-76d979ff86-6l8ht | conductor | internal | | nova-scheduler-cd946798c-wkjpn | scheduler | internal | | nova-conductor-76d979ff86-l8s94 | conductor | internal | | nova-scheduler-cd946798c-vdmvb | scheduler | internal | | compute-1 | compute | nova | | compute-0 | compute | nova | +-----------------------------------+-------------+----------+
participants (2)
-
parkeryan(闫志杰)
-
Wang, Yi C