*** charlesw has joined #magnetodb | 02:01 | |
*** openstackgerrit has quit IRC | 02:01 | |
*** openstackgerrit has joined #magnetodb | 02:22 | |
*** vnaboychenko has quit IRC | 03:43 | |
*** charlesw has quit IRC | 03:53 | |
*** vnaboychenko has joined #magnetodb | 04:20 | |
*** k4n0 has joined #magnetodb | 04:46 | |
*** rushiagr_away is now known as rushiagr | 05:16 | |
openstackgerrit | Ajaya Agrawal proposed a change to stackforge/magnetodb: Added debug env to tox https://review.openstack.org/120873 | 06:10 |
---|---|---|
openstackgerrit | Ajaya Agrawal proposed a change to stackforge/magnetodb: Added debug env to tox https://review.openstack.org/120873 | 06:12 |
*** ajayaa has joined #magnetodb | 06:15 | |
openstackgerrit | Oleksandr Minakov proposed a change to stackforge/magnetodb: (WIP) Adds table size in monitoring API https://review.openstack.org/122330 | 06:16 |
*** vnaboychenko has quit IRC | 06:40 | |
openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: (WIP) "ALL_OLD" return_values for put_item https://review.openstack.org/121911 | 07:41 |
*** k4n0 has quit IRC | 08:37 | |
*** k4n0 has joined #magnetodb | 08:52 | |
*** k4n0 has quit IRC | 09:22 | |
*** k4n0 has joined #magnetodb | 09:34 | |
*** charlesw has joined #magnetodb | 10:59 | |
openstackgerrit | Dmitriy Ukhlov proposed a change to stackforge/magnetodb: Use by default TokenAwarePolicy https://review.openstack.org/122389 | 11:04 |
ajayaa | Hi charlesw! | 11:15 |
ajayaa | charlesw, I enabled notification to rabbitmq through config file. While importing magneto.common.notifier.rpc_notifier it throws an import error. | 11:17 |
openstackgerrit | Dmitriy Ukhlov proposed a change to stackforge/magnetodb: Use by default TokenAwarePolicy https://review.openstack.org/122389 | 11:18 |
ajayaa | That is a run time error and occurs at magnetodb/openstack/common/notifier/api.py(162) | 11:18 |
ajayaa | I think you have forgotten to add __init__.py in magnetodb / magnetodb / common / notifier/ | 11:19 |
ajayaa | After adding a __init__.py file it runs fine. | 11:20 |
openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: (WIP) "ALL_OLD" return_values for put_item https://review.openstack.org/121911 | 11:21 |
ajayaa | Hi all. Am I missing something? Has anyone tried it and didn't face a problem? | 11:22 |
charlesw | ajayaa, integration with rabbitmq or other messaging broker has not been verified. I'll take a look. | 11:26 |
ajayaa | charlesw, I was just doint that and found out that adding __init__.py in magnetodb/commom/notifier/ it runs fine. | 11:27 |
ajayaa | charlesw, Shall I go ahead and file a bug about it? | 11:28 |
charlesw | yes please | 11:28 |
*** charlesw has quit IRC | 11:33 | |
*** vnaboychenko has joined #magnetodb | 11:51 | |
*** k4n0 has quit IRC | 12:01 | |
*** rushiagr is now known as rushiagr_away | 12:14 | |
*** rushiagr_away is now known as rushiagr | 12:24 | |
*** vnaboychenko has quit IRC | 12:37 | |
isviridov | Hello everybody | 12:55 |
isviridov | ajayaa, thank you for checking the notifications, please paste the link to bug here as well | 12:56 |
ajayaa | isviridov, https://bugs.launchpad.net/magnetodb/+bug/1371070 | 12:57 |
ajayaa | np. | 12:57 |
achuprin_ | Hi everyone! | 12:57 |
isviridov | Hey achuprin_ | 12:57 |
isviridov | Is ominakov- around? | 12:57 |
ominakov- | Hi guys! | 12:58 |
achuprin_ | Hi ominakov- | 12:58 |
isviridov | Hi ominakov- , just wanted to make sure you are here :) | 12:58 |
achudnovets | hi guys! | 12:59 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Add queued storage manager https://review.openstack.org/122404 | 12:59 |
ajayaa | Hi everyone! | 12:59 |
isviridov | Looks like everybody are joining for weekly meeting. | 12:59 |
isviridov | It is taking place in #openstack-meetings | 12:59 |
isviridov | * -meeting | 13:00 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: (WIP)Add queued storage manager https://review.openstack.org/122404 | 13:01 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: (WIP)Add queued storage manager https://review.openstack.org/122404 | 13:02 |
*** keith_newstadt has joined #magnetodb | 13:03 | |
*** miarmak has joined #magnetodb | 13:05 | |
*** miarmak has quit IRC | 13:09 | |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: (WIP)Add queued storage manager https://review.openstack.org/122404 | 13:10 |
*** charlesw has joined #magnetodb | 13:15 | |
openstackgerrit | Aleksey Chuprin proposed a change to stackforge/magnetodb: Edited function fix_etc_hosts https://review.openstack.org/122228 | 13:19 |
*** charlesw has quit IRC | 13:24 | |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: (WIP)Add queued storage manager https://review.openstack.org/122404 | 13:25 |
openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: (WIP) "ALL_OLD" return_values for put_item https://review.openstack.org/121911 | 13:31 |
*** charlesw has joined #magnetodb | 13:40 | |
rushiagr | keith_newstadt: I wanted to know what MDB team is planning to use for cassandra provisioning, managing and scaling | 14:00 |
*** ajayaa has quit IRC | 14:00 | |
rushiagr | I don't want to walk the path which is different from what the MDB community is trying to go | 14:00 |
rushiagr | or are we leaving this question out of mdb completely? | 14:01 |
keith_newstadt | i think we should approach the subject of deployment the same way other openstack projects do, e.g. swift or nova | 14:02 |
keith_newstadt | at symantec, we'd ultimately like to be using heat for all our deployment | 14:02 |
keith_newstadt | also, i don't think mdb should be implemented specifically to scaling and managing cassandra | 14:03 |
keith_newstadt | as it will be possible to run mbd on top of other database technologies | 14:04 |
isviridov | rushiagr, we will try reuse trove if possible, but only for deployments within tenant | 14:04 |
rushiagr | keith_newstadt: okay, directly heat versus trove managed (which might internally use heat for scaling) | 14:04 |
rushiagr | keith_newstadt: I agree with that | 14:05 |
rushiagr | keith_newstadt: and yes, when we'll go for an incubation request, we will be asked how many backends (databases)we support, etc | 14:05 |
rushiagr | keith_newstadt: my only concern is an example I found out on AWS's DynamoDB page | 14:05 |
rushiagr | keith_newstadt: say a customer wants to migrate to mdb, in the first couple hours, he'll dump his gigabytes of data into mdb | 14:06 |
rushiagr | and after that, he'll use MDB for a mostly-read-heavy load | 14:06 |
rushiagr | in this case, heat autoscaling won't work... | 14:07 |
rushiagr | oh, are we just saying that scaling, or autoscaling is better to be kept completely out of mdb? | 14:07 |
achudnovets | rushiagr: why autoscaling won't work? | 14:07 |
keith_newstadt | sorry, guys, i have to join my next meeting | 14:08 |
rushiagr | achudnovets: because load is not showing a predictable pattern | 14:08 |
keith_newstadt | i'll catch up in a bit... | 14:08 |
rushiagr | keith_newstadt: no issues. Sure. | 14:08 |
rushiagr | keith_newstadt: I'll be leaving soon too, but please write your opinion when you come back. I'll read it when I come back | 14:08 |
isviridov | rushiagr, IMO autoscaling for database can be risky thing and effect the SLA dramatically | 14:08 |
isviridov | rushiagr, that is why C* management and deployment is out of scope for now. | 14:09 |
rushiagr | isviridov: well, not right now, but eventually we'll need to I guess | 14:09 |
rushiagr | isviridov: I agree with you, C* management can, and should be left completely out of mdb | 14:09 |
rushiagr | isviridov: what is the problem with trove and single tenant? | 14:12 |
achudnovets | rushiagr: partially agree. You can provide your own scaling metric, based on C* stats for example. But I totally agree with isviridov about autoscaling DBs :) | 14:12 |
*** ikhudoshyn_ is now known as ikhudoshyn | 14:13 | |
*** ominakov- is now known as ominakov | 14:13 | |
rushiagr | achudnovets: okay. I'll think about autoscaling more | 14:14 |
rushiagr | so mdb is not going to worry about managing C* nodes, am I right? | 14:14 |
isviridov | rushiagr, yeap | 14:15 |
achudnovets | +1 for not worry about managing C* nodes | 14:15 |
rushiagr | isviridov: okay. Just wanted to know mdb's stance, so that we can make our decisions based on that | 14:15 |
rushiagr | isviridov: achudnovets: thanks for the input | 14:15 |
isviridov | rushiagr, always wellcome | 14:16 |
rushiagr | isviridov: :) | 14:16 |
isviridov | * welcome | 14:16 |
achudnovets | rushiagr: thanks for good questions and notes :) | 14:16 |
rushiagr | achudnovets: :) | 14:17 |
rushiagr | see you people around tomorrow. Bye for now :) | 14:24 |
isviridov | rushiagr, see you | 14:24 |
charlesw | Sorry missed the party. It was not on my calendar somehow. | 14:26 |
charlesw | C* auto scaling is a big topic by itself. +1 for leaving it out of MDB. | 14:27 |
isviridov | charlesw, hello. Here is meeting minutes http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-09-18-13.01.html | 14:28 |
charlesw | Netflix has done some work on it. They have a project called Priam | 14:28 |
rushiagr | charlesw: yeah, right | 14:28 |
rushiagr | charlesw: it was delightful to see them trying out their comprehensive tests in just about two hours, and shutting off everything else right after that :) | 14:29 |
charlesw | https://github.com/Netflix/Priam | 14:29 |
rushiagr | charlesw: thanks for the link. Seems they've done pretty comprehensive study of cassandra-on-cloud | 14:31 |
charlesw | Even though Priam is for AWS, I wonder if it can be adapted to work in OpenStack | 14:31 |
charlesw | Thanks isviridov. I saw the topic on get item count and table size. I believe C* doesn't maintain such numbers. You can only get ballpark figures. Will wait for ominakov's reaserch. | 14:34 |
rushiagr | charlesw: I think I'll have a look at Priam, study in some detail | 14:51 |
*** vnaboychenko has joined #magnetodb | 14:51 | |
charlesw | rushiagr: thanks, please share any findings/comments | 14:52 |
rushiagr | charlesw: sure I will | 14:52 |
rushiagr | but not today. See ya'll tomorrow | 14:52 |
charlesw | rushiagr: sure, see you | 14:54 |
*** rushiagr is now known as rushiagr_away | 14:56 | |
*** keith_newstadt has quit IRC | 14:57 | |
ikhudoshyn | https://wiki.openstack.org/wiki/MagnetoDB/specs/async-schema-operations | 14:59 |
*** vnaboychenko has quit IRC | 15:01 | |
*** keith_newstadt has joined #magnetodb | 15:03 | |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: (WIP)Add queued storage manager https://review.openstack.org/122404 | 15:05 |
openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Add queued storage manager https://review.openstack.org/122404 | 15:27 |
openstackgerrit | Dmitriy Ukhlov proposed a change to stackforge/magnetodb: Improve json schema validation for left requests https://review.openstack.org/122445 | 15:28 |
achudnovets | charlesw: btw, my congratulations :)! | 15:31 |
*** openstackgerrit has quit IRC | 15:33 | |
charlesw | Thanks! You guys have been very helpful. | 15:44 |
*** openstackgerrit has joined #magnetodb | 16:03 | |
openstackgerrit | A change was merged to stackforge/magnetodb: Use by default TokenAwarePolicy https://review.openstack.org/122389 | 16:22 |
openstackgerrit | A change was merged to stackforge/magnetodb: Fixes bug with scan on hash key attribute https://review.openstack.org/120654 | 16:26 |
*** vnaboychenko has joined #magnetodb | 16:47 | |
*** jeromatron has joined #magnetodb | 16:57 | |
*** jeromatron has quit IRC | 17:05 | |
*** jeromatron has joined #magnetodb | 17:08 | |
*** jeromatron has quit IRC | 17:18 | |
*** jeromatron has joined #magnetodb | 17:20 | |
*** jeromatron has quit IRC | 17:22 | |
*** jeromatron has joined #magnetodb | 17:25 | |
*** openstackgerrit has quit IRC | 17:31 | |
*** openstackgerrit has joined #magnetodb | 17:33 | |
*** jeromatron has quit IRC | 17:35 | |
*** jeromatron has joined #magnetodb | 17:35 | |
*** jeromatron has quit IRC | 17:37 | |
*** jeromatron has joined #magnetodb | 17:41 | |
*** jeromatron has quit IRC | 17:45 | |
*** jeromatron has joined #magnetodb | 17:46 | |
*** rushiagr_away is now known as rushiagr | 17:46 | |
*** jeromatron has quit IRC | 17:50 | |
*** keith_newstadt has quit IRC | 17:50 | |
*** jeromatron has joined #magnetodb | 17:53 | |
*** rushiagr is now known as rushiagr_away | 18:03 | |
*** rushiagr_away is now known as rushiagr | 18:15 | |
*** rushiagr is now known as rushiagr_away | 18:20 | |
*** rushiagr_away is now known as rushiagr | 18:20 | |
*** rushiagr is now known as rushiagr_away | 18:40 | |
*** rushiagr_away is now known as rushiagr | 18:49 | |
*** jeromatron has quit IRC | 18:58 | |
*** rushiagr is now known as rushiagr_away | 18:58 | |
*** jeromatron has joined #magnetodb | 19:00 | |
*** jeromatron has quit IRC | 19:24 | |
*** jeromatron has joined #magnetodb | 19:26 | |
*** openstackgerrit has quit IRC | 19:45 | |
*** jeromatron has quit IRC | 20:29 | |
*** jeromatron has joined #magnetodb | 20:31 | |
*** jeromatron has quit IRC | 20:53 | |
*** jeromatron has joined #magnetodb | 21:01 | |
*** openstackgerrit has joined #magnetodb | 21:09 | |
*** charlesw has quit IRC | 21:34 | |
*** charlesw has joined #magnetodb | 22:49 | |
*** jeromatron has quit IRC | 23:07 | |
*** jeromatron has joined #magnetodb | 23:07 | |
*** jeromatron has quit IRC | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!