If you don't know what IndentationError is, I think there is a long way to go before you familiar with Python.
I suggest you discus something about developer issue in this Development Mailing List Your problem is that you have modify the file /opt/stack/ceilometer/ceilometer/compute/notifications/cpu.py, but use wrong indentation, for example, you're using tab in linux vim, but set wrong configuration for .vimrc, so it gets wrong indentation comparing to original code Let's end it, please On Wed, Nov 12, 2014 at 10:41 AM, Du Jun <dj199...@gmail.com> wrote: > Hi all, > > I think I have found the reason why I am unable to get compute.node.cpu* > information from command: > > $ ceilometer meter-list > > I get the error message from ceilometer-agent-notification.log > > 2014-11-11 17:10:40.015 19486 ERROR stevedore.extension [-] Could not load > 'cpu_user_percent': unexpected indent (cpu.py, line 58) > > 2014-11-11 17:10:40.015 19486 ERROR stevedore.extension [-] unexpected > indent (cpu.py, line 58) > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension Traceback (most > recent call last): > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension File > "/usr/local/lib/python2.7/dist-packages/stevedore/extension.py", line 162, > in _load_plugins > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension > verify_requirements, > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension File > "/usr/local/lib/python2.7/dist-packages/stevedore/extension.py", line 178, > in _load_one_plugin > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension plugin = > ep.load(require=verify_requirements) > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension File > "/usr/local/lib/python2.7/dist-packages/pkg_resources.py", line 2184, in > load > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension ['__name__']) > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension File > "/opt/stack/ceilometer/ceilometer/compute/notifications/cpu.py", line 58 > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension if info: > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension ^ > > 2014-11-11 17:10:40.015 19486 TRACE stevedore.extension IndentationError: > unexpected indent > > > It seems that the python stevedore throws the error. I am not familiar > with python stevedore, so I have no idea about the error message now. Any > help will be appreciated. > > > > -- > > Regards, > > Frank > > 2014-11-11 10:52 GMT+08:00 Du Jun <dj199...@gmail.com>: > >> $ ceilometer sample-list -m compute.node.cpu.idle.time >> >> I still get nothing. >> >> >> -- >> Regards, >> Frank >> >> 2014-11-07 21:17 GMT+08:00 Hang H Liu <hang...@cn.ibm.com>: >> >>> You didn't provide the full name of the meter. Here are results in my >>> system. >>> >>> localadmin@ostest2:~/devstack$ ceilometer sample-list -m >>> compute.node.cpu >>> +-------------+------+------+--------+------+-----------+ >>> | Resource ID | Name | Type | Volume | Unit | Timestamp | >>> +-------------+------+------+--------+------+-----------+ >>> +-------------+------+------+--------+------+-----------+ >>> >>> localadmin@ostest2:~/devstack$ ceilometer sample-list -m >>> compute.node.cpu.idle.time | head >>> >>> +-----------------+----------------------------+------------+-----------------+------+----------------------------+ >>> | Resource ID | Name | Type | Volume >>> | Unit | Timestamp | >>> >>> +-----------------+----------------------------+------------+-----------------+------+----------------------------+ >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.876353234e+16 | ns | 2014-11-07T13:15:06.580099 | >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.876282715e+16 | ns | 2014-11-07T13:14:06.587392 | >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.87621264e+16 | ns | 2014-11-07T13:13:06.556272 | >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.876141325e+16 | ns | 2014-11-07T13:12:05.596962 | >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.876070965e+16 | ns | 2014-11-07T13:11:05.576771 | >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.875998092e+16 | ns | 2014-11-07T13:10:03.597978 | >>> | ostest2_ostest2 | compute.node.cpu.idle.time | cumulative | >>> 3.87592522e+16 | ns | 2014-11-07T13:09:01.583991 | >>> >>> >>> Best Regards, >>> Liu, Hang(Henry) >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> Du Jun <dj199...@gmail.com> 写于 2014/11/07 15:46:21: >>> >>> > From: Du Jun <dj199...@gmail.com> >>> > To: "OpenStack Development Mailing List (not for usage questions)" >>> > <openstack-dev@lists.openstack.org> >>> > Date: 2014/11/07 15:50 >>> >>> > Subject: Re: [openstack-dev] [ceilometer] unable to collect >>> > compute.node.cpu.* data >>> > >>> > Nothing shows when I type command: >>> > >>> > vcap@ubuntu:~$ ceilometer sample-list --meter compute.node.cpu >>> > +-------------+------+------+--------+------+-----------+ >>> > | Resource ID | Name | Type | Volume | Unit | Timestamp | >>> > +-------------+------+------+--------+------+-----------+ >>> > +-------------+------+------+--------+------+-----------+ >>> > >>> > So, I guess there is no sample data concerning on "compute.node.cpu" >>> > in the database. >>> > >>> > I assume the problem is about the "pipeline.yaml", the pipeline in >>> > my devstack system is: >>> > >>> > --- >>> > sources: >>> > - name: meter_source >>> > interval: 600 >>> > meters: >>> > - "*" >>> > sinks: >>> > - meter_sink >>> > - name: cpu_source >>> > interval: 600 >>> > meters: >>> > - "cpu" >>> > sinks: >>> > - cpu_sink >>> > - name: disk_source >>> > interval: 600 >>> > meters: >>> > - "disk.read.bytes" >>> > - "disk.read.requests" >>> > - "disk.write.bytes" >>> > - "disk.write.requests" >>> > sinks: >>> > - disk_sink >>> > - name: network_source >>> > interval: 600 >>> > meters: >>> > - "network.incoming.bytes" >>> > - "network.incoming.packets" >>> > - "network.outgoing.bytes" >>> > - "network.outgoing.packets" >>> > sinks: >>> > - network_sink >>> > sinks: >>> > - name: meter_sink >>> > transformers: >>> > publishers: >>> > - notifier:// >>> > - name: cpu_sink >>> > transformers: >>> > - name: "rate_of_change" >>> > parameters: >>> > target: >>> > name: "cpu_util" >>> > unit: "%" >>> > type: "gauge" >>> > scale: "100.0 / (10**9 * >>> > (resource_metadata.cpu_number or 1))" >>> > publishers: >>> > - notifier:// >>> > - name: disk_sink >>> > transformers: >>> > - name: "rate_of_change" >>> > parameters: >>> > source: >>> > map_from: >>> > name: "disk\\.(read|write)\\.(bytes|requests)" >>> > unit: "(B|request)" >>> > target: >>> > map_to: >>> > name: "disk.\\1.\\2.rate" >>> > unit: "\\1/s" >>> > type: "gauge" >>> > publishers: >>> > - notifier:// >>> > - name: network_sink >>> > transformers: >>> > - name: "rate_of_change" >>> > parameters: >>> > source: >>> > map_from: >>> > name: >>> "network\\.(incoming|outgoing)\\.(bytes|packets)" >>> > unit: "(B|packet)" >>> > target: >>> > map_to: >>> > name: "network.\\1.\\2.rate" >>> > unit: "\\1/s" >>> > type: "gauge" >>> > publishers: >>> > - notifier:// >>> > >>> > Can anyone tell me whether it's true? >>> > >>> > @hangliu, would you please show me your pipeline.yaml, if possible. >>> Thanks! >>> > >>> > -- >>> > Regards, >>> > Frank >>> > >>> > 2014-11-06 22:37 GMT+08:00 Neal, Phil <phil.n...@hp.com>: >>> > Frank, I'd echo Hang Liu's suggestion, but also encourage you to >>> > take this question to the general OpenStack mailing >>> > list (see https://wiki.openstack.org/wiki/Mailing_Lists). >>> > >>> > - Phil >>> > >>> > From: Hang H Liu [mailto:hang...@cn.ibm.com <hang...@cn.ibm.com>] >>> > Sent: Wednesday, November 05, 2014 7:36 AM >>> > To: OpenStack Development Mailing List (not for usage questions) >>> > Subject: Re: [openstack-dev] [ceilometer] unable to collect >>> > compute.node.cpu.* data >>> > >>> > Same steps I can get below results. >>> > You may need debug into get_meters() in ceilometer/storage/ >>> > impl_sqlalchemy.py to see if some filters are taking effect. >>> > >>> > >>> > localadmin@ostest2:~/devstack$ ceilometer meter-list >>> > +---------------------------------+------------+--------- >>> > +-------------------------------------- >>> > +----------------------------------+----------------------------------+ >>> > | Name | Type | Unit | Resource >>> > ID | User ID | >>> > Project ID | >>> > +---------------------------------+------------+--------- >>> > +-------------------------------------- >>> > +----------------------------------+----------------------------------+ >>> > | compute.node.cpu.frequency | gauge | MHz | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.idle.percent | gauge | % | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.idle.time | cumulative | ns | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.iowait.percent | gauge | % | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.iowait.time | cumulative | ns | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.kernel.percent | gauge | % | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.kernel.time | cumulative | ns | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.percent | gauge | % | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.user.percent | gauge | % | >>> > ostest2_ostest2 | None >>> > | None | >>> > | compute.node.cpu.user.time | cumulative | ns | >>> > ostest2_ostest2 | None >>> > >>> > >>> > >>> > "Lu, Lianhao" <lianhao...@intel.com> 写于 2014/11/05 15:23:14: >>> > >>> > > From: "Lu, Lianhao" <lianhao...@intel.com> >>> > > To: "OpenStack Development Mailing List (not for usage questions)" >>> > > <openstack-dev@lists.openstack.org> >>> > > Date: 2014/11/05 15:31 >>> > > Subject: Re: [openstack-dev] [ceilometer] unable to collect >>> > > compute.node.cpu.* data >>> > > >>> > > Hi Frank, >>> > > >>> > > Could you try ‘celometer sample-list’ to see if the compute.node.cpu >>> > > samples are there? >>> > > >>> > > -Lianhao >>> > > >>> > > From: Du Jun [mailto:dj199...@gmail.com <dj199...@gmail.com>] >>> > > Sent: Wednesday, November 05, 2014 3:44 AM >>> > > To: openstack-dev@lists.openstack.org >>> > > Subject: [openstack-dev] [ceilometer] unable to collect >>> > > compute.node.cpu.* data >>> > > >>> > > Hi all, >>> > > >>> > > I attempt to collect compute.node.cpu as the following link mentions: >>> > > >>> > > http://docs.openstack.org/developer/ceilometer/ >>> > measurements.html#compute-nova >>> > > >>> > > I set: >>> > > >>> > > compute_monitors = ComputeDriverCPUMonitor >>> > > >>> > > in /etc/nova/nova.conf and restart nova-compute, nova-scheduler, >>> > > ceilometer-agent-notification, ceilometer-api, ceilometer-collector. >>> > > >>> > > From ceilometer-agent-notification's log, I can see agent transform >>> > > and publish data samples compute.node.cpu.* >>> > > >>> > > What's more, from ceilometer database, I can see all the meters >>> > > compute.node.cpu.* >>> > > >>> > > mysql> select * from meter; >>> > > +----+---------------------------------+------------+-----------+ >>> > > | id | name | type | unit | >>> > > +----+---------------------------------+------------+-----------+ >>> > > | 39 | compute.node.cpu.frequency | gauge | MHz | >>> > > | 41 | compute.node.cpu.idle.percent | gauge | % | >>> > > | 38 | compute.node.cpu.idle.time | cumulative | ns | >>> > > | 45 | compute.node.cpu.iowait.percent | gauge | % | >>> > > | 42 | compute.node.cpu.iowait.time | cumulative | ns | >>> > > | 36 | compute.node.cpu.kernel.percent | gauge | % | >>> > > | 44 | compute.node.cpu.kernel.time | cumulative | ns | >>> > > | 37 | compute.node.cpu.percent | gauge | % | >>> > > | 43 | compute.node.cpu.user.percent | gauge | % | >>> > > | 40 | compute.node.cpu.user.time | cumulative | ns | >>> > > >>> > > >>> > > However, when I type >>> > > >>> > > ceilometer meter-list >>> > > >>> > > It shows nothing about compute.node.cpu.*, so I wonder what's wrong >>> > > with my steps. >>> > > >>> > > -- >>> > > Regards, >>> > > Frank_______________________________________________ >>> > > OpenStack-dev mailing list >>> > > OpenStack-dev@lists.openstack.org >>> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> > _______________________________________________ >>> > OpenStack-dev mailing list >>> > OpenStack-dev@lists.openstack.org >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> > _______________________________________________ >>> > OpenStack-dev mailing list >>> > OpenStack-dev@lists.openstack.org >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- blog: zqfan.github.com git: github.com/zqfan
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
