[Openstack] Error in Installation of ceilometer in Ubuntu 12.04 LTS

2013-06-08 Thread johnu
Hi Everyone,
 I have facing strange issue in installation of
openstack with ceilometer. I am using devstack automated script to install
ceilometer as told in
http://ceilometer.readthedocs.org/en/latest/install.html.

I added the following lines in localrc


# Configure the notifier to talk to the message queue
# and turn on usage audit events
EXTRA_OPTS=(notification_driver=nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier)

# Enable the ceilometer services
enable_service 
ceilometer-acompute,ceilometer-acentral,ceilometer-collector,ceilometer-api


But, when i am running ceilometer-collector or ceilometer-agent, I am
getting error saying
AttributeError: 'module' object has no attribute 'packs'

Please help me in installing ceilometer in openstack.I have even tried by
installing openstack first and manually installed ceilometer as told in the
above link. But I was getting different error
ArgsAlreadyParsedError(cannot register CLI option


I can manually do any of the steps or I am ready to reinstall completely.
Can someone help me to install ceilometer in openstack?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] experimenting with ceilometer via devstack

2012-08-17 Thread Doug Hellmann
John Tran 's patch just landed in devstack to enable ceilometer support.
Thanks, John!

To turn on ceilometer, add this line to your localrc before running
devstack:

enable_service ceilometer-acompute,ceilometer-acentral,
ceilometer-collector

The default configuration results in a MongoDB database called ceilometer
containing all of the metering data. You can access it directly using the
mongo shell via the command mongo ceilometer.

The ceilometer API server does not have a wrapper script, but you can start
the dev server by running

python -m ceilometer.api

The server will listen for requests on port 9000 by default.

Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] swift proxys and dedecated ceilometer

2013-07-24 Thread Julien Danjou
On Wed, Jul 24 2013, Axel Christiansen wrote:

 To be sure, the ceilometer-agent-central and ceilometer-collector do
 go on the proxys. And just the ceilometer-api ist for the dedecated
 ceilometer-host?

No, they all can go to your dedicated host. Ceilometer agent central
access Swift via its API (so via swift-proxies).

-- 
Julien Danjou
// Free Software hacker / freelance consultant
// http://julien.danjou.info


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] swift proxys and dedecated ceilometer

2013-07-24 Thread Axel Christiansen
Hi Julien,


thx a lot for the real quick help.

Yes, only swift. These meters:
storage.objects
storage.objects.size
storage.objects.containers
storage.objects.incoming.bytes
storage.objects.outgoing.bytes



To be sure, the ceilometer-agent-central and ceilometer-collector do
go on the proxys. And just the ceilometer-api ist for the dedecated
ceilometer-host?


Axel


Am 24.07.13 15:33, schrieb Julien Danjou:
 On Wed, Jul 24 2013, Axel Christiansen wrote:
 
 Hi Axel,
 
 If you want to only meter Swift, you just need:
 
 ceilometer-agent-central ceilometer-collector
 
 And to retrieve your data:
 ceilometer-api
 


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Metering] News from 24/05 to 30/05

2012-05-30 Thread Julien Danjou
Hi,

Here's a few things done in the last week concerning ceilometer:

- Various bugs have been opened to have more visibility on the project
  progress
  https://bugs.launchpad.net/ceilometer
- Test suite have been fixed wrt db usage
  
https://github.com/stackforge/ceilometer/commit/dbccf0ce6974fc3665f0ffd63a9b08725339d6cf
- A floating IP pollster have been added
  
https://github.com/stackforge/ceilometer/commit/d4635bede100934d1535b334dfc5a694bffe7d97
- We now publish and receive metering message
  
https://github.com/stackforge/ceilometer/commit/b76f67d11f5bed61818b9dcaf77b20bfb087547b
- Ceilometer specific configuration uses openstack.common.cfg
  
https://github.com/stackforge/ceilometer/commit/a49e59b1151ce87c8f4ed6e12368e01dbbb6243a
- Ceilometer now uses tox and has the standard Jenkins jobs installed
  
https://github.com/stackforge/ceilometer/commit/5e0a32f47505d342676099518ec3fad558c61511
- Add listeners for other instance-related events
  
https://github.com/stackforge/ceilometer/commit/d615fb872ddceaf1ddef7e3997bcf2523cab283e

-- 
Julien Danjou
// eNovance  http://enovance.com
// ✉ julien.dan...@enovance.com  ☎ +33 1 49 70 99 81

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] Release plan for 0.1

2012-09-12 Thread Graham Binns
Hi all,

Based on the discussion in the last Ceilometer meeting[1], here's my
proposal for dates for the Ceilometer 0.1 release calendar:

 - Feature freeze for 0.1 QA: 2012-09-28
 - Release: 2012-10-12

Arguments for / against welcome.

 [1] 
http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.log.html

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] ceilometer-agent-central starting fail

2013-04-10 Thread Liu Wenmao
I solve this problem by two steps:

1 modify /etc/init/ceilometer-agent-central.conf
exec start-stop-daemon --start --chuid ceilometer --exec
/usr/local/bin/ceilometer-agent-central --
--config-file=/etc/ceilometer/ceilometer.conf
2 add some lines to /etc/ceilometer/ceilometer.conf:
os-username=ceilometer
os-password=nsfocus
os-tenant-name=service
os-auth-url=http://controller:5000/v2.0



On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao marvel...@gmail.com wrote:

 Hi all:

 I have just install ceilometer grizzly github version, but fail to
 start ceilometer-agent-central service. I think it is due to that I didn't
 set up the keystone user/password like other projects. but I follow the
 instructions(
 http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
 but it does not include the ceilometer configuration.

 # service ceilometer-agent-central start
 ceilometer-agent-central start/running, process 5679

 # cat /etc/init/ceilometer-agent-central.conf
 description ceilometer-agent-compute
 author Chuck Short zul...@ubuntu.com

 start on runlevel [2345]
 stop on runlelvel [!2345]

 chdir /var/run

 pre-start script
 mkdir -p /var/run/ceilometer
 chown ceilometer:ceilometer /var/run/ceilometer

 mkdir -p /var/lock/ceilometer
 chown ceilometer:ceilometer /var/lock/ceilometer
 end script

 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central


 /var/log/ceilometer/ceilometer-agent-central.log
 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall] in
 looping call
 Traceback (most recent call last):
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py,
 line 67, in _inner
 self.f(*self.args, **self.kw)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py,
 line 76, in interval_task
 auth_url=cfg.CONF.os_auth_url)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 134, in __init__
 self.authenticate()
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 205, in authenticate
 token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 174, in get_raw_token_from_identity_servicetoken=token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 202, in _base_authN
 resp, body = self.request(url, 'POST', body=params, headers=headers)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 366, in request
 raise exceptions.from_response(resp, resp.text)
 Unauthorized: Unable to communicate with identity service: {error:
 {message: Invalid user / password, code: 401, title: Not
 Authorized}}. (HTTP 401)
 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.threadgroup]
 Unable to communicate with identity service: {error: {message: Invalid
 user / password, code: 401, title: Not Authorized}}. (HTTP 401)

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Error in Installation of ceilometer in Ubuntu 12.04 LTS

2013-06-08 Thread Zhou Z Xing
Hi Johnu

It seems that your kombu is not at right version that ceilometer 
needs. please update your python kombu package and try again

Thanks  Best Wishes,

xingzhou




johnu johnugeorge...@gmail.com 
Sent by: Openstack 
openstack-bounces+xingzhou=cn.ibm@lists.launchpad.net
2013/06/09 01:26

To
openstack@lists.launchpad.net, 
cc

Subject
[Openstack] Error in Installation of ceilometer in Ubuntu 12.04 LTS






Hi Everyone, 
 I have facing strange issue in installation of 
openstack with ceilometer. I am using devstack automated script to install 
ceilometer as told in  
http://ceilometer.readthedocs.org/en/latest/install.html.

I added the following lines in localrc


# Configure the notifier to talk to the message queue
# and turn on usage audit events
EXTRA_OPTS=(notification_driver=nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier)

# Enable the ceilometer services
enable_service 
ceilometer-acompute,ceilometer-acentral,ceilometer-collector,ceilometer-api

But, when i am running ceilometer-collector or ceilometer-agent, I am 
getting error saying 
AttributeError: 'module' object has no attribute 'packs'

Please help me in installing ceilometer in openstack.I have even tried by 
installing openstack first and manually installed ceilometer as told in 
the above link. But I was getting different error
ArgsAlreadyParsedError(cannot register CLI option


I can manually do any of the steps or I am ready to reinstall completely. 
Can someone help me to install ceilometer in openstack?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Error in Installation of ceilometer in Ubuntu 12.04 LTS

2013-06-09 Thread johnu
Thanks for your help. Zhou.
I did easy_install --upgrade kombu and that solved my issue.


On Sat, Jun 8, 2013 at 6:44 PM, Zhou Z Xing xingz...@cn.ibm.com wrote:

 Hi Johnu

 It seems that your kombu is not at right version that ceilometer
 needs. please update your python kombu package and try again

 Thanks  Best Wishes,

 xingzhou



  *johnu johnugeorge...@gmail.com*
 Sent by: Openstack openstack-bounces+xingzhou=
 cn.ibm@lists.launchpad.net

 2013/06/09 01:26
   To
 openstack@lists.launchpad.net,
 cc
   Subject
 [Openstack] Error in Installation of ceilometer in Ubuntu 12.04 LTS




 Hi Everyone,
  I have facing strange issue in installation of
 openstack with ceilometer. I am using devstack automated script to install
 ceilometer as told in  *
 http://ceilometer.readthedocs.org/en/latest/install.html*http://ceilometer.readthedocs.org/en/latest/install.html
 .

 I added the following lines in localrc


 # Configure the notifier to talk to the message queue
 # and turn on usage audit events

 EXTRA_OPTS=(notification_driver=nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier)

 # Enable the ceilometer services
 enable_service
 ceilometer-acompute,ceilometer-acentral,ceilometer-collector,ceilometer-api

 But, when i am running ceilometer-collector or ceilometer-agent, I am
 getting error saying
 AttributeError: 'module' object has no attribute 'packs'

 Please help me in installing ceilometer in openstack.I have even tried by
 installing openstack first and manually installed ceilometer as told in the
 above link. But I was getting different error
 ArgsAlreadyParsedError(cannot register CLI option


 I can manually do any of the steps or I am ready to reinstall completely.
 Can someone help me to install ceilometer in openstack?
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Ceilometer returns empty list

2013-06-19 Thread Jobin Raju George
Hey all!

I have installed ceilometer using the manual installation guide given
at Ceilometer
installation guide
 http://docs.openstack.org/developer/ceilometer/install/manual.html
I have not installed swift since I just need the compute data such as CPU
utilization, CPU utilization time, Memory utilization etc.

The components ceilometer-api, ceilometer-agent-compute,
ceilometer-agent-central and ceilometer-collector are running fine and
logging to respective files.


However, when I query ceilometer using curl as:


curl -X GET -H 'X-Auth-Token:my_token_here' 
http://localhost:8777/v2/meters/instance?q.field=metadata.event_typeq.value=compute.instance.exists



I get an empty list: []


Where am I going wrong? Please ask for details, if required. Thanks a lot!

-- 

Thanks and regards,

Jobin Raju George

Third Year, Information Technology

College of Engineering Pune

Alternate e-mail: georgejr10...@coep.ac.in
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] swift proxys and dedecated ceilometer

2013-07-24 Thread Axel Christiansen
Dear List,


i am trying to figure out what ceilometer components nedds to bo
installed an what nodes.

I have 2 swift-proxy-hosts and 1 ceiloemeter-host



These are the packages debian7 respectively the grizzly repo offers:

ceilometer-agent-central - OpenStack efficient metering counters system
- central agent
ceilometer-agent-compute - OpenStack efficient metering counters system
- compute agent
ceilometer-api - OpenStack efficient metering counters system (API service)
ceilometer-collector - OpenStack efficient metering counters system -
collector service
ceilometer-common - OpenStack efficient metering counters system -
common files
python-ceilometer - OpenStack efficient metering counters system -
Python libraries
python-ceilometerclient - Client library for Openstack Ceilometer API server



Thank you, Axel


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer] Grizzly RC1 released

2013-03-26 Thread Julien Danjou
Hi,

We're pleased to announce that the RC1 version for the Grizzly release
of Ceilometer is available!

   https://launchpad.net/ceilometer/grizzly/grizzly-rc1

Unless release-critical issues are found that warrant a release
candidate respin, this version will be formally released as the
Ceilometer 2013.1 version on April 4. You are therefore strongly
encouraged to test and validate this tarball.

If you find an issue that could be considered release-critical, please
file it at:

 https://bugs.launchpad.net/ceilometer/+filebug

Note that the master branch for Ceilometer is now open for Havana
development, and feature freeze restriction no longer apply.

-- 
Julien Danjou
-- Free Software hacker - freelance consultant
-- http://julien.danjou.info


pgpzk9vLkH8Up.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error 401 Unauthorized

2013-05-27 Thread Bruno Oliveira
Hello stackers,

I'm having a really hard time setting up ceilometer-api so I thought
if I could ask you guys for some enlightment.

I can clearly see data being pulled in the screens that are running
/ceilometer-collector, ./ceilometer-agent-compute ,./ceilometer-agent-central

Even the screen running ceilometer-api-server starts with no problem.

But I cannot reach the api at all via curl. Neither by using its
actual port (8777)
nor using the port set in the virtual host of apache. All I'm getting
is auth error

$ curl http://127.0.0.1:8777  OR  $ curl http://127.0.0.1:9090
=
html
 head
  title401 Unauthorized/title
 /head
 body
  h1401 Unauthorized/h1
  This server could not verify that you are authorized to access the
document you requested. Either you supplied the wrong credentials
(e.g., bad password), or your browser does not understand how to
supply the credentials required.br /br /
Authentication required
=


On top of that, the only thing I had to do in a non-standard basis, was to
setup ceilometer virtual host to answer request on port 9090 of apache
instead of the default 80 (since horizon is bind to it).


Here's a copy of my running ceilometer.conf
=
/etc/ceilometer/ceilometer.conf
=
[DEFAULT]
os_username=ceilometer
os_password=MYSECRET
os_tenant_name=admin
os_auth_url=http://localhost:5000/v2.0
signing_dirname = /tmp/keystone-signing-ceilometer
metering_api_port=8777
auth_strategy=keystone
nova_control_exchange=nova
hypervisor_inspector=libvirt
libvirt_type=kvm
glance_control_exchange=glance
quantum_control_exchange=quantum
debug=true
verbose=true
(...)
*logging writing parameters here*
(...)
log_dir=/var/log/ceilometer
rpc_backend=ceilometer.openstack.common.rpc.impl_kombu
rabbit_host=localhost
rabbit_port=5672
rabbit_userid=guest
rabbit_password=ficrowstran02
rabbit_retry_backoff=2
rabbit_max_retries=0
database_connection=mongodb://localhost:27017/ceilometer
sql_connection_debug=0
cinder_control_exchange=cinder
enable_v1_api=true

[rpc_notifier2]

[matchmaker_redis]

[publisher_meter]
metering_secret=METERING_SECRET

[keystone_authtoken]
auth_host = localhost
auth_port = 5000
admin_user = ceilometer
admin_password = MYSECRET
admin_tenant_name = admin
auth_uri = http://localhost:5000/v2.0/
=


The ceilometer user pointed at admin_user under the
[keystone_authtoken] section, as well as in os_username under the
[DEFAULT] section,
was created in keystone and it'sbind to the admin tenant.


$ keystone tenant-get admin
+-+--+
|   Property  |  Value   |
+-+--+
| description |  |
|   enabled   |   True   |
|  id | 670f5dd4070d44b6a8308277a236d1af |
| name|  admin   |
+-+--+

$ keystone user-get ceilometer
+--+--+
| Property |  Value   |
+--+--+
|  email   |  ceilome...@example.com  |
| enabled  |   True   |
|id| a98ec068f5f349439acef431e826d7ff |
|   name   |ceilometer|
| tenantId | 670f5dd4070d44b6a8308277a236d1af |
+--+--+


Finally, here's the ceilometer site running on apache. the user
and group 'stackadmin' are valid users indeed in the machine

$ id stackadmin

uid=1000(stackadmin) gid=1000(stackadmin)
groups=1000(stackadmin),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),111(libvirtd),113(lpadmin),114(sambashare


=
/etc/apache2/sites-available/ceilometer
=
VirtualHost *:9090
WSGIDaemonProcess ceilometer user=stackadmin group=stackadmin threads=5
WSGIScriptAlias / /opt/stack/ceilometer/ceilometer/api/app.wsgi
SetEnv APACHE_RUN_USER stackadmin
SetEnv APACHE_RUN_GROUP stackadmin
WSGIProcessGroup ceilometer
ErrorLog /var/log/apache2/ceilometer_error.log
LogLevel warn
CustomLog /var/log/apache2/ceilometer_access.log combined
/VirtualHost
=


Despite of everything, I keep getting that 401 Unauthorized
auth error.

Do you guys have any suggestions of what I can try to fix it ?

Thank you all.

--

Bruno de Oliveira
Developer, System Analyst

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error 401 Unauthorized

2013-05-28 Thread Ildiko Vancsa
Hi All,

I'm new to OpenStack and Ceilometer as well, so I have a few questions. :)

Does Ceilometer supports a Web UI or it is available via command line and
curl only? I installed the environment with DevStack as I wanted to check
how it works and looks like and it sets ceilometer in the apache2 serveice
as an enabled site, but I could not find any information about how to set
it up correctly.

Thanks and Best Regards,
Ildiko
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] how to enable cpu meter?

