Bug 1753950 - Utilization data is not captured for openstack infrastructure provider
Summary: Utilization data is not captured for openstack infrastructure provider
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.10.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.z
Assignee: Marek Aufart
QA Contact: Jad Haj Yahya
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1659453
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 10:51 UTC by Rahul Chincholkar
Modified: 2023-09-07 20:38 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-24 18:57:00 UTC
Category: Bug
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:
dmetzger: mirror+


Attachments (Terms of Use)
Openstack_Infra_Dashboard-Undercloud.png (92.67 KB, image/png)
2019-09-20 10:51 UTC, Rahul Chincholkar
no flags Details

Description Rahul Chincholkar 2019-09-20 10:51:35 UTC
Created attachment 1617152 [details]
Openstack_Infra_Dashboard-Undercloud.png

Description of problem:
- Utilization data for Openstack Infrastructure provider (Undercloud/Director) is not collected by CloudForms
- Dashboard View for Openstack Infrastructure provider is not showing the widget data (screenshot attached `Openstack_Infra_Dashboard-Undercloud.png`)


Version-Release number of selected component (if applicable):
5.10.9.1

How reproducible:
Always

Steps to Reproduce:
1. Add Openstack infrastructure in CF
2. Enable C & U roles in CF and configured
3. Confirm, the metrics are collected in undercloud telemetry
4. Observe the CF dashboard view and utilization data for Openstack infrastructure provider

Actual results:
- Openstack infrastructure provider dashboard does not show widget information (screenshot attached `Openstack_Infra_Dashboard-Undercloud.png`), 
  Global Utilization shows 0GB used for Memory which seems to be incorrect.
- Utilization data is not collected for Openstack Infrastructure provider

Expected results:
- Utilization data should be collected for openstack infra provider
- Dashboard should show the correct widget information

Additional info:
I noticed the below file in my CFME appliance
	~~~
	[root@beaker-cfme ~]# find / -name metrics_capture.rb | grep openstack | grep infra
	/opt/rh/cfme-gemset/bundler/gems/cfme-providers-openstack-8e00a8f4633b/app/models/manageiq/providers/openstack/infra_manager/metrics_capture.rb
	/opt/rh/cfme-gemset/bundler/gems/manageiq-providers-openstack-8e00a8f4633b/app/models/manageiq/providers/openstack/infra_manager/metrics_capture.rb
	~~~

the names of metrics from this file seem different:
	~~~
	  CPU_METERS     = %w(hardware.cpu.util)
	  MEMORY_METERS  = %w(hardware.memory.used
	                      hardware.memory.total
	                      hardware.memory.buffer
	                      hardware.memory.cached)
	  SWAP_METERS    = %w(hardware.memory.swap.avail
	                      hardware.memory.swap.total)
	  DISK_METERS    = %w(hardware.system_stats.io.outgoing.blocks
	                      hardware.system_stats.io.incoming.blocks)
	  NETWORK_METERS = %w(hardware.network.ip.incoming.datagrams
	                      hardware.network.ip.outgoing.datagrams)
	~~~

from what we see in gnocchi metrics for undercloud resource.
	~~~
	| metrics               | compute.instance.booting.time: 785cb85d-3b54-4c57-8340-023ce5058742 |
	|                       | cpu.delta: fade16b5-68d4-4a1a-af6a-6f5c48cb562b                     |
	|                       | cpu: 0af86528-e215-48e9-87f9-323b3c6022cd                           |
	|                       | cpu_l3_cache: 626f2749-f366-4ce1-94cd-10c4b770e641                  |
	|                       | cpu_util: e1a1ca6b-72f1-4703-b66d-8119ea8b333d                      |
	|                       | disk.allocation: 0e5e0019-3af2-4b6d-a423-3f202444093b               |
	|                       | disk.capacity: 3e80d1f3-5b1d-4ba1-a6a6-0842c75ab773                 |
	|                       | disk.ephemeral.size: d3b2e7e2-14a3-4c3c-8d71-ba8385c5c1d6           |
	|                       | disk.iops: 1efa4c14-c872-445e-bbfd-cc6fe3fb7953                     |
	|                       | disk.latency: 0d351ef4-1be3-4888-9097-922d6d2ddc6a                  |
	|                       | disk.read.bytes.rate: dea80922-2240-4ba9-a56f-1a69051985ab          |
	|                       | disk.read.bytes: d2c96fc1-34fd-400a-9504-7ff030dfe1ef               |
	|                       | disk.read.requests.rate: c6058699-7121-430c-ac22-5784f2d585c3       |
	|                       | disk.read.requests: 3c999548-f292-4423-817d-4324caabc236            |
	|                       | disk.root.size: 7302cb47-235c-4477-a8c0-a9cd5c504ced                |
	|                       | disk.usage: efb12f12-b499-4b69-9457-89f39f4c9d25                    |
	|                       | disk.write.bytes.rate: 69e17da5-7159-4b97-a632-a8ce5c122ba6         |
	|                       | disk.write.bytes: b2710b78-8b2f-4e42-a540-06f965e481db              |
	|                       | disk.write.requests.rate: d8a17e00-1148-44d9-a839-2089abebd554      |
	|                       | disk.write.requests: 57d0730a-0972-4ecd-8ed2-8b94c55f3860           |
	|                       | memory.bandwidth.local: 8bf06237-81ed-4df0-8657-fde9787b0754        |
	|                       | memory.bandwidth.total: f3bbaf30-691c-44d0-9dc7-d2988988247d        |
	|                       | memory.resident: 4c4aba7c-0c21-4a45-88ca-4caa07485769               |
	|                       | memory.swap.in: b5ae63e5-639b-4b0e-a1bd-b3bd3be16580                |
	|                       | memory.swap.out: e40d2c30-d458-4995-8f5c-60415f57029c               |
	|                       | memory.usage: 80bf135b-bbab-48ce-867f-e95842d5e451                  |
	|                       | memory: 3db79523-736c-4a3c-a067-d0ffe134e4f6                        |
	|                       | perf.cache.misses: 76c6cf09-7871-4fd8-9e97-5c6ab5134e3c             |
	|                       | perf.cache.references: 0f290bba-3ee6-447e-bcb1-9aff84952cd9         |
	|                       | perf.cpu.cycles: 181cc7cd-03eb-4603-8ac3-4ac6091f85b9               |
	|                       | perf.instructions: 918bb5f0-d359-4e0b-acf3-ffcb8983263c             |
	|                       | vcpus: a7ad9e63-bd72-48b0-8227-21d15c7ff659                         |
	~~~

