Thursday, 2014-10-16

*** jeromatron has quit IRC00:13
*** charlesw has joined #magnetodb00:39
*** charlesw has quit IRC01:13
*** charlesw has joined #magnetodb01:17
*** achuprin_ has quit IRC02:31
*** achuprin_ has joined #magnetodb02:46
*** vivekd has joined #magnetodb03:41
*** charlesw has quit IRC03:42
*** vivekd has quit IRC04:17
*** vivekd has joined #magnetodb04:27
*** rushiagr_away is now known as rushiagr04:37
*** vnaboychenko has joined #magnetodb04:57
*** k4n0 has joined #magnetodb05:29
*** rushiagr is now known as rushiagr_away06:00
*** vivekd has quit IRC06:04
*** achuprin_ has quit IRC06:37
*** achuprin_ has joined #magnetodb06:50
*** vnaboychenko has quit IRC07:14
*** romainh has joined #magnetodb07:59
*** isviridov_away is now known as isviridov08:24
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds documentation on health check request
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Improves tempest table creation and deletion waiting mechanism
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds documentation on health check request
*** vnaboychenko has joined #magnetodb10:15
*** openstackgerrit has quit IRC10:19
*** vnaboychenko has quit IRC10:19
*** openstackgerrit has joined #magnetodb10:21
openstackgerritIlya Sviridov proposed a change to stackforge/magnetodb-specs: Test patchset
openstackgerritIllia Khudoshyn proposed a change to stackforge/magnetodb: Fix time format in log
openstackgerritAndreas Jaeger proposed a change to stackforge/magnetodb-specs: Cleanup branding and requirements
*** keith_newstadt has joined #magnetodb11:49
*** keith_newstadt has quit IRC11:54
*** keith_newstadt has joined #magnetodb11:54
isviridovHere is a kilo scope
isviridovI believe that blueprint list is complete and prioritized12:00
isviridovThe bugs should be triaged12:01
isviridovHere is meeting agenda for today
isviridovFeel free to extend12:11
isviridovrushiagr_away, around?12:11
isviridovrushiagr_away, do you know if ajayaa will join the meeting?12:11
openstackgerritA change was merged to stackforge/magnetodb-specs: Cleanup branding and requirements
isviridovHello everybody12:59
isviridovMeeting time?12:59
isviridovkeith_newstadt, rushiagr_away, dukhlov, ikhudoshyn, achudnovets o/13:00
achuprin_Hi team!13:00
isviridovGreat nick achuprin_ :)13:00
keith_newstadthi all13:01
isviridovHello keith_newstadt13:01
isviridovLooks like nobody from Relience with us today13:01
isviridovkeith_newstadt, what about Charles and Nuno?13:01
isviridovWill they join us&13:02
keith_newstadti'll check in...13:02
isviridovkeith_newstadt, would be great. There are not many people today13:03
* isviridov thinks if it is reasonable to have meeting today or send update via ML13:03
isviridovdukhlov, hey13:04
isviridovanybody else here?13:04
*** avinogradov has joined #magnetodb13:05
keith_newstadtcharles just responded that he's on his way.  still driving in.13:05
* isviridov thinks less people less topics13:05
isviridovOk, let us start13:05
isviridov#startmeting magnetodb13:06
isviridov#startmetting magnetodb13:06
isviridov#startmeeting magnetodb13:06
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:06
openstackThe meeting name has been set to 'magnetodb'13:06
isviridovHi there13:06
isviridovSo today agenda
isviridovAnd let us go throgh action items from last time13:07
isviridov#topic Go through action items13:08
isviridovajayaa review current list of metrics13:08
isviridovHe it not with us today, but I've updated the BP #link
isviridovbased on uscases we have now. Pls see whiteboard section13:09
isviridovThe metrics list in google spreadsheet is also updated with 'Data destination' column13:09
isviridovI mean #link
isviridovAny comments here?13:10
dukhlovnot from my side13:11
isviridovOk, move on?13:11
isviridovisviridov start create spec repo like
isviridovHere is a progress13:11
isviridovSo, here it is #link
dukhlovgreat news13:12
*** charlesw has joined #magnetodb13:12
isviridovI will update the docs a bit, but we can go with it already13:12
isviridovStartinng from kilo we are following standard community BP approval process13:13
isviridovI will move all current drafts from wiki to specs13:14
isviridov#topic Juno release status update
isviridovI think we have done with juno and I'm going to prerare release today13:15
isviridovThe branch stable/juno will be created for critical and security fixes13:15
isviridovAny objections, comments?13:16
isviridovdukhlov, charlesw ?13:16
charleswfine with me13:16
dukhlovok for me13:17
isviridov#topic Kilo roadmap overview and discussion
isviridovI believe it is the biggest topic for today.13:17
isviridovThe Kilo milestone scope #link
isviridovThere are several really huge blueprints13:18
isviridovMultidatacenter replication13:19
isviridovIntegration with Celiometer13:19
isviridovCassandra backend driver redesign13:19
isviridovExport/Import data operations13:19
isviridovSupport of global indexes13:19
isviridovI beleave we are slow with specs. We have only several designs approved.13:20
dukhlovwhat about backups?13:20
isviridovDo you mean 'Export/Import data operations'?13:21
isviridovI believe it is what we have to do in scope of mdb13:21
dukhlovno, I mean cassandra low level backups13:21
charleswBackup/recovery should be different13:21
dukhlovDo we skip Backups for kilo?13:22
keith_newstadtit feels like a lower priority to me13:23
isviridovdukhlov, it should be eather job of administrators or database management layer -trove13:23
keith_newstadtas it could be delivered as part of operations13:23
isviridovdukhlov, what do you think?13:23
dukhlovok, clear13:23
dukhlovthat is right way for me, but in this case we need to create trove integration bp13:24
isviridovdukhlov, not sure that we really need it in kilo13:24
isviridovI suggest to wait for trove evolution :)13:25
isviridovdukhlov, 'Cassandra backend driver redesign' should be specified well13:26
dukhlovI plan to write spec next week13:27
isviridovdukhlov, as you know we have some simplifications in monitoring during waiting for this13:27
isviridovdukhlov, cool13:27
isviridov#action dukhlov write a spec for 'Cassandra backend driver redesign'13:27
isviridov#action isviridov sync with ajayaa about 'Integration with Celiometer' status13:28
* isviridov added remind for himself13:28
isviridovkeith_newstadt, what is the demand for 'Support of global indexes' from your point of view?13:29
isviridovkeith_newstadt, I13:29
isviridov've set it as Low prior13:29
keith_newstadtwe don't have anyone asking for it at the moment13:30
keith_newstadti think lower priority is fine.  better that we make what we have as solid and operable as possible.13:30
isviridovkeith_newstadt, agree13:30
charlesw+1 to put more focus on operation side13:31
dukhlovCassandra 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 it13:31
* isviridov just realised that it would be great to send kilo roadmap to ML13:31
isviridov#action isviridov share kilo scope with communnity via ML13:31
isviridovdukhlov, +113:32
isviridovdukhlov, great to know13:32
isviridovLooks like no other voices, let us move discussion to ML13:33
isviridovdukhlov, keith_newstadt, charlesw?13:34
isviridovAre we done with it for now?13:34
charleswdukhlov, what's the timeline for C* 3.0?13:34
dukhlovcharles: have no idea13:35
dukhlovI will check13:35
isviridovdukhlov, :)13:35
isviridovdukhlov, no ideas, just hope13:35
isviridovOk, let us move on13:36
isviridov#topic Open discussion13:36
isviridovcharlesw, will you attend summmit?13:36
charleswnot going this time13:36
isviridovcharlesw, :(13:37
isviridovWe have a design session there. 90 mins !13:37
charleswgood luck with that, keith will be there13:37
isviridovWould be great to have cores there.13:38
keith_newstadtwe were limited on how many we could send13:38
keith_newstadtit should be easier next time when the summit is in north america13:38
isviridovkeith_newstadt, here it is the same :( I know guy from Mirantis who pays for himself13:39
isviridovkeith_newstadt, yeap13:39
isviridovGentlemen we have some time left13:40
keith_newstadthow about cores from mirantis?  who is coming?13:40
isviridovkeith_newstadt, it is only me13:40
keith_newstadtwe will need to promote the session, as it will be important to have community participation13:41
isviridovsure thing. I have to clarify the schedule13:41
keith_newstadti know some folks around boston that i can reach out to13:41
keith_newstadthaving a link will help13:42
isviridov#action isviridov clarify schedule of Ecosystem MagnetoDB design session13:42
isviridovI have not found it in shed before13:42
isviridovkeith_newstadt, returning back to kilo are you interested in horizon integration for mdb?13:43
charleswAre we going to have some lab time for design session. Last time I attended a couple and felt very helpful.13:44
keith_newstadti think it is interesting, more from the community perspective than the symantec perspective13:44
keith_newstadtonly limited functionality - view tables, sizes, etc. but not manage data13:44
keith_newstadtenough to give visibility to the community13:44
keith_newstadti think a clear and easy set up, perhaps some open hosting, and sample code would be good as well13:45
isviridovkeith_newstadt, yes. We have TechTalks for this also13:45
keith_newstadtit is very compelling when you start to use it hands-on with real use cases13:45
isviridovcharlesw, what do you mean 'lab time'?13:46
charleswmeaning hands-on lab exercises13:47
*** SpyRay has joined #magnetodb13:47
charleswAnother topic, anybody interested in a Java client?13:47
*** avinogradov has quit IRC13:49
dukhlovJava Client to MagnetoDB?13:49
keith_newstadtwe have had requests for client libraries within symantec13:49
isviridovcharlesw, it is a great idea, but there are workshops for this. We have to figure out what format is the best13:49
charleswA fluent style Java API can be more user friendly than REST API13:49
isviridovcharlesw, I'm very interested in blueprint for this :)13:49
isviridovkeith_newstadt, charlesw there are already existing implementations, would be great to look and probably contribute13:51
isviridovhere it is #link
charleswdukhlov, yes I meant Java client to MagnetoDB13:53
isviridov#action isviridov do realease of mdb Juno13:53
* isviridov one more remind :)13:53
isviridovcharlesw, does nuno uses IRC?13:54
charleswI'll ask him13:55
isviridovThere is a patch from him, probably it will be easier to clarify details in chat13:55
* isviridov 4 mins left13:56
isviridovAre we done or 4 mins for coffe?13:56
keith_newstadt+1 :)13:56
isviridovaostapenko, wow. You were here13:57
isviridovThank you guys13:57
*** keith_newstadt has quit IRC13:57
charleswthanks for organizing13:57
openstackMeeting ended Thu Oct 16 13:57:33 2014 UTC.  Information about MeetBot at . (v 0.1.4)13:57
*** vnaboychenko has joined #magnetodb13:57
openstackMinutes (text):
isviridovvnaboychenko, hey13:57
*** keith_newstadt has joined #magnetodb13:58
*** isviridov is now known as isviridov_afk14:00
achudnovetshey guys. Are we going to add jolokia agent to ccm for our devstack integration? It's aabout bp
dukhlovhey achudnovets14:02
* isviridov_afk break canceled14:02
dukhlovI think we should do this14:02
isviridov_afkdukhlov, +114:03
achudnovetsdukhlov: I think so.14:03
isviridov_afkachudnovets, is it possible to do it with ccm?14:03
isviridov_afkIt is the main concern I have14:03
isviridov_afkSpyRay, achuprin_ around?14:04
achudnovetsisviridov_afk: I'll look at it, but I think it should be possible. It's just an another java agent :)14:05
*** isviridov_afk is now known as isviridov14:05
isviridovYeap, we have done it already with heap setting.14:06
*** keith_newstadt has quit IRC14:06
isviridovShouldn't be a problem14:06
isviridovAnd we will be able to write functional test for it. Thats great14:06
*** keith_newstadt has joined #magnetodb14:07
isviridovHow jolokia is distributed?14:07
achudnovetsbut this agent first should be downloaded, so we need to change a bit our devstack integration code. If achuprin_ can help me with it...14:07
isviridovachudnovets, SpyRay is a correct guy14:08
achudnovetsisviridov: it's jar file14:08
isviridovachudnovets, there are list in maven repo
achudnovetsisviridov: Oh, thanks! I forget about maven :)14:09
SpyRaySure, i can help with jolokia agent14:09
isviridovachudnovets, will you add it to spec?14:09
achudnovetsisviridov: ok, I'll do14:10
achudnovetsisviridov, dukhlov, SpyRay: thanks for you help :)14:10
isviridovSpyRay, it is passed to cassandra as cmd parameter14:10
isviridovSpyRay, just another JVM_OPTS for you14:11
isviridov!m achudnovets14:12
[o__o]You're doing good work, achudnovets!14:12
openstackisviridov: Error: "m" is not a valid command.14:12
isviridov!m SpyRay14:12
[o__o]You're doing good work, SpyRay!14:12
openstackisviridov: Error: "m" is not a valid command.14:12
isviridov[o__o] and openstack bots have different oppinios14:13
*** isviridov is now known as isviridov_afk14:13
SpyRayfor do this we will need to parse some files before 'ccm start'14:13
charleswany security concern about jolokia?14:14
*** isviridov_afk is now known as isviridov14:16
isviridovSpyRay, what do you mean?14:16
isviridovcharlesw, it will be used between C* and mdb-api nodes. The same network as usuall data14:17
*** keith_newstadt has quit IRC14:17
charleswThanks isviridov, so jolokia is for internal use only, not opening up whole C* JMX beans, right?14:20
isviridovcharlesw, exactly. We are using it to collect JMX data from python14:21
SpyRayisviridov, I said that I think that add jolokia will not be difficult14:21
isviridovachudnovets, probably it should be described more in spec14:22
isviridovSpyRay, cool!14:22
achudnovetsisviridov: ok14:26
*** vnaboychenko has quit IRC14:34
*** isviridov is now known as isviridov_afk14:35
*** k4n0 has quit IRC14:40
*** SpyRay has quit IRC14:43
*** openstackgerrit has quit IRC14:48
*** openstackgerrit has joined #magnetodb14:50
*** jeromatron has joined #magnetodb15:08
*** jeromatron has quit IRC15:33
*** jeromatron has joined #magnetodb15:33
*** jeromatron has quit IRC15:36
*** jeromatron has joined #magnetodb15:45
*** openstackstatus has joined #magnetodb16:13
*** ChanServ sets mode: +v openstackstatus16:13
-openstackstatus- NOTICE: An error in a configuration change to mitigate the poodle vulnerability caused a brief outage of from 16:06-16:12. The problem has been corrected and is working again.16:18
*** jeromatron has quit IRC16:21
*** jeromatron has joined #magnetodb16:30
*** nunofsantos has joined #magnetodb16:37
*** nunofsantos is now known as nunosantos16:39
*** nunosantos has left #magnetodb16:39
*** nunosantos has joined #magnetodb17:02
*** nunosantos has quit IRC17:03
*** nunosantos has joined #magnetodb17:04
*** nunosantos has quit IRC17:05
*** nunosantos has joined #magnetodb17:07
*** nunosantos has quit IRC17:17
openstackgerritAlexander Chudnovets proposed a change to stackforge/magnetodb: Adds table size in monitoring API
*** nunosantos has joined #magnetodb17:20
*** vnaboychenko has joined #magnetodb18:08
*** jeromatron has quit IRC18:09
*** jeromatron has joined #magnetodb18:11
*** vnaboychenko has quit IRC18:21
*** vnaboychenko has joined #magnetodb18:41
*** vnaboychenko has joined #magnetodb18:41
*** vnaboych_ has joined #magnetodb19:02
*** vnaboychenko has quit IRC19:02
*** boris-42 has quit IRC19:02
*** boris-42 has joined #magnetodb19:03
*** jeromatron has quit IRC19:48
*** romainh has quit IRC19:56
*** jeromatron has joined #magnetodb20:33
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Fixes logging.conf.sample
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Fixes logging.conf.sample
*** jeromatron has quit IRC21:42
*** jeromatron has joined #magnetodb21:43
*** nunosantos has quit IRC21:51
*** charlesw has quit IRC21:56
*** jeromatron has quit IRC22:04

Generated by 2.14.0 by Marius Gedminas - find it at!