2013-05-28 Thread alexander barakin
On Tue, May 28, 2013 at 4:13 PM, Julien Danjou jul...@danjou.info wrote:

 On Tue, May 28 2013, alexander barakin wrote:

  i use fresh devstack without local modifications on ubuntu 12.04
  i have run the example image cirros-0.3.1-x86_64-uec and see the
 following
  meters in output of ceilometer meter-list:

 You need to run `ceilometer-agent-compute'.


this process works.
output in devstack screen ceilometer-acompute tab:
 $ cd /opt/stack/last/ceilometer  sg libvirtd
/opt/stack/last/ceilometer/bin/ceilometer-agent-compute --config-file
/etc/ceilometer/ceilometer.conf || touch
/opt/stack/last/status/stack/ceilometer-acompute.failure
2013-05-28 13:34:48 INFO [ceilometer.pipeline] Pipeline config:
[{'publishers': ['meter'], 'interval': 600, 'transformers': None, 'name':
'meter_pipeline', 'counters': ['*']}]
2013-05-28 13:34:48 INFO [ceilometer.openstack.common.rpc.common]
Connected to AMQP server on localhost:5672
2013-05-28 13:34:48 INFO [requests.packages.urllib3.connectionpool]
Starting new HTTP connection (1): 10.4.128.1
2013-05-28 13:34:48 INFO [requests.packages.urllib3.connectionpool]
Starting new HTTP connection (1): 10.4.128.1
2013-05-28 13:34:50AUDIT [ceilometer.pipeline] Flush pipeline
meter_pipeline
2013-05-28 13:44:48AUDIT [ceilometer.pipeline] Flush pipeline
meter_pipeline
...

p.s. i forgot to mention about this line in devstack's localrc:
enable_service
ceilometer-acompute,ceilometer-acentral,ceilometer-collector,ceilometer-api
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer] Bug squash day on 4th January 2013

2012-12-24 Thread Julien Danjou
Hi fellow OpenStackers,

The Ceilometer team is pleased to announce that it organizes a bug
squashing day on the Friday 4th January 2013.

You can find more information about the Ceilometer project on its wiki
page¹. The organization details for this day are available on its own
page² also.
If you're already curious about how to contribute to Ceilometer, you can
read the associated page³.

This event will mainly happen on IRC (#openstack-metering on Freenode),
and all participants are encoured to join. People will be there to
welcome and help new comers to contribute to Ceilometer!


¹  http://wiki.openstack.org/Ceilometer

²  http://wiki.openstack.org/Ceilometer/BugSquashingDay/20130104

³  http://wiki.openstack.org/Ceilometer/Contributing

-- 
Julien Danjou
/* Free Software hacker  freelance
   http://julien.danjou.info */


pgpMPQ5br08qV.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] swift proxys and dedecated ceilometer

2013-07-24 Thread Julien Danjou
On Wed, Jul 24 2013, Axel Christiansen wrote:

Hi Axel,

If you want to only meter Swift, you just need:

 ceilometer-agent-central
 ceilometer-collector

And to retrieve your data:
 ceilometer-api

-- 
Julien Danjou
/* Free Software hacker * freelance consultant
   http://julien.danjou.info */


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] ceilometer-agent-central starting fail

2013-04-11 Thread Liu Wenmao
Thanks, the ceilometer seems to lack some default options in configuration
files and the official guidance. (
http://docs.openstack.org/developer/ceilometer/configuration.html)

So maybe it is not ready for users yet?


On Wed, Apr 10, 2013 at 8:28 PM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:




 On Wed, Apr 10, 2013 at 6:10 AM, Liu Wenmao marvel...@gmail.com wrote:

 Actually this is not over.

 The main reason of service failure is that central/manager.py
 and service.py use different vairables:

 central/manager.py
  70 def interval_task(self, task):
  71 self.keystone = ksclient.Client(
  72 username=cfg.CONF.*os_username*,
  73 password=cfg.CONF.os_password,
  74 tenant_id=cfg.CONF.os_tenant_id,
  75 tenant_name=cfg.CONF.os_tenant_name,
  76 auth_url=cfg.CONF.os_auth_url)

 44 CLI_OPTIONS = [
  45 cfg.StrOpt('*os-username*',
  46default=os.environ.get('OS_USERNAME', 'ceilometer'),
  47help='Username to use for openstack service access'),
  48 cfg.StrOpt('os-password',
  49default=os.environ.get('OS_PASSWORD', 'admin'),
  50help='Password to use for openstack service access'),
  51 cfg.StrOpt('os-tenant-id',
  52default=os.environ.get('OS_TENANT_ID', ''),
  53help='Tenant ID to use for openstack service access'),
  54 cfg.StrOpt('os-tenant-name',
  55default=os.environ.get('OS_TENANT_NAME', 'admin'),
  56help='Tenant name to use for openstack service
 access'),
  57 cfg.StrOpt('os_auth_url',
  58default=os.environ.get('OS_AUTH_URL',
  59   'http://localhost:5000/v2.0'),

 So after I change all - to _ and modify all options in
 /etc/ceilometer/ceilometer.conf, the service starts OK.


 The thing that fixed it was changing - to _ in your configuration
 file. The options library allows option names to have - in them so they
 look nice as command line switches, but the option name uses the _.

 Doug





 On Wed, Apr 10, 2013 at 2:02 PM, Liu Wenmao marvel...@gmail.com wrote:

 I solve this problem by two steps:

 1 modify /etc/init/ceilometer-agent-central.conf
 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central --
 --config-file=/etc/ceilometer/ceilometer.conf
 2 add some lines to /etc/ceilometer/ceilometer.conf:
 os-username=ceilometer
 os-password=nsfocus
 os-tenant-name=service
 os-auth-url=http://controller:5000/v2.0



 On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao marvel...@gmail.com wrote:

 Hi all:

 I have just install ceilometer grizzly github version, but fail to
 start ceilometer-agent-central service. I think it is due to that I didn't
 set up the keystone user/password like other projects. but I follow the
 instructions(
 http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
 but it does not include the ceilometer configuration.

 # service ceilometer-agent-central start
 ceilometer-agent-central start/running, process 5679

 # cat /etc/init/ceilometer-agent-central.conf
 description ceilometer-agent-compute
 author Chuck Short zul...@ubuntu.com

 start on runlevel [2345]
 stop on runlelvel [!2345]

 chdir /var/run

 pre-start script
 mkdir -p /var/run/ceilometer
 chown ceilometer:ceilometer /var/run/ceilometer

 mkdir -p /var/lock/ceilometer
 chown ceilometer:ceilometer /var/lock/ceilometer
 end script

 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central


 /var/log/ceilometer/ceilometer-agent-central.log
 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall]
 in looping call
 Traceback (most recent call last):
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py,
 line 67, in _inner
 self.f(*self.args, **self.kw)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py,
 line 76, in interval_task
 auth_url=cfg.CONF.os_auth_url)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 134, in __init__
 self.authenticate()
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 205, in authenticate
 token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 174, in get_raw_token_from_identity_servicetoken=token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 202, in _base_authN
 resp, body = self.request(url, 'POST', body=params, headers=headers)
   File
 /usr/local/lib/python2.7/dist-packages

Re: [Openstack] [metering] ceilometer dev docs on readthedocs.org

2012-07-03 Thread Loic Dachary
On 07/03/2012 07:46 PM, Doug Hellmann wrote:
 I've set up the ceilometer development documentation build on RTD at 
 http://ceilometer.readthedocs.org/en/latest/index.html

Hi,

I've updated https://launchpad.net/ceilometer to list this link.

Cheers


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-15 Thread Shengjie_Min
Hi guys,

The blueprint is registered : 
https://blueprints.launchpad.net/ceilometer/+spec/hbase-storage-backend, Any 
idea what's the next step ? :)

Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer] Ganglia Ceilometer integration

2013-01-08 Thread Shengjie_Min
Hi guys,

Just out of curiosity, Have we ever had any previous threads discussing about 
possibility of integrating Ceilometer with ganglia as a monitoring approach? 
Didn't manage to find any from the mailing list archive.

Thanks,
Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] How to purge old meter data of Ceilometer

2013-04-04 Thread Harri Pyy
With the default 1 minute interval, Ceilometer collects quite large amounts of 
meter data.

Does Ceilometer provide a TTL configuration option for the meter data, or some 
other functionality or API for purging old meter data?
 
Thanks for any help,
Harri


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] support for older versions of ceilometer

2013-05-30 Thread Tim Bell
 

Doug,

 

Can you advise on what the plan/policy will be for Havana ?

 

-  Will I be able to run Havana core components such as Nova with 
Grizzly ceilometer ?

-  Will I be able to run Havana ceilometer with Grizzly core components 
(with reduced functionality compared to the Havana
core components) ?

 

Tim

 

From: Openstack [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] 
On Behalf Of Doug Hellmann
Sent: 30 May 2013 18:59
To: openstack@lists.launchpad.net
Subject: [Openstack] [ceilometer] support for older versions of ceilometer

 

The ceilometer team has had a few requests for help with older versions of 
ceilometer or running the grizzly version of ceilometer
with older versions of other OpenStack components lately. We appreciate the 
level of interest in the project but, as much as we
would like to, unfortunately we are not always able to help everyone with these 
mixed configurations. During the early phases of
our development we tried to maintain compatibility with folsom, even well into 
the grizzly development cycle. We are no longer doing
that, however, and so to make clear what support we can offer, the ceilometer 
team has put together the statement below. It has been
added to our documentation, and we are posting here to make sure everyone has a 
chance to see it.

 

Regards,

Doug

 

 

The ceilometer team has limited capacity to provide support for older versions 
of the project. Because the project graduated from
incubation around the time of the grizzly release, that is the first version 
for which we will provide regular ongoing support
following the standard deprecation cycle for OpenStack [1]. The grizzly version 
of ceilometer  cannot be installed on the same
server with earlier versions of OpenStack because of conflicting package 
requirements, but is API compatible with the folsom release
if installed separately.

 

[1] https://wiki.openstack.org/wiki/StableBranch

 



smime.p7s
Description: S/MIME cryptographic signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Ceilometer- All meters are not getting updated

2013-06-13 Thread johnu
Hi Everyone,
When I am running ceilometer, only some of the meters
are getting updated.(When I see ceilometer meter-list , I could see only
cpu_util, image, instance). What can be the reason that the other meters
are not getting updated.?.

Thanks,
Johnu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] ceilometer-agent-central starting fail

2013-04-09 Thread Liu Wenmao
Hi all:

I have just install ceilometer grizzly github version, but fail to
start ceilometer-agent-central service. I think it is due to that I didn't
set up the keystone user/password like other projects. but I follow the
instructions(
http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
but it does not include the ceilometer configuration.

# service ceilometer-agent-central start
ceilometer-agent-central start/running, process 5679

# cat /etc/init/ceilometer-agent-central.conf
description ceilometer-agent-compute
author Chuck Short zul...@ubuntu.com

start on runlevel [2345]
stop on runlelvel [!2345]

chdir /var/run

pre-start script
mkdir -p /var/run/ceilometer
chown ceilometer:ceilometer /var/run/ceilometer

mkdir -p /var/lock/ceilometer
chown ceilometer:ceilometer /var/lock/ceilometer
end script

exec start-stop-daemon --start --chuid ceilometer --exec
/usr/local/bin/ceilometer-agent-central


/var/log/ceilometer/ceilometer-agent-central.log
2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall] in
looping call
Traceback (most recent call last):
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py,
line 67, in _inner
self.f(*self.args, **self.kw)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py,
line 76, in interval_task
auth_url=cfg.CONF.os_auth_url)
  File
/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
line 134, in __init__
self.authenticate()
  File
/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
line 205, in authenticate
token)
  File
/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
line 174, in get_raw_token_from_identity_servicetoken=token)
  File
/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
line 202, in _base_authN
resp, body = self.request(url, 'POST', body=params, headers=headers)
  File
/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
line 366, in request
raise exceptions.from_response(resp, resp.text)
Unauthorized: Unable to communicate with identity service: {error:
{message: Invalid user / password, code: 401, title: Not
Authorized}}. (HTTP 401)
2013-04-10 13:01:39ERROR [ceilometer.openstack.common.threadgroup]
Unable to communicate with identity service: {error: {message: Invalid
user / password, code: 401, title: Not Authorized}}. (HTTP 401)
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error 401 Unauthorized

2013-05-28 Thread Fei Long Wang
Hi Bruno,

Please follow this link:
http://docs.openstack.org/developer/ceilometer/configuration.html#keystone-middleware-authentication

Generally, you just need add some entries in ceilometer.conf like this:
[keystone_authtoken]
signing_dir = /var/cache/ceilometer
admin_tenant_name = service
admin_password = passw0rd
admin_user = ceilometer
auth_protocol = http

Thanks  Best regards,
Fei Long Wang (王飞龙)
--
Scrum Master, Cloud Solutions and OpenStack Development
Tel: 8610-82450513 | T/L: 905-0513
Email: flw...@cn.ibm.com
China Systems  Technology Laboratory in Beijing
--




From:   Bruno Oliveira brunnop.olive...@gmail.com
To: OpenStack openstack@lists.launchpad.net,
Date:   05/27/2013 10:14 PM
Subject:[Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error
401 Unauthorized
Sent by:Openstack openstack-bounces
+flwang=cn.ibm@lists.launchpad.net



Hello stackers,

I'm having a really hard time setting up ceilometer-api so I thought
if I could ask you guys for some enlightment.

I can clearly see data being pulled in the screens that are running
/ceilometer-collector, ./ceilometer-agent-compute ,./ceilometer-agent-central


Even the screen running ceilometer-api-server starts with no problem.

But I cannot reach the api at all via curl. Neither by using its
actual port (8777)
nor using the port set in the virtual host of apache. All I'm getting
is auth error

$ curl http://127.0.0.1:8777  OR  $ curl http://127.0.0.1:9090
=
html
 head
  title401 Unauthorized/title
 /head
 body
  h1401 Unauthorized/h1
  This server could not verify that you are authorized to access the
document you requested. Either you supplied the wrong credentials
(e.g., bad password), or your browser does not understand how to
supply the credentials required.br /br /
Authentication required
=


On top of that, the only thing I had to do in a non-standard basis, was to
setup ceilometer virtual host to answer request on port 9090 of apache
instead of the default 80 (since horizon is bind to it).


Here's a copy of my running ceilometer.conf
=
/etc/ceilometer/ceilometer.conf
=
[DEFAULT]
os_username=ceilometer
os_password=MYSECRET
os_tenant_name=admin
os_auth_url=http://localhost:5000/v2.0
signing_dirname = /tmp/keystone-signing-ceilometer
metering_api_port=8777
auth_strategy=keystone
nova_control_exchange=nova
hypervisor_inspector=libvirt
libvirt_type=kvm
glance_control_exchange=glance
quantum_control_exchange=quantum
debug=true
verbose=true
(...)
*logging writing parameters here*
(...)
log_dir=/var/log/ceilometer
rpc_backend=ceilometer.openstack.common.rpc.impl_kombu
rabbit_host=localhost
rabbit_port=5672
rabbit_userid=guest
rabbit_password=ficrowstran02
rabbit_retry_backoff=2
rabbit_max_retries=0
database_connection=mongodb://localhost:27017/ceilometer
sql_connection_debug=0
cinder_control_exchange=cinder
enable_v1_api=true

[rpc_notifier2]

[matchmaker_redis]

[publisher_meter]
metering_secret=METERING_SECRET

[keystone_authtoken]
auth_host = localhost
auth_port = 5000
admin_user = ceilometer
admin_password = MYSECRET
admin_tenant_name = admin
auth_uri = http://localhost:5000/v2.0/
=


The ceilometer user pointed at admin_user under the
[keystone_authtoken] section, as well as in os_username under the
[DEFAULT] section,
was created in keystone and it'sbind to the admin tenant.


$ keystone tenant-get admin
+-+--+
|   Property  |  Value   |
+-+--+
| description |  |
|   enabled   |   True   |
|  id | 670f5dd4070d44b6a8308277a236d1af |
| name|  admin   |
+-+--+

$ keystone user-get ceilometer
+--+--+
| Property |  Value   |
+--+--+
|  email   |  ceilome...@example.com  |
| enabled  |   True   |
|id| a98ec068f5f349439acef431e826d7ff |
|   name   |ceilometer|
| tenantId | 670f5dd4070d44b6a8308277a236d1af |
+--+--+


Finally, here's the ceilometer site running on apache. the user
and group 'stackadmin' are valid users indeed in the machine

$ id stackadmin

uid=1000(stackadmin) gid=1000(stackadmin)
groups=1000(stackadmin),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),111
(libvirtd),113(lpadmin),114(sambashare


=
/etc/apache2/sites-available/ceilometer
=
VirtualHost *:9090

Re: [Openstack] ceilometer-agent-central starting fail

2013-04-10 Thread Doug Hellmann
On Wed, Apr 10, 2013 at 6:10 AM, Liu Wenmao marvel...@gmail.com wrote:

 Actually this is not over.

 The main reason of service failure is that central/manager.py
 and service.py use different vairables:

 central/manager.py
  70 def interval_task(self, task):
  71 self.keystone = ksclient.Client(
  72 username=cfg.CONF.*os_username*,
  73 password=cfg.CONF.os_password,
  74 tenant_id=cfg.CONF.os_tenant_id,
  75 tenant_name=cfg.CONF.os_tenant_name,
  76 auth_url=cfg.CONF.os_auth_url)

 44 CLI_OPTIONS = [
  45 cfg.StrOpt('*os-username*',
  46default=os.environ.get('OS_USERNAME', 'ceilometer'),
  47help='Username to use for openstack service access'),
  48 cfg.StrOpt('os-password',
  49default=os.environ.get('OS_PASSWORD', 'admin'),
  50help='Password to use for openstack service access'),
  51 cfg.StrOpt('os-tenant-id',
  52default=os.environ.get('OS_TENANT_ID', ''),
  53help='Tenant ID to use for openstack service access'),
  54 cfg.StrOpt('os-tenant-name',
  55default=os.environ.get('OS_TENANT_NAME', 'admin'),
  56help='Tenant name to use for openstack service access'),
  57 cfg.StrOpt('os_auth_url',
  58default=os.environ.get('OS_AUTH_URL',
  59   'http://localhost:5000/v2.0'),

 So after I change all - to _ and modify all options in
 /etc/ceilometer/ceilometer.conf, the service starts OK.


The thing that fixed it was changing - to _ in your configuration file.
The options library allows option names to have - in them so they look
nice as command line switches, but the option name uses the _.

Doug





 On Wed, Apr 10, 2013 at 2:02 PM, Liu Wenmao marvel...@gmail.com wrote:

 I solve this problem by two steps:

 1 modify /etc/init/ceilometer-agent-central.conf
 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central --
 --config-file=/etc/ceilometer/ceilometer.conf
 2 add some lines to /etc/ceilometer/ceilometer.conf:
 os-username=ceilometer
 os-password=nsfocus
 os-tenant-name=service
 os-auth-url=http://controller:5000/v2.0



 On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao marvel...@gmail.com wrote:

 Hi all:

 I have just install ceilometer grizzly github version, but fail to
 start ceilometer-agent-central service. I think it is due to that I didn't
 set up the keystone user/password like other projects. but I follow the
 instructions(
 http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
 but it does not include the ceilometer configuration.

 # service ceilometer-agent-central start
 ceilometer-agent-central start/running, process 5679

 # cat /etc/init/ceilometer-agent-central.conf
 description ceilometer-agent-compute
 author Chuck Short zul...@ubuntu.com

 start on runlevel [2345]
 stop on runlelvel [!2345]

 chdir /var/run

 pre-start script
 mkdir -p /var/run/ceilometer
 chown ceilometer:ceilometer /var/run/ceilometer

 mkdir -p /var/lock/ceilometer
 chown ceilometer:ceilometer /var/lock/ceilometer
 end script

 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central


 /var/log/ceilometer/ceilometer-agent-central.log
 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall]
 in looping call
 Traceback (most recent call last):
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py,
 line 67, in _inner
 self.f(*self.args, **self.kw)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py,
 line 76, in interval_task
 auth_url=cfg.CONF.os_auth_url)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 134, in __init__
 self.authenticate()
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 205, in authenticate
 token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 174, in get_raw_token_from_identity_servicetoken=token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 202, in _base_authN
 resp, body = self.request(url, 'POST', body=params, headers=headers)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 366, in request
 raise exceptions.from_response(resp, resp.text)
 Unauthorized: Unable to communicate with identity service: {error:
 {message: Invalid user / password, code: 401, title: Not
 Authorized}}. (HTTP 401)
 2013-04-10 13:01:39

[Openstack] [Metering] News from 31/05 to 06/06

2012-06-06 Thread Julien Danjou
Hi,

Here's a few things done in the last week concerning ceilometer:

- The floating IP pollster have been merged
  
https://github.com/stackforge/ceilometer/commit/bbc706c4c02d2750df961474b00998b9766cd47a
- The configuration now uses openstack.common.cfg
  
https://github.com/stackforge/ceilometer/commit/a49e59b1151ce87c8f4ed6e12368e01dbbb6243a
- All instance events are listened to
  
https://github.com/stackforge/ceilometer/commit/d615fb872ddceaf1ddef7e3997bcf2523cab283e
- Updated to use the new Nova flag API
  
https://github.com/stackforge/ceilometer/commit/6fa69bbdccb9273ef1e55f08dc3db926ab20529c

Cheers,
-- 
Julien Danjou
// eNovance  http://enovance.com
// ✉ julien.dan...@enovance.com  ☎ +33 1 49 70 99 81

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Release plan for 0.1

2012-09-12 Thread Doug Hellmann
On Wed, Sep 12, 2012 at 12:47 PM, Graham Binns gra...@canonical.com wrote:

 Hi all,

 Based on the discussion in the last Ceilometer meeting[1], here's my
 proposal for dates for the Ceilometer 0.1 release calendar:

  - Feature freeze for 0.1 QA: 2012-09-28
  - Release: 2012-10-12

 Arguments for / against welcome.


Those dates seem reasonable to me.



  [1]
 http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.log.html

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [metering][ceilometer] Ceilometer and Keystone regions

2012-11-08 Thread Aguiar, Glaucimar (Brazil RD-ECL)
Hello,

Can Ceilometer collect data about instances in different keystone regions? Is 
this a valid/possible configuration?

Scenario 1: I have two regions defined in my keystone service, each one has a 
nova service in it. Can Ceilometer collect metering information from both 
regions? In a single database?
Scenario 2: I have two nova services in my keystone service region. Can 
Ceilometer support this configuration?

I appreciate any information on this, documentation pointers on this subject 
are helpful as well.

Thanks!
Glaucimar Aguiar




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-08 Thread Shengjie_Min
Thanks Julien, I will write up a blueprint soon.

Shengjie

-Original Message-
From: Julien Danjou [mailto:jul...@danjou.info] 
Sent: 07 November 2012 18:12
To: Min, Shengjie
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - 
blueprint?

On Wed, Nov 07 2012, shengjie_...@dell.com wrote:

Hi Shengjie,

 I am looking for a way to propose a blueprint to the ceilometer team - 
 Adding Hbase storage backend for ceilometer. Currently we have only 
 MongoDB and SQLalchemy as the possible ceilometer storage backend. 
 Given the storage interface is clearly designed and allows us to have 
 different backend, it would be nice to have more options which make 
 Ceilometer more adoptive to some providers' existing architectures. As 
 a cloud IAAS provider, Ceilometer might not be just considered as a 
 usage db, also it's being seen as a centralized place to store all the 
 usage data cross platforms. Additionally, all the historical usage 
 data stored can be used for historical usage analysis as well, this is 
 where MapReduce comes into play. With Hadoop Hbase, it allows usage 
 data to be stored in HDFS, also it gives us the ability to run large 
 scale massive MapRed analysis jobs in the future.

This is indeed a good idea, and as you pointed out, Ceilometer collector has 
been designed so this is being possible.

I think you can create a blueprint here:

  https://blueprints.launchpad.net/ceilometer

And write in what should be done.

--
Julien Danjou
;; Free Software hacker  freelance
;; http://julien.danjou.info

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [metering][ceilometer] Ceilometer and Keystone regions

2012-11-08 Thread Julien Danjou
On Thu, Nov 08 2012, Aguiar, Glaucimar (Brazil RD-ECL) wrote:

 Can Ceilometer collect data about instances in different keystone
 regions? Is this a valid/possible configuration?

 Scenario 1: I have two regions defined in my keystone service, each one has
 a nova service in it. Can Ceilometer collect metering information from both
 regions? In a single database?

Yes, you'll just have to deploy at least one ceilometer-collector in
each region on Nova and connect them to the same database. Plus
ceilometer-agent-compute on each nova-compute.

 Scenario 2: I have two nova services in my keystone service region. Can 
 Ceilometer support this configuration?

Yes, same answer as scenario 1, deploy at least a ceilometer-collector
for each Nova, plus ceilometer-agent-compute.

If you want to easily identify the region your meter stored in
Ceilometer come from, you can use the 'source' field of the meters to a
string that helps you recognize which region the meter come from (see
counter_source option in Ceilometer).

-- 
Julien Danjou
-- Free Software hacker  freelance
-- http://julien.danjou.info


pgpowwb8kk0eo.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [metering][ceilometer] Ceilometer and Keystone regions

2012-11-08 Thread Aguiar, Glaucimar (Brazil RD-ECL)
Great! Thanks!

On Nov 8, 2012, at 8:33 PM, Julien Danjou jul...@danjou.info wrote:

 On Thu, Nov 08 2012, Aguiar, Glaucimar (Brazil RD-ECL) wrote:
 
 Can Ceilometer collect data about instances in different keystone
 regions? Is this a valid/possible configuration?
 
 Scenario 1: I have two regions defined in my keystone service, each one has
 a nova service in it. Can Ceilometer collect metering information from both
 regions? In a single database?
 
 Yes, you'll just have to deploy at least one ceilometer-collector in
 each region on Nova and connect them to the same database. Plus
 ceilometer-agent-compute on each nova-compute.
 
 Scenario 2: I have two nova services in my keystone service region. Can 
 Ceilometer support this configuration?
 
 Yes, same answer as scenario 1, deploy at least a ceilometer-collector
 for each Nova, plus ceilometer-agent-compute.
 
 If you want to easily identify the region your meter stored in
 Ceilometer come from, you can use the 'source' field of the meters to a
 string that helps you recognize which region the meter come from (see
 counter_source option in Ceilometer).
 
 -- 
 Julien Danjou
 -- Free Software hacker  freelance
 -- http://julien.danjou.info

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack] [ceilometer] API /v1/meters/ return '404 Not Found'

2013-02-04 Thread Julien Danjou
On Mon, Feb 04 2013, Qinglong.Meng wrote:

 Hi all,
 I have deployed ceilometer with openstack F.
 Version:
 ceilometer: stable/folsom
 openstack: folsom
 nova: 2012.2.3

 The ceilometer services here:
 nova 6750 5522 0 17:16 pts/0 00:00:04 /usr/bin/python
 /usr/local/bin/ceilometer-collector
 nova 6762 5522 0 17:17 pts/0 00:00:04 /usr/bin/python
 /usr/local/bin/ceilometer-agent-central
 nova 6771 5522 0 17:17 pts/0 00:00:03 /usr/bin/python
 /usr/local/bin/ceilometer-agent-compute
 nova 7271 5522 0 17:23 pts/0 00:00:00 /usr/bin/python
 /usr/local/bin/ceilometer-api

  I try this api:
 http://docs.openstack.org/developer/ceilometer/webapi/v1.html
  * GET /v1/resources OK
  * GET /v1/projects OK
  * GET /v1/meters: I got the 404 not Found response.
  and I don't get the WARNNING and TRACE by ceilometer-api.

  Is the API correct or not implement?

 Any good idea?

Which version of Ceilometer did you deploy?
Indeed, not everything is implemented in the API, but /meters is
implemented in current development version as far as I can see.

-- 
Julien Danjou
-- Free Software hacker  freelance
-- http://julien.danjou.info


pgpJwDH_j2bTw.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Metering] News from 17/05 to 23/05

2012-05-23 Thread Julien Danjou
Hi,

Here's a few things done in the last week concerning ceilometer:

- Doug added plugin support to the notification portion of the
  collector daemon
  
https://github.com/stackforge/ceilometer/commit/73c9150afe7fc07018b0435ae7b24b52bd6a0a15
- Doug added a tool for recording notifications and replaying them
  
https://github.com/stackforge/ceilometer/commit/8f4ba1656c26ac7885c46f2fc8fcf9f519146f96
- Doug wrote a an architecture proposal:
  http://wiki.openstack.org/EfficientMetering/ArchitectureProposalV1
- I've added ceilometer-agent and ceilometer-collector daemons
  
https://github.com/stackforge/ceilometer/commit/5717e9c5c9a029d1b1daa72f2e7ac0ab1039bf0c
- I've added some code to fetch CPU time from libvirt
  
https://github.com/stackforge/ceilometer/commit/cc5b02dc84e26af050a0983764a5977e25bd3726

Cheers,
-- 
Julien Danjou
// eNovance  http://enovance.com
// ✉ julien.dan...@enovance.com  ☎ +33 1 49 70 99 81

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-07 Thread Shengjie_Min
Hi,

I am looking for a way to propose a blueprint to the ceilometer team - Adding 
Hbase storage backend for ceilometer. Currently we have only MongoDB and 
SQLalchemy as the possible ceilometer storage backend. Given the storage 
interface is clearly designed and allows us to have different backend, it would 
be nice to have more options which make Ceilometer more adoptive to some 
providers' existing architectures. As a cloud IAAS provider, Ceilometer might 
not be just considered as a usage db, also it's being seen as a centralized 
place to store all the usage data cross platforms. Additionally, all the 
historical usage data stored can be used for historical usage analysis as well, 
this is where MapReduce comes into play. With Hadoop Hbase, it allows usage 
data to be stored in HDFS, also it gives us the ability to run large scale 
massive MapRed analysis jobs in the future.

Thanks,
Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error 401 Unauthorized

2013-05-28 Thread Doug Hellmann
Right now we only have a web API, which you can use via the client library,
curl, or the command line tool. There are a few people working on
integrating ceilometer data with horizon, but I don't know the status of
that project.

Doug


On Tue, May 28, 2013 at 3:49 AM, Ildiko Vancsa ildiko.van...@gmail.comwrote:

 Hi All,

 I'm new to OpenStack and Ceilometer as well, so I have a few questions. :)

 Does Ceilometer supports a Web UI or it is available via command line and
 curl only? I installed the environment with DevStack as I wanted to check
 how it works and looks like and it sets ceilometer in the apache2 serveice
 as an enabled site, but I could not find any information about how to set
 it up correctly.

 Thanks and Best Regards,
 Ildiko

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer] Ganglia Ceilometer integration

2013-01-08 Thread Jiang, Yunhong
My 2 cents.

Basically there are two method to interact with Ganglia. One is to push all 
data from ceilometer into Gangalia, another one is your suggestion, put all 
data from Gangalia to ceilometer. 

According to current definition of ceilometer infrastructure to collect 
measurements within OpenStack, IMHO, possibly we take not take data from 
Gangalia. If some data in Gangalia that are openstack/cloud specific, we should 
have pollster in ceilometer to get it.

If Ganglia has interest in ceilometer data, we can achieve it through a 
specific publisher, to put data into Gangalia.

Thanks
--jyh

 -Original Message-
 From: openstack-bounces+yunhong.jiang=intel@lists.launchpad.net
 [mailto:openstack-bounces+yunhong.jiang=intel@lists.launchpad.net] On
 Behalf Of daniel_ley...@dell.com
 Sent: Tuesday, January 08, 2013 11:23 PM
 To: shengjie_...@dell.com
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] [Ceilometer] Ganglia Ceilometer integration
 
 Shengjie,
 
 I've been thinking quite a lot about that recently. I was considering putting 
 up a
 blueprint about supporting collection of metrics from Ganglia-monitored
 servers and pushing them into Ceilometer, assuming there isn't anything
 already up.
 
 I have run Ganglia on large numbers of servers in the past collecting metrics
 and was thinking that, particularly with monitoring tie-ins with Ceilometer, 
 it
 would be useful to have a producer that will scrape Ganglia's native XML-based
 metric reports and push metrics into Ceilometer for persistence and analysis. 
 I
 think that would complement the blueprint you raised about the HBase storage
 backend for storing would could quickly become a vast amount of data - more
 than the current backends could handle well - and if implemented properly
 should work well with the multi-producer work that is going on.
 
 
 Dan
 
 
 
 -Original Message-
 From: openstack-bounces+daniel_leyden=dell@lists.launchpad.net
 [mailto:openstack-bounces+daniel_leyden=dell@lists.launchpad.net] On
 Behalf Of Min, Shengjie
 Sent: 08 January 2013 13:02
 To: jul...@danjou.info
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] [Ceilometer] Ganglia Ceilometer integration
 
 Hi Julien,
 
 Just look at the blueprints and your post, seems like there is some effort
 around synaps, also something around heat, cloudwatch. Just trying to get a
 clear picture about the vision and direction around monitoring area.
 
 Shengjie
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error 401 Unauthorized

2013-05-27 Thread Angus Salkeld

On 27/05/13 11:14 -0300, Bruno Oliveira wrote:

Hello stackers,

I'm having a really hard time setting up ceilometer-api so I thought
if I could ask you guys for some enlightment.

I can clearly see data being pulled in the screens that are running
/ceilometer-collector, ./ceilometer-agent-compute ,./ceilometer-agent-central

Even the screen running ceilometer-api-server starts with no problem.

But I cannot reach the api at all via curl. Neither by using its
actual port (8777)
nor using the port set in the virtual host of apache. All I'm getting
is auth error

$ curl http://127.0.0.1:8777  OR  $ curl http://127.0.0.1:9090
=
html
head
 title401 Unauthorized/title
/head
body
 h1401 Unauthorized/h1
 This server could not verify that you are authorized to access the
document you requested. Either you supplied the wrong credentials
(e.g., bad password), or your browser does not understand how to
supply the credentials required.br /br /
Authentication required
=


Right, Authentication is required by the client, but you are not
passing it any credentials.

I'd suggest using python-ceilometerclient to do the auth for you:
So use it like any other openstack client.

try something like this:

asalkeld@elf python-ceilometerclient (master)$ . ../devstack/openrc admin admin
asalkeld@elf python-ceilometerclient (master)$ ceilometer resource-list
+--++-+--+
| Resource ID  | Source | User ID | Project ID  
 |
+--++-+--+
| a8ce423c-c1a1-41e3-af7c-b38d92f5e36f || None| 
1076d9bd669d422bbd74e1e2f54d1510 |
+--++-+--+
asalkeld@elf python-ceilometerclient (master)$ ceilometer meter-list
+--+---+---+--+-+--+
| Name | Type  | Unit  | Resource ID  | User ID 
| Project ID   |
+--+---+---+--+-+--+
| image| gauge | image | a8ce423c-c1a1-41e3-af7c-b38d92f5e36f | None
| 1076d9bd669d422bbd74e1e2f54d1510 |
| image.size   | gauge | B | a8ce423c-c1a1-41e3-af7c-b38d92f5e36f | None
| 1076d9bd669d422bbd74e1e2f54d1510 |
| image.update | delta | image | a8ce423c-c1a1-41e3-af7c-b38d92f5e36f | None
| 1076d9bd669d422bbd74e1e2f54d1510 |
| image.upload | delta | image | a8ce423c-c1a1-41e3-af7c-b38d92f5e36f | None
| 1076d9bd669d422bbd74e1e2f54d1510 |
+--+---+---+--+-+--+
asalkeld@elf python-ceilometerclient (master)$ ceilometer sample-list -m 
image.update
+--+--+---++---++
| Resource ID  | Name | Type  | Volume | Unit  
| Timestamp  |
+--+--+---++---++
| a8ce423c-c1a1-41e3-af7c-b38d92f5e36f | image.update | delta | 1.0| image 
| 2013-05-28T01:14:40.238000 |
+--+--+---++---++


Remember you can only see the samples/meter/resources that you own or all if 
you are admin.


-Angus




On top of that, the only thing I had to do in a non-standard basis, was to
setup ceilometer virtual host to answer request on port 9090 of apache
instead of the default 80 (since horizon is bind to it).


Here's a copy of my running ceilometer.conf
=
/etc/ceilometer/ceilometer.conf
=
[DEFAULT]
os_username=ceilometer
os_password=MYSECRET
os_tenant_name=admin
os_auth_url=http://localhost:5000/v2.0
signing_dirname = /tmp/keystone-signing-ceilometer
metering_api_port=8777
auth_strategy=keystone
nova_control_exchange=nova
hypervisor_inspector=libvirt
libvirt_type=kvm
glance_control_exchange=glance
quantum_control_exchange=quantum
debug=true
verbose=true
(...)
*logging writing parameters here*
(...)
log_dir=/var/log/ceilometer
rpc_backend=ceilometer.openstack.common.rpc.impl_kombu
rabbit_host=localhost
rabbit_port=5672
rabbit_userid=guest
rabbit_password=ficrowstran02
rabbit_retry_backoff=2
rabbit_max_retries=0
database_connection=mongodb://localhost:27017/ceilometer
sql_connection_debug=0
cinder_control_exchange=cinder
enable_v1_api=true

[rpc_notifier2]

[matchmaker_redis]

[publisher_meter]
metering_secret=METERING_SECRET

[keystone_authtoken]
auth_host = localhost
auth_port = 5000
admin_user = ceilometer
admin_password = MYSECRET

Re: [Openstack] Ceilometer Install

2013-04-26 Thread Riki Arslan
The command line I am using is: sudo /usr/local/bin/ceilometer-api.

However, the ceilometer.ini file is missing. The version of Ceilometer I am
using is ceilometer-2013.1~g2.tar.gz. And, I only have the following
configuration files:

/etc/ceilometer/ceilometer.conf
/etc/ceilometer/policy.json
/etc/ceilometer/sources.json

Thanks.


On Fri, Apr 26, 2013 at 1:10 AM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:




 On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I have
 installed the driver Mongo using sudo pip install pymongo.


 Ceilometer does use a database. You have to install the right driver. If
 you want Mongo, then it sounds like you've done the right thing. It's
 possible mako is also being used somewhere else, I'm not sure.



 Regarding the current problem; the traceback is as follows:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 That is coming from oslo.config. Can you post the ceilometer.ini file and
 command line you are using to start the service?

 Doug



 Thank for the help.


 On Thu, Apr 25, 2013 at 3:27 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:



 On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance
 endpoint 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed
 the v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError:
 No module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


 Mako is a dependency do sqlalchemy, I think. Are you using the
 sqlalchemy storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is
 as follows:
 AttributeError: 'OptGroup' object has no attribute
 '_get_argparse_group'


 That sounds like a problem with the config module. Was there a full
 traceback? If not, try adding the --debug option when starting the service.

 Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that
 was causing the conflict. After updating it, the conflict error 
 disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which
 presumably has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it 
 is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of
 the keystone client, so

[Openstack] [openstack] [ceilometer] API /v1/meters/ return '404 Not Found'

2013-02-04 Thread Qinglong.Meng
Hi all,
I have deployed ceilometer with openstack F.
Version:
ceilometer: stable/folsom
openstack: folsom
nova: 2012.2.3

The ceilometer services here:
nova 6750 5522 0 17:16 pts/0 00:00:04 /usr/bin/python
/usr/local/bin/ceilometer-collector
nova 6762 5522 0 17:17 pts/0 00:00:04 /usr/bin/python
/usr/local/bin/ceilometer-agent-central
nova 6771 5522 0 17:17 pts/0 00:00:03 /usr/bin/python
/usr/local/bin/ceilometer-agent-compute
nova 7271 5522 0 17:23 pts/0 00:00:00 /usr/bin/python
/usr/local/bin/ceilometer-api

 I try this api:
http://docs.openstack.org/developer/ceilometer/webapi/v1.html
 * GET /v1/resources OK
 * GET /v1/projects OK
 * GET /v1/meters: I got the 404 not Found response.
 and I don't get the WARNNING and TRACE by ceilometer-api.

 Is the API correct or not implement?

Any good idea?

Tks,
Best Regards,
-- 

Lawrency Meng
mail: mengql112...@gmail.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer question

2013-03-26 Thread Doug Hellmann
You want the statistics command from the v2 API.

ceilometer --ceilometer-api-version 2 help statistics

The CLI needs a little work to make the options clear, but the API
documentation may help explain:
http://docs.openstack.org/developer/ceilometer/webapi/v2.html

Doug

On Tue, Mar 26, 2013 at 12:22 PM, Wyllys Ingersoll 
wyllys.ingers...@evault.com wrote:


 Perhaps this is documented but I can't seem to find it…

 I want to use ceilometer to show usage from the swift objectstore.  What
 would the correct command be to extract that information? Currently, the
 various -list commands just spit out various meter types along with
 resource and project id values.

 Thanks,
   Wyllys Ingersoll
   EVault


 On Mar 26, 2013, at 11:47 AM, Julien Danjou jul...@danjou.info wrote:

  Hi,
 
  We're pleased to announce that the RC1 version for the Grizzly release
  of Ceilometer is available!
 
https://launchpad.net/ceilometer/grizzly/grizzly-rc1
 
  Unless release-critical issues are found that warrant a release
  candidate respin, this version will be formally released as the
  Ceilometer 2013.1 version on April 4. You are therefore strongly
  encouraged to test and validate this tarball.
 
  If you find an issue that could be considered release-critical, please
  file it at:
 
  https://bugs.launchpad.net/ceilometer/+filebug
 
  Note that the master branch for Ceilometer is now open for Havana
  development, and feature freeze restriction no longer apply.
 
  --
  Julien Danjou
  -- Free Software hacker - freelance consultant
  -- http://julien.danjou.info
  ATT1___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [metering] integrating Quantum and Ceilometer

2012-06-27 Thread Doug Hellmann
Hello,

As part of the ceilometer project¹, we're working on retrieving usage
data from various OpenStack components. We would like to integrate
with Quantum for information about network resource utilization that a
deployer might want to bill their tenants for.

Ceilometer has a plugin-based architecture, which makes it easy to add
new measurement types and data collectors. Our approach with other
measurements is to collect everything and let the ceilometer user decide
what to bill for and what to ignore (they can turn off measurements for
things they do not care about).

Depending on the project and the type of data, we can either
use the notification events generated by allocating/deallocating
a resource, or we can poll for metrics being collected elsewhere.
We will probably want to use both approaches for integrating
with Quantum (e.g., use events for things like IP allocation and
polling for I/O).

Do you have any advice on how to integrate Ceilometer and Quantum?
For example, does Quantum emit notifications and does it collect
(or provide an API to query) I/O statistics?

Thanks,
Doug


¹  http://launchpad.net/ceilometer
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [HyperV][Ceilometer] Performance statistics from Hyper-V with Ceilometer and libvirt

2013-06-06 Thread Julien Danjou
On Wed, Jun 05 2013, Bruno Oliveira wrote:

 So far, in the irc channel #openstack-ceilometer, I got to know that
 ceilometer, just like collectd, uses libvirt to query the hypervisors
 for data (thanks dhellmann !). BUT if check in the libvirt.org site,
 it's being said
 that there's support for Hyper-V: http://libvirt.org/drvhyperv.html
  (given a uri to connect to it).

First question is, is Hyper-V driver for Nova used via libvirt?
If yes, then libvirt should be patched to provide information to
Ceilometer.
If not, then Ceilometer should be patched to learn how to poll Hyper-V.

-- 
Julien Danjou
# Free Software hacker # freelance consultant
# http://julien.danjou.info


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [HyperV][Ceilometer] Performance statistics from Hyper-V with Ceilometer and libvirt

2013-06-07 Thread Peter Pouliot


https://blueprints.launchpad.net/ceilometer/+spec/hyper-v-agent

Sent from my Verizon Wireless 4G LTE Smartphone



 Original message 
From: Julien Danjou jul...@danjou.info
Date: 06/07/2013 4:37 AM (GMT-05:00)
To: Peter Pouliot ppoul...@microsoft.com
Cc: Bruno Oliveira brunnop.olive...@gmail.com,OpenStack 
openstack@lists.launchpad.net
Subject: Re: [Openstack] [HyperV][Ceilometer] Performance statistics from 
Hyper-V with Ceilometer and libvirt


On Thu, Jun 06 2013, Peter Pouliot wrote:

 The hyper-v driver uses WMI.
 Libvirt is not used. There is currently no support for celometer, however we
 should have havana blueprints meaning it is one of the things we are trying
 to deliver.

We'd be glad to have this support indeed. I don't think I saw any
blueprint about this on Ceilometer, did you already create them
somewhere?

--
Julien Danjou
;; Free Software hacker ; freelance consultant
;; http://julien.danjou.info
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [metering] ceilometer dev docs on readthedocs.org

2012-07-05 Thread Doug Hellmann
On Tue, Jul 3, 2012 at 3:38 PM, Loic Dachary l...@enovance.com wrote:

 On 07/03/2012 07:46 PM, Doug Hellmann wrote:
  I've set up the ceilometer development documentation build on RTD at
 http://ceilometer.readthedocs.org/en/latest/index.html
 
 Hi,

 I've updated https://launchpad.net/ceilometer to list this link.


Thanks, Loic!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] Monitoring physical devices

2012-11-01 Thread Zehnder Toni (zehndton)
Hi there,

I am looking for a way to monitor the whole OpenStack environment including 
physical servers as well as the network. 
On every physical compute node is the Ceilometer compute agent installed, 
right?!
1) Does the compute agent collect data of the physical machine as well or is it 
just collecting data of the virtual machines?
2) Could it be useful to enhance the Ceilometer agent to collect data from the 
physical servers? 

Toni

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-15 Thread Julien Danjou
On Thu, Nov 15 2012, shengjie_...@dell.com wrote:

 The blueprint is registered :
 https://blueprints.launchpad.net/ceilometer/+spec/hbase-storage-backend, Any
 idea what's the next step ? :)

Implementing? :)

And eventually adding more blueprint to depends on if you can't
implement this one directly because of some missing stuff.

-- 
Julien Danjou
/* Free Software hacker  freelance
   http://julien.danjou.info */


pgp8jDsQh0QEc.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] How does ceilometer work with multi-DC scenario

2012-11-20 Thread Shengjie_Min
Hi,

Has anybody come across the scenario you need to deploy two or more openstack 
swift or nova clusters for whatever DR or HA reasons. How Ceilometer is going 
to cope with that? Just wondering is there any plans or blueprints addressing 
the usage data replication/distinguish/isolation among multi-DCs?

Thanks,
Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer] Ganglia Ceilometer integration

2013-01-08 Thread Julien Danjou
On Tue, Jan 08 2013, shengjie_...@dell.com wrote:

 Just out of curiosity, Have we ever had any previous threads discussing
 about possibility of integrating Ceilometer with ganglia as a monitoring
 approach? Didn't manage to find any from the mailing list archive.

Doesn't ring a bell, indeed.

-- 
Julien Danjou
;; Free Software hacker  freelance
;; http://julien.danjou.info


pgpWaR3KSFLqz.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] How to purge old meter data of Ceilometer

2013-04-04 Thread Julien Danjou
On Thu, Apr 04 2013, Harri Pyy wrote:

 With the default 1 minute interval, Ceilometer collects quite large amounts 
 of meter data.

 Does Ceilometer provide a TTL configuration option for the meter data, or
 some other functionality or API for purging old meter data?

Not yet unfortunately.

-- 
Julien Danjou
;; Free Software hacker ; freelance consultant
;; http://julien.danjou.info


pgp1Idj4d32BF.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Ceilometer 2013.1 released

2013-04-04 Thread Julien Danjou
Hello,

Ceilometer 2013.1 has been released, ending the Grizzly development
cycle where we were an incubated project, and became an integrated one
for the Havana cycle.

The tarball can be found with the list of features and bugfixes here:

https://launchpad.net/ceilometer/grizzly/2013.1

Congratulations to everyone for this!

-- 
Julien Danjou
-- Free Software hacker - freelance consultant
-- http://julien.danjou.info


pgpGYgEau09B1.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer] Can not start agents, can't find a publisher manager

2013-04-10 Thread Zehnder Toni (zehndton)
I`ve a problem with the ceilometer agents. When I want to start one, it can`t 
find a publisher manager('meter_publisher').
The whole error is :

CRITICAL ceilometer [-] Pipeline {'publishers': ['meter_publisher'], 
'interval': 60, 'transformers': None, 'name': 'meter_pipeline', 'counters': 
['*']}: Publishers set(['meter_publisher']) invalid

Is there a solution for this problem? It looks similar to 
https://bugs.launchpad.net/devstack/+bug/1131467

Thanks,

Toni Zehnder
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] HBase Configuration/Instruction is now available on openstack docs

2013-05-10 Thread Shengjie_Min
Hi guys,

For those of you who wanted to try out HBase as the backend for Ceilometer. 
Glad to let you know the document for HBase configuration is available now on 
openstack docs:

http://docs.openstack.org/developer/ceilometer/configuration.html#hbase

If you had any issues or questions, feel free to ping me on IRC or drop me 
emails :)

All the best,
Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] how to enable cpu meter?

2013-05-28 Thread Julien Danjou
On Tue, May 28 2013, alexander barakin wrote:

 i use fresh devstack without local modifications on ubuntu 12.04
 i have run the example image cirros-0.3.1-x86_64-uec and see the following
 meters in output of ceilometer meter-list:

You need to run `ceilometer-agent-compute'.

