13:06:15 #startmeeting magnetodb 13:06:17 Meeting started Thu Oct 16 13:06:15 2014 UTC and is due to finish in 60 minutes. The chair is isviridov. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:06:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:06:20 The meeting name has been set to 'magnetodb' 13:06:31 Hi there 13:06:34 o/ 13:06:45 +1 13:07:41 So today agenda https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda 13:07:57 And let us go throgh action items from last time 13:08:10 #topic Go through action items 13:08:21 ajayaa review current list of metrics 13:08:52 He it not with us today, but I've updated the BP #link https://blueprints.launchpad.net/magnetodb/+spec/celiometer-integration 13:09:12 based on uscases we have now. Pls see whiteboard section 13:09:43 The metrics list in google spreadsheet is also updated with 'Data destination' column 13:09:56 I mean #link https://docs.google.com/a/mirantis.com/spreadsheets/d/1tYvgCSvkcOVED46MX8qSlUyrhNhHlyTrVkX7AXP-XR4/edit#gid=0 13:10:29 Any comments here? 13:11:16 not from my side 13:11:31 Ok, move on? 13:11:36 isviridov start create spec repo like https://github.com/openstack/nova-specs 13:11:44 Here is a progress 13:12:02 So, here it is #link http://magnetodb-specs.readthedocs.org/en/latest/ 13:12:05 great news 13:12:48 I will update the docs a bit, but we can go with it already 13:12:55 #link https://github.com/stackforge/magnetodb-specs 13:13:48 Startinng from kilo we are following standard community BP approval process 13:14:17 I will move all current drafts from wiki to specs 13:14:46 #topic Juno release status update https://launchpad.net/magnetodb/+milestone/juno-rc1 13:15:25 I think we have done with juno and I'm going to prerare release today 13:15:53 The branch stable/juno will be created for critical and security fixes 13:16:11 Any objections, comments? 13:16:14 dukhlov, charlesw ? 13:16:45 fine with me 13:17:10 ok for me 13:17:38 #topic Kilo roadmap overview and discussion https://launchpad.net/magnetodb/+milestone/kilo-1 13:17:50 I believe it is the biggest topic for today. 13:18:15 The Kilo milestone scope #link https://launchpad.net/magnetodb/+milestone/kilo-1 13:18:48 There are several really huge blueprints 13:19:06 Multidatacenter replication 13:19:10 Integration with Celiometer 13:19:15 Cassandra backend driver redesign 13:19:19 Export/Import data operations 13:19:23 Support of global indexes 13:20:36 I beleave we are slow with specs. We have only several designs approved. 13:20:47 what about backups? 13:21:14 Do you mean 'Export/Import data operations'? 13:21:44 I believe it is what we have to do in scope of mdb 13:21:44 no, I mean cassandra low level backups 13:21:48 Backup/recovery should be different 13:22:33 Do we skip Backups for kilo? 13:23:09 it feels like a lower priority to me 13:23:10 dukhlov, it should be eather job of administrators or database management layer -trove 13:23:19 as it could be delivered as part of operations 13:23:28 +1 13:23:42 dukhlov, what do you think? 13:23:43 ok, clear 13:24:30 that is right way for me, but in this case we need to create trove integration bp 13:24:57 dukhlov, not sure that we really need it in kilo 13:25:14 ок 13:25:21 I suggest to wait for trove evolution :) 13:25:57 +1 13:26:19 dukhlov, 'Cassandra backend driver redesign' should be specified well 13:26:48 Agree 13:27:06 I plan to write spec next week 13:27:16 dukhlov, as you know we have some simplifications in monitoring during waiting for this 13:27:21 dukhlov, cool 13:27:40 #action dukhlov write a spec for 'Cassandra backend driver redesign' 13:28:27 #action isviridov sync with ajayaa about 'Integration with Celiometer' status 13:28:40 * isviridov added remind for himself 13:29:20 keith_newstadt, what is the demand for 'Support of global indexes' from your point of view? 13:29:34 keith_newstadt, I 13:29:45 've set it as Low prior 13:30:07 we don't have anyone asking for it at the moment 13:30:26 i think lower priority is fine. better that we make what we have as solid and operable as possible. 13:30:48 keith_newstadt, agree 13:31:29 +1 to put more focus on operation side 13:31:37 Cassandra has plans to implement GSI for version 3. I think it is reasonable to wait for that if we dont have any use case for now to implement it 13:31:41 * isviridov just realised that it would be great to send kilo roadmap to ML 13:31:58 #action isviridov share kilo scope with communnity via ML 13:32:15 dukhlov, +1 13:32:21 dukhlov, great to know 13:33:43 Looks like no other voices, let us move discussion to ML 13:34:07 dukhlov, keith_newstadt, charlesw? 13:34:21 +1 13:34:22 Are we done with it for now? 13:34:36 dukhlov, what's the timeline for C* 3.0? 13:35:12 charles: have no idea 13:35:26 I will check 13:35:31 dukhlov, :) 13:35:37 dukhlov, no ideas, just hope 13:36:22 Ok, let us move on 13:36:27 #topic Open discussion 13:36:43 charlesw, will you attend summmit? 13:36:58 not going this time 13:37:12 charlesw, :( 13:37:23 We have a design session there. 90 mins ! 13:37:47 good luck with that, keith will be there 13:38:05 Would be great to have cores there. 13:38:29 we were limited on how many we could send 13:38:47 it should be easier next time when the summit is in north america 13:39:28 keith_newstadt, here it is the same :( I know guy from Mirantis who pays for himself 13:39:35 keith_newstadt, yeap 13:40:14 Gentlemen we have some time left 13:40:18 how about cores from mirantis? who is coming? 13:40:33 keith_newstadt, it is only me 13:41:15 we will need to promote the session, as it will be important to have community participation 13:41:42 sure thing. I have to clarify the schedule 13:41:59 i know some folks around boston that i can reach out to 13:42:15 having a link will help 13:42:19 #action isviridov clarify schedule of Ecosystem MagnetoDB design session 13:42:42 I have not found it in shed before 13:43:25 keith_newstadt, returning back to kilo are you interested in horizon integration for mdb? 13:44:11 Are we going to have some lab time for design session. Last time I attended a couple and felt very helpful. 13:44:11 i think it is interesting, more from the community perspective than the symantec perspective 13:44:36 only limited functionality - view tables, sizes, etc. but not manage data 13:44:46 enough to give visibility to the community 13:45:13 i think a clear and easy set up, perhaps some open hosting, and sample code would be good as well 13:45:42 keith_newstadt, yes. We have TechTalks for this also 13:45:43 it is very compelling when you start to use it hands-on with real use cases 13:45:59 :) 13:46:42 charlesw, what do you mean 'lab time'? 13:47:11 meaning hands-on lab exercises 13:47:55 Another topic, anybody interested in a Java client? 13:49:16 Java Client to MagnetoDB? 13:49:21 we have had requests for client libraries within symantec 13:49:28 sdks 13:49:29 charlesw, it is a great idea, but there are workshops for this. We have to figure out what format is the best 13:49:44 A fluent style Java API can be more user friendly than REST API 13:49:46 charlesw, I'm very interested in blueprint for this :) 13:51:15 keith_newstadt, charlesw there are already existing implementations, would be great to look and probably contribute 13:51:51 here it is #link http://developer.openstack.org/#sdk 13:52:05 #link http://jclouds.apache.org/guides/openstack/ 13:53:13 dukhlov, yes I meant Java client to MagnetoDB 13:53:36 #action isviridov do realease of mdb Juno 13:53:47 * isviridov one more remind :) 13:54:58 charlesw, does nuno uses IRC? 13:55:17 use* 13:55:18 I'll ask him 13:55:40 There is a patch from him, probably it will be easier to clarify details in chat 13:56:11 * isviridov 4 mins left 13:56:23 Are we done or 4 mins for coffe? 13:56:38 +1 :) 13:56:55 +1 13:57:05 aostapenko, wow. You were here 13:57:11 Thank you guys 13:57:23 #stopmeeting 13:57:30 thanks for organizing 13:57:33 #endmeeting