Comment 8 Rahul Chincholkar 2019-09-24 06:05:35 UTC
> What RHOS version is it?
It is RHOSP 13.

> Different metric names in OpenStack CLI and what CF OSP provider expects could lead to not working SNMP metrics on OpenStack side.
I am not sure if this was working with CFME (with undercloud infra provider) for earlier versions of Openstack. 
However, the metric names in Openstack for compuete/controller node, we see as below, are we referring these names as counter names in CFME?

        ~~~
	| metrics               | compute.instance.booting.time: 785cb85d-3b54-4c57-8340-023ce5058742 |
	|                       | cpu.delta: fade16b5-68d4-4a1a-af6a-6f5c48cb562b                     |
	|                       | cpu: 0af86528-e215-48e9-87f9-323b3c6022cd                           |
	|                       | cpu_l3_cache: 626f2749-f366-4ce1-94cd-10c4b770e641                  |
	|                       | cpu_util: e1a1ca6b-72f1-4703-b66d-8119ea8b333d                      |
	|                       | disk.allocation: 0e5e0019-3af2-4b6d-a423-3f202444093b               |
	|                       | disk.capacity: 3e80d1f3-5b1d-4ba1-a6a6-0842c75ab773                 |
	|                       | disk.ephemeral.size: d3b2e7e2-14a3-4c3c-8d71-ba8385c5c1d6           |
	|                       | disk.iops: 1efa4c14-c872-445e-bbfd-cc6fe3fb7953                     |
	|                       | disk.latency: 0d351ef4-1be3-4888-9097-922d6d2ddc6a                  |
	|                       | disk.read.bytes.rate: dea80922-2240-4ba9-a56f-1a69051985ab          |
	|                       | disk.read.bytes: d2c96fc1-34fd-400a-9504-7ff030dfe1ef               |
	|                       | disk.read.requests.rate: c6058699-7121-430c-ac22-5784f2d585c3       |
	|                       | disk.read.requests: 3c999548-f292-4423-817d-4324caabc236            |
	|                       | disk.root.size: 7302cb47-235c-4477-a8c0-a9cd5c504ced                |
	|                       | disk.usage: efb12f12-b499-4b69-9457-89f39f4c9d25                    |
	|                       | disk.write.bytes.rate: 69e17da5-7159-4b97-a632-a8ce5c122ba6         |
	|                       | disk.write.bytes: b2710b78-8b2f-4e42-a540-06f965e481db              |
	|                       | disk.write.requests.rate: d8a17e00-1148-44d9-a839-2089abebd554      |
	|                       | disk.write.requests: 57d0730a-0972-4ecd-8ed2-8b94c55f3860           |
	|                       | memory.bandwidth.local: 8bf06237-81ed-4df0-8657-fde9787b0754        |
	|                       | memory.bandwidth.total: f3bbaf30-691c-44d0-9dc7-d2988988247d        |
	|                       | memory.resident: 4c4aba7c-0c21-4a45-88ca-4caa07485769               |
	|                       | memory.swap.in: b5ae63e5-639b-4b0e-a1bd-b3bd3be16580                |
	|                       | memory.swap.out: e40d2c30-d458-4995-8f5c-60415f57029c               |
	|                       | memory.usage: 80bf135b-bbab-48ce-867f-e95842d5e451                  |
	|                       | memory: 3db79523-736c-4a3c-a067-d0ffe134e4f6                        |
	|                       | perf.cache.misses: 76c6cf09-7871-4fd8-9e97-5c6ab5134e3c             |
	|                       | perf.cache.references: 0f290bba-3ee6-447e-bcb1-9aff84952cd9         |
	|                       | perf.cpu.cycles: 181cc7cd-03eb-4603-8ac3-4ac6091f85b9               |
	|                       | perf.instructions: 918bb5f0-d359-4e0b-acf3-ffcb8983263c             |
	|                       | vcpus: a7ad9e63-bd72-48b0-8227-21d15c7ff659                         |
	~~~

Comment 12 dmetzger 2019-10-24 18:57:00 UTC
Closing this ticket after discussion between  Engineering/CEE/QE/PM. Based on current knowledge, the problem is solely on the provider side and will be resolved by https://bugzilla.redhat.com/show_bug.cgi?id=1659453

Closing as NOTABUG ... not a bug in CF


Note You need to log in before you can comment on or make changes to this bug.