-- 
Julien Danjou
-- Free Software hacker - freelance consultant
-- http://julien.danjou.info


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] support for older versions of ceilometer

2013-05-30 Thread Doug Hellmann
From what I understand, it is unusual to support mixing components from
different releases like that. Am I wrong?

Doug


On Thu, May 30, 2013 at 3:29 PM, Tim Bell tim.b...@cern.ch wrote:

 ** **

 Doug,

 ** **

 Can you advise on what the plan/policy will be for Havana ?

 ** **

 **-  **Will I be able to run Havana core components such as Nova
 with Grizzly ceilometer ?

 **-  **Will I be able to run Havana ceilometer with Grizzly core
 components (with reduced functionality compared to the Havana core
 components) ?

 ** **

 Tim

 ** **

 *From:* Openstack [mailto:openstack-bounces+tim.bell=
 cern...@lists.launchpad.net] *On Behalf Of *Doug Hellmann
 *Sent:* 30 May 2013 18:59
 *To:* openstack@lists.launchpad.net
 *Subject:* [Openstack] [ceilometer] support for older versions of
 ceilometer

 ** **

 The ceilometer team has had a few requests for help with older versions of
 ceilometer or running the grizzly version of ceilometer with older versions
 of other OpenStack components lately. We appreciate the level of interest
 in the project but, as much as we would like to, unfortunately we are not
 always able to help everyone with these mixed configurations. During the
 early phases of our development we tried to maintain compatibility with
 folsom, even well into the grizzly development cycle. We are no longer
 doing that, however, and so to make clear what support we can offer, the
 ceilometer team has put together the statement below. It has been added to
 our documentation, and we are posting here to make sure everyone has a
 chance to see it.

 ** **

 Regards,

 Doug

 ** **

 ** **

 The ceilometer team has limited capacity to provide support for older
 versions of the project. Because the project graduated from incubation
 around the time of the grizzly release, that is the first version for which
 we will provide regular ongoing support following the standard deprecation
 cycle for OpenStack [1]. The grizzly version of ceilometer  cannot be
 installed on the same server with earlier versions of OpenStack because of
 conflicting package requirements, but is API compatible with the folsom
 release if installed separately.

 ** **

 [1] https://wiki.openstack.org/wiki/StableBranch

 ** **

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer] Problem with nova resize events

