14:01:12 #startmeeting magnetodb 14:01:17 Meeting started Thu Mar 26 14:01:12 2015 UTC and is due to finish in 60 minutes. The chair is isviridov. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:20 The meeting name has been set to 'magnetodb' 14:01:24 Hi isviridov. 14:01:25 Who is here today? 14:01:29 o/ 14:01:30 o/ 14:01:37 o/ 14:02:20 Ok, today agenda #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#26_Mar.2C_2015.2C_14:00_UTC 14:02:34 And the first short topic 14:02:38 #topic Go through action items isviridov 14:02:50 #link http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-03-12-14.01.html 14:03:14 There was only one, and I can report that meeting schedule has been updated 14:03:22 Now it is every second week 14:03:27 o/ 14:03:38 I saw the logs of previous meeting. 14:03:45 fine with that btw. 14:03:51 #link https://wiki.openstack.org/wiki/Meetings#MagnetoDB_Team_meeting 14:04:16 Hello ominakov 14:04:26 ajayaa great! 14:04:33 hello guys 14:04:35 No other action items 14:04:38 Next topic 14:04:48 #topic Round of status isviridov 14:04:58 Who want to be first? 14:05:17 I'll go 14:05:49 ominakov welcome back 14:06:44 Since last meeting, we merged some patches: refactoring notification, adding health check body details, standalone health check metrics service. 14:07:50 Dima helped a lot. Truely a team effort. 14:08:08 Great to hear! 14:08:26 I can share my status 14:09:02 Actually I didn't spend a lot of time to project last weeks. 14:09:34 But I've ordered launchpad and released kilo-3 milestone 14:09:43 Also send short anonce in ML 14:09:49 #link https://launchpad.net/magnetodb/kilo/kilo-3 14:09:52 Over 14:10:45 dukhlov ajayaa ominakov any updates from your side? 14:11:11 isviridov, any plans about openstack incubation, 14:11:12 ? 14:11:22 Maybe you can share the vision going forward. 14:11:53 dukhlov charlesw sure 14:13:31 The latest update from TC I know was an annoncement that new big tent reform is applyed and now any project can apply for status as part of openstack 14:14:27 #link http://www.openstack.org/blog/2015/02/tc-update-project-reform-progress/ 14:15:42 isviridov, We are working on a mdb backend for Openstack services. We have ported Keystone to use MagnetoDB as the datastore. 14:16:18 So, now we have a clear rules how to start. However I have not found any recomened way how to do it. 14:16:47 We are trying to write a scalable and fault tolerant db layer for Openstack services. 14:17:03 ajayaa, sounds very cool, any details, links? 14:17:07 isviridov, Am I interrupting you? 14:17:19 http://ajayaa.github.io/distributed-db.html 14:17:27 Also personally it is not my first priority and I can't spend 100% time on it, so any help or ever initiative to drive this process is very appresiated 14:17:32 here is a demo of Keystone running with mdb as backend. 14:17:39 ajayaa it is ok. N.p. 14:18:07 The showrt answer, I 14:18:50 'll try to start preparation the documents/wiki pages next week according to https://wiki.openstack.org/wiki/Governance/NewProjectTeams 14:18:54 Here is a spec for the same. https://review.openstack.org/#/c/148521/ 14:19:02 If anyone would like to joing very welcome 14:19:16 charlesw that is about incubation 14:19:41 * isviridov checking links from ajayaa 14:21:08 The keystone spec will get accepted once Keystone people start reviewing specs for L. 14:21:32 ajayaa looks really cool, have you just removed keystone integration? 14:21:46 isviridov, yes. needed to. 14:22:15 otherwise we would be stuck in a loop. :) 14:23:02 Unexpected usage actually 14:23:37 actually, we have plans to move all of OS components to mdb in the future. 14:23:52 #What are your plans, about it? 14:23:56 I see 14:24:00 The real problem is OS apis were written initially assuming relational db as a backend. 14:24:21 But we are trying our best to support all the apis. 14:24:39 We have started to move glance as well. 14:24:48 Nova is the real challenge. 14:25:30 ajayaa what is feedback? 14:25:42 Also I wanted to let you people know that dynamodb api is a bit limited. 14:25:50 I mena from glance and other you have tried already 14:26:38 We are designing schema for glance now. But we have a working Keystone as I showed in the demo. 14:26:51 ajayaa, looks like mdb is not really good backend for glance, it needs to store huge images 14:26:54 * isviridov for protocol #link https://review.openstack.org/#/c/148521/2 14:27:12 dukhlov, it does not store images on its own. 14:27:25 only metadata? 14:27:35 dukhlov, yes. 14:27:44 ah, ok 14:27:47 The backend is swift or any object store. 14:29:08 The fact that mdb allows at maximum two columns per key is quite limiting btw. 14:29:45 especially when you are denormalizing data and storing it into a single table. 14:30:46 we can change it now I guess 14:30:51 But C* allows that. Can we by any chance allow more than two columns per key? 14:31:34 I would propose a spec for that if everyone is in favour of this? 14:31:38 now yes, after index LSI redesign I think we can extend our functionality 14:31:59 ajayaa I think we can, if we don't see performance impact 14:32:18 isviridov, dukhlov, C* already allows that. 14:32:29 and still support DDB API 14:32:51 We will just be a superset of ddb api. 14:33:47 ok, you can start to write spec 14:34:24 dukhlov, cool. 14:34:25 I can't guarantee now that we don't have anty problem there 14:34:49 anty? 14:34:50 but I think we will figure out this during reviewing spec 14:34:57 any 14:35:25 ajayaa have you shared your results with community? 14:35:30 I will write a spec. 14:35:52 isviridov, not yet. not the results. Just the spec with Keystone community. 14:36:40 I think it is important, to spread the info. NoSQL and Java always causes huge discussions 14:39:01 Looks like no other status. Next topic? 14:40:17 isviridov, I am doing that. 14:40:29 I am also attending the glance meeting now. 14:40:40 time clash. 14:41:13 * isviridov also joined 14:42:03 #topic Open discussion isviridov 14:42:09 The last topic 14:44:20 dukhlov charlesw do you think we a done for today? 14:46:56 Thank you guys for attending today meeting 14:47:03 #endmeeting