Need to add info about 'Offloading modes' and 'MTU' to Nodes report

Bug #1575666 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
Medium
Alexander Kislitsky

Bug Description

Steps to reproduce:
Need to add info about 'Offloading modes' and 'MTU' to Nodes report to know how customers use this feature

Expected result:
1. User can download Nodes report from https://product-stats.mirantis.com/
2. Report contains data for "Offloading modes" and "MTU"

summary: - Need to add info about 'Offloading modes' to Nodes report
+ Need to add info about 'Offloading modes' and 'MTU' to Nodes report
description: updated
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Changed in fuel:
status: New → Confirmed
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-stats (master)

Reviewed: https://review.openstack.org/310453
Committed: https://git.openstack.org/cgit/openstack/fuel-stats/commit/?id=85178d53c1a708da341b91480c2d2f0e40d3881a
Submitter: Jenkins
Branch: master

commit 85178d53c1a708da341b91480c2d2f0e40d3881a
Author: Alexander Kislitsky <email address hidden>
Date: Wed Apr 27 15:47:32 2016 +0300

    Interfaces detailed info added into nodes report

    Interfaces info changes:

    - interfaces details added
    - offloading modes added
    - interface properties added: SR-IOV, mtu, dpdk, numa_node

    Meta info about numa topology added: numa nodes, hugepages, distances
    Node error_type field removed. This field doesn't reflect actual
    node state.

    Check that all node attributes were exported added into test.

    Change-Id: I9b5f45dad43fefb0e60a563123dab833293e4332
    Closes-Bug: #1575669
    Closes-Bug: #1575666

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Alexandr Kostrikov (akostrikov-mirantis) wrote :

I have not found in recent report information:
bond_interfaces.count,error_type,group_id,id,manufacturer,meta.cpu.real,meta.cpu.spec.0.frequency,meta.cpu.spec.0.model,meta.cpu.spec.1.frequency,meta.cpu.spec.1.model,meta.cpu.spec.2.frequency,meta.cpu.spec.2.model,meta.cpu.spec.3.frequency,meta.cpu.spec.3.model,meta.cpu.spec.4.frequency,meta.cpu.spec.4.model,meta.cpu.spec.5.frequency,meta.cpu.spec.5.model,meta.cpu.spec.6.frequency,meta.cpu.spec.6.model,meta.cpu.spec.7.frequency,meta.cpu.spec.7.model,meta.cpu.spec.8.frequency,meta.cpu.spec.8.model,meta.cpu.spec.9.frequency,meta.cpu.spec.9.model,meta.cpu.total,meta.disks.0.model,meta.disks.0.name,meta.disks.0.removable,meta.disks.0.size,meta.disks.1.model,meta.disks.1.name,meta.disks.1.removable,meta.disks.1.size,meta.disks.2.model,meta.disks.2.name,meta.disks.2.removable,meta.disks.2.size,meta.disks.3.model,meta.disks.3.name,meta.disks.3.removable,meta.disks.3.size,meta.disks.4.model,meta.disks.4.name,meta.disks.4.removable,meta.disks.4.size,meta.disks.5.model,meta.disks.5.name,meta.disks.5.removable,meta.disks.5.size,meta.disks.6.model,meta.disks.6.name,meta.disks.6.removable,meta.disks.6.size,meta.disks.7.model,meta.disks.7.name,meta.disks.7.removable,meta.disks.7.size,meta.disks.8.model,meta.disks.8.name,meta.disks.8.removable,meta.disks.8.size,meta.disks.9.model,meta.disks.9.name,meta.disks.9.removable,meta.disks.9.size,meta.interfaces.count,meta.memory.devices.0.frequency,meta.memory.devices.0.size,meta.memory.devices.0.type,meta.memory.devices.1.frequency,meta.memory.devices.1.size,meta.memory.devices.1.type,meta.memory.devices.2.frequency,meta.memory.devices.2.size,meta.memory.devices.2.type,meta.memory.devices.3.frequency,meta.memory.devices.3.size,meta.memory.devices.3.type,meta.memory.devices.4.frequency,meta.memory.devices.4.size,meta.memory.devices.4.type,meta.memory.devices.5.frequency,meta.memory.devices.5.size,meta.memory.devices.5.type,meta.memory.devices.6.frequency,meta.memory.devices.6.size,meta.memory.devices.6.type,meta.memory.devices.7.frequency,meta.memory.devices.7.size,meta.memory.devices.7.type,meta.memory.devices.8.frequency,meta.memory.devices.8.size,meta.memory.devices.8.type,meta.memory.devices.9.frequency,meta.memory.devices.9.size,meta.memory.devices.9.type,meta.memory.maximum_capacity,meta.memory.slots,meta.memory.total,meta.system.family,meta.system.manufacturer,meta.system.product,meta.system.version,nic_interfaces.count,online,os,pending_addition,pending_deletion,pending_roles.0,pending_roles.1,pending_roles.2,pending_roles.3,pending_roles.4,platform_name,roles.0,roles.1,roles.2,roles.3,roles.4,status,cluster_id,cluster_fuel_version,master_node_uid,structure.fuel_packages

Changed in fuel:
status: Fix Committed → Confirmed
Revision history for this message
Alexander Kislitsky (akislitsky) wrote :

Moving to 10.0 release after discussion with @Anastasia.

Changed in fuel:
milestone: 9.0 → 10.0
tags: added: area-stats
Revision history for this message
Alexander Kislitsky (akislitsky) wrote :

Mtu and Offloading info is present in the nodes report (downloaded from production server):

- meta.interfaces.0.interface_properties.mtu, ...
- meta.interfaces.0.offloading_modes.0.name, meta.interfaces.0.offloading_modes.0.state, meta.interfaces.0.offloading_modes.0.sub. ...

Moving to FixCommitted.

Changed in fuel:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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