2013-07-24 Thread Alessandro Barabesi
Hi everybody,

I have the following problem when resizing an instance. I expected ceilometer 
to generate samples
for the following resize related events:

compute.instance.resize.prep.start/.end
compute.instance.resize.confirm.start/.end

and, maybe, also for:

compute.instance.resize.start/.end
compute.instance.finish_resize.start/.end


but if I query ceilmeter I only find samples with 
event_type=compute.instance.finish_resize.end

Can you tell me if ceilometer is meant to collect only the 
compute.instance.finish_resize.end event?


Many thanks
Alex


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-07 Thread Julien Danjou
On Wed, Nov 07 2012, shengjie_...@dell.com wrote:

Hi Shengjie,

 I am looking for a way to propose a blueprint to the ceilometer team -
 Adding Hbase storage backend for ceilometer. Currently we have only
 MongoDB and SQLalchemy as the possible ceilometer storage backend. Given the
 storage interface is clearly designed and allows us to have different
 backend, it would be nice to have more options which make Ceilometer more
 adoptive to some providers' existing architectures. As a cloud IAAS
 provider, Ceilometer might not be just considered as a usage db, also it's
 being seen as a centralized place to store all the usage data cross
 platforms. Additionally, all the historical usage data stored can be used
 for historical usage analysis as well, this is where MapReduce comes into
 play. With Hadoop Hbase, it allows usage data to be stored in HDFS, also it
 gives us the ability to run large scale massive MapRed analysis jobs in the
 future.

This is indeed a good idea, and as you pointed out, Ceilometer collector
has been designed so this is being possible.

I think you can create a blueprint here:

  https://blueprints.launchpad.net/ceilometer

And write in what should be done.

-- 
Julien Danjou
;; Free Software hacker  freelance
;; http://julien.danjou.info


pgp0Y6makV0xI.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] How does ceilometer work with multi-DC scenario

2012-11-20 Thread Julien Danjou
On Tue, Nov 20 2012, shengjie_...@dell.com wrote:

 Has anybody come across the scenario you need to deploy two or more
 openstack swift or nova clusters for whatever DR or HA reasons. How
 Ceilometer is going to cope with that? Just wondering is there any plans or
 blueprints addressing the usage data replication/distinguish/isolation among
 multi-DCs?

You can deploy several ceilometer and use several databases, or just one
and use a different 'source' field for each of your region/cluster to
differentiate where meters come from.

-- 
Julien Danjou
# Free Software hacker  freelance
# http://julien.danjou.info


pgpAMx4Vs8WRp.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer] Ganglia Ceilometer integration

2013-01-09 Thread Shengjie_Min
If Ganglia has interest in ceilometer data, we can achieve it through a 
specific publisher, to put data into Gangalia.

@yunhong, So it is more like the approach to CW or Synaps, isn't it? if the 
monitoring system is interested in the meters from Ceilometer, we can have 
different publishers to push data to different destinations(I think this can be 
a potential blueprint for ganglia). But that being said, if the backend is 
something like Cassandra, Mongo or even Hbase, the system metrics(from gmond) 
and openstack specific meters might be stored in a centralized storage just 
with different namespaces. Thoughts?

- Shengjie

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] support for older versions of ceilometer

2013-05-31 Thread Julien Danjou
On Thu, May 30 2013, Tim Bell wrote:

 I hope that ceilometer can also include this within the Havana timeframe as
 it becomes a key component of production, large scale
 clouds.

I think we all agree in principle. We'd be happy to enhance Ceilometer
and fix potential bugs in this direction, but we'll require some help
testing the upgrade path *before* Havana is released.

-- 
Julien Danjou
# Free Software hacker # freelance consultant
# http://julien.danjou.info


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Ceilometer with swift

2013-07-01 Thread Axel Christiansen
Dear List,


i am trying to retrieve measurements from swift via ceilometer.
ceilometer stores its measurements in db and so. looks good.


The ceilometer V2 Web API is expecting resource_id as UUID value, for
example. I can not find a UUID anywere. When listing resources (GET
/v2/resources/) the result contains a lot of ids for various things but
non in UUID format.

What am i doing wrong?


Thank you and nice day.

Axel

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer getting a Connection refused from

2013-07-02 Thread Julien Danjou
On Tue, Jul 02 2013, Jobin Raju George wrote:

 Here is my /etc/ceilometer/ceilometer.conf:
 http://pastebin.ubuntu.com/5835612/

