| *** charlesw_ has joined #magnetodb | 00:01 | |
| *** charlesw has quit IRC | 00:01 | |
| *** charlesw_ is now known as charlesw | 00:01 | |
| *** achanda has quit IRC | 00:37 | |
| *** achanda has joined #magnetodb | 00:43 | |
| *** achanda has quit IRC | 00:53 | |
| *** jeromatron has joined #magnetodb | 01:12 | |
| *** jeromatron has quit IRC | 01:29 | |
| *** jeromatron has joined #magnetodb | 01:30 | |
| *** achanda has joined #magnetodb | 01:53 | |
| *** achanda has quit IRC | 01:59 | |
| *** rushiagr_away is now known as rushiagr | 02:40 | |
| *** achanda has joined #magnetodb | 02:51 | |
| *** rushiagr is now known as rushiagr_away | 03:18 | |
| *** rushiagr_away is now known as rushiagr | 03:43 | |
| *** charlesw has quit IRC | 04:01 | |
| *** achanda has quit IRC | 04:52 | |
| *** miqui has joined #magnetodb | 04:53 | |
| *** achanda has joined #magnetodb | 05:01 | |
| *** vivekd has joined #magnetodb | 05:07 | |
| openstackgerrit | Merged stackforge/magnetodb: Moves to oslo.serialization from common code jsonutils https://review.openstack.org/152925 | 05:11 |
|---|---|---|
| *** jeromatron has quit IRC | 05:34 | |
| *** jeromatron has joined #magnetodb | 05:39 | |
| *** achanda has quit IRC | 06:00 | |
| vivekd | hi guys | 06:03 |
| vivekd | i see that there was an automatic update of the review URL in the associated bug after a patch was submitted | 06:03 |
| vivekd | eg. https://bugs.launchpad.net/magnetodb/+bug/1390407/comments/6 | 06:03 |
| vivekd | but after i submitted a patch https://review.openstack.org/#/c/152879 for bug https://bugs.launchpad.net/magnetodb/+bug/1410605 | 06:03 |
| vivekd | there has been no automatic update of the that review URL in the that bug | 06:03 |
| vivekd | any idea why ? | 06:04 |
| *** achanda has joined #magnetodb | 06:24 | |
| *** jeromatron has quit IRC | 06:28 | |
| *** achanda has quit IRC | 06:41 | |
| *** ajayaa has joined #magnetodb | 06:57 | |
| *** achanda has joined #magnetodb | 07:41 | |
| *** achanda has quit IRC | 07:47 | |
| *** achanda has joined #magnetodb | 07:54 | |
| *** achanda has quit IRC | 08:29 | |
| *** achanda has joined #magnetodb | 08:34 | |
| *** achanda has quit IRC | 08:53 | |
| *** achanda has joined #magnetodb | 08:55 | |
| *** achanda has quit IRC | 09:09 | |
| *** ajayaa has quit IRC | 09:10 | |
| *** ajayaa has joined #magnetodb | 09:10 | |
| *** achanda has joined #magnetodb | 09:11 | |
| *** achanda has quit IRC | 09:19 | |
| *** vivekd has quit IRC | 09:24 | |
| *** ygbo has joined #magnetodb | 09:26 | |
| *** ajayaa has quit IRC | 09:30 | |
| *** ajayaa has joined #magnetodb | 09:31 | |
| *** vivekd has joined #magnetodb | 10:15 | |
| *** denis_makogon has joined #magnetodb | 11:14 | |
| *** shashankchakelam has joined #magnetodb | 11:29 | |
| shashankchakelam | Hello, I'm new to MagnetoDB and I'm having trouble cloning the git repo | 12:16 |
| shashankchakelam | I can clone nova, swift, etc. I've also verified that I have my public ssh key uploaded to launchpad and review.openstack.org | 12:16 |
| shashankchakelam | but when i attempt a git clone of the mangnetodb repo, I get "Permission denied (publickey)." | 12:17 |
| shashankchakelam | anyone know why? | 12:17 |
| shashankchakelam | Hmm, turns out the "git clone git@github.com:stackforge/magnetodb.git" mentioned in the wiki doesn't work for me but running "git clone https://github.com/stackforge/magnetodb.git" worked | 12:21 |
| *** keith_newstadt has joined #magnetodb | 12:32 | |
| shashankchakelam | stackoverflow helped me realize my ignorance. Me not having ssh keys setup on github.com was what it was complaining about | 12:37 |
| openstackgerrit | Merged stackforge/magnetodb: Moves to oslo.utils instead of common code timeutils https://review.openstack.org/153035 | 12:54 |
| *** shashankchakelam has quit IRC | 12:56 | |
| *** vivekd has quit IRC | 12:56 | |
| *** keith_newstadt has quit IRC | 12:58 | |
| openstackgerrit | Merged stackforge/magnetodb: Fixes bug with model serialization https://review.openstack.org/151618 | 12:58 |
| *** keith_newstadt has joined #magnetodb | 12:58 | |
| ajayaa | Hi guys. Can I have cas update on primary key fields? | 13:34 |
| ajayaa | aostapenko ^^ | 13:34 |
| ajayaa | isviridov | 13:34 |
| ajayaa | It seems the answer is no, but just wanted to confirm. | 13:35 |
| ajayaa | dukhlov | 13:35 |
| ajayaa | ^^ | 13:35 |
| dukhlov | Hello ajayaa | 13:36 |
| ajayaa | Hi dukhlov | 13:36 |
| ajayaa | Is my question clear enough to answer? | 13:37 |
| *** charlesw has joined #magnetodb | 13:37 | |
| dukhlov | do you mean, can you specify condition for PK field? | 13:38 |
| ajayaa | yes. | 13:41 |
| ajayaa | dukhlov. | 13:41 |
| dukhlov | yes, you can | 13:41 |
| *** charlesw has quit IRC | 13:42 | |
| ajayaa | for e.g. if key is something like (h1, r1) then I would like to change it to (h1, r2). | 13:42 |
| ajayaa | dukhlov ^^ | 13:42 |
| dukhlov | but I see only one usecase - update if EXISTS of update if not exists | 13:42 |
| dukhlov | no, you can not update primary key value | 13:44 |
| ajayaa | I would like to avoid locking in my application. | 13:44 |
| dukhlov | only specify condition for PK | 13:44 |
| ajayaa | So compare and set works only on non-primary key fields. | 13:44 |
| dukhlov | ok, describe your usecase in more details | 13:45 |
| ajayaa | wait, I will paste the schema somewhere. | 13:46 |
| dukhlov | ok | 13:46 |
| ajayaa | http://paste.openstack.org/show/167438/ | 13:47 |
| ajayaa | schema ^^ | 13:47 |
| ajayaa | How should I update the name field for a row? | 13:47 |
| *** shashankchakelam has joined #magnetodb | 13:48 | |
| ajayaa | dukhlov, are you there? | 13:51 |
| dukhlov | yes | 13:51 |
| ajayaa | How should I update name field of a row without introducing race conditions. | 13:52 |
| ajayaa | I am assuming you saw the schema. | 13:52 |
| dukhlov | I see now what you want | 13:52 |
| *** miqui_ has joined #magnetodb | 13:53 | |
| ajayaa | Do you think it is possible with this schema with existing query capabilities of MagnetoDB? | 13:54 |
| dukhlov | we don't support such operation. I guess DynamoDB too | 13:55 |
| dukhlov | but we have't check it | 13:55 |
| ajayaa | I will check dynamodb documentation. Even if it's possible with DynamoDB it is hard to implement with cas. | 13:56 |
| dukhlov | even if we are talking about cassandra, we need to read old row first and then can remove old row and add new one in single batch | 13:56 |
| ajayaa | Would it be possible to add this functionality in mdb? | 13:57 |
| ajayaa | I think a better question is if dynamodb does not permit such thing, is it a bad idea to do in mdb? | 13:57 |
| dukhlov | We try to avoid implementing new features not supported by DynamoDB | 13:58 |
| isviridov | Hello everyone | 13:59 |
| dukhlov | because if in future they add something like we already have we will need to chenge our API | 13:59 |
| isviridov | It is meeting time | 13:59 |
| miqui_ | ...hello.... | 13:59 |
| dukhlov | but it is discussable | 13:59 |
| dukhlov | hello | 13:59 |
| *** shashankchakelam has quit IRC | 13:59 | |
| ajayaa | dukhlov, What happens if the row is deleted already by a parallel thread. Would the batch fail? | 13:59 |
| ajayaa | Hi all. | 14:00 |
| dukhlov | ajayaa: after meeting, ok? | 14:00 |
| isviridov | ajayaa dukhlov miqui_ hello | 14:00 |
| isviridov | dukhlov thx | 14:00 |
| ajayaa | dukhlov +1 | 14:00 |
| isviridov | #startmeeting magnetodb | 14:00 |
| openstack | Meeting started Thu Feb 5 14:00:40 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| openstack | The meeting name has been set to 'magnetodb' | 14:00 |
| ikhudoshyn | o/ | 14:00 |
| aostapenko | o/ | 14:00 |
| isviridov | o/ | 14:00 |
| ajayaa | o/ | 14:00 |
| miqui_ | o/ | 14:01 |
| isviridov | Today agenda https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Agenda | 14:01 |
| isviridov | And we can start from first topic, I think | 14:01 |
| isviridov | #topic Go through action items isviridov | 14:01 |
| isviridov | The first action charlesw clarify what are plans for row TTL in C* community | 14:02 |
| isviridov | Not sure that charlesw around | 14:02 |
| isviridov | Let us move on | 14:02 |
| ikhudoshyn | +1 | 14:03 |
| isviridov | And discuss it later | 14:03 |
| isviridov | ominakov file blueprint about migration | 14:03 |
| isviridov | ominakov any news here? | 14:03 |
| ikhudoshyn | move on 2: moveon returns | 14:04 |
| isviridov | ikhudoshyn :) | 14:04 |
| isviridov | Ok, I think it is important let me share some info with team about it | 14:05 |
| ajayaa | that would be helpful. isviridov | 14:05 |
| isviridov | With introducing custom LSI implementation we have an installed production instance running now, so in order to cover this operational gap we have started working on migration utility from old cassandra datastructure to new one | 14:06 |
| isviridov | #link https://blueprints.launchpad.net/magnetodb/+spec/migration-script | 14:06 |
| isviridov | It is going to be export/import via file or SWIFT | 14:07 |
| isviridov | Sure it will introduce downtime during migration | 14:07 |
| isviridov | In the future, I think, we have to do migration/upgrade on fly, but not this time | 14:08 |
| isviridov | ajayaa does it help? | 14:08 |
| ajayaa | isviridov I will go through the spec once it is written. | 14:09 |
| ajayaa | Are we going to have one for this bp? | 14:09 |
| *** charlesw has joined #magnetodb | 14:09 | |
| isviridov | It is not yet, actually. I hope description in BP and code will document it good enought. | 14:10 |
| charlesw | sorry I'm late, heavy snow right now in Boston | 14:10 |
| isviridov | charlesw welcome | 14:10 |
| miqui_ | hello charlesw | 14:10 |
| ajayaa | Hi charlesw | 14:11 |
| isviridov | ajayaa actually it is in progress already and ominakov have to share the current state | 14:11 |
| charlesw | Hi guys | 14:11 |
| isviridov | ajayaa does it work for you? | 14:11 |
| ajayaa | isviridov, yes. | 14:11 |
| ajayaa | let's move on. | 14:11 |
| isviridov | charlesw clarify what are plans for row TTL in C* community | 14:11 |
| isviridov | Any news here? | 14:12 |
| charlesw | The row TTL question has been asked many times in C* board | 14:12 |
| charlesw | I dig into some of the hostory | 14:13 |
| charlesw | They have no plan to open up the row marker as a TTL column | 14:13 |
| * isviridov just updated agenda https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Agenda. Sorry for late notice | 14:13 | |
| charlesw | So the working around is to have all columns except primary key cloumns to have TTL set | 14:14 |
| ajayaa | What do you do incase of an update? | 14:14 |
| charlesw | To update columns, you will have to preserve your TTL, then update the row with original TTL | 14:15 |
| charlesw | basically a read before write | 14:15 |
| ajayaa | How do you get rid of primary key values? | 14:16 |
| ajayaa | They will still be there. | 14:16 |
| isviridov | charlesw any way to influence C* community? Do we have answer like 'no we will not do it' or it is last known view on it? | 14:16 |
| charlesw | it will be auto cleaned I believe | 14:16 |
| charlesw | It's a last view on it. the same Q has been asked many times | 14:17 |
| ajayaa | charlesw, you just said that all columns excepts primary keys will have ttl set. | 14:17 |
| isviridov | charlesw thx | 14:17 |
| charlesw | I don't believe you can set TTL on primary key | 14:17 |
| miqui_ | C* is cassandra right? | 14:18 |
| ajayaa | charlesw, If you do an insert with a ttl then primary keys also have ttl associated with them. | 14:18 |
| charlesw | but you can't get the ttl for primary key only | 14:19 |
| isviridov | miqui_ yes C* == Cassandra | 14:19 |
| isviridov | dukhlov you are our Casasndra wizard, what about implementation row TTL ourselves? Any thoughts? | 14:19 |
| *** keith_newstadt has quit IRC | 14:19 | |
| ajayaa | Primary keys are given some kind of special treatment in cassandra. If you did an insert with no ttl and updated some columns with ttl, then primary keys won't have ttl associated. | 14:21 |
| ajayaa | And the row won't be removed. If you did an insert with ttl then primary keys would also get cleaned up. | 14:21 |
| isviridov | dukhlov we can eather implement it and merge to upstream or keep it on our owns. Depends what will be easier. Let us think about it | 14:22 |
| ajayaa | +1 | 14:22 |
| ajayaa | isviridov | 14:22 |
| miqui_ | once ttl is hit...the expectation is wht? the whole record is gone? | 14:23 |
| dukhlov | It is interesting, but I don't like support separate casandra branch | 14:23 |
| isviridov | miqui_ exactly #link https://blueprints.launchpad.net/magnetodb/+spec/row-expiration | 14:24 |
| dukhlov | We need talk to cassandra developers first to get their opinion | 14:24 |
| isviridov | dukhlov agree | 14:24 |
| charlesw | We shouldn't allow update row with TTL. Will need to delete the row and re-insert with TTL | 14:24 |
| dukhlov | if they say that this feature will never merged.... | 14:24 |
| miqui_ | thanks isviridov | 14:24 |
| isviridov | Let us consider, that it is one of the options. Not implementing and not merging are different things. If we can do it, it could cost us less that keeping this logic in mdb | 14:26 |
| charlesw | Even though C* doesn't fully support row expiration, we can limit our scope to work with C* instead of branching out | 14:26 |
| isviridov | #idea implement row TTL in C* by ourselves | 14:27 |
| isviridov | charlesw agree, as we have this feature not in top of priorities | 14:27 |
| isviridov | Moving on? | 14:27 |
| dukhlov | yes, implement it ourselves looks much better to me instead branching | 14:28 |
| *** ajayaa has quit IRC | 14:28 | |
| dukhlov | isviridov: +1 | 14:28 |
| charlesw | +1 | 14:28 |
| isviridov | dukhlov I mean in C* code | 14:28 |
| charlesw | -1 for changing C* code | 14:29 |
| miqui_ | this is a tough choice... | 14:29 |
| *** ajayaa has joined #magnetodb | 14:29 | |
| miqui_ | a separate C* branch is probably worse in the long term... | 14:30 |
| miqui_ | IMHO | 14:30 |
| dukhlov | yes | 14:30 |
| ajayaa | +1 miqui_ | 14:30 |
| isviridov | Yes, branch is always terrible | 14:30 |
| dukhlov | anyway we have no resources for separate branch support now | 14:30 |
| isviridov | Let ius move on to kilo-2 milestone | 14:30 |
| isviridov | #topic k-2 status https://launchpad.net/magnetodb/+milestone/kilo-2 | 14:31 |
| isviridov | So this week we are releasing kilo-2 milestone, I've updated launchpad scope as you can see | 14:32 |
| *** achuprin_ has quit IRC | 14:32 | |
| isviridov | charlesw it looks like we have postpond Push table-related metrics to statsd and Real Time Request Metrics | 14:33 |
| charlesw | can you move the real time request metrics to kilo-3? The notification refactoring added quite some work and blocked the code review | 14:33 |
| *** jeromatron has joined #magnetodb | 14:33 | |
| charlesw | yes,isviridov. | 14:33 |
| isviridov | ikhudoshyn also Backup and restore for MagnetoDB and Backup Info data model and repository probably not going to happen this week | 14:34 |
| isviridov | charlesw sure, thx | 14:34 |
| ikhudoshyn | isviridov: yes, i'm afraid | 14:34 |
| isviridov | ikhudoshyn ok | 14:34 |
| ikhudoshyn | isviridov: hold on pls | 14:34 |
| isviridov | Anything else? | 14:34 |
| isviridov | aostapenko? | 14:34 |
| ikhudoshyn | Backup Info data model and repository probably actually merged | 14:35 |
| isviridov | Anything on the go and close to be finished and needs more attention? | 14:35 |
| aostapenko | nothing interesting from my side | 14:35 |
| isviridov | ikhudoshyn fixed | 14:36 |
| isviridov | Ok, seems we have clarified it | 14:36 |
| *** jeromatron has quit IRC | 14:36 | |
| isviridov | Open discussions? | 14:37 |
| isviridov | I would like to thank to aostapenko who made huge contribution this milestone | 14:37 |
| miqui_ | not much from me, just reading source, working on my mdb dev env... | 14:37 |
| isviridov | !m aostapenko | 14:38 |
| [o__o] | You're doing good work, aostapenko! | 14:38 |
| openstack | isviridov: Error: "m" is not a valid command. | 14:38 |
| isviridov | #topic Open discussion isviridov | 14:38 |
| aostapenko | isviridov: thank you :) | 14:38 |
| charlesw | isviridov, could you share your vision/roadmap to incubation? | 14:38 |
| isviridov | miqui_ nice | 14:38 |
| ominakov | hi, guys I have early poc for migration, but I think i should write spec first | 14:39 |
| isviridov | ominakov we have just agreed that spec is not teh most important thing for one time using tool | 14:39 |
| charlesw | ominakov, would love to see spec | 14:39 |
| isviridov | charlesw :) | 14:39 |
| isviridov | ominakov could you share you code first? | 14:40 |
| isviridov | * you | 14:40 |
| ominakov | yep, sure | 14:40 |
| isviridov | but if you have any spec we really appreciate it as well :) | 14:41 |
| *** jeromatron has joined #magnetodb | 14:41 | |
| isviridov | ominakov do you think you will finish with migration this week? | 14:41 |
| isviridov | ominakov the question is kilo-2 or kilo-3 | 14:41 |
| * isviridov remember teh question about incubation | 14:41 | |
| isviridov | So, charlesw we at the middle of reform now | 14:43 |
| ominakov | i guess i'll push working poc this week and in future we can add some features and optimize it | 14:44 |
| ajayaa | isviridov, I kind of fee bad when I don't see MagnetoDB on side of sahar, zaqar, murano etc... | 14:45 |
| ajayaa | feel* | 14:45 |
| miqui_ | why would that be the case? | 14:45 |
| isviridov | Just TC agree list of tags and the way how it will be given to projects all projects will be a part of openstack | 14:46 |
| *** charlesw has quit IRC | 14:46 | |
| *** charlesw_ has joined #magnetodb | 14:47 | |
| *** charlesw_ is now known as charlesw | 14:47 | |
| isviridov | ajayaa status of zaqar and other incubated projects will be changed and all projects will receive their tags | 14:47 |
| isviridov | integrated-release tag has been merged already #link https://review.openstack.org/#/c/146818/ | 14:47 |
| ajayaa | isviridov, waiting for the day when we get a tag. :D | 14:47 |
| *** achuprin_ has joined #magnetodb | 14:48 | |
| isviridov | ajayaa it will be list of tags, the most valuable I think is smth like 'used in production' | 14:48 |
| *** jeromatron has quit IRC | 14:49 | |
| isviridov | charlesw ajayaa have I answered? Can I describe smth else? | 14:50 |
| *** jeromatron has joined #magnetodb | 14:50 | |
| isviridov | BTW ajayaa sahara is integrated, murano is not incubated. JFYI | 14:50 |
| charlesw | What are the other valuable tags? How can we all help? | 14:50 |
| * isviridov probably has network lag | 14:51 | |
| *** jeromatron has quit IRC | 14:51 | |
| *** jeromatron has joined #magnetodb | 14:52 | |
| ajayaa | isviridov, my intention was to just list out some projects with which MagnetoDB should stand shoulder to shoulder. :) | 14:52 |
| isviridov | charlesw the list is still under definition, but it is build based on incubation, integration requirements. And we are doing our best to follow it, we have gate, functional, unit testing, great team and working process. What is most valuable now is making mdb better knows and improve it as a software | 14:53 |
| isviridov | ajayaa reasonable note, in some aspects we are higher than our mates, but sure not in all of them :) | 14:55 |
| isviridov | 3 mins left | 14:57 |
| isviridov | Any other question or topic | 14:57 |
| isviridov | Looks like we are done for today | 14:58 |
| isviridov | Thank you all for comming | 14:58 |
| isviridov | #endmeeting | 14:58 |
| ikhudoshyn | (bow) | 14:59 |
| openstack | Meeting ended Thu Feb 5 14:58:59 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-02-05-14.00.html | 14:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-02-05-14.00.txt | 14:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-02-05-14.00.log.html | 14:59 |
| *** charlesw_ has joined #magnetodb | 15:02 | |
| *** charlesw has quit IRC | 15:05 | |
| *** charlesw_ is now known as charlesw | 15:05 | |
| *** ajayaa has quit IRC | 15:19 | |
| *** isviridov is now known as isviridov_away | 15:25 | |
| *** achanda has joined #magnetodb | 15:53 | |
| openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Updates tempest pinned revision https://review.openstack.org/153267 | 15:57 |
| *** achanda has quit IRC | 16:05 | |
| *** jeromatron has quit IRC | 16:07 | |
| *** achuprin_ has quit IRC | 16:09 | |
| *** jeromatron has joined #magnetodb | 16:11 | |
| *** rushiagr is now known as rushiagr_away | 16:21 | |
| *** achuprin_ has joined #magnetodb | 16:25 | |
| *** ajayaa has joined #magnetodb | 16:27 | |
| *** jeromatron has quit IRC | 16:41 | |
| *** jeromatron has joined #magnetodb | 16:43 | |
| *** rushiagr_away is now known as rushiagr | 16:49 | |
| *** miqui_ has quit IRC | 16:52 | |
| *** denis_makogon has quit IRC | 17:05 | |
| *** shashankchakelam has joined #magnetodb | 17:07 | |
| *** shashankchakelam has left #magnetodb | 17:07 | |
| *** ygbo has quit IRC | 17:12 | |
| openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Updates tempest pinned revision https://review.openstack.org/153267 | 17:29 |
| *** jeromatron has quit IRC | 18:11 | |
| *** jeromatron has joined #magnetodb | 18:24 | |
| *** achanda has joined #magnetodb | 18:25 | |
| *** jeromatron has quit IRC | 18:27 | |
| openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Moves to oslo.i18n https://review.openstack.org/153325 | 18:30 |
| *** jeromatron has joined #magnetodb | 18:34 | |
| *** rushiagr is now known as rushiagr_away | 18:36 | |
| *** ajayaa has quit IRC | 18:39 | |
| *** miqui_ has joined #magnetodb | 18:40 | |
| openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Updates requirements.txt to using oslo.messaging>=1.6.0 https://review.openstack.org/153335 | 18:50 |
| *** achanda has quit IRC | 21:22 | |
| *** miqui_ has quit IRC | 21:28 | |
| *** achanda has joined #magnetodb | 21:50 | |
| *** jeromatron has quit IRC | 22:13 | |
| *** jeromatron has joined #magnetodb | 22:17 | |
| *** charlesw_ has joined #magnetodb | 22:25 | |
| *** charlesw has quit IRC | 22:26 | |
| *** charlesw_ is now known as charlesw | 22:26 | |
| *** jeromatron has quit IRC | 22:34 | |
| *** jeromatron has joined #magnetodb | 22:41 | |
| *** jeromatron has quit IRC | 23:33 | |
| *** charlesw has quit IRC | 23:36 | |
| *** openstack has joined #magnetodb | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!