Thursday, 2014-12-11

*** denis_makogon has quit IRC01:00
*** charlesw has joined #magnetodb01:13
*** vnaboychenko has quit IRC01:47
*** vnaboychenko has joined #magnetodb01:52
*** vnaboychenko has quit IRC02:03
*** vivekd has joined #magnetodb02:38
*** tnurlygayanov has quit IRC02:59
*** aostapenko has quit IRC02:59
*** idegtiarov has quit IRC02:59
*** vnaboychenko has joined #magnetodb03:01
*** tnurlygayanov has joined #magnetodb03:04
*** aostapenko has joined #magnetodb03:04
*** idegtiarov has joined #magnetodb03:04
*** vivekd has quit IRC03:38
*** vivekd has joined #magnetodb03:49
*** vivekd has quit IRC03:51
*** idegtiarov has quit IRC03:52
*** idegtiarov has joined #magnetodb03:53
*** vivekd has joined #magnetodb04:02
*** vivekd has quit IRC04:16
*** vivekd has joined #magnetodb04:33
*** charlesw has quit IRC05:21
*** jeromatron has joined #magnetodb05:35
*** jeromatron has quit IRC05:39
*** jeromatron has joined #magnetodb05:39
*** rushiagr_away is now known as rushiagr06:00
*** jeromatron has quit IRC06:21
*** jeromatron has joined #magnetodb06:24
*** jeromatron has quit IRC06:26
*** jeromatron has joined #magnetodb06:29
*** ajayaa has joined #magnetodb06:33
*** jeromatron has quit IRC06:38
*** jeromatron has joined #magnetodb06:41
*** jeromatron has quit IRC06:46
*** tnurlygayanov has quit IRC07:02
*** aostapenko has quit IRC07:02
*** tnurlygayanov has joined #magnetodb07:08
*** aostapenko has joined #magnetodb07:08
ajayaaisviridov, dukhlov, ikhudoshyn, please review https://review.openstack.org/#/c/140321/07:28
ajayaaIt's blocking the mdb metering code in ceilometer.07:29
*** k4n0 has joined #magnetodb07:44
*** denis_makogon has joined #magnetodb08:09
*** romainh has joined #magnetodb08:48
*** vnaboychenko has quit IRC09:17
*** denis_makogon has quit IRC09:41
*** keith_newstadt has joined #magnetodb11:36
*** keith_newstadt has quit IRC11:56
openstackgerritIllia Khudoshyn proposed stackforge/magnetodb: (WIP) Add backup manager  https://review.openstack.org/14102612:01
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id fiels to table description  https://review.openstack.org/14074012:03
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074012:03
*** vivekd has quit IRC12:22
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074012:27
*** ygbo has joined #magnetodb13:00
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074013:03
*** ajaya has joined #magnetodb13:07
*** ajayaa has quit IRC13:08
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074013:22
*** achuprin_ has joined #magnetodb13:50
isviridovHello everybody13:59
isviridovygbo, nice to see you here. Welcome to mdb chat!13:59
achuprin_Hi everyone14:00
isviridovI think it is time to start14:00
isviridov#startmeeting magnetodb14:00
openstackMeeting started Thu Dec 11 14:00:19 2014 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
isviridovWho is with us today?14:00
*** nunosantos has joined #magnetodb14:00
isviridovHello nunosantos14:00
ominakovhi, guys14:00
nunosantoshello14:00
dukhlovhello14:01
achuprin_o/14:01
aostapenkohi14:01
isviridovWhat is the weather in Boston now?14:01
isviridovnunosantos any snow?14:01
ygboThanks isviridov14:01
ikhudoshyn0/14:02
isviridov\014:02
isviridovOk, let start14:02
ajayao/14:02
nunosantosno major snow yet. cold though14:02
isviridovThe agenda for today https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Agenda14:02
isviridovnunosantos there was a lot of snow here, but now mostly all melt14:03
isviridov#topic Go through action items isviridov14:03
isviridovSeems there are no action items from last time14:04
isviridovhttp://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-04-14.00.html14:04
isviridovI believe we have what to discuss in Open discussions part14:04
isviridov#Open discussion isviridov14:05
achudnovetso/14:05
isviridovachudnovets would you like to start?14:05
* isviridov doesn't see charlesw14:05
achudnovetsok14:06
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074014:06
*** charlesw has joined #magnetodb14:06
achudnovetswe have an idea to change monitoring API url14:07
achudnovetsand use something like this /v1/admin/monitoring/tables?tenant_id=bla-bla14:07
charleswdo you have any doc?14:07
isviridovcharlesw hey, we are discussing exposing the statistics per table, but in comfortable way for statsd14:07
achudnovetsnot yet14:07
achudnovetsit's just an idea now14:08
isviridovcharlesw there is no doc yet, but there is a problem we would like to hear your oppinion about14:08
achudnovetsresponse will contain uuid, table name, tenant id and table stats14:08
achudnovetsresponse can be filtered by tenant, table id, table name etc14:09
achudnovetsbig question is auth for this api14:09
achudnovetspersonally I would prefer to use keystone auth14:10
dukhlovachudnovets, what does admin mean in /v1/admin/monitoring/tables?tenant_id=bla-bla?14:10
achudnovetsadmin is just part of url14:10
achudnovetslike 'data'14:10
charleswI have same question. Why url is not hierarchical?14:11
dukhlovbut we have data, management monitoring14:11
dukhlovit is type of aplication14:11
ikhudoshyn+1 to Dima14:11
dukhlovadmin is something new to me14:11
achudnovetswe can stick all non-data url under 'admin' url part. Or we can live it as it is14:12
dukhlovyes we can but why?14:12
achudnovetsmain idea is to use single url for all monitoring tasks14:12
isviridovBefore we proced with url, let us define the problem.14:12
dukhlovdo we have some reason for that?14:13
ikhudoshynachudnovets: why not just /v1/monitoring/...?14:13
isviridovdukhlov let me clarify14:13
isviridovikhudoshyn current Monitoring API is designed for user, and really difficult to  use by monitoring tools like collectd, nagios so on. Mostly because of dependency to to keystone and necessity to manage credentials. So, the idea is to introduce an api for collecting this data under the cloud14:13
achudnovetsikhudoshyn: it's ok for me14:13
*** jeromatron has joined #magnetodb14:14
ikhudoshynisviridov: ic14:14
achudnovetsisviridov: I would like to say the main problem is that client needs to know all tenants to be able to monitor them14:14
isviridovikhudoshyn for /v1/monitoring we still have to manage authorization and don't have a tenant_list feature, to see statistics over all mdb14:15
dukhlovisviridov, it is authentification staff and should be configurable14:15
isviridovachudnovets just mentioned, thank you14:15
isviridovdukhlov ikhudoshyn charlesw let us move back to problem14:16
ikhudoshynisviridov: than it looks like a completely separate app14:16
ikhudoshynwith a separate endpoint, not just url14:16
isviridovThe suggested solution is one more api, anu other ideas?14:16
ikhudoshyn+1 for another api14:16
achudnovets-114:16
dukhlov-114:16
dukhlovagain, what is the problem?14:17
isviridovachudnovets dukhlov ideas?14:17
*** jeromatron has quit IRC14:17
achudnovetsI think it can be just part of existing API but it should be accessible only by users with admin role14:17
isviridovdukhlov again, current Monitoring API is designed for user, and really difficult to  use by monitoring tools like collectd, nagios so on. Mostly because of dependency to to keystone and necessity to manage credentials and no ability to have a tenant list.\14:18
ikhudoshyndukhlov: seems like the problem is we need <tenant_id> to make /v1/monitoring/<tenant_id>/ url14:18
isviridovikhudoshyn exactly14:18
dukhlovok, so 2 problems - authentification and how to get tenant list14:18
dukhlovright?14:18
isviridovachudnovets it means we need to have keystone call before calling mdb. F.e. in nagios14:19
achudnovetsso my idea is /v1/monitoring/tables with filters. Only admin can use it. 403 in all other cases14:19
charleswdukhlov, +114:19
isviridovdukhlov let us start from these two14:19
achudnovetsisviridov: yes14:19
ikhudoshynachudnovets: how do you know he is an admin?14:19
dukhlovauthentification should be configurable, we can switch off it if it is needed14:19
isviridovdukhlov right, but to switch off/on we need it separate first14:20
achudnovetsisviridov: admin role in "magnetodb" tenant14:20
achudnovetspolisy.json14:20
*** miqui_ has joined #magnetodb14:21
ikhudoshynachudnovets: i.e. we still need request to keystone first?14:21
achudnovets* policy.json14:21
dukhlovabout tenant list... we need provide path to monitored resourse14:21
achudnovetsikhudoshyn: yes14:21
dukhlovand that is all14:21
isviridovachudnovets anyhow it involves keystone, it is the same we have now. You can call keystone for tenant list and call mdb n-times for data.14:21
ikhudoshyndukhlov: the idea is to grab all stats in a single request14:21
isviridovikhudoshyn it is more optimization, but with specific api we can do a lot of optimizations14:22
dukhlovok let /v1/monitoring will return all tennants metrics14:22
achudnovetsisviridov: partially agree. You'll need very simple keystone config for /v1/monitoring/tables valiant14:22
achudnovets*variant14:23
isviridovdukhlov what about authorization if so?14:24
isviridovmiqui_ welcome to meeting14:24
ikhudoshynachudnovets: did i get it right, now we have a long and complex way to do it, and separate api will give us another one, fast and convenient?14:24
miqui_hi isviridov...14:25
*** dukhlov has left #magnetodb14:25
achudnovetsikhudoshyn: what do you mean "separate api"? new service?14:26
*** dukhlov has joined #magnetodb14:26
ikhudoshynyep14:26
isviridovikhudoshyn yes, or better to say reasonable for monitoring purposes14:26
dukhlovtest14:26
ikhudoshyndukhlov: passed14:26
isviridovdukhlov test14:26
achudnovetsdukhlov: pong )14:26
charleswIs it based on the idea we discussed last week, using domain admin role?14:26
*** jeromatron has joined #magnetodb14:27
achudnovetscharlesw: yep, it's about monitoring api.14:28
dukhlovtest214:29
ikhudoshyndukhlov: passed214:29
dukhlov"/v1/monitoring/tenants/tenant_id" for specific tenant14:30
* isviridov what a nice formatting14:30
dukhlov"/v1/monitoring/tenants/tenant_id/tables/table_name" for specific table14:31
ikhudoshyndukhlov: too long14:31
achudnovetsikhudoshyn: +114:31
dukhlovwe can deploy two different pipelines for different urls but use the same application14:32
dukhlovtoo long but it is path to resource to be monitored14:33
ikhudoshyndukhlov: -1 for the same app14:33
nunosantosmaybe remove the “tables” part, just tadd the table name adter tenant_id14:33
nunosantos* add14:33
achudnovetsdukhlov: I think we can use single url for monitoring.14:33
charleswnunosantos, -1, not by openstack convention14:34
achudnovetsurl like /v1/monitoring/ or /v1/monitoring/tables14:34
*** chao_li has joined #magnetodb14:35
charleswwhy not /v1/monitoring/tenants?14:35
miqui_what about keeping url simple and passing additional params in the http headers?14:35
achudnovetsbecause it's not info about tenants14:35
isviridovdukhlov I don't like the way of mixing existing functionality and hacking with deployment.14:35
miqui_or part of a json payload?14:35
achudnovetsmiqui_: it will be GET request with params14:36
miqui_k..14:36
achudnovetsif we'll have monitoring with data API I'd like to use keystone auth for it. If it will be separate app, then we can use any type of auth14:38
ikhudoshynachudnovets: +114:38
ajaya+1 for a different app. Ideally we should not mix user apis with management apis.14:40
* isviridov do we have any other topics to discuss/14:40
ominakovachudnovets, what do you mean in "monitoring with data API" ?14:40
achudnovetsominakov: just like current implementation14:41
ajayaisviridov, I have a question regarding incubation of mdb? Are we planning to apply for incubation? If yes, when? What benefit do we get by becoming an incubated project?14:42
miqui_if the big picture goal it to become an openstack core project.. then this is a big first step..14:43
charleswachudnovets, what do you mean by any type of auth? Do you mean we need to come up with a separate authN other than keystone?14:43
isviridovajaya yes we are planning to do it, I really hoped to do it last cycle, so the plan is this cycle.14:44
achudnovetscharlesw: yes. I think ikhudoshyn and isviridov means that we can use non-keystone auth for monitoring. Is it right?14:45
ikhudoshynachudnovets: possibly14:45
isviridovajaya the main benefit is some king of endorsement of project14:46
ajayaisviridov, so if all goes well then mdb would be an incubated project by end of kilo?14:46
*** achuprin_ has quit IRC14:48
isviridovajaya we will see, the incubation process and status is changing now, but teh goal is to reach this status whatever it is.14:48
isviridovajaya more details http://lists.openstack.org/pipermail/openstack-tc/2014-November/000887.html14:48
*** achuprin_ has joined #magnetodb14:48
charleswisviridov, let us know what we all can do to get there14:48
isviridovcharlesw sure14:49
isviridovWhere are we with monitoring?14:49
isviridovachudnovets could you summarize?14:50
achudnovetsok14:50
miqui_+1 on incubation, am late in the game..but i'll do what i can...14:50
isviridovmiqui_ great to see you with us.  What company are you working on?14:52
miqui_i work for Hewlett-Packard14:52
isviridovCool, it helps with diversity of team, what is one of requerements. Waiting for your patches :)14:53
achudnovetsso the idea is to change monitoring API url and create separate app for it. or we can change our existing controllers for monitoring api. I can prepare spec for it and then we can discuss it in gerrit14:54
charleswmiqui, what location? I'm with Symantec, Boston14:55
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074014:55
isviridov#action achudnovets create a spec for integration with external monitoring systems14:55
miqui_charlesw: Atlanta14:55
* isviridov charlesw and miqui_ are going to have some beer14:55
* isviridov seems not14:55
*** jeromatron has quit IRC14:55
* isviridov 4 mins left14:56
isviridovCountdown14:58
isviridov314:58
isviridov214:58
isviridov114:58
isviridovThank you fro comming, see you in IRC and ML14:58
isviridov#endmeeting14:59
openstackMeeting ended Thu Dec 11 14:59:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-11-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-11-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-11-14.00.log.html14:59
charleswbye guys14:59
miqui_buy...14:59
ajayabye14:59
nunosantosbye14:59
dukhlovbye14:59
achuprin_bye14:59
miqui_*bye14:59
*** nunosantos has quit IRC15:00
*** chao_li has quit IRC15:03
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074015:04
*** rushiagr is now known as rushiagr_away15:16
openstackgerritCharles Wang proposed stackforge/magnetodb-specs: Add request metrics speccification  https://review.openstack.org/13895015:20
*** ajaya has quit IRC15:20
openstackgerritCharles Wang proposed stackforge/magnetodb-specs: Add request metrics speccification  https://review.openstack.org/13895015:34
openstackgerritIllia Khudoshyn proposed stackforge/magnetodb: (WIP) Add backup manager  https://review.openstack.org/14102615:36
*** jeromatron has joined #magnetodb15:52
*** jeromatron has quit IRC16:02
*** jeromatron has joined #magnetodb16:07
*** jeromatron has quit IRC16:10
*** jeromatron has joined #magnetodb16:11
*** jeromatron has quit IRC16:13
*** isviridov is now known as isviridov_away16:16
*** jeromatron has joined #magnetodb16:19
*** jeromatron has quit IRC16:24
openstackgerritAndrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description  https://review.openstack.org/14074016:25
*** jeromatron has joined #magnetodb16:27
*** jeromatron has quit IRC16:29
*** rushiagr_away is now known as rushiagr16:29
*** jeromatron has joined #magnetodb16:34
*** jeromatron has quit IRC16:36
*** romainh has left #magnetodb16:39
*** jeromatron has joined #magnetodb16:49
*** jeromatron has quit IRC17:02
*** jeromatron has joined #magnetodb17:04
*** jeromatron has quit IRC17:26
*** jeromatron has joined #magnetodb17:27
*** ygbo has quit IRC17:28
*** jeromatron has quit IRC17:34
*** jeromatron has joined #magnetodb17:35
*** jeromatron has quit IRC17:57
*** jeromatron has joined #magnetodb17:59
*** jeromatron has quit IRC18:22
*** rushiagr is now known as rushiagr_away18:40
*** jeromatron has joined #magnetodb19:16
*** jeromatron has quit IRC19:34
*** jeromatron has joined #magnetodb19:35
*** jeromatron has quit IRC20:22
*** jeromatron has joined #magnetodb20:24
*** vnaboychenko has joined #magnetodb21:02
*** keith_newstadt has joined #magnetodb21:13
*** keith_newstadt has quit IRC21:13
*** keith_newstadt has joined #magnetodb21:14
*** jeromatron has quit IRC21:47
*** jeromatron has joined #magnetodb21:49
*** jeromatron has quit IRC22:24
*** keith_newstadt has quit IRC22:34
*** jeromatron has joined #magnetodb22:49
*** keith_newstadt has joined #magnetodb23:03
*** jeromatron has quit IRC23:12
*** jeromatron has joined #magnetodb23:16
*** charlesw has quit IRC23:25
*** keith_newstadt has quit IRC23:53

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