So the problem is that you configured it to use mongodb at
mongodb://10.112.107.107:27017/ceilometer but mongodb doesn't seem to
answer on this IP/port considering the error. I really dont'get what you
don't get, it seems pretty obvious to me you should install MongoDB
where you configured Ceilometer to look, right?

-- 
Julien Danjou
# Free Software hacker # freelance consultant
# http://julien.danjou.info


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer Install

2013-05-06 Thread Doug Hellmann
It looks like you still have incompatible versions of things installed.

The configuration library changed during grizzly. The old version and new
version cannot be used together in the same program because they both try
to modify different copies of a global variable. The exception you're
getting is, I think, due to the fact that the API service loads the
keystone middleware to handle authentication. You have a version of the
middleware that uses oslo.config, and a version of ceilometer that uses the
older oslo-incubator version of the configuration library.

The ceilometer team is small, so we have limited capacity to support old
versions (especially pre-incubated versions). We do intend to support
grizzly, but can only offer moderate help with folsom. The g2 release
tarballs *should* be compatible at the communication layer with folsom
versions of the other components, but it looks like you can't install them
into the same Python installation as the other services.

You can separate ceilometer code from the other services a couple of
different ways. The simplest would be to use a separate VM to run
ceilometer. That would let you follow all of the normal instructions, and
ensure that you don't have mismatched versions of libraries. The other way
is to install ceilometer into a virtualenv. That would take more care,
since you need to ensure that the virtualenv does not look at the globally
installed site-packages. I haven't tried doing this, so I can't provide
more detailed steps, and you will likely need to experiment a bit to get it
right.

The one piece of ceilometer that does *need* to be installed in the same
location as the other services is the plugin for the nova compute agent. We
spent a fair amount of time making sure there was a version of that plugin
compatible with folsom, so we believe it should work. However, if you are
just testing ceilometer, or not using it for billing instance-hours, you
could skip deploying that piece entirely.

Doug



