On 2018-06-14 1:30 AM, Ignazio Cassano wrote:
> Hello Gordon, what do you mean with "coordination service" ?
it is what handles locking/coordination across multiple workers. you
configure it via a config option in your gnocchi.conf file.
as you didn't define one it is using your indexer by
i would probably ask this question on gnocchi[1] as i don't know how many devs
read this. you should also add what numerical version of gnocchi you're using
and what coordination service you're using.
if i were to quickly guess, i'm going to to assume you're not using a dedicated
coordination
On 2018-05-15 2:40 AM, Ignazio Cassano wrote:
> gnocchi resource delete instance id
>
>
> Does the above procedure remove data either from database or
> /var/lib/gnocchi directory ?
not immediately, it will mark the data for deletion. there is a
'janitor' service that runs periodically that
On 2018-05-14 10:16 AM, Ignazio Cassano wrote:
> Hi everyone,
> I am osing ocata on centos 7 with ceilometer and gnocchi.
> The gnocchi backend is nfs and I would like to know if it is possible
> remove old data on the backend file system.
> Dome directories on the backend are 6 months old.
>
On 2018-02-23 11:20 AM, Masha Atakova wrote:
> I reconfigured the setup accordingly, to use gnocchi as a storage, but
> the problem is: ceilometer has multiple types of metrics while gnocchi
> doesn’t have metric types at all.
> And it doesn’t really make sense to store metrics of cumulative
On 31/10/17 07:55 PM, andres sanchez ramos wrote:
> 2017-10-31 23:45:35.707 14436 ERROR cotyledon ParserError: while parsing
> a block mapping
> 2017-10-31 23:45:35.707 14436 ERROR cotyledon in "", line 2,
> column 1:
> 2017-10-31 23:45:35.707 14436 ERROR cotyledon sources:
> 2017-10-31
On 26/10/17 08:33 AM, andres sanchez ramos wrote:
>
> import pbr.version
> version_info = pbr.version.VersionInfo('ceilometer')
>
> and the output was 7.0.3
what happens if you use:
- name: meter_source
interval: 60
meters:
- switch.flow.duration_seconds
On 24/10/17 04:45 AM, andres sanchez ramos wrote:
> I had tried to configure my pipeline so it would also gather information
> from ODL since i was trying to get as much information as possible. I
> commented out everything related to ODL and the errors stopped. Any
> ideas about the cause of
On 2017-10-19 09:20 AM, andres sanchez ramos wrote:
> Hello,
>
>
> I have been trying to modify my ceilometer setup in order to include
> hardware measurement but have not been able to do so. Looking into the
> logs there are a lot of errors like this:
>
>
> 2017-10-19 12:09:46.467 30274
adding ops list
On 2017-10-13 11:01 AM, Julien Danjou wrote:
> Hey there,
>
> We deprecated the Ceilometer API last year (Ocata) and our latest user
> survery shows than more than 50% of our users are now using Gnocchi or
> something else than the old deprecated storage methods.
thanks to all
On 26/06/17 06:07 PM, Tracy Comstock Roesler wrote:
> If I understand what you¹re saying, you think I can try
> direct://?publisher=gnocchi in the pipeline.yaml on the controller nodes,
> but not the compute nodes to bypass the collector?
sorry, i just looked at the code again, it was only
On 24/06/17 10:49 PM, Mike Smith wrote:
> We use ceilometer-compute and we would like to have it push metrics directly
> to Gnocchi, bypassing the rabbit queues that ceilometer uses in the default
> Mitaka configuration. Currently our ceilometer-compute pushes to the
> notification queue,
On 23/06/17 02:50 PM, Tracy Comstock Roesler wrote:
> We’ve been using gnocchi in mitaka for a few months now but we’ve run
> into some issues with performance, predominantly because of the number
> of data points sent along rabbitmq.
i'm not sure what rabbitmq has to do with gnocchi since
On 16/06/17 04:32 AM, Amit Kumar wrote:
> Hi
>
> I have installed OpenStack using OpenStack-Ansible 14.1.1. I have
> installed Ceilometer, Aodh and using Mongo DB. I am trying simple
> autoscaling scenario. On Horizon GUI, I have not been able to see the
> resource usage getting updated
On 14/06/17 05:15 AM, Ignazio Cassano wrote:
>
> source admin-openrc
>
> gnocchi metric list
>
> The request you have made requires authentication. (HTTP 401)
i have no idea what admin-openrc sets, i'm guessing this?
https://docs.openstack.org/ocata/install-guide-rdo/keystone-openrc.html
the
On 13/06/17 01:17 PM, Ignazio Cassano wrote:
> Hi Gordon, I had no enough time for trying with devstack.
you gave up after a day?
how about paste your ceilometer.conf and gnocchi.conf. did you follow
the steps here?
On 12/06/17 10:30 AM, Ignazio Cassano wrote:
> 2017-06-12 15:43:09.594 35526 CRITICAL ceilometer [-] Unauthorized:
> Unauthorized (HTTP 401)
the credentials you're using aren't valid.
my advice is to launch devstack with gnocchi and ceilometer enabled.
from there, take a look at the
On 12/06/17 06:41 AM, Ignazio Cassano wrote:
> I am trying to configure ocata with gnocchi on a cluster environment on
> centos 7 controllers.
> If I not modify /usr/lib/systemd/system/openstack-gnocchi-api.service,
> gnocchi
> try to bind on port 8000.
you should be leveraging uwsgi or apache
On 30/05/17 10:42 AM, mate...@mailbox.org wrote:
>
> Second thing, that I don't understand is how to get access to stored
> data. For instance, with ceilometer I can execute /ceilometer
> sample-list -m memory.usage -q resource_id= /
> and receive memory usage for some instance. Now, If i
hi,
as all of you know, we moved all storage out of ceilometer so it is
handles only data generation and normalisation. there seems to be very
little contribution to panko which handles metadata indexing, event
storage so given how little it's being adopted and how little resources
are being
hi,
since i've been referencing this to a few people already, i've done some
basic benchmarking on the upcoming gnocchi release which should be
released in next few weeks. here is a short deck highlighting a few updates:
https://www.slideshare.net/GordonChung/gnocchi-v4-preview
if you have
On 26/05/17 09:31 AM, Mathieu Gagné wrote:
>
> With Mitaka, I found that you need to run this command to get resource
> types created in Gnocchi:
>
> gnocchi-upgrade --create-legacy-resource-types
>
> With latest version, Ceilometer handles that part.
this ^... thanks Mathieu!
if you are using
On 23/05/17 10:16 AM, mate...@mailbox.org wrote:
> / 2017-05-23 13:29:10.961 1931583 ERROR ceilometer.dispatcher.gnocchi
> [-] Failed to connect to Gnocchi./
> /2017-05-23 13:29:10.962 1931583 ERROR stevedore.extension [-] Could not
> load 'gnocchi': Unexpected exception for
>
On 08/04/17 01:00 PM, Paras pradhan wrote:
> y current configuration I am using 300 GB 10K SAS (in hardware raid 1)
> and iostat report does not look good (upto 100% unilization) with
> ceilometer consuming high CPU and Memory. Does it help adding more
> spindles and move to raid 10?
>
i don't
On 28/03/17 03:28 PM, Ionut Biru - Fleio wrote:
> Hello,
>
>
> I do have a cloud under administration, my setup is fairly basic, I have
> deployed openstack using Openstack Ansible, currently I'm a Newton and
> planning to upgrade on Ocata.
>
>
> I'm having a problem with gnocchi metricd falling
can you add what version of gnocchi, gnocchiclient and oslo.policy you
have? might be easier if open a bug[1]. i don't see anything wrong at
first glance and i don't recall there being a similar issue in past.
[1] https://bugs.launchpad.net/gnocchi
On 23/02/17 11:54 AM, Tracy Comstock Roesler
hi,
unfortunately i noticed this thread never made it to the operators list.
there is a thread regarding the removal of Ceilometer Event API in
Ocata[1]. this is only related to the storage and access of events. the
generation of events remains in Ceilometer.
as a quick summary: the telemetry
On 18/11/16 05:10 PM, Danek Duvall wrote:
>> this pollster is used by other hypervisor polling. there was a patch for
>> libvirt driver to use libvirt native functionality to retrieve cpu_util
>> info rather than computing it[3]. unfortunately, at the time, the
>> functionality was in a
hi,
if you're using libvirt driver than it's derived. i assume the
CPUUtilPollster you're referencing is the instance pollster[1] and not
the node pollster[2]. this pollster is used by other hypervisor polling.
there was a patch for libvirt driver to use libvirt native functionality
to
hi folks,
as announced recently, we released Gnocchi v3[1][2]! this marked a major
change in how we process and store data in Gnocchi as we worked on
building a truly open source time-series service.
as we were building it, i've been benchmarking the results and feeding
it back into our
Agreed. i'm doing some benchmarking myself currently which i will
publish soon. whenever y'all do start testing, we welcome any feedback.
On 26/09/2016 4:43 AM, Tobias Urdin wrote:
> Hello Gordon,
>
> I have talked to a lot of different people at various companies, most of
> them (including us)
i don't want to speak for rest of Telemetry contributors but i don't
think many(any) of us suggest using MongoDB or Ceilometer's API for
storage. It is basically a data dump of what Ceilometer is collecting so
it will be very, very verbose for most/all use cases.
as Joseph mentioned,
driver).
cheers,
--
gord
From: Erik McCormick <emccorm...@cirrusseven.com>
Sent: August 1, 2016 12:52:10 PM
To: Sam Morrison
Cc: gordon chung; openstack-operators
Subject: Re: [Openstack-operators] [gnocchi] monitoring storage use case inquiry
On
hi folks,
the Gnocchi dev team is working on pushing out a new serialization
format to improve disk footprint and while we're at it, we're looking at
other changes as well. to get a bit more insight to help decide what
changes we make, one useful metric would be to know what your
requirements
forward. also, will be testing some enhancements we've been discussing
for Gnocchi 3.x
hope it helps.
cheers,
On 25/06/2016 8:50 AM, Curtis wrote:
> On Fri, Jun 24, 2016 at 2:09 PM, gordon chung <g...@live.ca> wrote:
>> hi,
>>
>> i realised i didn't post this beyond IR
hi,
i realised i didn't post this beyond IRC, so here are some initial
numbers for some performance/benchmarking i did on Gnocchi.
http://www.slideshare.net/GordonChung/gnocchi-profiling-21x
as a headsup, the data above is using Ceph and with pretty much a
default configuration. i'm currently
hi folks,
as you know Gnocchi api is different from Ceilometer's v2 metering api
(for the better). to help describe the differences and possibly help
with the transition, i've created a few slides[1] to describe how a
command in Ceilometer can be done similarly in Gnocchi.
to learn how to
On 04/03/2016 5:15 PM, Stig Telfer wrote:
>
>> On 4 Mar 2016, at 15:40, gordon chung <g...@live.ca> wrote:
>>
>>> One part of the documentation set that we were missing was a guide to how
>>> to migrate from ceilometer to a ceilometer/gnocchi combination (
> One part of the documentation set that we were missing was a guide to how to
> migrate from ceilometer to a ceilometer/gnocchi combination (which I
> understand is the ultimate architecture). We would like to migrate the
> historical data we have stored in ceilometer.
>
> The main line
hi Mike,
the actual frequency of alerts corresponds to the frequency of alarm
evaluations[1]. the evaluation frequency defaults to 60s but can be
changed by setting 'evaluation_interval' option in your conf file.
On 03/03/2016 5:20 PM, Mike Smith wrote:
> We are using Ceilometer to tell us
A couple things about this seem less than ideal:
* 2 means we load redundant stuff unless we edit entry_points.txt.
We do not want to encourage this sort of behavior. entry_points is
not configuration[1]. We should configure elsewhere to declare I
care about things X (including the
hi folks,
there's a session coming up at the summit so we can discuss Ceilometer and
give/get some feedback but i wanted to highlight some of the work we've been
doing, specifically relating to storing measurement values. as many of you have
heard/read, we're building this thing called
___
From: morgan.fainb...@gmail.com
Date: Thu, 16 Apr 2015 07:50:43 -0700
To: dsta...@dstanek.com
CC: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] logging for Keystone on user/project
delete/create operations
On Apr 16,
...@live.ca; openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [openstack-dev] [Ceilometer] Real world
experience with Ceilometer deployments - Feedback requested
On 03/10/2015 06:18 PM, gordon chung wrote:
I actually like the format, we should all switch to outlook
hi,
just to follow-up, thanks for the input, the usability of ceilometer is
obviously a concern of ours and something the team tries to address with the
resources we have.
as a quick help/update, here are some points of interests that i think might
help:- if using Juno+, DO use the notifier://
sorry, i apparently don't know how to format emails...
cheers,
gord
From: g...@live.ca
To: openstack-operators@lists.openstack.org; openstack-...@lists.openstack.org
Date: Tue, 10 Mar 2015 16:05:47 -0400
Subject: Re: [openstack-dev] [Openstack-operators] [Ceilometer] Real world
experience with
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [openstack-dev] [Ceilometer] Real world
experience with Ceilometer deployments - Feedback requested
On 03/10/2015 04:34 PM, gordon chung wrote:
sorry, i apparently don't know how to format emails...
I actually like the format
47 matches
Mail list logo
