Masakari dashboard should use nova service list for populating host candidates
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
masakari-dashboard | Status tracked in Yoga | |||||
Train |
Fix Released
|
Medium
|
Unassigned | |||
Ussuri |
Fix Committed
|
Medium
|
Unassigned | |||
Victoria |
Fix Committed
|
Medium
|
Unassigned | |||
Wallaby |
Fix Committed
|
Medium
|
Unassigned | |||
Xena |
Fix Committed
|
Medium
|
Unassigned | |||
Yoga |
Fix Released
|
Medium
|
Pavlo Shchelokovskyy |
Bug Description
Currently masakari-dashboard uses nova hypervisor list api and hypervisor names to populate the lst of candidates when creating a host.
However, masakari itself uses nova service list instead, and validates the input against it as well since https:/
Since hypervisor host name and compute service host are not necessarily the same (the former for example may be full FQDN while latter just a short hostname) this leads to inability to add hosts to segment via Masakar Dashboard, as request is denied by masakari api
Maakari-dashborad should use the same api to retrieve list of host candidate as masakari-api does, namely compute service list.
The slight change will be that the IDs printed next to the candidate name will change too, as the service ID is generally not the same as hypervisor id.
Changed in masakari-dashboard: | |
assignee: | nobody → Pavlo Shchelokovskyy (pshchelo) |
Changed in masakari-dashboard: | |
status: | New → In Progress |
Changed in masakari-dashboard: | |
importance: | Undecided → Medium |
Reviewed: https:/ /review. opendev. org/c/openstack /masakari- dashboard/ +/810308 /opendev. org/openstack/ masakari- dashboard/ commit/ 021d1c184e5d87b 5b4df5e067954f6 f1cb46b6c4
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 021d1c184e5d87b 5b4df5e067954f6 f1cb46b6c4
Author: Pavlo Shchelokovskyy <email address hidden>
Date: Tue Sep 21 17:15:35 2021 +0300
Use service list instead of hypervisor list
the host names in them are not necessarily the same, 5950bdb1fc2d686 e2301fc6d95 in Masakari.
and Masakari service itself validates the input against
the nova service list, not hypervisor list,
since change I9c591d33f17a8d
Closes-Bug: #1944679 4435c35d410fcb5 6a086a732ef
Change-Id: Id017b91c59aff5