When ceilometer run in vmware, the statistic for vm net will get phynical nics

Bug #1646663 reported by yaoyuan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Fix Released
Undecided
yaoyuan

Bug Description

In my test, I run openstack with vmware.
When I check the statistic "network.incoming.bytes.rate", I get redundant data:

[root@tecs30-all ~(keystone_admin)]# ceilometer sample-list -m network.incoming.bytes.rate |grep 5ebd1188-29e7-474f-bb7a-53c7d5c823e8
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic0 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.795000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic1 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.794000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic2 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.793000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic3 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.792000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic4 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.791000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic5 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.789000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-4000 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:38:07.788000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic0 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.937000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic1 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.935000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic2 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.934000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic3 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.933000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic4 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.932000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic5 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.931000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-4000 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:47.930000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic0 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.712000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic1 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.711000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic2 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.709000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic3 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.708000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic4 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.707000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic5 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.706000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-4000 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:27.704000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic0 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.789000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic1 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.788000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic2 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.787000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic3 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.786000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic4 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.785000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic5 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.784000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-4000 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:37:07.783000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic0 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.702000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic1 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.701000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic2 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.700000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic3 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.699000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic4 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.698000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-vmnic5 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.697000 |
| instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8-4000 | network.incoming.bytes.rate | gauge | 0.0 | B/s | 2016-11-30T09:36:47.696000 |

In these samples, vminc* are pyhnical nics, and not belong to the vm"instance-0000000e-5ebd1188-29e7-474f-bb7a-53c7d5c823e8", so this sample needs to be filtered out。

Revision history for this message
yaoyuan (yaoyuan) wrote :
yaoyuan (yaoyuan)
Changed in ceilometer:
assignee: nobody → yaoyuan (yaoyuan)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ceilometer (master)

Fix proposed to branch: master
Review: https://review.openstack.org/406807

Changed in ceilometer:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ceilometer (master)

Reviewed: https://review.openstack.org/406807
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=a954f964cc871e841ac7eed6c3d9280413cc8fe9
Submitter: Jenkins
Branch: master

commit a954f964cc871e841ac7eed6c3d9280413cc8fe9
Author: dsxyy <email address hidden>
Date: Mon Dec 5 16:51:40 2016 +0800

    filtered out the phynical nics when query vm nics with VMware API

    When querying the info for vm nics with param set to vm moid, VSphere API will
    return all nics in this vm and all nics in the host. Maybe we need to filter
    out the phynical nics.

    Change-Id: I3a87203eadec7a33343f41474212e1a2005ec500
    Closes-Bug: #1646663

Changed in ceilometer:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ceilometer 8.0.0

This issue was fixed in the openstack/ceilometer 8.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.