Thanks Sudipto for pointing out the tool; another light weight tool I am thinking is 'ethtool', in order to collect basic NIC info, including "speed".
Rao Adnan Khan AT&T Integrated Cloud (AIC) Development | SE Software Development & Engineering (SD&E) Emai: [email protected] Cell phone: 972-342-5638 RESTRICTED - PROPRIETARY INFORMATION This email is the property of AT&T and intended solely for the use of the addressee. If you have reason to believe you have received this in error, please delete this immediately; any other use, retention, dissemination, copying or printing of this email is strictly prohibited. -----Original Message----- From: Sudipto Biswas [mailto:[email protected]] Sent: Monday, June 20, 2016 12:12 AM To: [email protected]; [email protected] Subject: Re: [openstack-dev] Recommended ways to find compute node's bandwidth (physical NIC) Thanks Jay for pointing this out. Adnan, Yeah - you could use PcP - if that module gets integrated with Nova. For your benefit, here are some of the metrics that PcP can provide related to the physical NIC: pminfo | grep network.interface <== Listing the available metrics. network.interface.collisions network.interface.mtu network.interface.speed network.interface.baudrate network.interface.duplex network.interface.up network.interface.running network.interface.inet_addr network.interface.ipv6_addr network.interface.ipv6_scope network.interface.hw_addr network.interface.in.bytes network.interface.in.packets network.interface.in.errors network.interface.in.drops network.interface.in.fifo network.interface.in.frame network.interface.in.compressed network.interface.in.mcasts network.interface.out.bytes network.interface.out.packets network.interface.out.errors network.interface.out.drops network.interface.out.fifo network.interface.out.carrier network.interface.out.compressed network.interface.total.bytes network.interface.total.packets network.interface.total.errors network.interface.total.drops network.interface.total.mcasts # pmval network.interface.out.bytes <== A sample metric value. metric: network.interface.out.bytes host: <my_host> semantics: cumulative counter (converting to rate) units: byte (converting to byte / sec) samples: all wlp3s0 lo virbr0 wc0 em1 virbr0-nic 0.0 0.0 0.0 0.0 0.0 0.0 85.96 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 1588. 4031. 0.0 787.6 0.0 0.0 492.7 0.0 0.0 155.9 0.0 0.0 As you might observe, there's a plenty for you to draw inferences. Hope this helps! Cheers, Sudipto On Monday 20 June 2016 09:07 AM, Jay Pipes wrote: > On 06/16/2016 04:16 PM, KHAN, RAO ADNAN wrote: >> I am writing a nova filter that will check for the compute node (max, >> avg) bandwidth, before instantiating an instance. What are some of the >> recommended tools that can provide this info in real time? Does any >> openstack component hold this info already? > > You may want to chat with Sudipta Biswas (cc'd). The PCP module (yes, > it's an awkward name for a performance profiling module...) does some > of what you're looking for and Sudipta has been attempting to > integrate it with Nova for this express purpose. > > Best, > -jay > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
