Thursday, 2014-11-20

« Wednesday, 2014-11-19 Index Friday, 2014-11-21 »
*** nunosantos has joined #magnetodb00:26
*** charlesw has joined #magnetodb01:39
*** vnaboychenko has quit IRC02:10
*** charlesw has quit IRC02:23
*** rushiagr_away is now known as rushiagr03:27
*** charlesw has joined #magnetodb03:30
*** rushiagr is now known as rushiagr_away03:53
*** nunosantos has quit IRC04:06
*** charlesw has quit IRC04:20
*** vnaboychenko has joined #magnetodb04:26
*** rushiagr_away is now known as rushiagr04:33
*** vnaboychenko has quit IRC04:33
*** vnaboych_ has joined #magnetodb04:33
*** vivekd has joined #magnetodb04:47
*** ajayaa has joined #magnetodb05:57
*** vivekd has quit IRC06:02
*** vivekd has joined #magnetodb06:15
*** k4n0 has joined #magnetodb06:33
*** romainh has joined #magnetodb07:15
*** vnaboych_ has quit IRC08:03
*** vnaboychenko has joined #magnetodb11:04
*** vnaboychenko has quit IRC11:08
openstackgerritDmitriy Ukhlov proposed stackforge/magnetodb: (DRAFT)Add cassandra custom secondary index to code base  https://review.openstack.org/10750012:02
*** rushiagr is now known as rushiagr_away12:15
*** rushiagr_away is now known as rushiagr12:46
openstackgerritIlya Sviridov proposed stackforge/magnetodb: Cleaning up C* on unstack.sh  https://review.openstack.org/13559312:55
isviridovHello everybody13:30
isviridovJust a remind we have a weekly meeting in 30 mins13:30
isviridovHere it agenda https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Nov_20.2C_2014.2C_14:00_UTC13:30
*** k4n0 has quit IRC13:38
*** keith_newstadt has joined #magnetodb13:43
*** miqui has joined #magnetodb13:46
*** nunosantos has joined #magnetodb13:49
*** miqui_ has joined #magnetodb13:50
*** keith_newstadt has quit IRC13:50
*** keith_newstadt has joined #magnetodb13:51
*** miqui__ has joined #magnetodb13:52
*** ajayaa has quit IRC13:53
*** miqui___ has joined #magnetodb13:54
*** achuprin_ has joined #magnetodb13:54
isviridovmiqui_ : miqui__ miqui miqui___ hello13:54
* isviridov a lot of clients13:55
*** miqui____ has joined #magnetodb13:55
*** miqui_____ has joined #magnetodb13:55
nunosantosisviridov: you spoke too soon ;-)13:56
*** miqui___ has quit IRC13:56
*** miqui___ has joined #magnetodb13:57
achuprin_Hi team!13:57
isviridovachuprin : hello13:58
*** miqui__ has quit IRC13:58
*** miqui has quit IRC13:58
*** miqui____ has quit IRC13:58
*** miqui_ has quit IRC13:58
*** miqui___ has quit IRC13:58
*** rushiagr is now known as rushiagr_away13:59
*** miqui has joined #magnetodb13:59
ikhudoshyno/14:00
isviridov#startmeeting magnetodb14:00
openstackMeeting started Thu Nov 20 14:00:30 2014 UTC and is due to finish in 60 minutes.  The chair is isviridov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
openstackThe meeting name has been set to 'magnetodb'14:00
isviridovHello everybody14:00
nunosantoso/14:00
isviridovnunosantos : o/14:01
dukhlov_o/14:01
achuprin_o/14:01
isviridovmiqui : miqui_____ welcome to mdb weekly meeting14:01
ikhudoshyndukhlov works as a traffic regulator14:01
dukhlov_o_|14:02
miqui_____hello14:02
miqui_____sorry had some irc client uissues on my side..14:02
isviridovmiqui_____ : have we meet each other on summit?14:02
miqui_____i was in april 2014 atlanta summit14:02
isviridovToday agenda #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Agenda14:03
miqui_____your nick seems familiar somehow..14:03
isviridovmiqui_____ : welcome back if so :)14:03
miqui_____..thanks...14:03
isviridovLet us start from action items14:04
isviridov#topic Go through action items isviridov14:04
isviridov#link http://eavesdrop.openstack.org/meetings/isviridov/2014/isviridov.2014-11-13-14.01.html14:04
isviridovACTION: dukhlov data encryption support blueprint14:04
dukhlovhm14:05
* isviridov good start14:05
dukhlovspecification for this blueprint is under review now14:05
isviridov#link https://review.openstack.org/#/c/134936/14:06
isviridov#link https://review.openstack.org/#/c/133505/14:06
dukhlovI got -1 from isviridov, but there were only grammar mistakes14:06
*** ajayaa has joined #magnetodb14:06
dukhlovI'm waiting for other feedback14:07
*** rushiagr_away is now known as rushiagr14:07
isviridovdukhlov : I was a bit surprised that we have the general one. I mean - Specification for data-encryption-support. Do you think we need it?14:07
*** charlesw has joined #magnetodb14:08
isviridovcharlesw : hello14:09
dukhlovok, for encryption support we need to have implemented at least part of management API14:09
charleswHi14:09
rushiagr o/14:09
isviridovhi rushiagr14:09
ajayaaHi everyone.14:09
isviridovhello ajayaa14:10
dukhlovso I added sub smaller blueprint - part of management API for encryption and set it as dependency for encryption support blueprint14:10
isviridovcharlesw : rushiagr ajayaa discussing https://review.openstack.org/#/c/134936/14:11
isviridovdukhlov : ok. I think we have to link them during merge14:11
isviridovdukhlov : great job!14:12
dukhlovas you wish14:12
isviridovOk, let us move to next item14:12
isviridovACTION: ikhudoshyn file a bug about dynamodb version support documentation14:12
ikhudoshyndone14:12
ikhudoshynhttps://bugs.launchpad.net/magnetodb/+bug/139457514:13
isviridovikhudoshyn : yes, I've seen. Great14:13
isviridovOk, we have 2 other topics to discuss14:14
isviridovACTION: keith_newstadt isviridov ikhudoshyn clarify if we can avoid having two different apis for db backup/restore inside of openstack14:14
*** miqui has quit IRC14:14
isviridovACTION: keith_newstadt isviridov ikhudoshyn clarify if we can avoid having two different implementations of that api14:14
*** miqui has joined #magnetodb14:14
isviridovLet us do it together with bp discussion14:14
ominakovsorry guys, i'm late14:14
isviridov#topic Discuss Backup/restore API specification draft https://review.openstack.org/#/c/133933/ ikhudoshyn14:15
*** miqui_ has joined #magnetodb14:15
ikhudoshynit hangs for couple weeks yet14:15
ikhudoshynonly small amount of comments arise14:15
ikhudoshyni tried to address all of them14:16
isviridov#link http://docs-draft.openstack.org/33/133933/12/check/gate-magnetodb-specs-docs/e0b7b92/doc/build/html/specs/kilo/approved/backup-restore-api.html for easier reading14:16
*** miqui_ has quit IRC14:17
ajayaaisviridov, that is helpful.14:17
*** keith_newstadt has quit IRC14:17
*** keith_newstadt has joined #magnetodb14:17
charleswduring backup/restore, shouldn't the tenant/table be locked?14:18
ikhudoshynwe don't see any general reason14:19
ikhudoshynit may still be required for some implementations of backup14:19
ikhudoshynsome of us thought about exporting data in json format as the 1st approach14:20
ikhudoshynwe dont seem to need any loking in that case14:20
ikhudoshyn* locking14:20
isviridovikhudoshyn : but, I believe, all others will need it and it affects usage scenario. Do you think that we have to describe teh locking process within this spec?14:22
ikhudoshynnot in *that* spec since it only describes API14:22
ikhudoshyni'd prefer not to manage table/tenant locking manually14:23
charleswWe should document it so we can manage user expectations whether locking is used or not14:23
ikhudoshyncharlesw: somewhere..14:24
charleswok, preferably at API level14:24
isviridovikhudoshyn: as API Impact section  if any is expected14:25
ikhudoshynas I said i'd rather not to lock it manually -- so we could just add new tables status, like MAINTENANCE14:25
ajayaaikhudoshyn, +114:27
charlesw+114:27
isviridovikhudoshyn : does it mean the users requests will be rejected if table is in this status?14:27
miqui_____..that would de3pend of the use case..14:28
ikhudoshynyep.. i thought about 40314:28
ikhudoshynguess there should be more suitable err code14:28
miqui_____1 - hey here your latest snapshot http 20014:28
miqui_____2 - or simply 40314:28
ikhudoshynnot sure latest snapshot is always available14:28
isviridovikhudoshyn +1, also for writing as well14:29
charlesw503 Service Unavailable may be more appropriate14:29
miqui_____hmm good point...if that is the case then 50314:29
ikhudoshyncharlesw: we might think more..14:30
ikhudoshynactually it is not the whole service that is unavailable..14:30
isviridov#idea  we could just add new tables status, like MAINTENANCE14:30
ajayaa423 Locked14:30
ajayaa?14:30
ikhudoshynajayaa: exactly14:31
ikhudoshyntnx14:31
isviridov#idea 423 Locked on request during backup14:31
ikhudoshyn* when in MAINTENANCE status14:31
ikhudoshynnot necessary for every backup14:32
isviridovikhudoshyn : +114:32
isviridovikhudoshyn : charlesw ajayaa miqui_____ move on?14:33
ajayaa+114:33
ikhudoshynagree, I'm just waiting for yr +/1's14:33
ikhudoshyn* +/-1's14:33
isviridovikhudoshyn : you will have it :)14:34
isviridov#topic Open discussion isviridov14:34
ajayaaCode review: https://review.openstack.org/#/c/124391/14:34
ajayaa*needed14:34
isviridovspec #link https://wiki.openstack.org/wiki/MagnetoDB/specs/rbac14:35
isviridovajayaa : great progress!14:36
isviridov#action dukhlov charlesw ikhudoshyn isviridov review  https://review.openstack.org/#/c/124391/14:36
miqui_____for my part... am new to the project..14:37
isviridovajayaa : I just don't remember if we have finished with a spec14:37
miqui_____so am going through the bugs and see where i can start14:37
ajayaaisviridov, This was before we had a spec system in place. :)14:38
isviridovmiqui_____ : welcome on board!14:38
miqui_____...thanks!!14:38
ajayaaBut the wiki page is informative enough I guess.14:39
isviridovmiqui_____ : pay attention to https://bugs.launchpad.net/magnetodb/+bugs?field.tag=low-hanging-fruit and https://launchpad.net/magnetodb/+milestone/kilo-1 bugs14:39
miqui_____awesome... thanks...14:39
isviridovmiqui_____ : looking for your patches. Always feel free to ask.14:39
isviridovmiqui_____ : what is your timezone?14:40
miqui_____EST14:40
miqui_____EST ( US east coast)14:40
isviridovajayaa : yeap, let me look at it. I believe we will add monitoring action at least.14:41
charlesw@miqui, welcome, we are in same tz14:41
miqui_____cool...14:41
ajayaaisviridov, I didn't get you.14:41
isviridovajayaa : there is a list of apis to restict, and we have monitoring api now14:43
ajayaaisviridov, got you! okay.14:43
isviridovajayaa : anyhow great spec!14:43
ajayaaisviridov, We can add it later by filing a bug and then fixing it.14:43
isviridovYeap14:44
isviridovTeam, anything else to discuss now?14:45
isviridovSeems we are done14:46
ikhudoshynlooks like14:46
charleswI have a spec WIP, not ready yet. But I'd like to hear your use cases and comments. https://wiki.openstack.org/wiki/MagnetoDB/specs/requestmetrics14:46
isviridovcharlesw : the first q why not in spec repo?14:47
isviridov#link https://wiki.openstack.org/wiki/MagnetoDB/specs/requestmetrics14:48
charlesw@isviridov, can you educate us on the process?14:48
ikhudoshynthe same as with our usual repo14:48
ikhudoshynbut magnetodb-specs14:49
ikhudoshyngit clone, branch, set up git-review, commit, git review14:49
isviridovcharlesw : I've seen something similar in swift. So, actually it is one more monitoring14:49
charleswI was using our wiki template: https://wiki.openstack.org/wiki/MagnetoDB/specs/template14:50
*** keith_newstadt has quit IRC14:51
*** keith_newstadt has joined #magnetodb14:51
isviridovcharlesw : why not put it as a part of monitoring api?14:51
charleswI looked at swift as well they have 3 different ways: recon, informant, and statsd w/o middleware14:52
charleswwe don't need an API for monitoring. We can publish it thru statsd/graphite/ganglia/etc14:53
charleswsimilar to swift14:53
isviridovcharlesw : yes we can, but in such case we are loosing this information for celiometer14:53
isviridovcharlesw : what do you think?14:54
charleswright, there are some areas unclear like whether to use/work with ceilometer14:54
charleswthat's the kind of comments I'd like to hear more:)14:55
isviridovOk, I think that would be greate to keep it under Monitoring API as one source of cluster metrics. And call it via any monitoring solutions like nagios so on.14:56
miqui_____..even sensuapp14:56
isviridovcharlesw : how fast do you need it?14:57
charlesw@isviridov, I'll think about it. Thanks for comments.14:58
charleswprobably the week after thanksgiving14:58
isviridovAnother approach can be just implement it for statsd as it is easier and faster, and move to Monitoring API just solution is more or less machure.14:58
charleswthe overhead/perf impact can be big14:59
isviridovWith Monitoring API we have to implement own storage to keep data about every node14:59
*** miqui has quit IRC15:00
isviridovcharlesw : what performance impact do you mean?15:00
* isviridov time is over15:00
charleswwe need to capture metrics for every request. For statsd, just udp post can be done.15:00
charleswgot to go, have another meeting15:00
isviridovcharlesw : but data can be cashed and agregted in memory15:01
isviridovcharlesw : sure15:01
isviridovThank you everybody for comming15:01
isviridov#endmeeting15:01
openstackMeeting ended Thu Nov 20 15:01:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-11-20-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-11-20-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-11-20-14.00.log.html15:01
*** nunosantos has quit IRC15:02
*** isviridov is now known as isviridov_away15:05
*** miqui has joined #magnetodb15:05
*** miqui_____ has quit IRC15:18
*** miqui_ has joined #magnetodb15:22
*** vivekd has quit IRC15:25
*** miqui has quit IRC15:25
*** miqui has joined #magnetodb15:31
*** miqui has quit IRC15:32
*** miqui has joined #magnetodb15:34
*** miqui has quit IRC15:35
*** miqui has joined #magnetodb15:44
*** keith_newstadt has quit IRC16:09
*** achuprin_ has quit IRC16:12
*** keith_newstadt has joined #magnetodb16:17
*** achuprin_ has joined #magnetodb16:27
*** vnaboychenko has joined #magnetodb16:33
openstackgerritMerged stackforge/magnetodb: Cleaning up C* on unstack.sh  https://review.openstack.org/13559316:37
*** vnaboych_ has joined #magnetodb16:45
*** vnaboychenko has quit IRC16:45
*** keith_newstadt has quit IRC17:01
openstackgerritChao Li proposed stackforge/magnetodb: Add validation for the hash and range key  https://review.openstack.org/13605917:04
*** nunosantos has joined #magnetodb17:08
*** Viswanath has joined #magnetodb17:24
*** Viswanath has quit IRC17:27
*** romainh has quit IRC17:27
*** vnaboych_ has quit IRC17:35
*** vnaboychenko has joined #magnetodb17:52
*** vnaboych_ has joined #magnetodb17:52
*** vnaboychenko has quit IRC17:52
*** ajayaa has quit IRC18:41
*** keith_newstadt has joined #magnetodb18:41
*** rushiagr is now known as rushiagr_away18:45
*** Viswanath has joined #magnetodb19:00
*** Viswanath has quit IRC19:07
*** keith_newstadt has quit IRC20:10
*** keith_newstadt has joined #magnetodb20:19
openstackgerritChao Li proposed stackforge/magnetodb: Add validation for the hash and range key  https://review.openstack.org/13287120:58
*** nunosantos has quit IRC21:55
*** denis_makogon has quit IRC22:08
*** dmakogon_ has joined #magnetodb22:09
openstackgerritChao Li proposed stackforge/magnetodb: Add validation for the hash and range key some previous bug fixed  https://review.openstack.org/13287122:10
*** keith_newstadt has quit IRC23:05
openstackgerritChao Li proposed stackforge/magnetodb: Add validation for the hash and range key  https://review.openstack.org/13287123:17
« Wednesday, 2014-11-19 Index Friday, 2014-11-21 »

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