it is not
complete solution, but some kind of the hook.
What do you think about that?
Any thoughts and propositions are kindly welcome.
[1] https://bugs.launchpad.net/mos/+bug/1360240
[2] http://docs.mongodb.org/manual/reference/limits/
[3] https://review.openstack.org/#/c/106376/
-- Igor Degt
So the question is
should we specify query only for MongoDB or change queries for all
backends?
> In this case it's not necessary to know deep of tree.
>
> Thanks,
> Nadya
>
>
>
Cheers,
Igor D.
>
> On Fri, Aug 29, 2014 at 3:21 PM, Igor Degtiarov
> wrote:
>
om
urllib.parse
I have proposed change request with fix:
https://review.openstack.org/121003
Cheers,
-- Igor D.
On Mon, Sep 8, 2014 at 5:02 PM, Igor Degtiarov
wrote:
> On Thu, Sep 4, 2014 at 1:16 PM, Nadya Privalova
> wrote:
>
>> IMHO it's ok and even very na
sh the patch with current implementation soon.
Sincerely,
Igor Degtiarov
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
tion.
On Wed, Apr 30, 2014 at 4:36 PM, Dmitriy Ukhlov wrote:
> Hello Igor!
>
> Could you clarify, please, Why do we need "event_id + reversed_timestamp"
> row key?
> Isn't "event_id" identify row?
>
>
> On Tue, Apr 29, 2014 at 11:08 AM, Igor De
Hi,
I have found that filter model for Events has mandatory parameters
start_time and end_time
of the events period. So, it seems that structure for rowkey as ''timestamp
+ event_id" will be more suitable.
I have started to work on bp
https://blueprints.launchpad.net/ceilometer/+spec/hbase-event
gor,
>
> Sounds reasonable.
>
>
> On 05/21/2014 02:38 PM, Igor Degtiarov wrote:
>
>>
>> Hi,
>>
>> I have found that filter model for Events has mandatory parameters
>> start_time and end_time
>> of the events period. So, it seems that structure for r
Hi, Qiming Teng.
Now all backends support events. So you may use MongoDB instead of
MySQL, or if you like you may choose HBase.
Cheers, Igor.
-- Igor
On Thu, Sep 25, 2014 at 7:43 AM, Preston L. Bannister
wrote:
> Sorry, I am jumping into this without enough context, but ...
>
>
> On Wed, Sep 2
more then 0 then
patch are not taken.
I have taken as pattern Sahara's solution and proposed a patch for ceilometer:
https://review.openstack.org/#/c/125906/
Cheers,
Igor Degtiarov
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
gt;> >> Personally this idea looks really nice to me, as this will help to
>> >> avoid
>> >> strange code being merged and not found via reviewing process.
>> >>
>> >> Cheers,
>> >> Dina
>> >>
>> >> On Fri, Oct 3, 2014 at 12
Hi stackers,
I'm working on solving bug [1]. Time to live feature has native
implementation in MongoDB thru index.
Now we remove docs from resource table if they have no relations with
existing samples in meter table while samples are removed when time to
live is expired. So it seems that we can
Hi,
Actually the same question, what is wrong with Tox now?
-- Igor
On Wed, Aug 6, 2014 at 1:19 PM, Narasimhan, Vivekanandan <
vivekanandan.narasim...@hp.com> wrote:
> Hi,
>
>
>
> Recently , the Tox runs started to fail in my workspace.
>
> It fails consistently during installing dependencies
r help in choosing optimal way for implementation.
(In specs review there is silence now)
[1]
https://wiki.openstack.org/wiki/Meetings/Ceilometer/Liberty_Virtual_Mid-Cycle
[2] https://review.openstack.org/#/c/162167
[3] https://review.openstack.org/#/c/199005
Igor Degtiarov
Software Engineer
; specs as part of liberty?
And the second one: are we going to create special rep for AODH specs or
ceilometer-specs is ok for all new projects?
Thank you in advance,
Igor Degtiarov
Software Engineer
Mirantis Inc.
www.mirantis.com
On Fri, Aug 7, 2015 at 10:59 AM, Ryota Mibu wrote:
> Hi,
>
Gordon thanks for quick answer.
I'll add a patch with new dir for mitaka specs and move my specs there.
cheers,
Igor Degtiarov
Software Engineer
Mirantis Inc.
www.mirantis.com
On Mon, Aug 17, 2015 at 7:02 PM, gord chung wrote:
> good questions...
>
> On 17/08/2015 10:19 AM,
Hi!
Looks good to me, especially for cases when after some incident we gather a
great amount of notifications in queue and stated to work with it so some
data will have incorrect timestamp if it set only when sample is created.
Cheers,
Igor Degtiarov
Software Engineer
Mirantis Inc
Meters are measurable value. So it cannot be a string.
If you really need to have notifications about event that is exist but
cannot be measured you can use Events.
http://docs.openstack.org/admin-guide-cloud/telemetry-events.html
Cheers,
Igor Degtiarov
Software Engineer
Mirantis Inc
Hi Tim
I've check your case on my devstack. And I've received new hs06 meter
in my meter list.
So something wrong with your local env.
Cheers,
Igor D.
Igor Degtiarov
Software Engineer
Mirantis Inc
www.mirantis.com
On Fri, Mar 20, 2015 at 5:40 PM, Tim Bell wrote:
>
>
> I’
I am just curious have you restarted ceilometer services after
pipeline.yaml has been changed?
Igor Degtiarov
Software Engineer
Mirantis Inc
www.mirantis.com
On Sat, Mar 21, 2015 at 1:21 PM, Tim Bell wrote:
> No errors in the notification logs.
>
>
>
> Should this work w
19 matches
Mail list logo
