Thursday, 2015-01-29

*** charlesw has quit IRC00:03
*** jeromatron has quit IRC00:06
*** openstackgerrit has quit IRC00:21
*** openstackgerrit has joined #magnetodb00:21
*** charlesw has joined #magnetodb00:23
*** achanda has quit IRC00:56
*** achanda has joined #magnetodb01:00
*** openstackgerrit has quit IRC01:05
*** openstackgerrit has joined #magnetodb01:05
*** achanda has quit IRC02:09
*** achanda has joined #magnetodb02:10
*** jeromatron has joined #magnetodb02:12
*** openstackgerrit has quit IRC02:20
*** openstackgerrit has joined #magnetodb02:21
*** jeromatron has quit IRC02:34
*** jeromatron has joined #magnetodb02:42
*** jeromatron has quit IRC03:00
*** rushiagr_away is now known as rushiagr03:06
*** openstackgerrit has quit IRC03:20
*** openstackgerrit has joined #magnetodb03:20
*** achanda has quit IRC03:32
*** rushiagr is now known as rushiagr_away03:45
*** achanda has joined #magnetodb03:56
*** achanda has quit IRC04:06
*** jeromatron has joined #magnetodb04:23
*** charlesw has quit IRC04:27
*** vivekd has joined #magnetodb04:37
*** achanda has joined #magnetodb04:45
*** achanda has quit IRC04:46
*** rushiagr_away is now known as rushiagr04:49
*** achanda has joined #magnetodb04:57
*** jeromatron has quit IRC06:13
*** achanda has quit IRC06:53
*** achanda has joined #magnetodb06:58
*** achanda has quit IRC07:19
*** romainh has joined #magnetodb07:54
*** romainh has left #magnetodb07:54
*** vivekd_ has joined #magnetodb08:28
*** vivekd has quit IRC08:31
*** vivekd_ is now known as vivekd08:31
*** ygbo has joined #magnetodb08:58
*** rushiagr is now known as rushiagr_away09:07
*** rushiagr_away is now known as rushiagr09:10
*** achanda has joined #magnetodb09:21
*** isviridov_away is now known as isviridov09:23
isviridovHello everyone09:23
vivekdhello isviridov09:34
vivekdisviridov: the gate-magnetodb-devstack-dsvm and gate-magnetodb-cassandra-tox are failing against my patch @ https://review.openstack.org/#/c/149600/09:49
vivekdisviridov: and I see lot of "ClusterIsNotConnectedException" & "'Unable to connect to any servers' in their respective console09:49
vivekdisviridov: are those two gates stable or are there any issues in it?09:49
isviridovgate-magnetodb-cassandra-tox is considered as unstable and non-voting at this moment. devstack job must work. Let me check09:51
isviridovThere were several releases of olso.* libs yesterday09:51
vivekdok isviridov09:52
isviridovvivekd looks like cassandra-driver has been released and updated to 2.1.409:59
isviridovPreviously it was ok with localhost in config, now looks like it should be 127.0.0.110:00
isviridovI mean http://logs.openstack.org/00/149600/5/check/gate-magnetodb-devstack-dsvm/345b810/logs/etc/magnetodb/magnetodb-api.conf.txt.gz10:00
isviridovThe line "contact_points": ["localhost"],10:00
* isviridov at first look10:00
isviridovLet me try it10:02
vivekdisviridov: ok10:02
openstackgerritIlya Sviridov proposed stackforge/magnetodb: Update configs  https://review.openstack.org/15115910:05
isviridovvivekd I've reproduced it locally. It is driver update.10:47
isviridovLets us fix driver version for now10:47
vivekdisviridov: thanks a lot :-)10:47
*** ajayaa has joined #magnetodb10:53
openstackgerritIlya Sviridov proposed stackforge/magnetodb: Fix cassandra-driver version  https://review.openstack.org/15117510:58
openstackgerritAlexander Chudnovets proposed stackforge/magnetodb: (WIP) Monitoring API URLs refactoring  https://review.openstack.org/14524711:11
*** achanda has quit IRC11:22
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Fixes bug with not query retrying if item changed  https://review.openstack.org/15094411:44
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094311:45
aostapenkovivekd: patch with fix is merging now. Please your patch in about 40 minutes11:46
aostapenkovivekd: however you'll need to write functional test for your patch too11:47
vivekdok aostapenko11:47
vivekdoh ok11:47
vivekdaostapenko: do i need to write functional tests and submit it with the same patch or creating a new patch and review request is how it needs to be done?11:49
aostapenkowith same. I'll give you a tip in ten minutes11:50
vivekdok aostapenko thank you!11:50
aostapenkoMove this tests to the same file in stable dir:11:52
aostapenkohttps://github.com/stackforge/magnetodb/blob/master/contrib/tempest/tempest/api/keyvalue/in_progress/rest/test_create_table_negative.py#L196-L21011:52
aostapenkohttps://github.com/stackforge/magnetodb/blob/master/contrib/tempest/tempest/api/keyvalue/in_progress/rest/test_create_table_negative.py#L147-L17411:52
aostapenkodon't forget to remove this tests from old file, and please add to this tests error message check. You can use https://github.com/stackforge/magnetodb/blob/master/contrib/tempest/tempest/api/keyvalue/stable/rest/test_create_table_negative.py#L288-L294 as an example11:55
aostapenkovivekd: Please, feel free to ask11:56
vivekdsure aostapenko11:57
openstackgerritAlexander Chudnovets proposed stackforge/magnetodb: (WIP) Monitoring API URLs refactoring  https://review.openstack.org/14524711:58
vivekdaostapenko: what is the difference between the stable and 'in_progress' dirs?12:05
aostapenkovivekd: tests in stable dir vote in dvsm job. We put tests for implemented features there12:07
openstackgerritMerged stackforge/magnetodb: Fix cassandra-driver version  https://review.openstack.org/15117512:23
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Fixes bug with not query retrying if item changed  https://review.openstack.org/15094412:25
vivekdaostapenko: ok. how come someone wrote the tests already, even before the bug was fixed ? :-)12:28
aostapenkovivekd: We've covered many cases for not implemented features and not fixed bugs. in_progress dir was created for this purposes12:32
aostapenkotest in this dir are running in dvsm job too. but they do not vote12:32
openstackgerritVivek Dhayaal proposed stackforge/magnetodb: Fix key schema validation for table and LSIs  https://review.openstack.org/14960012:36
vivekdoh ok aostapenko. thank you!12:36
aostapenkovivekd: rebase your change please, bugfix with job is merged already12:39
vivekdoh ok aostapenko12:39
openstackgerritAlexander Chudnovets proposed stackforge/magnetodb: Monitoring API URLs refactoring  https://review.openstack.org/14524712:40
achudnovets_o/12:43
openstackgerritAlexander Chudnovets proposed stackforge/magnetodb: Monitoring API URLs refactoring  https://review.openstack.org/14524712:44
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094312:44
aostapenkovivekd: you can do it by pushing rebase button https://review.openstack.org/#/c/149600/ if no conflicts are met12:46
openstackgerritVivek Dhayaal proposed stackforge/magnetodb: Fix key schema validation for table and LSIs  https://review.openstack.org/14960012:48
vivekdoh that's cool aostapenko . i should use that next time onwards. this time i rebased locally and pushed12:52
openstackgerritDmitriy Ukhlov proposed stackforge/magnetodb: Move setting up default encoding into setup_global_env  https://review.openstack.org/15081013:12
*** rushiagr is now known as rushiagr_away13:40
openstackgerritDmitriy Ukhlov proposed stackforge/magnetodb: Move setting up default encoding into setup_global_env  https://review.openstack.org/15081013:56
isviridovHey everyone. It is meeting time13:59
isviridovAnybody here for meeting?14:00
achudnovets_hi14:00
miquihi14:00
isviridovachudnovets_ miqui14:00
isviridovaostapenko ikhudoshyn14:00
isviridov#startmeeting magnetodb14:00
openstackMeeting started Thu Jan 29 14:00:52 2015 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
isviridovachudnovets_ miqui o/14:01
isviridovNot too many today14:01
ikhudoshyno/14:01
isviridovHello ikhudoshyn14:02
ajayaao/14:02
isviridovOk, let us start with action items as usually14:02
ominakovo/14:02
isviridov#topic Go through action items isviridov14:02
isviridovominakov hi14:02
isviridovaostapenko charlesw isviridov brainstorm the scenario14:02
isviridovOk, it is about testing of concurrent writes14:03
* isviridov looking for BP14:03
isviridov#link https://blueprints.launchpad.net/magnetodb/+spec/test-concurrent-writes14:03
isviridovI consider it as done. The BP is in approved state now14:04
openstackgerritDmitriy Ukhlov proposed stackforge/magnetodb: Move setting up default encoding into setup_global_env  https://review.openstack.org/15081014:04
isviridovDuring testing we have discovered a bug https://bugs.launchpad.net/magnetodb/+bug/141547814:04
ikhudoshynthere's a patch from aostapenko14:04
isviridovI believe it is not the last one14:05
ikhudoshyni just mean it's not merged yet14:05
ikhudoshynwhy u say its done?14:05
aostapenkoo/14:05
*** dukhlov_ has joined #magnetodb14:05
isviridovikhudoshyn yeap. I'm not sure that it will be only one patch14:05
dukhlov_hello14:05
isviridovikhudoshyn because action was to 'brainstorm the scenario'. You can read two patterns in BP description14:06
aostapenkoikhudoshyn: this patch does not fix bug that isviridov mentions14:06
ikhudoshyna, got it, its bout AI not BP14:06
isviridovikhudoshyn yeap14:06
isviridovaostapenko exactly14:07
isviridovaostapenko anything to add?14:07
isviridovLooks like not14:07
ikhudoshynmove on?14:08
isviridovNext AI is dukhlov_ charlesw aostapenko isviridov review https://review.openstack.org/#/c/146534/14:08
isviridovIt is merged, my congrats!14:08
dukhlov_merged14:08
isviridovWe are done with action items14:09
isviridov#topic Open discussion14:09
isviridovikhudoshyn I've seen reoly from charlesw in Notification refactoring BP, please take a look14:10
ikhudoshynsure14:10
miquiisviridov: my feedback is am still learning/ramping up on the project...14:10
miqui..its been slow lately ...14:10
isviridovmiqui great to hear from you14:11
isviridovWhat are you looking at right now?14:11
ajayaaHi guys. I wanted to talk about ttl feature.14:11
miquiisviridov: how to test it and understand the code overall..14:12
isviridovajayaa yes, we have started discussion internally but no outcome in mail list. Sorry14:12
ajayaaI sent a mail in the mailing list last to last week. Sadly nobody gave a look.14:12
ajayaaisviridov, okay. Let me know your thoughts on mailing list.14:13
isviridovmiqui are you online after meeting? I would love to unswer your Q then.14:13
* isviridov serching for his notes14:13
isviridovdukhlov_ please join14:13
ajayaaThis blog post would help to understand the problems associated with ttl.14:14
ajayaahttp://ajayaa.github.io/cassandra-difference-between-insert-update/14:14
isviridov#topic TTL feature for a row14:14
miquiisviridov: , thanks i'll be online, but i have to  focus on something else...14:14
isviridov#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/054628.html14:14
miquiisviridov: is tomorrow good?14:14
ajayaaplease read it when you are free.14:14
isviridovmiqui don't hesistate to contact me any question14:14
miquioh k, great... thanks...14:14
isviridovajayaa will do, but let us use this time to share oppinions we have already14:15
ajayaamiqui, You can ping me also. I will be happy to help.14:15
ajayaaisviridov, yes.14:15
ajayaa+114:15
miqui..thanks...14:15
isviridovSo, the idea you are suggesting (please correct me) is to allow TTL only for inserting14:16
ajayaayes.14:16
ikhudoshynajayaa: that actually does not sound really good for me, sry14:16
isviridovBut with next update we will loose original TTL14:16
*** jeromatron has joined #magnetodb14:17
ajayaaexactly. Cassandra provides column level ttl.14:17
isviridovCQL what illustrates it #link http://paste.openstack.org/show/163676/14:17
ajayaainstead if row level. It is one of those features which is being demanded by the community for a long time.14:17
ikhudoshynthere's two other approaches we could also consider: 1) provide per-column TTL and use C* native one 2) DIY per row ttl14:18
ajayaaDIY?14:18
ikhudoshyndo-it-yourself ))14:19
ajayaaahh14:19
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094314:19
dukhlov_we can easily implement like per-row TTL for inserts only14:19
ikhudoshynjust introduce servie attribute with per-row ttl and handle it on our own14:19
isviridovikhudoshyn noy sure we can implement 1 with current data structure as far as we have a one column with set of attributes in C*14:20
ikhudoshyndukhlov_: and claim that TTL on updates is unavailable?14:20
dukhlov_yes14:20
dukhlov_or implemet updates using inserts14:21
ikhudoshyndukhlov_: that would sound weird from user perspective14:21
dukhlov_read whole row and insert it again14:21
ajayaaikhudoshyn, We would have to update all the columns for a row incase of an update.14:21
ajayaaOtherwise some columns would dissappear and some would remain.14:21
ajayaaFor that you would need to fetch the row before updating.14:22
dukhlov_our update_item request now works in this way14:22
ikhudoshynajayaa: i actually meant not using C* native TTL, but intro separate attribute and check/update it manually14:22
dukhlov_it reads whole row then peform modification and store it14:22
ajayaaohh...We need to run a process or thread which would clean up the data regularly.14:23
ikhudoshynajayaa: sure we'll need it14:23
dukhlov_it is inefficient but now it works in this way14:23
isviridovdukhlov_ any possibilities to improve it?14:24
* isviridov evaluating if we have to rely on current implemetation or it will be changed soon14:24
ajayaadukhlov, If you have specified return values as ALL_OLD then it is read, I think.14:25
*** charlesw has joined #magnetodb14:25
isviridovajayaa with own TTL we have to take care about cleaning14:25
dukhlov_we should choose Dynamo DB API support or efficiency14:25
ajayaaYou have written it, I might have missed something.14:25
ajayaadukhlov_ ^^14:25
ajayaaisviridov, agreed.14:25
dukhlov_no not only for return ald item14:27
ajayaadukhlov_ +1. I that is done in put_item. You are right.14:27
dukhlov_fort example when you want increase number value by +114:27
ajayaahttps://github.com/stackforge/magnetodb/blob/master/magnetodb/storage/driver/cassandra/cassandra_with_custom_lsi_impl.py#L86314:28
dukhlov_cassandra cann't do this14:28
ajayaagot it. :)14:28
ajayaaThere is a counter type in cassandra.14:29
ikhudoshynajayaa: we evaluated that one, it's pretty limited14:29
dukhlov_yes, but you can't create counter field with other types14:30
ajayaaikhudoshyn, okay. I would love to have a discussion sometime later around that. Let's not hijack ttl thread for now.14:30
ikhudoshynagree14:30
dukhlov_you need to create separate table with counters only14:30
ajayaaDo we have a consensus on how to go about ttl?14:31
isviridovOk, let me summarize14:31
isviridovThe only way for now looks like implementation ow raw TTL using custom field14:31
isviridovThe performance is not expected the best14:32
ikhudoshynisviridov: +114:32
isviridovTTL could be implemented to put and update14:32
isviridovdukhlov_ ikhudoshyn ajayaa?14:33
*** rushiagr_away is now known as rushiagr14:33
ajayaa+1 for custom which would provide consistency.14:34
dukhlov_I'm worried about sense of such efforts14:34
dukhlov_If Cassandra add row-level ttl in future14:34
charleswshould we check with C* folks to see if they have any plan for that?14:35
dukhlov_I don't think that it is so complicated14:35
isviridovcharlesw +114:35
ikhudoshyncharlesw: +114:35
ajayaa+114:35
dukhlov_charlesw: +114:35
aostapenko+114:35
ajayaaIf we can get a timeline for that then it would be awesome.14:36
isviridovajayaa charlesw what are you excpectation for availability of this functionality if there are any?14:37
* isviridov actually it is question to Symatec, Relience :)14:37
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094314:37
ajayaaWe don't have an immediate requirement but something like nice to have.14:38
charleswOn symantec side, we are not in urgent need for that14:38
isviridovClear. charlesw will to check if C* is going to ass row level TTL?14:38
isviridov* will you14:39
charleswsure, I'll dig into that14:39
isviridov#action charlesw clarify what are plans for row TTL in C* community14:40
openstackgerritDmitriy Ukhlov proposed stackforge/magnetodb: Move setting up default encoding into setup_global_env  https://review.openstack.org/15081014:40
isviridov#agreed try leverage C* nativre TTL14:40
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094314:40
isviridovI've moved https://blueprints.launchpad.net/magnetodb/+spec/row-expiration to kilo-3 for now14:40
ajayaaokay.14:41
isviridovGreat discussion!14:41
isviridovNext topic? Any suggestions?14:41
isviridovominakov how it is going with migration solution?14:42
charleswwe should have a formal/standard way of upgrade/migration14:43
ominakovnow, I'am testing it on real env and have some issues - some tables failed with CREATE_FAILED status14:43
charleswyou should remove those tables14:44
charlesware they existing CREATE_FAILED tables?14:44
isviridovominakov any BP for it?14:44
ominakovisviridov, not yet (14:45
ominakovcharlesw, nope, it first time creating14:45
isviridovominakov please create it with description of approach you are using, now it is not clear for community14:45
ominakovsure, i'll do it14:46
charleswAlso please submit your patch for review14:46
isviridov#action ominakov file blueprint about migration14:47
isviridov#topic Open discussion14:47
ikhudoshynhttps://review.openstack.org/14690914:48
isviridovikhudoshyn will check14:49
ikhudoshyntnx14:50
isviridovAnythink else?14:50
isviridov* anything14:50
aostapenko:)14:50
ajayaanope. Thanks guy!14:50
ajayaaguys*14:50
isviridovFinshed for today? 3..2..1..14:51
isviridovThank you for comming14:51
charleswThanks for organinzing14:51
ikhudoshyncya guys14:51
isviridovvivekd miqui ygbo there is a PyCharm Pro license for MagnetoDB contributors if you need it, just ping me14:52
*** ajayaa has quit IRC14:52
isviridov#endmeeting14:52
openstackMeeting ended Thu Jan 29 14:52:38 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-01-29-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-01-29-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-01-29-14.00.log.html14:52
*** isviridov is now known as isviridov_break14:53
*** jeromatron has quit IRC14:56
*** jeromatron has joined #magnetodb15:02
*** achanda has joined #magnetodb15:31
*** jeromatr_ has joined #magnetodb15:34
*** jeromatron has quit IRC15:38
*** achanda has quit IRC15:41
*** isviridov_break is now known as isviridov15:43
isviridovmiqui what kind of  task are you looking for?15:43
miquihi isviridov, just setting up developer env, run it successfully, so that i can then code+test15:45
miquibtw, i'll take your pycharm lic offer...15:45
miquithanks...15:45
isviridovmiqui so you have to install all components needed by mdb. Now it is keystone, mysql, cassandra, rabbitmq. The easiest way to do it is using devstack. here is devstack integration for mdb just look at the document https://github.com/stackforge/magnetodb/tree/master/contrib/devstack15:55
isviridovI would suggest to do it in vm15:56
isviridovmiqui here is a quick start https://magnetodb.readthedocs.org/en/latest/developer_guide.html15:56
*** vivekd has quit IRC15:57
miquithanks isviridov15:57
miquiyeah, saw this one, had some issues launching devstack....geez15:57
miquibut sure will keep on it..15:58
isviridovJust you installed devstack, take a look how tempest is running following this doc https://wiki.openstack.org/wiki/MagnetoDB/QA/Tests_on_env_with_devstack15:58
aostapenkoisviridov, dukhlov, charlesw look please ikhudoshyn's patch https://review.openstack.org/14690915:58
* isviridov aostapenko is promoting ikhudoshyn15:58
isviridovmiqui feel free to ask issues as well. For logs please use paste http://paste.openstack.org/15:59
*** jeromatr_ has quit IRC16:00
isviridovmiqui you are testing developer guide and onboarding process. So whatever issue you are facing will improve it.16:00
isviridovmiqui check private messages about PyCharm license16:00
miquiyeah..thats right...collecting feedback for ya..16:00
*** charlesw_ has joined #magnetodb16:05
*** charlesw has quit IRC16:06
*** charlesw_ is now known as charlesw16:06
aostapenkoikhudoshyn, dukhlov, isviridov review https://review.openstack.org/150944 https://review.openstack.org/15094316:14
aostapenkocharlesw16:14
achudnovets_and this one, plz https://review.openstack.org/#/c/145247 :)16:16
openstackgerritIlya Sviridov proposed stackforge/magnetodb: Removed py26 env from tox.ini  https://review.openstack.org/14747416:17
openstackgerritMerged stackforge/magnetodb: Fix key schema validation for table and LSIs  https://review.openstack.org/14960016:19
*** jeromatron has joined #magnetodb16:21
*** charlesw has quit IRC16:32
*** jeromatron has quit IRC16:35
openstackgerritIlya Sviridov proposed stackforge/magnetodb: Fixed import sequence  https://review.openstack.org/15130616:42
openstackgerritIlya Sviridov proposed stackforge/magnetodb: (WIP)Recover tempest html report generation  https://review.openstack.org/14754616:47
openstackgerritIlya Sviridov proposed stackforge/python-magnetodbclient: (WIP)Move to graduated oslo libraries as much as possible  https://review.openstack.org/14417916:49
*** ajayaa has joined #magnetodb16:53
*** jeromatron has joined #magnetodb16:59
isviridovBye everyone. See you tomorrow17:17
*** isviridov is now known as isviridov_away17:17
*** ygbo has quit IRC17:18
openstackgerritMerged stackforge/magnetodb: Add restore manager  https://review.openstack.org/14690917:27
openstackgerritMerged stackforge/magnetodb: Fixes bug with not query retrying if item changed  https://review.openstack.org/15094417:28
*** jeromatron has quit IRC17:47
*** jeromatron has joined #magnetodb17:50
*** rushiagr is now known as rushiagr_away18:02
openstackgerritMerged stackforge/magnetodb: Removed py26 env from tox.ini  https://review.openstack.org/14747418:05
*** achanda has joined #magnetodb18:29
*** openstackgerrit has quit IRC18:50
*** openstackgerrit has joined #magnetodb18:51
*** achanda has quit IRC19:10
*** achanda has joined #magnetodb19:18
*** achuprin_ has quit IRC19:19
*** achuprin_ has joined #magnetodb19:27
*** charlesw has joined #magnetodb19:30
*** jeromatron has quit IRC19:35
*** jeromatron has joined #magnetodb19:36
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094319:45
*** ajayaa has quit IRC19:47
*** openstackgerrit has quit IRC20:04
*** openstackgerrit has joined #magnetodb20:05
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Fixes bug with update nonexistent item with return values "ALL_OLD"  https://review.openstack.org/15137720:43
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds tempest concurrent tests  https://review.openstack.org/15094320:50
openstackgerritAlexander Chudnovets proposed stackforge/magnetodb: Monitoring API URLs refactoring  https://review.openstack.org/14524720:50
*** achanda has quit IRC20:55
*** miqui has quit IRC21:18
*** achanda has joined #magnetodb21:19
*** miqui has joined #magnetodb21:21
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Fix bug with update item that contains only key attributes  https://review.openstack.org/15139421:48
*** achanda has quit IRC22:03
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds test for checking update item with ALL_OLD atomicity  https://review.openstack.org/15140222:05
*** achanda has joined #magnetodb22:14
*** achanda has quit IRC22:14
*** achanda has joined #magnetodb22:17
openstackgerritAbhishek Chanda proposed stackforge/python-magnetodbclient: Move to graduated oslo libraries as much as possible  https://review.openstack.org/14417922:34
*** openstackgerrit has quit IRC22:51
*** openstackgerrit has joined #magnetodb22:52
*** jeromatron has quit IRC23:21
*** charlesw has quit IRC23:34

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