On Mon, May 6, 2013 at 9:43 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I have also installed ceilometer-2013.1~g2~20130107.449.tar.gz from the
 tarballs list and still getting the same error:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 37, in module
 cfg.CONF(sys.argv[1:])
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 On Mon, May 6, 2013 at 3:56 PM, Riki Arslan riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I actually got it from a link on your website:


 http://doughellmann.com/2013/01/ceilometer-grizzly-2-milestone-available.html

 So, do you think this one is not good?


 On Thu, May 2, 2013 at 7:33 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Mon, Apr 29, 2013 at 6:42 PM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 I thought it might help if mentioned little more:

 /etc/ceilometer.conf file has the following parameters added:

 os_username=ceilometer
 os_password=$PASSWORD
 os_tenant_name=service
 os_auth_url=http://localhost:5000/v2.0/

 I checked CLI_OPTIONS in service.py and it looks allright:

 CLI_OPTIONS = [
 cfg.StrOpt('os-username',
default=os.environ.get('OS_USERNAME', 'ceilometer'),
help='Username to use for openstack service access'),
 cfg.StrOpt('os-password',
default=os.environ.get('OS_PASSWORD', 'admin'),
help='Password to use for openstack service access'),
 cfg.StrOpt('os-tenant-id',
default=os.environ.get('OS_TENANT_ID', ''),
help='Tenant ID to use for openstack service access'),
 cfg.StrOpt('os-tenant-name',
default=os.environ.get('OS_TENANT_NAME', 'admin'),
help='Tenant name to use

Re: [Openstack] Ceilometer Install

2013-05-07 Thread Riki Arslan
Thank you for the through explanation. I have no problem running the
Collector, Central and Compute Agents. So, I believe only the API Server is
trying to use the old oslo-incubator version.

I am still weighing the options.

Just a quick question; since the only thing that does not work in my
environment is the API Server, I believe -as long as I can query MongoDB
directly-, I think I wouldn't need it anyway. Would you say this is correct?


On Mon, May 6, 2013 at 6:08 PM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:

 It looks like you still have incompatible versions of things installed.

 The configuration library changed during grizzly. The old version and new
 version cannot be used together in the same program because they both try
 to modify different copies of a global variable. The exception you're
 getting is, I think, due to the fact that the API service loads the
 keystone middleware to handle authentication. You have a version of the
 middleware that uses oslo.config, and a version of ceilometer that uses the
 older oslo-incubator version of the configuration library.

 The ceilometer team is small, so we have limited capacity to support old
 versions (especially pre-incubated versions). We do intend to support
 grizzly, but can only offer moderate help with folsom. The g2 release
 tarballs *should* be compatible at the communication layer with folsom
 versions of the other components, but it looks like you can't install them
 into the same Python installation as the other services.

 You can separate ceilometer code from the other services a couple of
 different ways. The simplest would be to use a separate VM to run
 ceilometer. That would let you follow all of the normal instructions, and
 ensure that you don't have mismatched versions of libraries. The other way
 is to install ceilometer into a virtualenv. That would take more care,
 since you need to ensure that the virtualenv does not look at the globally
 installed site-packages. I haven't tried doing this, so I can't provide
 more detailed steps, and you will likely need to experiment a bit to get it
 right.

 The one piece of ceilometer that does *need* to be installed in the same
 location as the other services is the plugin for the nova compute agent. We
 spent a fair amount of time making sure there was a version of that plugin
 compatible with folsom, so we believe it should work. However, if you are
 just testing ceilometer, or not using it for billing instance-hours, you
 could skip deploying that piece entirely.

 Doug



 On Mon, May 6, 2013 at 9:43 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I have also installed ceilometer-2013.1~g2~20130107.449.tar.gz from the
 tarballs list and still getting the same error:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 37, in module
 cfg.CONF(sys.argv[1:])
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 On Mon, May 6, 2013 at 3:56 PM, Riki Arslan riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I actually got it from a link on your website:


 http://doughellmann.com/2013/01/ceilometer-grizzly-2-milestone-available.html

 So, do you think this one is not good?


 On Thu, May 2, 2013 at 7:33 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Mon, Apr 29, 2013 at 6:42 PM, Riki Arslan riki.ars...@cloudturk.net
  wrote:

 I thought it might help if mentioned little more:

 /etc/ceilometer.conf file has the following parameters added:

 os_username=ceilometer
 os_password=$PASSWORD
 os_tenant_name=service
 os_auth_url=http://localhost:5000/v2.0/

 I checked CLI_OPTIONS in service.py and it looks allright:

 CLI_OPTIONS = [
 cfg.StrOpt('os-username',
default=os.environ.get('OS_USERNAME

Re: [Openstack] Ceilometer Install

2013-05-08 Thread Doug Hellmann
The database schema isn't part of the formal API, so if you're OK with code
breaking as we make changes to that schema then it would be fine to run
without the API. If you want to ensure your app continues to work across
those changes, it should be straightforward to set up the API server in a
virtualenv.

Doug


On Tue, May 7, 2013 at 7:13 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 Thank you for the through explanation. I have no problem running the
 Collector, Central and Compute Agents. So, I believe only the API Server is
 trying to use the old oslo-incubator version.

 I am still weighing the options.

 Just a quick question; since the only thing that does not work in my
 environment is the API Server, I believe -as long as I can query MongoDB
 directly-, I think I wouldn't need it anyway. Would you say this is correct?


 On Mon, May 6, 2013 at 6:08 PM, Doug Hellmann doug.hellm...@dreamhost.com
  wrote:

 It looks like you still have incompatible versions of things installed.

 The configuration library changed during grizzly. The old version and new
 version cannot be used together in the same program because they both try
 to modify different copies of a global variable. The exception you're
 getting is, I think, due to the fact that the API service loads the
 keystone middleware to handle authentication. You have a version of the
 middleware that uses oslo.config, and a version of ceilometer that uses the
 older oslo-incubator version of the configuration library.

 The ceilometer team is small, so we have limited capacity to support
 old versions (especially pre-incubated versions). We do intend to support
 grizzly, but can only offer moderate help with folsom. The g2 release
 tarballs *should* be compatible at the communication layer with folsom
 versions of the other components, but it looks like you can't install them
 into the same Python installation as the other services.

 You can separate ceilometer code from the other services a couple of
 different ways. The simplest would be to use a separate VM to run
 ceilometer. That would let you follow all of the normal instructions, and
 ensure that you don't have mismatched versions of libraries. The other way
 is to install ceilometer into a virtualenv. That would take more care,
 since you need to ensure that the virtualenv does not look at the globally
 installed site-packages. I haven't tried doing this, so I can't provide
 more detailed steps, and you will likely need to experiment a bit to get it
 right.

 The one piece of ceilometer that does *need* to be installed in the same
 location as the other services is the plugin for the nova compute agent. We
 spent a fair amount of time making sure there was a version of that plugin
 compatible with folsom, so we believe it should work. However, if you are
 just testing ceilometer, or not using it for billing instance-hours, you
 could skip deploying that piece entirely.

 Doug



 On Mon, May 6, 2013 at 9:43 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I have also installed ceilometer-2013.1~g2~20130107.449.tar.gz from the
 tarballs list and still getting the same error:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235,
 in run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 37, in module
 cfg.CONF(sys.argv[1:])
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 On Mon, May 6, 2013 at 3:56 PM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I actually got it from a link on your website:


 http://doughellmann.com/2013/01/ceilometer-grizzly-2-milestone-available.html

 So, do you think this one is not good?


 On Thu, May 2, 2013 at 7:33 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Mon, Apr 29, 2013 at 6:42 PM, Riki Arslan 
 riki.ars...@cloudturk.net

Re: [Openstack] Ceilometer Install

2013-05-06 Thread Riki Arslan
Hi Doug,

I actually got it from a link on your website:

http://doughellmann.com/2013/01/ceilometer-grizzly-2-milestone-available.html

So, do you think this one is not good?


On Thu, May 2, 2013 at 7:33 PM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:




 On Mon, Apr 29, 2013 at 6:42 PM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I thought it might help if mentioned little more:

 /etc/ceilometer.conf file has the following parameters added:

 os_username=ceilometer
 os_password=$PASSWORD
 os_tenant_name=service
 os_auth_url=http://localhost:5000/v2.0/

 I checked CLI_OPTIONS in service.py and it looks allright:

 CLI_OPTIONS = [
 cfg.StrOpt('os-username',
default=os.environ.get('OS_USERNAME', 'ceilometer'),
help='Username to use for openstack service access'),
 cfg.StrOpt('os-password',
default=os.environ.get('OS_PASSWORD', 'admin'),
help='Password to use for openstack service access'),
 cfg.StrOpt('os-tenant-id',
default=os.environ.get('OS_TENANT_ID', ''),
help='Tenant ID to use for openstack service access'),
 cfg.StrOpt('os-tenant-name',
default=os.environ.get('OS_TENANT_NAME', 'admin'),
help='Tenant name to use for openstack service access'),
 cfg.StrOpt('os-auth-url',
default=os.environ.get('OS_AUTH_URL',
   'http://localhost:5000/v2.0'),
help='Auth URL to use for openstack service access'),
 ]

 But still, according to the error I am getting, it can not parse
 _parse_cli_opts:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'

 I am really puzzled as Collector, Computer Agent and Central Agent are
 working fine and Api Server is not.


 I don't see a 2013.1~g2.tar.gz tarball listed under
 http://tarballs.openstack.org/ceilometer/. Where did you get the source
 you are working with?

 You may have a bad snapshot, since it is trying to combine
 ceilometer/openstack/common/cfg.py with oslo.config.

 Doug




 On Tue, Apr 30, 2013 at 12:56 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I have followed the document. The only thing that is different from the
 docs is that I did not copy the yaml file (it does not exist in tarball):

 cp etc/ceilometer/*.yaml /etc/ceilometer

 However, the tarball is the g2 version, which is the last version that
 was supposed to work with Folsom.

 It seems like Collector, Computer Agent and Central Agent are working. I
 only can't get the Api Server working.


 On Fri, Apr 26, 2013 at 6:19 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:

 It sounds like you haven't completed the installation instructions. I
 don't know if the manual steps listed at
 http://docs.openstack.org/developer/ceilometer/install/manual.htmlwork 
 with the tarball, but they should be close.

 Doug


 On Fri, Apr 26, 2013 at 3:46 AM, Riki Arslan riki.ars...@cloudturk.net
  wrote:

 The command line I am using is: sudo /usr/local/bin/ceilometer-api.

 However, the ceilometer.ini file is missing. The version of Ceilometer
 I am using is ceilometer-2013.1~g2.tar.gz. And, I only have the
 following configuration files:

 /etc/ceilometer/ceilometer.conf
 /etc/ceilometer/policy.json
 /etc/ceilometer/sources.json

 Thanks.


 On Fri, Apr 26, 2013 at 1:10 AM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Thu, Apr 25, 2013 at 8:37 AM

Re: [Openstack] Ceilometer Install

2013-05-02 Thread Doug Hellmann
On Mon, Apr 29, 2013 at 6:42 PM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I thought it might help if mentioned little more:

 /etc/ceilometer.conf file has the following parameters added:

 os_username=ceilometer
 os_password=$PASSWORD
 os_tenant_name=service
 os_auth_url=http://localhost:5000/v2.0/

 I checked CLI_OPTIONS in service.py and it looks allright:

 CLI_OPTIONS = [
 cfg.StrOpt('os-username',
default=os.environ.get('OS_USERNAME', 'ceilometer'),
help='Username to use for openstack service access'),
 cfg.StrOpt('os-password',
default=os.environ.get('OS_PASSWORD', 'admin'),
help='Password to use for openstack service access'),
 cfg.StrOpt('os-tenant-id',
default=os.environ.get('OS_TENANT_ID', ''),
help='Tenant ID to use for openstack service access'),
 cfg.StrOpt('os-tenant-name',
default=os.environ.get('OS_TENANT_NAME', 'admin'),
help='Tenant name to use for openstack service access'),
 cfg.StrOpt('os-auth-url',
default=os.environ.get('OS_AUTH_URL',
   'http://localhost:5000/v2.0'),
help='Auth URL to use for openstack service access'),
 ]

 But still, according to the error I am getting, it can not parse
 _parse_cli_opts:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'

 I am really puzzled as Collector, Computer Agent and Central Agent are
 working fine and Api Server is not.


I don't see a 2013.1~g2.tar.gz tarball listed under
http://tarballs.openstack.org/ceilometer/. Where did you get the source you
are working with?

You may have a bad snapshot, since it is trying to combine
ceilometer/openstack/common/cfg.py with oslo.config.

Doug




 On Tue, Apr 30, 2013 at 12:56 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I have followed the document. The only thing that is different from the
 docs is that I did not copy the yaml file (it does not exist in tarball):

 cp etc/ceilometer/*.yaml /etc/ceilometer

 However, the tarball is the g2 version, which is the last version that
 was supposed to work with Folsom.

 It seems like Collector, Computer Agent and Central Agent are working. I
 only can't get the Api Server working.


 On Fri, Apr 26, 2013 at 6:19 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:

 It sounds like you haven't completed the installation instructions. I
 don't know if the manual steps listed at
 http://docs.openstack.org/developer/ceilometer/install/manual.html work
 with the tarball, but they should be close.

 Doug


 On Fri, Apr 26, 2013 at 3:46 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 The command line I am using is: sudo /usr/local/bin/ceilometer-api.

 However, the ceilometer.ini file is missing. The version of Ceilometer
 I am using is ceilometer-2013.1~g2.tar.gz. And, I only have the
 following configuration files:

 /etc/ceilometer/ceilometer.conf
 /etc/ceilometer/policy.json
 /etc/ceilometer/sources.json

 Thanks.


 On Fri, Apr 26, 2013 at 1:10 AM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I
 have installed the driver Mongo using sudo pip install pymongo.


 Ceilometer does use a database. You have to install the right driver.
 If you want

Re: [Openstack] [ceilometer] support for older versions of ceilometer

2013-05-30 Thread Tim Bell
 

The difficulties of upgrading OpenStack while running production services was 
one of the major feedbacks from the user survey at
Portland. Core components are including N/N+1 upgrades into their plans for 
Havana so big bang (and high risk of extended downtime)
upgrades are no longer the default processes.

 

As a component matures through incubation to core, we also need to have these 
operational requirements covered. Upgrading 100s of
hypervisors and their controllers require staged upgrades.

 

I hope that ceilometer can also include this within the Havana timeframe as it 
becomes a key component of production, large scale
clouds.

 

Tim

 

From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com] 
Sent: 30 May 2013 22:35
To: Tim Bell
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [ceilometer] support for older versions of ceilometer

 

From what I understand, it is unusual to support mixing components from 
different releases like that. Am I wrong?

 

Doug

 

On Thu, May 30, 2013 at 3:29 PM, Tim Bell tim.b...@cern.ch 
mailto:tim.b...@cern.ch  wrote:

 

Doug,

 

Can you advise on what the plan/policy will be for Havana ?

 

-  Will I be able to run Havana core components such as Nova with 
Grizzly ceilometer ?

-  Will I be able to run Havana ceilometer with Grizzly core components 
(with reduced functionality compared to the Havana
core components) ?

 

Tim

 

From: Openstack [mailto:openstack-bounces+tim.bell 
mailto:openstack-bounces%2Btim.bell =cern...@lists.launchpad.net
mailto:cern...@lists.launchpad.net ] On Behalf Of Doug Hellmann
Sent: 30 May 2013 18:59
To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net 
Subject: [Openstack] [ceilometer] support for older versions of ceilometer

 

The ceilometer team has had a few requests for help with older versions of 
ceilometer or running the grizzly version of ceilometer
with older versions of other OpenStack components lately. We appreciate the 
level of interest in the project but, as much as we
would like to, unfortunately we are not always able to help everyone with these 
mixed configurations. During the early phases of
our development we tried to maintain compatibility with folsom, even well into 
the grizzly development cycle. We are no longer doing
that, however, and so to make clear what support we can offer, the ceilometer 
team has put together the statement below. It has been
added to our documentation, and we are posting here to make sure everyone has a 
chance to see it.

 

Regards,

Doug

 

 

The ceilometer team has limited capacity to provide support for older versions 
of the project. Because the project graduated from
incubation around the time of the grizzly release, that is the first version 
for which we will provide regular ongoing support
following the standard deprecation cycle for OpenStack [1]. The grizzly version 
of ceilometer  cannot be installed on the same
server with earlier versions of OpenStack because of conflicting package 
requirements, but is API compatible with the folsom release
if installed separately.

 

[1] https://wiki.openstack.org/wiki/StableBranch

 

 



smime.p7s
Description: S/MIME cryptographic signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-08 Thread Doug Hellmann
+1

It will be good to see if the storage API design works for other backends
like HBase.

Doug

On Thu, Nov 8, 2012 at 5:50 AM, shengjie_...@dell.com wrote:

 Thanks Julien, I will write up a blueprint soon.

 Shengjie

 -Original Message-
 From: Julien Danjou [mailto:jul...@danjou.info]
 Sent: 07 November 2012 18:12
 To: Min, Shengjie
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer
 - blueprint?

 On Wed, Nov 07 2012, shengjie_...@dell.com wrote:

 Hi Shengjie,

  I am looking for a way to propose a blueprint to the ceilometer team -
  Adding Hbase storage backend for ceilometer. Currently we have only
  MongoDB and SQLalchemy as the possible ceilometer storage backend.
  Given the storage interface is clearly designed and allows us to have
  different backend, it would be nice to have more options which make
  Ceilometer more adoptive to some providers' existing architectures. As
  a cloud IAAS provider, Ceilometer might not be just considered as a
  usage db, also it's being seen as a centralized place to store all the
  usage data cross platforms. Additionally, all the historical usage
  data stored can be used for historical usage analysis as well, this is
  where MapReduce comes into play. With Hadoop Hbase, it allows usage
  data to be stored in HDFS, also it gives us the ability to run large
  scale massive MapRed analysis jobs in the future.

 This is indeed a good idea, and as you pointed out, Ceilometer collector
 has been designed so this is being possible.

 I think you can create a blueprint here:

   https://blueprints.launchpad.net/ceilometer

 And write in what should be done.

 --
 Julien Danjou
 ;; Free Software hacker  freelance
 ;; http://julien.danjou.info

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [HyperV][Ceilometer] Performance statistics from Hyper-V with Ceilometer and libvirt

2013-06-11 Thread Peter Cheung
I would love to test the ceilometer on KVM


From: apilo...@cloudbasesolutions.com
To: brunnop.olive...@gmail.com
Date: Tue, 11 Jun 2013 17:28:27 +
CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] [HyperV][Ceilometer] Performance statistics from 
Hyper-V with Ceilometer and libvirt












Hi Bruno, 





We just started implementing the Ceilometer Hyper-V inspector for the compute 
agent (see hyper-v-agent blueprint).

Let me know if you'd like to help in testing it. :-)





Thanks,





Alessandro










On Jun 6, 2013, at 00:40 , Bruno Oliveira brunnop.olive...@gmail.com wrote:

Dear Stackers,



Please I'd like to ask your expertise on ceilometer to try

an approach for monitoring a compute nova running hyper-v



I got a running environment of devstack with KVM on a single-node

machine being fully monitored by ceilometer. I'm being able to

access its API to see the data collected as well.



On the other hand, I'm using Cloudbase's (cloudbase.it) Openstack Compute

Hyper-V Installer (driver), which greatly help me deploying VMs from

the devstack

node to the hyper-v server. All is working smoothly.



So far, in the irc channel #openstack-ceilometer, I got to know that

ceilometer, just like collectd, uses libvirt to query the hypervisors

for data (thanks dhellmann !). BUT if check in the libvirt.org site,

it's being said

that there's support for Hyper-V: http://libvirt.org/drvhyperv.html

(given a uri to connect to it).



1. So I'm wondering if all I need to get Ceilometer working for windows

would be compiling it under my windows envionment with mingw chaintool,

for example?



2. Has anyone ever tried this or got any other way to make it data collection

from hyper-v successful ?



3. Do you guys have any other approach that you would suggest (installing

snmp on each of the cloud servers/instances is not an option) ?



Please, share your thoughts. I'd greatly appreciate it.



Thank you very very much.



--



Bruno Oliveira

Developer, Software Engineer



___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp








___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp   
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer][Ceilometer-API] Ceilometer-API Error 401 Unauthorized

2013-05-29 Thread Bruno Oliveira
Oh... Got it, Angus. Thank you!

I finally got it that for when using curl, I have first to get an AUTH
token
from keystone, in order to use that returned token in the HTTP GET for
the API.

Just sharing what I did:

$ curl -d '{auth:{passwordCredentials:{username: ceilometer,
password: SECRET}}}' -H Content-type: application/json
http://localhost:35357/v2.0/tokens


Returns:

{access: {token: {issued_at: 2013-05-29T15:17:07.501333, expires:
2013-05-30T15:17:07Z, id:
MIICbgYJKoZIhvcNAQcCoIICXzCCAlsCAQExCTAHBgUrDgMCGjCCAUcGCSqGSIb3DQEHAaCCATgEggE0eyJhY2Nlc3MiOiB7InRva2VuIjogeyJpc3N1ZWRfYXQiOiAiMjAxMy0wNS0yOVQxNToxNzowNy41MDEzMzMiLCAiZXhwaXJlcyI6ICIyMDEzLTA1LTMwVDE1OjE3OjA3WiIsICJpZCI6ICJwbGFjZWhvbGRlciJ9LCAic2VydmljZUNhdGFsb2ciOiBbXSwgInVzZXIiOiB7InVzZXJuYW1lIjogImFkbWluIiwgInJvbGVzX2xpbmtzIjogW10sICJpZCI6ICJkOTIwZmM4NWVjZDk0MjZlYmQ5ZTNmOGM3MzAwZjVkNCIsICJyb2xlcyI6IFtdLCAibmFtZSI6ICJhZG1pbiJ9LCAibWV0YWRhdGEiOiB7ImlzX2FkbWluIjogMCwgInJvbGVzIjogW119fX0xgf8wgfwCAQEwXDBXMQswCQYDVQQGEwJVUzEOMAwGA1UECBMFVW5zZXQxDjAMBgNVBAcTBVVuc2V0MQ4wDAYDVQQKEwVVbnNldDEYMBYGA1UEAxMPd3d3LmV4YW1wbGUuY29tAgEBMAcGBSsOAwIaMA0GCSqGSIb3DQEBAQUABIGAiiB9a3o5N2piewbmZU3Ng9ShhPHB4WiigGUocdrNeE24+RktDoRrM+uZKptjd6aanlAGbrAUKpi5Uj-oNAbmKUt1CK-154aUaUpcy8NJFNwIZA2hBafbofOWU6FceVDIc1yztr0bZRdSD-vDl0hrISi0mL961yU+uXFQRxeNtqY=},
serviceCatalog: [], user: {username: admin, roles_links: [],
id: d920fc85ecd9426ebd9e3f8c7300f5d4, roles: [], name: admin},
metadata: {is_admin: 0, roles: []}}}


Where the token is the value of the id therefore, a GET to get all the
meters, can be:


$ curl -k -D -H X-Auth-Token: MIICbgYJKoZIhvcNAQcCoIICXzCCAl
sCAQExCTAHBgUrDgMCGjCCAUcGCSqGSIb3DQEHAaCCATgEggE0eyJhY2Nlc3
MiOiB7InRva2VuIjogeyJpc3N1ZWRfYXQiOiAiMjAxMy0wNS0yOVQxNToxNz
owNy41MDEzMzMiLCAiZXhwaXJlcyI6ICIyMDEzLTA1LTMwVDE1OjE3OjA3Wi
IsICJpZCI6ICJwbGFjZWhvbGRlciJ9LCAic2VydmljZUNhdGFsb2ciOiBbXS
wgInVzZXIiOiB7InVzZXJuYW1lIjogImFkbWluIiwgInJvbGVzX2xpbmtzIj
ogW10sICJpZCI6ICJkOTIwZmM4NWVjZDk0MjZlYmQ5ZTNmOGM3MzAwZjVkNC
IsICJyb2xlcyI6IFtdLCAibmFtZSI6ICJhZG1pbiJ9LCAibWV0YWRhdGEiOi
B7ImlzX2FkbWluIjogMCwgInJvbGVzIjogW119fX0xgf8wgfwCAQEwXDBXMQ
swCQYDVQQGEwJVUzEOMAwGA1UECBMFVW5zZXQxDjAMBgNVBAcTBVVuc2V0MQ
4wDAYDVQQKEwVVbnNldDEYMBYGA1UEAxMPd3d3LmV4YW1wbGUuY29tAgEBMA
cGBSsOAwIaMA0GCSqGSIb3DQEBAQUABIGAiiB9a3o5N2piewbmZU3Ng9ShhP
HB4WiigGUocdrNeE24+RktDoRrM+uZKptjd6aanlAGbrAUKpi5Uj-oNAbmKUt1CK-
154aUaUpcy8NJFNwIZA2hBafbofOWU6FceVDIc1yztr0bZRdSD-
vDl0hrISi0mL961yU+uXFQRxeNtqY=  -X 'GET' -v http://localhost:8777/v2/meters


Which, indeed returned the metrics I was looking for.
Thank you a lot. I really appreciate it.

I tried using ceilometer-client (I just git cloned it, and ran sudo python
setup.py install,
nothing went wrong apparently), but when trying to run it like this:


$ ceilometer --os-username ceilometer --os-password ficrowstran02
--os-tenant-name admin --os-auth-url http://localhost:5000/v2.0 statistics

Returns:  invalid literal for int() with base 10: ''


Maybe because my AUTH Token is exceeds the 32/64-bit addressing of a
integer? Not sure... I'll figure it out and do the follow-up here.


Thank you for the great help!




On Mon, May 27, 2013 at 10:21 PM, Angus Salkeld asalk...@redhat.com wrote:

 On 27/05/13 11:14 -0300, Bruno Oliveira wrote:

 Hello stackers,

 I'm having a really hard time setting up ceilometer-api so I thought
 if I could ask you guys for some enlightment.

 I can clearly see data being pulled in the screens that are running
 /ceilometer-collector, ./ceilometer-agent-compute
 ,./ceilometer-agent-central

 Even the screen running ceilometer-api-server starts with no problem.

 But I cannot reach the api at all via curl. Neither by using its
 actual port (8777)
 nor using the port set in the virtual host of apache. All I'm getting
 is auth error

 $ curl http://127.0.0.1:8777  OR  $ curl http://127.0.0.1:9090
 ==**===
 html
 head
  title401 Unauthorized/title
 /head
 body
  h1401 Unauthorized/h1
  This server could not verify that you are authorized to access the
 document you requested. Either you supplied the wrong credentials
 (e.g., bad password), or your browser does not understand how to
 supply the credentials required.br /br /
 Authentication required
 ==**===


 Right, Authentication is required by the client, but you are not
 passing it any credentials.

 I'd suggest using python-ceilometerclient to do the auth for you:
 So use it like any other openstack client.

 try something like this:

 asalkeld@elf python-ceilometerclient (master)$ . ../devstack/openrc admin
 admin
 asalkeld@elf python-ceilometerclient (master)$ ceilometer resource-list
 +-**-++-+-**
 --**---+
 | Resource ID  | Source | User ID | Project ID
   |
 +-**-++-+-**
 --**---+
 | a8ce423c-c1a1

Re: [Openstack] Ceilometer Install

2013-04-29 Thread Riki Arslan
I thought it might help if mentioned little more:

/etc/ceilometer.conf file has the following parameters added:

os_username=ceilometer
os_password=$PASSWORD
os_tenant_name=service
os_auth_url=http://localhost:5000/v2.0/

I checked CLI_OPTIONS in service.py and it looks allright:

CLI_OPTIONS = [
cfg.StrOpt('os-username',
   default=os.environ.get('OS_USERNAME', 'ceilometer'),
   help='Username to use for openstack service access'),
cfg.StrOpt('os-password',
   default=os.environ.get('OS_PASSWORD', 'admin'),
   help='Password to use for openstack service access'),
cfg.StrOpt('os-tenant-id',
   default=os.environ.get('OS_TENANT_ID', ''),
   help='Tenant ID to use for openstack service access'),
cfg.StrOpt('os-tenant-name',
   default=os.environ.get('OS_TENANT_NAME', 'admin'),
   help='Tenant name to use for openstack service access'),
cfg.StrOpt('os-auth-url',
   default=os.environ.get('OS_AUTH_URL',
  'http://localhost:5000/v2.0'),
   help='Auth URL to use for openstack service access'),
]

But still, according to the error I am getting, it can not parse
_parse_cli_opts:

Traceback (most recent call last):
  File /usr/local/bin/ceilometer-api, line 5, in module
pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
  File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
run_script
self.require(requires)[0].run_script(script_name, ns)
  File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
run_script
execfile(script_filename, namespace, namespace)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
line 38, in module
service.prepare_service()
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
line 80, in prepare_service
cfg.CONF(argv[1:], project='ceilometer')
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
line 1024, in __call__
self._cli_values, leftovers = self._parse_cli_opts(args)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
line 1527, in _parse_cli_opts
opt._add_to_cli(self._oparser, group)
  File
/usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
line 591, in _add_to_cli
container = self._get_argparse_container(parser, group)
  File
/usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
line 633, in _get_argparse_container
return group._get_argparse_group(parser)
AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'

I am really puzzled as Collector, Computer Agent and Central Agent are
working fine and Api Server is not.


On Tue, Apr 30, 2013 at 12:56 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I have followed the document. The only thing that is different from the
 docs is that I did not copy the yaml file (it does not exist in tarball):

 cp etc/ceilometer/*.yaml /etc/ceilometer

 However, the tarball is the g2 version, which is the last version that was
 supposed to work with Folsom.

 It seems like Collector, Computer Agent and Central Agent are working. I
 only can't get the Api Server working.


 On Fri, Apr 26, 2013 at 6:19 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:

 It sounds like you haven't completed the installation instructions. I
 don't know if the manual steps listed at
 http://docs.openstack.org/developer/ceilometer/install/manual.html work
 with the tarball, but they should be close.

 Doug


 On Fri, Apr 26, 2013 at 3:46 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 The command line I am using is: sudo /usr/local/bin/ceilometer-api.

 However, the ceilometer.ini file is missing. The version of Ceilometer I
 am using is ceilometer-2013.1~g2.tar.gz. And, I only have the
 following configuration files:

 /etc/ceilometer/ceilometer.conf
 /etc/ceilometer/policy.json
 /etc/ceilometer/sources.json

 Thanks.


 On Fri, Apr 26, 2013 at 1:10 AM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan riki.ars...@cloudturk.net
  wrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I
 have installed the driver Mongo using sudo pip install pymongo.


 Ceilometer does use a database. You have to install the right driver.
 If you want Mongo, then it sounds like you've done the right thing. It's
 possible mako is also being used somewhere else, I'm not sure.



 Regarding the current problem; the traceback is as follows:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line

[Openstack] [metering] ceilometer dev docs on readthedocs.org

2012-07-03 Thread Doug Hellmann
I've set up the ceilometer development documentation build on RTD at
http://ceilometer.readthedocs.org/en/latest/index.html

Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Ceilometer] Project Technical Leader election result

2012-08-03 Thread Julien Danjou
Hi,

The PTL election for Ceilometer¹ is over.

The winner is Nick Barcet.

Congratulations !


The results are available here:

http://www.opavote.org/vote/491028

¹  http://wiki.openstack.org/EfficientMetering/PTLElectionProcess

Cheers,
-- 
Julien Danjou
// Free Software hacker  freelance
// http://julien.danjou.info


pgpWkJFf1lvVk.pgp
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer] Project Technical Leader election result

2012-08-03 Thread Chmouel Boudjnah
On Fri, Aug 3, 2012 at 10:22 AM, Julien Danjou jul...@danjou.info wrote:
 The PTL election for Ceilometer¹ is over.
 The winner is Nick Barcet.

congratulation Nick, well deserved.

Chmouel.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [metering][ceilometer] Unified Instrumentation, Metering, Monitoring ...

2012-11-01 Thread Sandy Walsh
Hey!

Here's a first pass at a proposal for unifying StackTach/Ceilometer and other 
instrumentation/metering/monitoring efforts. 

It's v1, so bend, spindle, mutilate as needed ... but send feedback!

http://wiki.openstack.org/UnifiedInstrumentationMetering

Thanks,
Sandy

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer] Ganglia Ceilometer integration

2013-01-08 Thread Shengjie_Min
Hi Julien,

Just look at the blueprints and your post, seems like there is some effort 
around synaps, also something around heat, cloudwatch. Just trying to get a 
clear picture about the vision and direction around monitoring area. 

Shengjie

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] ceilometer-agent-central starting fail

2013-04-12 Thread Doug Hellmann
On Thu, Apr 11, 2013 at 11:34 PM, Liu Wenmao marvel...@gmail.com wrote:

 Thanks, the ceilometer seems to lack some default options in configuration
 files and the official guidance. (
 http://docs.openstack.org/developer/ceilometer/configuration.html)


I have opened a bug to address the missing details in the configuration
documentation. https://bugs.launchpad.net/ceilometer/+bug/1168375

Doug



 So maybe it is not ready for users yet?


 On Wed, Apr 10, 2013 at 8:28 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 10, 2013 at 6:10 AM, Liu Wenmao marvel...@gmail.com wrote:

 Actually this is not over.

 The main reason of service failure is that central/manager.py
 and service.py use different vairables:

 central/manager.py
  70 def interval_task(self, task):
  71 self.keystone = ksclient.Client(
  72 username=cfg.CONF.*os_username*,
  73 password=cfg.CONF.os_password,
  74 tenant_id=cfg.CONF.os_tenant_id,
  75 tenant_name=cfg.CONF.os_tenant_name,
  76 auth_url=cfg.CONF.os_auth_url)

 44 CLI_OPTIONS = [
  45 cfg.StrOpt('*os-username*',
  46default=os.environ.get('OS_USERNAME', 'ceilometer'),
  47help='Username to use for openstack service access'),
  48 cfg.StrOpt('os-password',
  49default=os.environ.get('OS_PASSWORD', 'admin'),
  50help='Password to use for openstack service access'),
  51 cfg.StrOpt('os-tenant-id',
  52default=os.environ.get('OS_TENANT_ID', ''),
  53help='Tenant ID to use for openstack service access'),
  54 cfg.StrOpt('os-tenant-name',
  55default=os.environ.get('OS_TENANT_NAME', 'admin'),
  56help='Tenant name to use for openstack service
 access'),
  57 cfg.StrOpt('os_auth_url',
  58default=os.environ.get('OS_AUTH_URL',
  59   'http://localhost:5000/v2.0'),

 So after I change all - to _ and modify all options in
 /etc/ceilometer/ceilometer.conf, the service starts OK.


 The thing that fixed it was changing - to _ in your configuration
 file. The options library allows option names to have - in them so they
 look nice as command line switches, but the option name uses the _.

 Doug





 On Wed, Apr 10, 2013 at 2:02 PM, Liu Wenmao marvel...@gmail.com wrote:

 I solve this problem by two steps:

 1 modify /etc/init/ceilometer-agent-central.conf
 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central --
 --config-file=/etc/ceilometer/ceilometer.conf
 2 add some lines to /etc/ceilometer/ceilometer.conf:
 os-username=ceilometer
 os-password=nsfocus
 os-tenant-name=service
 os-auth-url=http://controller:5000/v2.0



 On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao marvel...@gmail.comwrote:

 Hi all:

 I have just install ceilometer grizzly github version, but fail to
 start ceilometer-agent-central service. I think it is due to that I didn't
 set up the keystone user/password like other projects. but I follow the
 instructions(
 http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
 but it does not include the ceilometer configuration.

 # service ceilometer-agent-central start
 ceilometer-agent-central start/running, process 5679

 # cat /etc/init/ceilometer-agent-central.conf
 description ceilometer-agent-compute
 author Chuck Short zul...@ubuntu.com

 start on runlevel [2345]
 stop on runlelvel [!2345]

 chdir /var/run

 pre-start script
 mkdir -p /var/run/ceilometer
 chown ceilometer:ceilometer /var/run/ceilometer

 mkdir -p /var/lock/ceilometer
 chown ceilometer:ceilometer /var/lock/ceilometer
 end script

 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central


 /var/log/ceilometer/ceilometer-agent-central.log
 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall]
 in looping call
 Traceback (most recent call last):
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py,
 line 67, in _inner
 self.f(*self.args, **self.kw)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py,
 line 76, in interval_task
 auth_url=cfg.CONF.os_auth_url)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 134, in __init__
 self.authenticate()
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 205, in authenticate
 token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 174, in get_raw_token_from_identity_servicetoken=token)
   File
 /usr/local/lib/python2.7/dist-packages

Re: [Openstack] ceilometer and heat tutorial

2013-04-30 Thread Pádraig Brady
On 04/28/2013 07:35 PM, Michaël Van de Borne wrote:
 Le 26/04/2013 20:28, Steven Hardy a écrit :
 On Fri, Apr 26, 2013 at 05:02:54PM +0200, Michaël Van de Borne wrote:
 Hi all,

 I'm looking for install and usage tutorials for ceilometer and heat.
 The best I could find so far are these:
 - ceilometer: http://docs.openstack.org/developer/ceilometer/install.html
 - heat: 
 https://wiki.openstack.org/wiki/Heat/GettingStartedUsingMasterOnUbuntu

 Unfortunately, they seem to be intended for developers. Still have
 to git clone the softwares.

 I'm looking for tutorials like this one:
 http://docs.openstack.org/trunk/basic-install/content/
 (using apt-get, telling how to configure everything on every node,
 and finishing with a simple use case to validate the installation).

 Does anyone have something like this?
 For Heat, the we don't yet have this sort of package-orientated
 documentation, for Ubuntu this is because heat is not yet packaged for
 Ubuntu, it is now in Debian Experimental though:

 https://launchpad.net/debian/experimental/+source/heat/2013.1-1

 Heat is packaged for Fedora, there are some instructions here:

 http://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack

 thank you steve. Would you please keep posted as soon as a tutorial is 
 available. I'm looking forward to test Heat.

 Anybody has a good tutorial about ceilometer?

Note there was a newer Grizzly test day for Fedora which included
Ceilometer notes as well as the previously mentioned heat notes:

https://fedoraproject.org/wiki/Test_Day:2013-04-02_OpenStack#Heat_basic_functionality
https://fedoraproject.org/wiki/Test_Day:2013-04-02_OpenStack#Ceilometer_functionality

Note also that both heat and ceilometer are packaged for RHEL and derivatives,
which you can try quickly in a VM or on baremetal by following the simple 
process at
http://openstack.redhat.com/Quickstart and then following the Ceilometer 
instructions
at the URL above.

thanks,
Pádraig.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Metrics from Ceilometer

2013-05-16 Thread Rima Grati
Hello,

Please i need to know which kind of metric Ceilometer can extract (it can
extract the bandwith, the uptime of a system.)

Thank you
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] support for older versions of ceilometer

2013-05-30 Thread Doug Hellmann
The ceilometer team has had a few requests for help with older versions of
ceilometer or running the grizzly version of ceilometer with older versions
of other OpenStack components lately. We appreciate the level of interest
in the project but, as much as we would like to, unfortunately we are not
always able to help everyone with these mixed configurations. During the
early phases of our development we tried to maintain compatibility with
folsom, even well into the grizzly development cycle. We are no longer
doing that, however, and so to make clear what support we can offer, the
ceilometer team has put together the statement below. It has been added to
our documentation, and we are posting here to make sure everyone has a
chance to see it.

Regards,
Doug


The ceilometer team has limited capacity to provide support for older
versions of the project. Because the project graduated from incubation
around the time of the grizzly release, that is the first version for which
we will provide regular ongoing support following the standard deprecation
cycle for OpenStack [1]. The grizzly version of ceilometer  cannot be
installed on the same server with earlier versions of OpenStack because of
conflicting package requirements, but is API compatible with the folsom
release if installed separately.

[1] https://wiki.openstack.org/wiki/StableBranch
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] support for older versions of ceilometer

2013-05-31 Thread Doug Hellmann
On Fri, May 31, 2013 at 4:11 AM, Julien Danjou jul...@danjou.info wrote:

 On Thu, May 30 2013, Tim Bell wrote:

  I hope that ceilometer can also include this within the Havana timeframe
 as
  it becomes a key component of production, large scale
  clouds.

 I think we all agree in principle. We'd be happy to enhance Ceilometer
 and fix potential bugs in this direction, but we'll require some help
 testing the upgrade path *before* Havana is released.


Right, and upgrades are a different issue than running production systems
long-term on mixed versions.

Most of the problems between grizzly or trunk ceilometer and folsom have
had to do with proof-of-concept deployments where people were trying to
install a modern ceilometer on the same server as another component that
was older. Because the services require incompatible libraries and were
running on the same host using the same site-packages directories, there
are conflicts and things broke (either ceilometer, or the other service).
Deploying into virtualenvs or using separate hosts will reduce (if not
eliminate) these problems. The protocol ceilometer uses to talk over the
message bus is compatible between versions, AFAIK, so should not have
issues with rolling upgrades.

Doug



 --
 Julien Danjou
 # Free Software hacker # freelance consultant
 # http://julien.danjou.info

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [HyperV][Ceilometer] Performance statistics from Hyper-V with Ceilometer and libvirt

2013-06-05 Thread Bruno Oliveira
ERRATA:

irc-channel is #openstack-metering,
not #openstack-ceilometer
--

Bruno Oliveira
Developer, Software Engineer
+55 11 9-6193-3987
skype: brunnop.oliveira
brunnop.olive...@gmail.com





On Wed, Jun 5, 2013 at 6:40 PM, Bruno Oliveira
brunnop.olive...@gmail.com wrote:
 Dear Stackers,

 Please I'd like to ask your expertise on ceilometer to try
 an approach for monitoring a compute nova running hyper-v

 I got a running environment of devstack with KVM on a single-node
  machine being fully monitored by ceilometer. I'm being able to
 access its API to see the data collected as well.

 On the other hand, I'm using Cloudbase's (cloudbase.it) Openstack Compute
 Hyper-V Installer (driver), which greatly help me deploying VMs from
 the devstack
 node to the hyper-v server. All is working smoothly.

 So far, in the irc channel #openstack-ceilometer, I got to know that
 ceilometer, just like collectd, uses libvirt to query the hypervisors
 for data (thanks dhellmann !). BUT if check in the libvirt.org site,
 it's being said
 that there's support for Hyper-V: http://libvirt.org/drvhyperv.html
  (given a uri to connect to it).

 1. So I'm wondering if all I need to get Ceilometer working for windows
 would be compiling it under my windows envionment with mingw chaintool,
 for example?

 2. Has anyone ever tried this or got any other way to make it data collection
 from hyper-v successful ?

 3. Do you guys have any other approach that you would suggest (installing
 snmp on each of the cloud servers/instances is not an option) ?

 Please, share your thoughts. I'd greatly appreciate it.

 Thank you very very much.

 --

 Bruno Oliveira
 Developer, Software Engineer

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [HyperV][Ceilometer] Performance statistics from Hyper-V with Ceilometer and libvirt

2013-06-06 Thread Peter Pouliot
The hyper-v driver uses WMI.
Libvirt is not used.   There is currently no support for celometer, however we 
should have havana blueprints meaning it is one of the things we are trying to 
deliver.

P


Sent from my Verizon Wireless 4G LTE Smartphone



 Original message 
From: Julien Danjou jul...@danjou.info
Date: 06/06/2013 7:56 AM (GMT-05:00)
To: Bruno Oliveira brunnop.olive...@gmail.com
Cc: OpenStack openstack@lists.launchpad.net
Subject: Re: [Openstack] [HyperV][Ceilometer] Performance statistics from 
Hyper-V with Ceilometer and libvirt


On Wed, Jun 05 2013, Bruno Oliveira wrote:

 So far, in the irc channel #openstack-ceilometer, I got to know that
 ceilometer, just like collectd, uses libvirt to query the hypervisors
 for data (thanks dhellmann !). BUT if check in the libvirt.org site,
 it's being said
 that there's support for Hyper-V: http://libvirt.org/drvhyperv.html
  (given a uri to connect to it).

First question is, is Hyper-V driver for Nova used via libvirt?
If yes, then libvirt should be patched to provide information to
Ceilometer.
If not, then Ceilometer should be patched to learn how to poll Hyper-V.

--
Julien Danjou
# Free Software hacker # freelance consultant
# http://julien.danjou.info
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Availability of metrics from SWIFT - Object Storage

2013-06-26 Thread Narayanan, Krishnaprasad
Hallo All,

Based on the documentation from Ceilometer, I see the metrics from all the 
components except SWIFT. Can I get to know whether Ceilometer offers any 
metrics from the SWIFT component?

Thanks
Krishnaprasad
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer][Healthnmon] Monitoring Alarm in openstack

2013-07-02 Thread Angus Salkeld

On 02/07/13 11:29 +0200, Emanuel Marzini wrote:

Thank you!
It's true that in Havana disappear Healthnmon that will be merge with
Ceilometer?


Not that I am aware of, Ceilometer is just getting Alarming
functionality.

-Angus



2013/7/2 Angus Salkeld asalk...@redhat.com


On 01/07/13 13:42 +0200, Emanuel Marzini wrote:


Hi,
I want to retrive Vm information from Openstack. I am interested of CPU 
RAM utilization.
I known that someone use collectd, libvirt ecc.. or product like
Ceilometer
or Healthnmon.
I am also interested to receive alarm information from the cloud provider
if the CPU or RAM value exceeds a threshold.
I read that from Havana, Ceilometer and Healthnmon will be merged, it's
true? Might be a good solution to my problems?



Ceilometer is getting alarms this cycle. Heat will start using
them for autoscaling (cpu/mem stats).

https://blueprints.launchpad.**net/ceilometer/+spec/alarminghttps://blueprints.launchpad.net/ceilometer/+spec/alarming

Regards
Angus



Thanks in advance
Emanuel



 __**_

Mailing list: 
https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : 
https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
More help   : 
https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp




__**_
Mailing list: 
https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : 
https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
More help   : 
https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer Install

2013-05-06 Thread Riki Arslan
I have also installed ceilometer-2013.1~g2~20130107.449.tar.gz from the
tarballs list and still getting the same error:

Traceback (most recent call last):
  File /usr/local/bin/ceilometer-api, line 5, in module
pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
  File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
run_script
self.require(requires)[0].run_script(script_name, ns)
  File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
run_script
execfile(script_filename, namespace, namespace)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
line 37, in module
cfg.CONF(sys.argv[1:])
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
line 1024, in __call__
self._cli_values, leftovers = self._parse_cli_opts(args)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
line 1527, in _parse_cli_opts
opt._add_to_cli(self._oparser, group)
  File
/usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
line 591, in _add_to_cli
container = self._get_argparse_container(parser, group)
  File
/usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
line 633, in _get_argparse_container
return group._get_argparse_group(parser)
AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


On Mon, May 6, 2013 at 3:56 PM, Riki Arslan riki.ars...@cloudturk.netwrote:

 Hi Doug,

 I actually got it from a link on your website:


 http://doughellmann.com/2013/01/ceilometer-grizzly-2-milestone-available.html

 So, do you think this one is not good?


 On Thu, May 2, 2013 at 7:33 PM, Doug Hellmann doug.hellm...@dreamhost.com
  wrote:




 On Mon, Apr 29, 2013 at 6:42 PM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 I thought it might help if mentioned little more:

 /etc/ceilometer.conf file has the following parameters added:

 os_username=ceilometer
 os_password=$PASSWORD
 os_tenant_name=service
 os_auth_url=http://localhost:5000/v2.0/

 I checked CLI_OPTIONS in service.py and it looks allright:

 CLI_OPTIONS = [
 cfg.StrOpt('os-username',
default=os.environ.get('OS_USERNAME', 'ceilometer'),
help='Username to use for openstack service access'),
 cfg.StrOpt('os-password',
default=os.environ.get('OS_PASSWORD', 'admin'),
help='Password to use for openstack service access'),
 cfg.StrOpt('os-tenant-id',
default=os.environ.get('OS_TENANT_ID', ''),
help='Tenant ID to use for openstack service access'),
 cfg.StrOpt('os-tenant-name',
default=os.environ.get('OS_TENANT_NAME', 'admin'),
help='Tenant name to use for openstack service access'),
 cfg.StrOpt('os-auth-url',
default=os.environ.get('OS_AUTH_URL',
   'http://localhost:5000/v2.0'),
help='Auth URL to use for openstack service access'),
 ]

 But still, according to the error I am getting, it can not parse
 _parse_cli_opts:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235,
 in run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'

 I am really puzzled as Collector, Computer Agent and Central Agent are
 working fine and Api Server is not.


 I don't see a 2013.1~g2.tar.gz tarball listed under
 http

[Openstack] Clarification on Ceilometer Implementation

2012-06-06 Thread Kobagana Kumar
Hi all,

I am trying to implement Agent module in Ceilometer. Regarding that I
have few doubts:

How Ceilometer capturing the usage details?

As we are already know nova simple usage module captures the usage
details of nova. It works at API level. But here in ceilometer we are
trying to implement Agent module at compute level. For that how can we
capture the usage details?


What is the format of Plug- In?

We can implement plug-in in various ways. We can use dictionary format,
JSON format, etc. In which format Ceilometer implementing the plug - in
and what are the attributes in that.


Thanks  Regards,
Bharath Kumar

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Metering] Meeting agenda for Thursday at 16:00 UTC (June 21st, 2012)

2012-06-21 Thread Nick Barcet
On 06/20/2012 08:55 PM, Nick Barcet wrote:
 Hi,
 
 The metering project team holds a weekly meeting in #openstack-meeting,
 Thursdays at 1600 UTC. Everyone is welcome.
 
 http://wiki.openstack.org/Meetings/MeteringAgenda
 
 Topics for this week:
 
 * Review last week's actions
   - nijaba: to point to the calculator in the blueprint
   - dhellmann: start mapping API queries to database engine methods
   - dhellmann: look at existing plugins and pick one of each for
 examples in docs
   - dhellmann: email info on examples to nijaba
   - nijaba: to prime the doc once info received from dhellmann
   - nijaba: to prepare incubation application for review at the next meeting
   - dachary: talk to Dragon about SystemData / ceilometer and try to
 create cooperation
   - dhellmann: to talk to Quantum devs about integration with ceilometer
   - dachary: to talk to swift devs about integration with ceilometer
   - nijaba: to talk to cinder devs about integration with ceilometer
   - dachary: talk to Dragon about SystemData / ceilometer and try to
 create cooperation (i.e. nova)
   - jd_: to talk to glance devs about integration with ceilometer
 
 * Status of the essex compatibility effort that jd is leading
 
 Feel free to add other points you would like to discuss to the wiki page.

The meeting took place and here is a summary:

==
#openstack-meeting: Ceilometer
==

Meeting summary
---

* LINK: http://wiki.openstack.org/Meetings/MeteringAgenda  (nijaba,
  16:00:03)
* dachary will unfortunately not be able to join us this week for work
  related reasons, he asked me to present his excuses.  (nijaba,
  16:00:23)
* actions from previous meetings  (nijaba, 16:01:04)

* nijaba: to point to the calculator in the blueprint  (nijaba,
  16:01:17)
  * LINK: http://wiki.openstack.org/EfficientMetering#Volume_of_data
(nijaba, 16:01:17)

* dhellmann: start mapping API queries to database engine methods
  (nijaba, 16:01:46)

* dhellmann: look at existing plugins and pick one of each for examples
  in docs and email info on examples to nijaba  (nijaba, 16:04:14)

* nijaba: to prime the doc once info received from dhellmann  (nijaba,
  16:09:09)
  * ACTION: nijaba: to prime the doc on plugins  (nijaba, 16:09:09)

* nijaba: to prepare incubation application for review at the next
  meeting  (nijaba, 16:10:27)
  * LINK:
http://wiki.openstack.org/Projects/IncubatorApplicationCeilometer
(nijaba, 16:10:27)
  * ACTION: during next week meeting we will vote on the Incubation
application  (nijaba, 16:12:44)

* dachary: talk to Dragon about SystemData / ceilometer and try to
  create cooperation  (nijaba, 16:13:08)
  * ACTION: dachary: talk to Dragon about SystemData / ceilometer and
try to create cooperation  (nijaba, 16:13:22)

* dhellmann: to talk to Quantum devs about integration with ceilometer
  (nijaba, 16:13:32)
  * ACTION: dhellmann: talk to Quantum devs about integration with
ceilometer  (dhellmann, 16:14:13)

* dachary: to talk to swift devs about integration with ceilometer
  (nijaba, 16:14:29)
  * ACTION: dachary: to talk to swift devs about integration with
ceilometer  (nijaba, 16:14:45)

* nijaba: to talk to cinder devs about integration with ceilometer
  (nijaba, 16:14:57)

* jd___: to talk to glance devs about integration with ceilometer
  (nijaba, 16:16:47)

* Status of the essex compatibility effort that jd is leading  (nijaba,
  16:21:42)
  * ACTION: jd___ check that openstack-ci runs the tests for Essex
(jd___, 16:27:00)
  * ACTION: jd___ add some tests on daemon launching  (jd___, 16:27:11)

* discussion about cinder integration  (nijaba, 16:27:49)
  * ACTION: nijaba to question best method to authenticate admin client
calls from ceilometer to cinder (and other projects)  (nijaba,
16:36:00)
  * ACTION: nijaba to include adding events to cinder to previous action
(nijaba, 16:43:37)
  * LINK: http://wiki.openstack.org/NovaVolumeMeetings  (nijaba,
16:46:01)

* open discussion  (nijaba, 16:47:55)
  * ACTION: dhellmann and nijba will be joining and nijaba will initiate
a private thread with jgriffith  (nijaba, 16:51:26)



Meeting ended at 16:52:14 UTC.



Action items, by person
---

* dhellmann
  * dhellmann: talk to Quantum devs about integration with ceilometer
  * dhellmann and nijaba will be joining and nijaba will initiate a
private thread with jgriffith
* dachary
  * dachary: talk to Dragon about SystemData / ceilometer and try to
create cooperation
  * dachary: to talk to swift devs about integration with ceilometer
* jd___
  * jd___ check that openstack-ci runs the tests for Essex
  * jd___ add some tests on daemon launching
* jgriffith
  * dhellmann and nijba will be joining and nijaba will initiate a
private thread with jgriffith
* nijaba
  * nijaba: to prime the doc on plugins
  * nijaba to question best method to authenticate admin client calls
from

Re: [Openstack] [Announce][Ceilometer] Release 0.1 (Folsom)

2012-10-12 Thread Atul Jha
Hi all,

Just a small correction the documentation URL is  
http://ceilometer.readthedocs.org/en/latest/index.html

snip
Dear Fellow stackers,

We are pleased to announce today the release of ceilometer 0.1 (Folsom).
 As its version number implies, it is still a project in its infancy, as
it has not yet been incubated as an OpenStack project.  It should,
however, be ready to be used by the most adventurous ones as it offers a
fairly nice coverage of OpenStack, a workable database backend, and a
clean and sweet admin API to retrieve metering information from.

What is ceilometer?
==
The ceilometer project aims to deliver a unique point of contact for
billing systems to acquire all of the measurements they need to
establish customer billing, across all current OpenStack core components
with work underway to support future OpenStack components. We hope that,
once accepted for incubation, it’s official name will become OpenStack
Metering.

What does Ceilometer cover at the moment?
=
Ceilometer covers meters collected from Compute (nova), Network
(quantum), Image (glance), and Volume (cinder).  We’re obviously missing
Object (swift) in this first release, but we have this clearly on our
roadmap for our Grizzly release, and maybe even before depending on the
agility of our contributors.

Regarding Nova, most of the Nova meters will only work with libvirt
fronted hypervisors at the moment, and our test coverage was mostly done
on KVM. Contributors are of course welcome to implement meters for other
virtualization backends.

A detailed list of meters can be found at:
  http://ceilometer.readthedocs.org/en/latest/measurements.html

Detailed release notes are at:
  http://ceilometer.readthedocs.org/en/latest/releasenotes/folsom.html

Where is ceilometer’s release?
==
As for all other OpenStack project, it can be found on the tarballs
server, and more specifically at
  http://tarballs.openstack.org/ceilometer/
and we hope you will be able to find packages in most distributions soon.

Note that, even though we are not yet an official OpenStack project, the
infra team has been supporting us wonderfully and we’ve been using
OpenStack infrastructure happily since the beginning of this project.
Big thanks to the infra team for their help and wonderful setup.

Who has contributed to ceilometer so far?
==
Doug Hellmann, Julien Danjou, Eoghan Glynn, Loic Dachary, John Tran,
Steven Berler, Jay Pipes, Graham Bins, Francis Lacoste, Thierry Carrez,
Anne Gentle, Surya Prabhakar, Nick Barcet and the OpenStack
Infrastructure team have provided help in making this release possible
(we hope we did not miss anyone here...).

Why doesn’t ceilometer do this?
===
We would enjoy hearing about the missing feature that we either never
thought about or haven’t had time to write yet.  You can tell us about
it on the mailing list (see below) or even better, if you are coming to
the OpenStack Developer summit, join us in one of our technical workshop
sessions at the summit on Monday morning:

Monday 9:50am - State of Metering

http://openstacksummitfall2012.sched.org/event/bf543d09fcf4de3f5b4a1008341e5524
Monday 11am - Customizing Ceilometer to measure your cloud

http://openstacksummitfall2012.sched.org/event/c3bca2fa753590b2429759810b753c19
Monday 11:50am - Beyond metering - Extending Ceilometer

http://openstacksummitfall2012.sched.org/event/235e725deb3c224dfd4da88726729faf

or come to the conference presentation Doug Hellmann and Nick Barcet
will be giving:

Monday at 2:40pm - What about billing? An introduction to Ceilometer

http://openstacksummitfall2012.sched.org/event/94fb2cd407b143af4c3fbd979d9c8f91

Where to find more about Ceilometer?

Project home and bug tracker:
 http://launchpad.net/ceilometer

Documentation:
  http://ceiilometer.readthedocs.org

Mailing list:
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  (prefix subjects with [metering] for faster responses)

Wiki:
  http://wiki.openstack.org/EfficientMetering

Code hosting:
  https://github.com/stackforge/ceilometer

Tarballs:
  http://tarballs.openstack.org/ceilometer/

Code reviews:

https://review.openstack.org/#/q/status:open+project:stackforge/ceilometer,n,z

Jenkins:
  https://jenkins.openstack.org/view/Ceilometer/

IRC:
  #openstack-metering on freenode


We hope that you’ll find this contribution valuable.

On behalf of the ceilometer team,
--
Nick Barcet nick.bar...@canonical.com
aka: nijaba, nicolas
/snip

Congrats to Nijaba and Ceilometer team for this milestone. :)

Cheers!!,
Atul Jha aka koolhead17

http://www.csscorp.com/common/email-disclaimer.php

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer - blueprint?

2012-11-15 Thread Jiang, Yunhong
Do you plan to implement it? Per my understanding, If yes, then begin 
implementation, and don't forget to add something like for bp  in your 
patch. Otherwise, wait someone who has interests to work on it :)

Thanks
--jyh

 -Original Message-
 From: openstack-bounces+yunhong.jiang=intel@lists.launchpad.net
 [mailto:openstack-bounces+yunhong.jiang=intel@lists.launchpad.net] On
 Behalf Of shengjie_...@dell.com
 Sent: Thursday, November 15, 2012 10:11 PM
 To: doug.hellm...@dreamhost.com
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer -
 blueprint?
 
 Hi guys,
 
 
 
 The blueprint is registered :
 https://blueprints.launchpad.net/ceilometer/+spec/hbase-storage-backend,
 Any idea what's the next step ? J
 
 
 
 Shengjie


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [ceilometer] How does ceilometer work with multi-DC scenario

2012-11-22 Thread Shengjie_Min

You can deploy several ceilometer and use several databases, or just one and 
use a different 'source' field for each of your region/cluster to 
differentiate where meters come from.

Let's say if you deploy one ceilometer instance for two swift clusters 
'swift-cluster-1' and 'swift-cluster-2'. According to the design, if we use 
'source' field for region/cluster to tell what cluster the meters come from. 
The Ceilometer API doesn't seem being well thought through yet.

A single region case:
If you want to get the meters for TenantA, this API will simply do the job:
GET /v1/projects/(project)/meters/(meter)

Two regions case:
If you want to get the meters for TenantA from 'swift-cluster-1' specifically.  
According to the API design we have now, there is no API can do that directly 
unless you do some complex API calls combination.

Shengjie

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Grizzly-3 development milestone available (Ceilometer, Heat)

2013-02-22 Thread Nicolas Barcet
On Fri, Feb 22, 2013 at 10:15 AM, Thierry Carrez thie...@openstack.org wrote:
 Thierry Carrez wrote:
 The last milestone of the Grizzly development cycle, grizzly-3 is
 now available for testing. This milestone contains almost all of the
 features that will be shipped in the final 2013.1 (Grizzly) release on
 April 4, 2013.

 And with perfect sync now, our two grizzly-incubated projects,
 Ceilometer and Heat, also have their grizzly-3 milestone available:

 https://launchpad.net/ceilometer/grizzly/grizzly-3
 https://launchpad.net/heat/grizzly/grizzly-3

 Happy testing and bugfixing!

 --
 Thierry Carrez (ttx)
 Release Manager, OpenStack

You can read more about the Grizzly-3 milestone for Ceilometer at:

https://launchpad.net/ceilometer/+announcement/11199

Cheers,
--
Nicolas Barcet nico...@barcet.com
a.k.a. nijaba, nick

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer] Grizzly RC1 released

2013-03-26 Thread Razique Mahroua
Fantastic.Great work :)
Razique Mahroua-Nuage  Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15

Le 26 mars 2013 à 16:47, Julien Danjou jul...@danjou.info a écrit :Hi,We're pleased to announce that the RC1 version for the Grizzly releaseof Ceilometer is available! https://launchpad.net/ceilometer/grizzly/grizzly-rc1Unless release-critical issues are found that warrant a releasecandidate respin, this version will be formally released as theCeilometer 2013.1 version on April 4. You are therefore stronglyencouraged to test and validate this tarball.If you find an issue that could be considered release-critical, pleasefile it at: https://bugs.launchpad.net/ceilometer/+filebugNote that the "master" branch for Ceilometer is now open for Havanadevelopment, and feature freeze restriction no longer apply.-- Julien Danjou-- Free Software hacker - freelance consultant-- http://julien.danjou.info___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer Install

2013-04-25 Thread Doug Hellmann
On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I have
 installed the driver Mongo using sudo pip install pymongo.


Ceilometer does use a database. You have to install the right driver. If
you want Mongo, then it sounds like you've done the right thing. It's
possible mako is also being used somewhere else, I'm not sure.



 Regarding the current problem; the traceback is as follows:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


That is coming from oslo.config. Can you post the ceilometer.ini file and
command line you are using to start the service?

Doug



 Thank for the help.


 On Thu, Apr 25, 2013 at 3:27 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:



 On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance endpoint
 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed the
 v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError: No
 module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


 Mako is a dependency do sqlalchemy, I think. Are you using the sqlalchemy
 storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is as
 follows:
 AttributeError: 'OptGroup' object has no attribute
 '_get_argparse_group'


 That sounds like a problem with the config module. Was there a full
 traceback? If not, try adding the --debug option when starting the service.

 Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan riki.ars...@cloudturk.net
  wrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that
 was causing the conflict. After updating it, the conflict error 
 disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which
 presumably has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of
 the keystone client, so the installation of ceilometer is not able to
 upgrade to the version we need.

 Doug



 Your help is greatly appreciated.

 Thank you in advance.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Ceilometer][Healthnmon] Monitoring Alarm in openstack

2013-07-01 Thread Angus Salkeld

On 01/07/13 13:42 +0200, Emanuel Marzini wrote:

Hi,
I want to retrive Vm information from Openstack. I am interested of CPU 
RAM utilization.
I known that someone use collectd, libvirt ecc.. or product like Ceilometer
or Healthnmon.
I am also interested to receive alarm information from the cloud provider
if the CPU or RAM value exceeds a threshold.
I read that from Havana, Ceilometer and Healthnmon will be merged, it's
true? Might be a good solution to my problems?


Ceilometer is getting alarms this cycle. Heat will start using
them for autoscaling (cpu/mem stats).

https://blueprints.launchpad.net/ceilometer/+spec/alarming

Regards
Angus



Thanks in advance
Emanuel



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Ceilometer][Healthnmon]

2013-07-02 Thread Doug Hellmann
The work to merge ceilometer and healthnmon hasn't made much progress, yet.

The ceilometer team is working on collecting information about CPU and RAM
utilization for triggering alarms for Heat. That work is schedule for the
havana release, and is moving along nicely. We could use some help with
code reviews, but I think the overall design is worked out.

Doug


On Mon, Jul 1, 2013 at 5:51 AM, Emanuel Marzini jema...@gmail.com wrote:

 Hi,
 I want to retrive Vm information from Openstack. I am interested of CPU 
 RAM utilization.
 I known that someone use collectd, libvirt ecc.. or product like
 Ceilometer or Healthnmon.
 I am also interested to receive alarm information from the cloud provider
 if the CPU or RAM value exceeds a threshold.
 I read that from Havana, Ceilometer and Healthnmon will be merged, it's
 true? Might be a good solution to my problems?

 Thanks in advance
 Emanuel

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer question

2013-03-26 Thread Wyllys Ingersoll
Thanks, Ill try that and see how it goes.

Wyllys



On Mar 26, 2013, at 12:56 PM, Doug Hellmann 
doug.hellm...@dreamhost.commailto:doug.hellm...@dreamhost.com wrote:

You want the statistics command from the v2 API.

ceilometer --ceilometer-api-version 2 help statistics

The CLI needs a little work to make the options clear, but the API 
documentation may help explain: 
http://docs.openstack.org/developer/ceilometer/webapi/v2.html

Doug

On Tue, Mar 26, 2013 at 12:22 PM, Wyllys Ingersoll 
wyllys.ingers...@evault.commailto:wyllys.ingers...@evault.com wrote:

Perhaps this is documented but I can't seem to find it…

I want to use ceilometer to show usage from the swift objectstore.  What would 
the correct command be to extract that information? Currently, the various 
-list commands just spit out various meter types along with resource and 
project id values.

Thanks,
  Wyllys Ingersoll
  EVault


On Mar 26, 2013, at 11:47 AM, Julien Danjou 
jul...@danjou.infomailto:jul...@danjou.info wrote:

 Hi,

 We're pleased to announce that the RC1 version for the Grizzly release
 of Ceilometer is available!

   https://launchpad.net/ceilometer/grizzly/grizzly-rc1

 Unless release-critical issues are found that warrant a release
 candidate respin, this version will be formally released as the
 Ceilometer 2013.1 version on April 4. You are therefore strongly
 encouraged to test and validate this tarball.

 If you find an issue that could be considered release-critical, please
 file it at:

 https://bugs.launchpad.net/ceilometer/+filebug

 Note that the master branch for Ceilometer is now open for Havana
 development, and feature freeze restriction no longer apply.

 --
 Julien Danjou
 -- Free Software hacker - freelance consultant
 -- http://julien.danjou.info
 ATT1___
 Mailing list: https://launchpad.net/~openstack
 Post to : 
 openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Announce][Ceilometer] Release 0.1 (Folsom)

2012-10-12 Thread Nick Barcet
Dear Fellow stackers,

We are pleased to announce today the release of ceilometer 0.1 (Folsom).
 As its version number implies, it is still a project in its infancy, as
it has not yet been incubated as an OpenStack project.  It should,
however, be ready to be used by the most adventurous ones as it offers a
fairly nice coverage of OpenStack, a workable database backend, and a
clean and sweet admin API to retrieve metering information from.

What is ceilometer?
==
The ceilometer project aims to deliver a unique point of contact for
billing systems to acquire all of the measurements they need to
establish customer billing, across all current OpenStack core components
with work underway to support future OpenStack components. We hope that,
once accepted for incubation, it’s official name will become OpenStack
Metering.

What does Ceilometer cover at the moment?
=
Ceilometer covers meters collected from Compute (nova), Network
(quantum), Image (glance), and Volume (cinder).  We’re obviously missing
Object (swift) in this first release, but we have this clearly on our
roadmap for our Grizzly release, and maybe even before depending on the
agility of our contributors.

Regarding Nova, most of the Nova meters will only work with libvirt
fronted hypervisors at the moment, and our test coverage was mostly done
on KVM. Contributors are of course welcome to implement meters for other
virtualization backends.

A detailed list of meters can be found at:
  http://ceilometer.readthedocs.org/en/latest/measurements.html

Detailed release notes are at:
  http://ceilometer.readthedocs.org/en/latest/releasenotes/folsom.html

Where is ceilometer’s release?
==
As for all other OpenStack project, it can be found on the tarballs
server, and more specifically at
  http://tarballs.openstack.org/ceilometer/
and we hope you will be able to find packages in most distributions soon.

Note that, even though we are not yet an official OpenStack project, the
infra team has been supporting us wonderfully and we’ve been using
OpenStack infrastructure happily since the beginning of this project.
Big thanks to the infra team for their help and wonderful setup.

Who has contributed to ceilometer so far?
==
Doug Hellmann, Julien Danjou, Eoghan Glynn, Loic Dachary, John Tran,
Steven Berler, Jay Pipes, Graham Bins, Francis Lacoste, Thierry Carrez,
Anne Gentle, Surya Prabhakar, Nick Barcet and the OpenStack
Infrastructure team have provided help in making this release possible
(we hope we did not miss anyone here...).

Why doesn’t ceilometer do this?
===
We would enjoy hearing about the missing feature that we either never
thought about or haven’t had time to write yet.  You can tell us about
it on the mailing list (see below) or even better, if you are coming to
the OpenStack Developer summit, join us in one of our technical workshop
sessions at the summit on Monday morning:

Monday 9:50am - State of Metering

http://openstacksummitfall2012.sched.org/event/bf543d09fcf4de3f5b4a1008341e5524
Monday 11am - Customizing Ceilometer to measure your cloud

http://openstacksummitfall2012.sched.org/event/c3bca2fa753590b2429759810b753c19
Monday 11:50am - Beyond metering - Extending Ceilometer

http://openstacksummitfall2012.sched.org/event/235e725deb3c224dfd4da88726729faf

or come to the conference presentation Doug Hellmann and Nick Barcet
will be giving:

Monday at 2:40pm - What about billing? An introduction to Ceilometer

http://openstacksummitfall2012.sched.org/event/94fb2cd407b143af4c3fbd979d9c8f91

Where to find more about Ceilometer?

Project home and bug tracker:
 http://launchpad.net/ceilometer

Documentation:
  http://ceiilometer.readthedocs.org

Mailing list:
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  (prefix subjects with [metering] for faster responses)

Wiki:
  http://wiki.openstack.org/EfficientMetering

Code hosting:
  https://github.com/stackforge/ceilometer

Tarballs:
  http://tarballs.openstack.org/ceilometer/

Code reviews:

https://review.openstack.org/#/q/status:open+project:stackforge/ceilometer,n,z

Jenkins:
  https://jenkins.openstack.org/view/Ceilometer/

IRC:
  #openstack-metering on freenode


We hope that you’ll find this contribution valuable.

On behalf of the ceilometer team,
--
Nick Barcet nick.bar...@canonical.com
aka: nijaba, nicolas



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


  1   2   3   4   5   6   7   8   9   10   >