eg: If a pool of centos8 ppc64 nodes goes below 5 notify admins
Script reporting to zabbix on zabbix side we are not parsing the 8, 8stream
Acceptance criteria: * Re-balance CentOS 8 VMs flavor count
@bstinson @arrfab @siddharthvipul1 the JIRA was empty, can we fill this in with enough information so as to begin sizing the work if it is still something valid and needing to be done?
Metadata Update from @dkirwan: - Issue tagged with: need-more-info
Metadata Update from @dkirwan: - Issue untagged with: need-more-info - Issue priority set to: Waiting on Assignee - Issue tagged with: medium-gain, medium-trouble
Metadata Update from @arrfab: - Issue untagged with: medium-gain, medium-trouble - Issue assigned to arrfab - Issue priority set to: None (was: Waiting on Assignee) - Issue tagged with: high-gain, low-trouble
Metadata Update from @dkirwan: - Issue unmarked as depending on: #3
<img alt="duffy-allocation-pool.png" src="/centos-infra/issue/raw/files/970c7d626f6f709dc000b4c5da06c42534651bdfa727ca7ebe47cc6f52b25be7-duffy-allocation-pool.png" />
The zabbix-sender script was in fact automatically detecting correctly all release/architectures from the Duffy MySQL DB/table, but sending to zabbix server, that itself didn't know about all. I so modified the zabbix duffy template so that it stores all key/values pairs received from admin.ci and also have by default trigger on each item.
@siddharthvipul1 : we can easily adapt the minimal number of "Ready" node per release/arch combination so just let me know (started with 5 everywhere and 10 for 7/8 x86_64 which are probably the most requested ones)
Attached is a screenshot of the zabbix graphs showing data coming from Duffy
Metadata Update from @arrfab: - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Login to comment on this ticket.