*** denis_makogon has quit IRC | 01:00 | |
*** charlesw has joined #magnetodb | 01:13 | |
*** vnaboychenko has quit IRC | 01:47 | |
*** vnaboychenko has joined #magnetodb | 01:52 | |
*** vnaboychenko has quit IRC | 02:03 | |
*** vivekd has joined #magnetodb | 02:38 | |
*** tnurlygayanov has quit IRC | 02:59 | |
*** aostapenko has quit IRC | 02:59 | |
*** idegtiarov has quit IRC | 02:59 | |
*** vnaboychenko has joined #magnetodb | 03:01 | |
*** tnurlygayanov has joined #magnetodb | 03:04 | |
*** aostapenko has joined #magnetodb | 03:04 | |
*** idegtiarov has joined #magnetodb | 03:04 | |
*** vivekd has quit IRC | 03:38 | |
*** vivekd has joined #magnetodb | 03:49 | |
*** vivekd has quit IRC | 03:51 | |
*** idegtiarov has quit IRC | 03:52 | |
*** idegtiarov has joined #magnetodb | 03:53 | |
*** vivekd has joined #magnetodb | 04:02 | |
*** vivekd has quit IRC | 04:16 | |
*** vivekd has joined #magnetodb | 04:33 | |
*** charlesw has quit IRC | 05:21 | |
*** jeromatron has joined #magnetodb | 05:35 | |
*** jeromatron has quit IRC | 05:39 | |
*** jeromatron has joined #magnetodb | 05:39 | |
*** rushiagr_away is now known as rushiagr | 06:00 | |
*** jeromatron has quit IRC | 06:21 | |
*** jeromatron has joined #magnetodb | 06:24 | |
*** jeromatron has quit IRC | 06:26 | |
*** jeromatron has joined #magnetodb | 06:29 | |
*** ajayaa has joined #magnetodb | 06:33 | |
*** jeromatron has quit IRC | 06:38 | |
*** jeromatron has joined #magnetodb | 06:41 | |
*** jeromatron has quit IRC | 06:46 | |
*** tnurlygayanov has quit IRC | 07:02 | |
*** aostapenko has quit IRC | 07:02 | |
*** tnurlygayanov has joined #magnetodb | 07:08 | |
*** aostapenko has joined #magnetodb | 07:08 | |
ajayaa | isviridov, dukhlov, ikhudoshyn, please review https://review.openstack.org/#/c/140321/ | 07:28 |
---|---|---|
ajayaa | It's blocking the mdb metering code in ceilometer. | 07:29 |
*** k4n0 has joined #magnetodb | 07:44 | |
*** denis_makogon has joined #magnetodb | 08:09 | |
*** romainh has joined #magnetodb | 08:48 | |
*** vnaboychenko has quit IRC | 09:17 | |
*** denis_makogon has quit IRC | 09:41 | |
*** keith_newstadt has joined #magnetodb | 11:36 | |
*** keith_newstadt has quit IRC | 11:56 | |
openstackgerrit | Illia Khudoshyn proposed stackforge/magnetodb: (WIP) Add backup manager https://review.openstack.org/141026 | 12:01 |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id fiels to table description https://review.openstack.org/140740 | 12:03 |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 12:03 |
*** vivekd has quit IRC | 12:22 | |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 12:27 |
*** ygbo has joined #magnetodb | 13:00 | |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 13:03 |
*** ajaya has joined #magnetodb | 13:07 | |
*** ajayaa has quit IRC | 13:08 | |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 13:22 |
*** achuprin_ has joined #magnetodb | 13:50 | |
isviridov | Hello everybody | 13:59 |
isviridov | ygbo, nice to see you here. Welcome to mdb chat! | 13:59 |
achuprin_ | Hi everyone | 14:00 |
isviridov | I think it is time to start | 14:00 |
isviridov | #startmeeting magnetodb | 14:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
openstack | The meeting name has been set to 'magnetodb' | 14:00 |
isviridov | Who is with us today? | 14:00 |
*** nunosantos has joined #magnetodb | 14:00 | |
isviridov | Hello nunosantos | 14:00 |
ominakov | hi, guys | 14:00 |
nunosantos | hello | 14:00 |
dukhlov | hello | 14:01 |
achuprin_ | o/ | 14:01 |
aostapenko | hi | 14:01 |
isviridov | What is the weather in Boston now? | 14:01 |
isviridov | nunosantos any snow? | 14:01 |
ygbo | Thanks isviridov | 14:01 |
ikhudoshyn | 0/ | 14:02 |
isviridov | \0 | 14:02 |
isviridov | Ok, let start | 14:02 |
ajaya | o/ | 14:02 |
nunosantos | no major snow yet. cold though | 14:02 |
isviridov | The agenda for today https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Agenda | 14:02 |
isviridov | nunosantos there was a lot of snow here, but now mostly all melt | 14:03 |
isviridov | #topic Go through action items isviridov | 14:03 |
isviridov | Seems there are no action items from last time | 14:04 |
isviridov | http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-04-14.00.html | 14:04 |
isviridov | I believe we have what to discuss in Open discussions part | 14:04 |
isviridov | #Open discussion isviridov | 14:05 |
achudnovets | o/ | 14:05 |
isviridov | achudnovets would you like to start? | 14:05 |
* isviridov doesn't see charlesw | 14:05 | |
achudnovets | ok | 14:06 |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 14:06 |
*** charlesw has joined #magnetodb | 14:06 | |
achudnovets | we have an idea to change monitoring API url | 14:07 |
achudnovets | and use something like this /v1/admin/monitoring/tables?tenant_id=bla-bla | 14:07 |
charlesw | do you have any doc? | 14:07 |
isviridov | charlesw hey, we are discussing exposing the statistics per table, but in comfortable way for statsd | 14:07 |
achudnovets | not yet | 14:07 |
achudnovets | it's just an idea now | 14:08 |
isviridov | charlesw there is no doc yet, but there is a problem we would like to hear your oppinion about | 14:08 |
achudnovets | response will contain uuid, table name, tenant id and table stats | 14:08 |
achudnovets | response can be filtered by tenant, table id, table name etc | 14:09 |
achudnovets | big question is auth for this api | 14:09 |
achudnovets | personally I would prefer to use keystone auth | 14:10 |
dukhlov | achudnovets, what does admin mean in /v1/admin/monitoring/tables?tenant_id=bla-bla? | 14:10 |
achudnovets | admin is just part of url | 14:10 |
achudnovets | like 'data' | 14:10 |
charlesw | I have same question. Why url is not hierarchical? | 14:11 |
dukhlov | but we have data, management monitoring | 14:11 |
dukhlov | it is type of aplication | 14:11 |
ikhudoshyn | +1 to Dima | 14:11 |
dukhlov | admin is something new to me | 14:11 |
achudnovets | we can stick all non-data url under 'admin' url part. Or we can live it as it is | 14:12 |
dukhlov | yes we can but why? | 14:12 |
achudnovets | main idea is to use single url for all monitoring tasks | 14:12 |
isviridov | Before we proced with url, let us define the problem. | 14:12 |
dukhlov | do we have some reason for that? | 14:13 |
ikhudoshyn | achudnovets: why not just /v1/monitoring/...? | 14:13 |
isviridov | dukhlov let me clarify | 14:13 |
isviridov | ikhudoshyn 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 cloud | 14:13 |
achudnovets | ikhudoshyn: it's ok for me | 14:13 |
*** jeromatron has joined #magnetodb | 14:14 | |
ikhudoshyn | isviridov: ic | 14:14 |
achudnovets | isviridov: I would like to say the main problem is that client needs to know all tenants to be able to monitor them | 14:14 |
isviridov | ikhudoshyn for /v1/monitoring we still have to manage authorization and don't have a tenant_list feature, to see statistics over all mdb | 14:15 |
dukhlov | isviridov, it is authentification staff and should be configurable | 14:15 |
isviridov | achudnovets just mentioned, thank you | 14:15 |
isviridov | dukhlov ikhudoshyn charlesw let us move back to problem | 14:16 |
ikhudoshyn | isviridov: than it looks like a completely separate app | 14:16 |
ikhudoshyn | with a separate endpoint, not just url | 14:16 |
isviridov | The suggested solution is one more api, anu other ideas? | 14:16 |
ikhudoshyn | +1 for another api | 14:16 |
achudnovets | -1 | 14:16 |
dukhlov | -1 | 14:16 |
dukhlov | again, what is the problem? | 14:17 |
isviridov | achudnovets dukhlov ideas? | 14:17 |
*** jeromatron has quit IRC | 14:17 | |
achudnovets | I think it can be just part of existing API but it should be accessible only by users with admin role | 14:17 |
isviridov | dukhlov 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 |
ikhudoshyn | dukhlov: seems like the problem is we need <tenant_id> to make /v1/monitoring/<tenant_id>/ url | 14:18 |
isviridov | ikhudoshyn exactly | 14:18 |
dukhlov | ok, so 2 problems - authentification and how to get tenant list | 14:18 |
dukhlov | right? | 14:18 |
isviridov | achudnovets it means we need to have keystone call before calling mdb. F.e. in nagios | 14:19 |
achudnovets | so my idea is /v1/monitoring/tables with filters. Only admin can use it. 403 in all other cases | 14:19 |
charlesw | dukhlov, +1 | 14:19 |
isviridov | dukhlov let us start from these two | 14:19 |
achudnovets | isviridov: yes | 14:19 |
ikhudoshyn | achudnovets: how do you know he is an admin? | 14:19 |
dukhlov | authentification should be configurable, we can switch off it if it is needed | 14:19 |
isviridov | dukhlov right, but to switch off/on we need it separate first | 14:20 |
achudnovets | isviridov: admin role in "magnetodb" tenant | 14:20 |
achudnovets | polisy.json | 14:20 |
*** miqui_ has joined #magnetodb | 14:21 | |
ikhudoshyn | achudnovets: i.e. we still need request to keystone first? | 14:21 |
achudnovets | * policy.json | 14:21 |
dukhlov | about tenant list... we need provide path to monitored resourse | 14:21 |
achudnovets | ikhudoshyn: yes | 14:21 |
dukhlov | and that is all | 14:21 |
isviridov | achudnovets 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 |
ikhudoshyn | dukhlov: the idea is to grab all stats in a single request | 14:21 |
isviridov | ikhudoshyn it is more optimization, but with specific api we can do a lot of optimizations | 14:22 |
dukhlov | ok let /v1/monitoring will return all tennants metrics | 14:22 |
achudnovets | isviridov: partially agree. You'll need very simple keystone config for /v1/monitoring/tables valiant | 14:22 |
achudnovets | *variant | 14:23 |
isviridov | dukhlov what about authorization if so? | 14:24 |
isviridov | miqui_ welcome to meeting | 14:24 |
ikhudoshyn | achudnovets: 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 #magnetodb | 14:25 | |
achudnovets | ikhudoshyn: what do you mean "separate api"? new service? | 14:26 |
*** dukhlov has joined #magnetodb | 14:26 | |
ikhudoshyn | yep | 14:26 |
isviridov | ikhudoshyn yes, or better to say reasonable for monitoring purposes | 14:26 |
dukhlov | test | 14:26 |
ikhudoshyn | dukhlov: passed | 14:26 |
isviridov | dukhlov test | 14:26 |
achudnovets | dukhlov: pong ) | 14:26 |
charlesw | Is it based on the idea we discussed last week, using domain admin role? | 14:26 |
*** jeromatron has joined #magnetodb | 14:27 | |
achudnovets | charlesw: yep, it's about monitoring api. | 14:28 |
dukhlov | test2 | 14:29 |
ikhudoshyn | dukhlov: passed2 | 14:29 |
dukhlov | "/v1/monitoring/tenants/tenant_id" for specific tenant | 14:30 |
* isviridov what a nice formatting | 14:30 | |
dukhlov | "/v1/monitoring/tenants/tenant_id/tables/table_name" for specific table | 14:31 |
ikhudoshyn | dukhlov: too long | 14:31 |
achudnovets | ikhudoshyn: +1 | 14:31 |
dukhlov | we can deploy two different pipelines for different urls but use the same application | 14:32 |
dukhlov | too long but it is path to resource to be monitored | 14:33 |
ikhudoshyn | dukhlov: -1 for the same app | 14:33 |
nunosantos | maybe remove the “tables” part, just tadd the table name adter tenant_id | 14:33 |
nunosantos | * add | 14:33 |
achudnovets | dukhlov: I think we can use single url for monitoring. | 14:33 |
charlesw | nunosantos, -1, not by openstack convention | 14:34 |
achudnovets | url like /v1/monitoring/ or /v1/monitoring/tables | 14:34 |
*** chao_li has joined #magnetodb | 14:35 | |
charlesw | why not /v1/monitoring/tenants? | 14:35 |
miqui_ | what about keeping url simple and passing additional params in the http headers? | 14:35 |
achudnovets | because it's not info about tenants | 14:35 |
isviridov | dukhlov 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 |
achudnovets | miqui_: it will be GET request with params | 14:36 |
miqui_ | k.. | 14:36 |
achudnovets | if 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 auth | 14:38 |
ikhudoshyn | achudnovets: +1 | 14: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 | |
ominakov | achudnovets, what do you mean in "monitoring with data API" ? | 14:40 |
achudnovets | ominakov: just like current implementation | 14:41 |
ajaya | isviridov, 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 |
charlesw | achudnovets, 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 |
isviridov | ajaya yes we are planning to do it, I really hoped to do it last cycle, so the plan is this cycle. | 14:44 |
achudnovets | charlesw: yes. I think ikhudoshyn and isviridov means that we can use non-keystone auth for monitoring. Is it right? | 14:45 |
ikhudoshyn | achudnovets: possibly | 14:45 |
isviridov | ajaya the main benefit is some king of endorsement of project | 14:46 |
ajaya | isviridov, so if all goes well then mdb would be an incubated project by end of kilo? | 14:46 |
*** achuprin_ has quit IRC | 14:48 | |
isviridov | ajaya we will see, the incubation process and status is changing now, but teh goal is to reach this status whatever it is. | 14:48 |
isviridov | ajaya more details http://lists.openstack.org/pipermail/openstack-tc/2014-November/000887.html | 14:48 |
*** achuprin_ has joined #magnetodb | 14:48 | |
charlesw | isviridov, let us know what we all can do to get there | 14:48 |
isviridov | charlesw sure | 14:49 |
isviridov | Where are we with monitoring? | 14:49 |
isviridov | achudnovets could you summarize? | 14:50 |
achudnovets | ok | 14:50 |
miqui_ | +1 on incubation, am late in the game..but i'll do what i can... | 14:50 |
isviridov | miqui_ great to see you with us. What company are you working on? | 14:52 |
miqui_ | i work for Hewlett-Packard | 14:52 |
isviridov | Cool, it helps with diversity of team, what is one of requerements. Waiting for your patches :) | 14:53 |
achudnovets | so 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 gerrit | 14:54 |
charlesw | miqui, what location? I'm with Symantec, Boston | 14:55 |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 14:55 |
isviridov | #action achudnovets create a spec for integration with external monitoring systems | 14:55 |
miqui_ | charlesw: Atlanta | 14:55 |
* isviridov charlesw and miqui_ are going to have some beer | 14:55 | |
* isviridov seems not | 14:55 | |
*** jeromatron has quit IRC | 14:55 | |
* isviridov 4 mins left | 14:56 | |
isviridov | Countdown | 14:58 |
isviridov | 3 | 14:58 |
isviridov | 2 | 14:58 |
isviridov | 1 | 14:58 |
isviridov | Thank you fro comming, see you in IRC and ML | 14:58 |
isviridov | #endmeeting | 14:59 |
openstack | Meeting ended Thu Dec 11 14:59:10 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-11-14.00.html | 14:59 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-11-14.00.txt | 14:59 |
openstack | Log: http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-12-11-14.00.log.html | 14:59 |
charlesw | bye guys | 14:59 |
miqui_ | buy... | 14:59 |
ajaya | bye | 14:59 |
nunosantos | bye | 14:59 |
dukhlov | bye | 14:59 |
achuprin_ | bye | 14:59 |
miqui_ | *bye | 14:59 |
*** nunosantos has quit IRC | 15:00 | |
*** chao_li has quit IRC | 15:03 | |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 15:04 |
*** rushiagr is now known as rushiagr_away | 15:16 | |
openstackgerrit | Charles Wang proposed stackforge/magnetodb-specs: Add request metrics speccification https://review.openstack.org/138950 | 15:20 |
*** ajaya has quit IRC | 15:20 | |
openstackgerrit | Charles Wang proposed stackforge/magnetodb-specs: Add request metrics speccification https://review.openstack.org/138950 | 15:34 |
openstackgerrit | Illia Khudoshyn proposed stackforge/magnetodb: (WIP) Add backup manager https://review.openstack.org/141026 | 15:36 |
*** jeromatron has joined #magnetodb | 15:52 | |
*** jeromatron has quit IRC | 16:02 | |
*** jeromatron has joined #magnetodb | 16:07 | |
*** jeromatron has quit IRC | 16:10 | |
*** jeromatron has joined #magnetodb | 16:11 | |
*** jeromatron has quit IRC | 16:13 | |
*** isviridov is now known as isviridov_away | 16:16 | |
*** jeromatron has joined #magnetodb | 16:19 | |
*** jeromatron has quit IRC | 16:24 | |
openstackgerrit | Andrei V. Ostapenko proposed stackforge/magnetodb: Adds table_id field to table description https://review.openstack.org/140740 | 16:25 |
*** jeromatron has joined #magnetodb | 16:27 | |
*** jeromatron has quit IRC | 16:29 | |
*** rushiagr_away is now known as rushiagr | 16:29 | |
*** jeromatron has joined #magnetodb | 16:34 | |
*** jeromatron has quit IRC | 16:36 | |
*** romainh has left #magnetodb | 16:39 | |
*** jeromatron has joined #magnetodb | 16:49 | |
*** jeromatron has quit IRC | 17:02 | |
*** jeromatron has joined #magnetodb | 17:04 | |
*** jeromatron has quit IRC | 17:26 | |
*** jeromatron has joined #magnetodb | 17:27 | |
*** ygbo has quit IRC | 17:28 | |
*** jeromatron has quit IRC | 17:34 | |
*** jeromatron has joined #magnetodb | 17:35 | |
*** jeromatron has quit IRC | 17:57 | |
*** jeromatron has joined #magnetodb | 17:59 | |
*** jeromatron has quit IRC | 18:22 | |
*** rushiagr is now known as rushiagr_away | 18:40 | |
*** jeromatron has joined #magnetodb | 19:16 | |
*** jeromatron has quit IRC | 19:34 | |
*** jeromatron has joined #magnetodb | 19:35 | |
*** jeromatron has quit IRC | 20:22 | |
*** jeromatron has joined #magnetodb | 20:24 | |
*** vnaboychenko has joined #magnetodb | 21:02 | |
*** keith_newstadt has joined #magnetodb | 21:13 | |
*** keith_newstadt has quit IRC | 21:13 | |
*** keith_newstadt has joined #magnetodb | 21:14 | |
*** jeromatron has quit IRC | 21:47 | |
*** jeromatron has joined #magnetodb | 21:49 | |
*** jeromatron has quit IRC | 22:24 | |
*** keith_newstadt has quit IRC | 22:34 | |
*** jeromatron has joined #magnetodb | 22:49 | |
*** keith_newstadt has joined #magnetodb | 23:03 | |
*** jeromatron has quit IRC | 23:12 | |
*** jeromatron has joined #magnetodb | 23:16 | |
*** charlesw has quit IRC | 23:25 | |
*** keith_newstadt has quit IRC | 23:53 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!