Friday, 2014-10-31

*** boris-42 has quit IRC01:23
*** vivekd has joined #magnetodb02:46
*** jeromatron has joined #magnetodb04:06
*** rushiagr_away is now known as rushiagr05:12
*** jeromatron has quit IRC05:15
*** ajayaa has joined #magnetodb05:28
*** k4n0 has joined #magnetodb06:34
*** romainh has joined #magnetodb08:27
ajayaaisviridov, https://review.openstack.org/#/c/126335/3/specs/kilo/magnetodb-notifications.rst08:51
ajayaaisviridov_away ^^08:51
*** vivekd has quit IRC08:54
*** isviridov_away is now known as isviridov08:59
isviridovHello ajayaa, cool!09:00
isviridovLet me take a look09:00
isviridovajayaa : what is resource id in samples?09:05
ajayaaThat is a unique field per resource. In our case it would represent a unique table in mdb.09:06
ajayaaAs of now I don't think UUIDs are being sent in notifications.09:06
ajayaaBut we will send them I guess.09:06
ajayaaisviridov ^^09:07
isviridovI see now. How does multitenancy work here?09:15
isviridovIt seems like we are using samples where events should be used.09:15
isviridovI mean http://docs.openstack.org/developer/ceilometer/events.html#events-vs-samples09:16
isviridovWith samples we have some changing data for specific resource. F.e. cpu usage for instanse, of size for table.09:17
isviridovProbably we can handle table count per tenant as sample, where tenant is resource.09:18
isviridovWhat do you think?09:19
ajayaaisviridov, I was using cinder as a reference. When a volume is created, a notification is generated from cinder which is caught by ceilometer. Then a sample is created from this notification.09:22
ajayaaisviridov, If we just keep count of tables, we won't be able to store number of indices per table.09:23
ajayaaisviridov, I just came across events. I am not sure whether an event or sample is fit for our usecase.09:25
*** boris-42 has joined #magnetodb09:46
isviridovajayaa : ok, I see. Not sure that cinder is the best example, because some things was implemented to provide bacis monitoring of availability09:51
isviridovI mean 'volume' meter09:51
isviridovI think we have to follow heat or sahara, as far as in both cases they are publishing data about abstrac entities like stack or cluster.09:52
isviridovLet me comment in your review.09:52
ajayaaisviridov, It is easy to get count of tables per tenant from samples. You can pass a query parameter to ceilometer client.09:52
isviridovajayaa : yeap, I've found it. Thank you09:53
isviridovWhy it is -1 by jenkins? Any ideas?09:53
ajayaaisviridov, nope. I will take a look.09:57
*** openstackgerrit has joined #magnetodb10:03
isviridovajayaa : added several comments, actually the idea is to do it now for only two types events table.create and table.delete in order to count the tables and track activity.10:11
isviridovI also suggest removing index count, as ambigous and keep it simple on the first stage.10:12
ajayaaisviridov, I think the two type of events table.create and table.delete could be stored under the same meter.10:12
isviridovajayaa : what the meter?10:12
isviridovtable?10:12
ajayaayes.10:12
ajayaaThat way when you see two samples per resource_id per meter, you can infer that the table is deleted.10:13
ajayaaI need to check whether we can express this in ceilometer query so that we get count of tables per tenant.10:15
isviridovI'm looking at it as monitoring system also, not only backend for billing. I personally would like to track table connected  events  https://github.com/stackforge/magnetodb/blob/master/magnetodb/notifier/__init__.py#L40-L4510:17
isviridovBut they looks like events, not samles :) It is needed to clarify how to put to ceilo as well.10:17
isviridovajayaa : yes, please do so. Thanks10:18
ajayaaisviridov, It is convenient to add two type of meter. table.create and table.delete. That way we would count table.create samples and subtract count of table.delete samples to get number of tables per tenant.10:20
ajayaaYou were right. ;)10:21
isviridovNice10:21
* ajayaa reading more about events in ceilometer.10:25
*** rushiagr is now known as rushiagr_away10:52
openstackgerritIllia Khudoshyn proposed a change to stackforge/magnetodb: Raise ValidationError if attribute type is missing  https://review.openstack.org/13221911:43
*** boris-42 has quit IRC12:14
openstackgerritIllia Khudoshyn proposed a change to stackforge/magnetodb: Raise ValidationError if attribute type is missing  https://review.openstack.org/13221912:21
*** rushiagr_away is now known as rushiagr12:31
*** isviridov is now known as isviridov_away12:34
*** ajayaa has quit IRC12:34
*** miqui has joined #magnetodb12:48
ikhudoshynhttps://review.openstack.org/#/c/132219/ pls review12:55
*** charlesw has joined #magnetodb13:28
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: Adds monitoring API  https://review.openstack.org/12233013:34
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: Adds monitoring API  https://review.openstack.org/12233013:35
*** boris-42 has joined #magnetodb13:38
openstackgerritNuno Santos proposed a change to stackforge/magnetodb: Record and retrieve table creation timestamp  https://review.openstack.org/13154613:41
*** denis_makogon_ has joined #magnetodb13:57
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: Adds monitoring API  https://review.openstack.org/12233013:59
*** jeromatron has joined #magnetodb13:59
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: Adds monitoring API  https://review.openstack.org/12233014:06
*** jeromatron has quit IRC14:21
openstackgerritIllia Khudoshyn proposed a change to stackforge/magnetodb: Raise ValidationError if attribute type is missing  https://review.openstack.org/13221914:23
ikhudoshyncharlesw: around?14:25
*** jeromatron has joined #magnetodb14:27
openstackgerritIllia Khudoshyn proposed a change to stackforge/magnetodb: Raise ValidationError if attribute type is missing  https://review.openstack.org/13221914:28
*** jeromatron has quit IRC14:30
*** jeromatron has joined #magnetodb14:32
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: Adds Cassandra implemetation of monitoring API  https://review.openstack.org/13226714:33
*** romainh has quit IRC14:38
*** jeromatron has quit IRC14:39
*** jeromatron has joined #magnetodb14:46
*** romainh has joined #magnetodb14:51
*** boris-42 has quit IRC14:52
*** jeromatron has quit IRC14:53
*** jeromatron has joined #magnetodb14:54
*** boris-42 has joined #magnetodb14:54
*** boris-42 has quit IRC15:11
*** k4n0 has quit IRC15:27
*** jeromatron has quit IRC15:29
openstackgerritNuno Santos proposed a change to stackforge/magnetodb: Record and retrieve table creation timestamp  https://review.openstack.org/13154615:40
*** jeromatron has joined #magnetodb16:16
*** denis_makogon_ has quit IRC17:09
*** jeromatron has quit IRC17:58
*** romainh has quit IRC18:14
*** romainh1 has joined #magnetodb18:14
*** rushiagr is now known as rushiagr_away18:32
openstackgerritA change was merged to stackforge/magnetodb: Raise ValidationError if attribute type is missing  https://review.openstack.org/13221919:16
*** jeromatron has joined #magnetodb19:34
*** romainh1 has left #magnetodb20:13
*** jeromatron has quit IRC20:25
*** jeromatron has joined #magnetodb20:37
*** denis_makogon_ has joined #magnetodb21:18
*** nunosantos has quit IRC21:21
*** charlesw has quit IRC21:31
*** boris-42 has joined #magnetodb21:55
openstackgerritA change was merged to stackforge/magnetodb: Record and retrieve table creation timestamp  https://review.openstack.org/13154622:02
*** jeromatron has quit IRC22:06
*** jeromatron has joined #magnetodb22:07
*** denis_makogon_ has quit IRC22:08
*** jeromatron has quit IRC22:13
*** charlesw has joined #magnetodb23:40

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!