*** rushiagr is now known as rushiagr_away | 00:20 | |
*** charlesw has joined #magnetodb | 01:10 | |
*** vnaboychenko has quit IRC | 01:41 | |
*** vnaboychenko has joined #magnetodb | 02:21 | |
*** charlesw has quit IRC | 03:47 | |
*** jeromatron has joined #magnetodb | 04:14 | |
*** vnaboychenko has quit IRC | 04:15 | |
*** jeromatron has quit IRC | 05:25 | |
*** jeromatron has joined #magnetodb | 05:25 | |
*** rushiagr_away is now known as rushiagr | 05:29 | |
*** jeromatron has quit IRC | 05:32 | |
*** vivekd has joined #magnetodb | 06:11 | |
*** rushiagr is now known as rushiagr_away | 08:27 | |
*** k4n0 has joined #magnetodb | 08:28 | |
*** rushiagr_away is now known as rushiagr | 08:39 | |
*** romainh has joined #magnetodb | 08:43 | |
*** ajayaa has joined #magnetodb | 08:46 | |
openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: Moves passing tempest tests to stable directory https://review.openstack.org/131464 | 09:43 |
---|---|---|
*** vivekd has quit IRC | 09:46 | |
*** vivekd has joined #magnetodb | 09:47 | |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Forbid PUT and DELETE of same item in batch write https://review.openstack.org/131384 | 09:49 |
*** ajayaa has quit IRC | 10:34 | |
isviridov | Hello everybody | 10:34 |
*** rushiagr is now known as rushiagr_away | 10:39 | |
openstackgerrit | A change was merged to stackforge/magnetodb-specs: Cassandra implementation of monitoring api https://review.openstack.org/130801 | 10:39 |
ominakov | isviridov, hello | 10:55 |
isviridov | ominakov : hey | 10:55 |
isviridov | ominakov : great job http://magnetodb-specs.readthedocs.org/en/latest/ | 10:56 |
isviridov | !m ominakov | 10:56 |
[o__o] | You're doing good work, ominakov! | 10:56 |
openstack | isviridov: Error: "m" is not a valid command. | 10:56 |
isviridov | achudnovets : around? | 10:56 |
isviridov | ominakov : are you working on monitoring of Cassandra? | 10:59 |
isviridov | I mean is it you or achudnovets. Becauseaccording to API specs we have to updated implementation with support metric names | 11:00 |
ominakov | isviridov, yep, now i'am updating documentation and i think i'll can update implementation (because achudnovets is ill now) | 11:02 |
ominakov | isviridov, what do you think about this? | 11:02 |
isviridov | ominakov : sounds great! | 11:03 |
*** ajayaa has joined #magnetodb | 11:06 | |
*** ajaya has joined #magnetodb | 11:07 | |
*** boris-42 has quit IRC | 11:11 | |
isviridov | Hello ajaya | 11:12 |
ajaya | Hi isviridov. | 11:15 |
*** ajaya has quit IRC | 11:16 | |
*** ajaya has joined #magnetodb | 11:16 | |
isviridov | ajaya : how was your festival? | 11:20 |
ajaya | isviridov, It was awesome. :) | 11:20 |
ajaya | How did you know it was a festival? | 11:20 |
isviridov | rushiagr said me | 11:21 |
ajaya | isviridov, okay. | 11:21 |
isviridov | I wanted to talk to your about integration with celiometer | 11:22 |
isviridov | Do you have some time? | 11:22 |
ajaya | isviridov, yes. | 11:22 |
openstackgerrit | A change was merged to stackforge/magnetodb: Additional validation; UUIDs as internal table names https://review.openstack.org/125445 | 11:22 |
* isviridov trying to find patch with spec | 11:23 | |
isviridov | Yeap, here it is https://review.openstack.org/#/c/126335/ | 11:24 |
*** rushiagr_away is now known as rushiagr | 11:25 | |
ajaya | isviridov, When I proposed that spec, I thought metering is going to be done by sending notifications to ceilometer. | 11:25 |
isviridov | I've looked at it, and have several suggestions, but first it is only about notifications processing, what about polster driven implementation? | 11:25 |
isviridov | ajaya : aha do you think different now? | 11:26 |
ajaya | isviridov, Yes. | 11:27 |
ajaya | If for each api call a notification is generated, then we will overwhelm message bus and ceilometer also. | 11:27 |
ajaya | isviridov, For pollster driven implementation, I need to talk to ceilometer team. | 11:28 |
isviridov | Ok, great to know that we are on the same page now. | 11:28 |
isviridov | However, I would suggest splitting the integration into two parts, as far as polster driven implementation should be agreed in advance. | 11:28 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Forbid PUT and DELETE of same item in batch write https://review.openstack.org/131384 | 11:29 |
ajaya | Can you please tell me what you have in mind for these two parts? | 11:29 |
isviridov | Now I see that we can monitor table count per tenant (table crete/delete events) via notifications. | 11:31 |
ajaya | isviridov, +1 | 11:32 |
isviridov | Also we have 2 other metrics for now - table size and count items in table. It will be exposed via monitoring api | 11:33 |
isviridov | Here it is http://magnetodb-specs.readthedocs.org/en/latest/specs/kilo/approved/monitoring-api.html | 11:33 |
isviridov | The implementation for C* is on its way | 11:34 |
isviridov | Here I think the polster approach would be better. | 11:34 |
ajaya | isviridov, We will need a pollster implementation to send data from monitoring api to ceilometer. | 11:34 |
ajaya | +1 | 11:34 |
isviridov | ajaya : actually to poll data by celiometer from mdb monitoring api | 11:35 |
ajaya | isviridov, okay. | 11:36 |
ajaya | There are a lot of other metrics which will be collected by various daemons. | 11:37 |
ajaya | Where do you plan to store them?. | 11:37 |
isviridov | What daemons do you mean? | 11:37 |
ajaya | isviridov, Something like cpu load, network IO measured by daemons. | 11:39 |
isviridov | ajaya : why do we need it in celiometer? | 11:39 |
ajaya | isviridov, Do you think only table count and bytes used by a table are sufficient for metering and billing? | 11:40 |
isviridov | What I mean to say, mdb is service and internal state of infrastructure shouldn't be exposed to user. | 11:41 |
ajaya | isviridov, agree. | 11:41 |
isviridov | I think we have to extend the list, but wil meaninful data, granulated by user/project/tenant | 11:42 |
ajaya | isviridov, We need to measure the request count and bytes scanned per request etc. | 11:42 |
isviridov | So, technically it likely will be internal mdb counters, than infrastructure monitoring. | 11:42 |
openstackgerrit | Oleksandr Minakov proposed a change to stackforge/magnetodb: Adds documentation on monitoring API https://review.openstack.org/131165 | 11:42 |
ajaya | isviridov, Yes. We can maintain an internal counter and ceilometer could se it. | 11:43 |
ajaya | *use it. | 11:43 |
isviridov | ajaya : yes. Do you have a list came from your/your customer/your company usecases? | 11:44 |
isviridov | Here it is for Symantec https://docs.google.com/a/mirantis.com/spreadsheets/d/1tYvgCSvkcOVED46MX8qSlUyrhNhHlyTrVkX7AXP-XR4/edit#gid=0 | 11:44 |
ajaya | isviridov, I don't have a list. This document came up in one of the weekly meetings. | 11:45 |
isviridov | Just look at Data destination = Ceilometer/Billing solution | 11:45 |
isviridov | ajaya : yeap, but in order to imlement anythin it is needed to see the priorities first. And I personally believe the best way to set the priorities is to listen to users :) | 11:46 |
ajaya | isviridov, +1 | 11:47 |
isviridov | Ok, what are your plans about ceilo+mdb? | 11:48 |
ajaya | isviridov, Notifications are easy to implement and I have an idea of what to do in ceilometer. | 11:49 |
ajaya | I need to check with ceilometer guys for pollster driven implementation. | 11:50 |
isviridov | ajaya : Let me do it myself first, I believe it would be easier for me. | 11:51 |
isviridov | I mean before sharing the idea to ceilo community, it would be nide to discuss it pesonally to make it better and easier accepted | 11:52 |
isviridov | * nice | 11:52 |
ajaya | isviridov, okay. I am fine with it. :) | 11:52 |
ajaya | You have Dina Belova in mirantis who is ceilometer core. :) | 11:53 |
isviridov | I would suggest you finish with spec and update the blueprint as well https://blueprints.launchpad.net/ceilometer/+spec/support-magnetodb. With clear pointing to notifications | 11:53 |
isviridov | ajaya : yeap | 11:53 |
ajaya | isviridov, I will update the spec. I think for now we will be catching table creation and deletion notifications in ceilometer. | 11:55 |
isviridov | Yes. | 11:55 |
ajaya | isviridov, Also number of indices could be inferred from the schema. | 11:56 |
isviridov | ajaya : you are right, we can publish it to notification message as well | 11:57 |
ajaya | isviridov, The schema is being published right now in notifications. | 11:57 |
isviridov | Technically it doesn't affec anything for now, but it is important as API itself | 11:57 |
isviridov | ajaya : great catch! | 11:58 |
* isviridov have not looked at this part for a long time | 11:58 | |
ajaya | http://paste.openstack.org/show/126446/ | 11:59 |
ajaya | Here is sample of notification emitted while creating a table. | 12:00 |
isviridov | 10x | 12:01 |
isviridov | BTW we have UUID for each table, internally now https://review.openstack.org/#/c/125445/ | 12:01 |
ajaya | isviridov, I saw that. Great. | 12:02 |
isviridov | Looking forward to seeing your spec update to join the discussion | 12:05 |
*** isviridov changes topic to "MagnetoDB - key-value store for OpenStack (https://wiki.openstack.org/wiki/MagnetoDB, logs @ https://botbot.me/freenode/magnetodb/) | Our Kilo OpenStack summit design session http://goo.gl/czt5mL| ask isviridov is any Qs" | 12:07 | |
ajaya | isviridov, The design session link is broken. ;) | 12:10 |
*** isviridov changes topic to "MagnetoDB - key-value store for OpenStack (https://wiki.openstack.org/wiki/MagnetoDB, logs @ https://botbot.me/freenode/magnetodb/) | Our Kilo OpenStack summit design session http://goo.gl/czt5mL | ask isviridov is any Qs" | 12:10 | |
isviridov | Thx. Just one space missed | 12:10 |
isviridov | ajaya : BTW welcome to resiter and like, tweet :) | 12:11 |
*** isviridov is now known as isviridov_away | 12:32 | |
*** vivekd has quit IRC | 13:07 | |
*** charlesw has joined #magnetodb | 13:21 | |
openstackgerrit | Igor Degtiarov proposed a change to stackforge/magnetodb-specs: Migration to pecan https://review.openstack.org/131764 | 13:25 |
*** jeromatron has joined #magnetodb | 13:34 | |
*** rushiagr is now known as rushiagr_away | 13:47 | |
*** jeromatron has quit IRC | 13:52 | |
*** jeromatron has joined #magnetodb | 14:07 | |
openstackgerrit | Igor Degtiarov proposed a change to stackforge/magnetodb-specs: Migration to pecan https://review.openstack.org/131764 | 14:08 |
isviridov_away | !m idegtiarov | 14:25 |
[o__o] | You're doing good work, idegtiarov! | 14:25 |
openstack | isviridov_away: Error: "m" is not a valid command. | 14:25 |
*** ikhudoshyn has left #magnetodb | 14:29 | |
openstackgerrit | Igor Degtiarov proposed a change to stackforge/magnetodb-specs: Migration to pecan https://review.openstack.org/131764 | 14:37 |
*** jeromatron has quit IRC | 14:45 | |
*** jeromatron has joined #magnetodb | 15:01 | |
*** rushiagr_away is now known as rushiagr | 15:08 | |
*** ikhudoshyn has joined #magnetodb | 15:13 | |
ikhudoshyn | https://review.openstack.org/#/c/131384/ guys pls review | 15:14 |
*** miqui has joined #magnetodb | 15:17 | |
isviridov_away | ikhudoshyn : will do | 15:20 |
*** isviridov_away is now known as isviridov | 15:20 | |
isviridov | Hello miqui, how are you today? | 15:21 |
openstackgerrit | Igor Degtiarov proposed a change to stackforge/magnetodb-specs: Migration to pecan https://review.openstack.org/131764 | 15:30 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Forbid multiple operations with an item in batch write https://review.openstack.org/131384 | 15:38 |
*** keith_newstadt has joined #magnetodb | 15:41 | |
*** ajaya has quit IRC | 15:49 | |
*** keith_newstadt has quit IRC | 15:49 | |
openstackgerrit | Dmitriy Ukhlov proposed a change to stackforge/magnetodb: Add Forbidden exception https://review.openstack.org/131807 | 15:53 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Forbid multiple operations with an item in batch write https://review.openstack.org/131384 | 15:54 |
*** k4n0 has quit IRC | 16:03 | |
openstackgerrit | Nuno Santos proposed a change to stackforge/magnetodb: Record and retrieve table creation timestamp https://review.openstack.org/131546 | 16:25 |
*** keith_newstadt has joined #magnetodb | 16:53 | |
*** jeromatron has quit IRC | 16:56 | |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Forbid multiple operations with an item in batch write https://review.openstack.org/131384 | 16:57 |
openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: Moves passing tempest tests to stable directory https://review.openstack.org/131464 | 17:13 |
*** jeromatron has joined #magnetodb | 17:16 | |
*** denis_makogon has joined #magnetodb | 17:28 | |
*** jeromatron has quit IRC | 17:29 | |
*** jeromatron has joined #magnetodb | 17:30 | |
*** jeromatron has quit IRC | 17:32 | |
isviridov | ominakov : do you have ability to set bug status as triaged now? | 17:38 |
ominakov | isviridov, nope | 17:40 |
isviridov | ominakov : please try now | 17:40 |
*** jeromatron has joined #magnetodb | 17:41 | |
ominakov | isviridov, yes, all set | 17:42 |
*** denis_makogon has left #magnetodb | 17:42 | |
isviridov | ominakov : welcome to bug supervisor group | 17:43 |
*** jeromatron has quit IRC | 17:43 | |
isviridov | ominakov : you know, I've also set tags ux and data-api to each bug you have mentioned | 17:43 |
isviridov | ominakov : what about this one https://bugs.launchpad.net/magnetodb/+bug/1347722 ? | 17:44 |
isviridov | Is it actual? | 17:44 |
*** jeromatron has joined #magnetodb | 17:45 | |
ominakov | isviridov, i'll check it | 17:46 |
*** jeromatron has quit IRC | 17:47 | |
isviridov | ominakov : got you. Thanks for info | 17:47 |
*** keith_newstadt has quit IRC | 17:50 | |
*** keith_newstadt has joined #magnetodb | 17:50 | |
*** isviridov is now known as isviridov_away | 17:51 | |
*** miqui has quit IRC | 17:56 | |
*** keith_newstadt has quit IRC | 18:02 | |
*** jeromatron has joined #magnetodb | 18:07 | |
*** romainh has quit IRC | 18:09 | |
*** ajayaa has quit IRC | 19:07 | |
*** rushiagr is now known as rushiagr_away | 19:10 | |
openstackgerrit | Nuno Santos proposed a change to stackforge/magnetodb: Document errors and exceptions for REST API https://review.openstack.org/131857 | 19:14 |
*** jeromatron has quit IRC | 19:19 | |
*** jeromatron has joined #magnetodb | 19:32 | |
*** jeromatron has quit IRC | 19:35 | |
*** romainh has joined #magnetodb | 19:59 | |
*** jeromatron has joined #magnetodb | 20:22 | |
-openstackstatus- NOTICE: Restarting gerrit to get fixed CI javascript | 20:56 | |
*** openstackgerrit has quit IRC | 21:50 | |
*** charlesw has quit IRC | 22:15 | |
*** romainh has left #magnetodb | 23:08 | |
*** jeromatron has quit IRC | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!