| *** vnaboychenko has quit IRC | 00:22 | |
| *** openstackstatus has quit IRC | 00:23 | |
| *** openstackstatus has joined #magnetodb | 00:23 | |
| *** ChanServ sets mode: +v openstackstatus | 00:23 | |
| *** vnaboychenko has joined #magnetodb | 01:05 | |
| *** charlesw has joined #magnetodb | 02:40 | |
| *** openstackgerrit has quit IRC | 02:45 | |
| *** vnaboychenko has quit IRC | 02:54 | |
| *** rushiagr_away is now known as rushiagr | 03:12 | |
| *** jeromatron has joined #magnetodb | 03:29 | |
| *** vivekd has joined #magnetodb | 03:33 | |
| *** jeromatron has quit IRC | 03:33 | |
| *** charlesw has quit IRC | 03:35 | |
| *** rushiagr is now known as rushiagr_away | 04:08 | |
| *** rushiagr_away is now known as rushiagr | 04:37 | |
| *** jeromatron has joined #magnetodb | 04:41 | |
| *** jeromatron has quit IRC | 04:44 | |
| *** jeromatron has joined #magnetodb | 04:48 | |
| *** jeromatron has quit IRC | 04:54 | |
| *** jeromatron has joined #magnetodb | 04:54 | |
| *** jeromatron has quit IRC | 05:08 | |
| *** jeromatron has joined #magnetodb | 05:08 | |
| *** jeromatron has quit IRC | 05:11 | |
| *** jeromatron has joined #magnetodb | 05:14 | |
| *** ajayaa has joined #magnetodb | 05:17 | |
| *** jeromatron has quit IRC | 05:17 | |
| *** jeromatron has joined #magnetodb | 05:23 | |
| *** jeromatron has quit IRC | 05:31 | |
| *** jeromatron has joined #magnetodb | 05:54 | |
| *** jeromatron has quit IRC | 05:59 | |
| *** jeromatron has joined #magnetodb | 06:00 | |
| *** jeromatron has quit IRC | 06:05 | |
| *** jeromatron has joined #magnetodb | 06:14 | |
| *** k4n0 has joined #magnetodb | 06:56 | |
| *** romainh has joined #magnetodb | 07:02 | |
| *** k4n0 has quit IRC | 07:02 | |
| *** k4n0 has joined #magnetodb | 07:14 | |
| *** k4n0 has quit IRC | 07:42 | |
| *** k4n0 has joined #magnetodb | 07:54 | |
| *** jeromatron has quit IRC | 10:05 | |
| *** tnurlygayanov has joined #magnetodb | 10:14 | |
| ikhudoshyn | o/ | 10:23 |
|---|---|---|
| *** ajayaa has quit IRC | 11:38 | |
| *** ajayaa has joined #magnetodb | 11:52 | |
| *** ajayaa has quit IRC | 12:08 | |
| *** rushiagr is now known as rushiagr_away | 12:20 | |
| *** openstackgerrit has joined #magnetodb | 12:24 | |
| isviridov | 0/ | 12:25 |
| openstackgerrit | Illia Khudoshyn proposed a change to stackforge/magnetodb: Use oslo.notify for notifications https://review.openstack.org/126489 | 12:46 |
| isviridov | Hello everybody | 12:47 |
| isviridov | Anything to add to meeting agenda #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Oct_9.2C_2014.2C_13:00_UTC | 12:48 |
| *** rushiagr_away is now known as rushiagr | 12:49 | |
| ikhudoshyn | isviridov, hi there | 12:57 |
| ikhudoshyn | isviridov, could u pls share that fancy link with AIs from the last meeting? | 12:57 |
| ikhudoshyn | oops | 12:58 |
| ikhudoshyn | u've just done it | 12:58 |
| *** achuprin_ has joined #magnetodb | 12:58 | |
| isviridov | ikhudoshyn, hi. Yep it is in agenda | 12:59 |
| achuprin_ | Hi team! | 12:59 |
| dukhlov | hello | 12:59 |
| isviridov | Hello dukhlov | 13:00 |
| isviridov | #startmeeting magnetodb | 13:00 |
| openstack | Meeting started Thu Oct 9 13:00: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:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| openstack | The meeting name has been set to 'magnetodb' | 13:00 |
| isviridov | Who is here? | 13:00 |
| isviridov | o/ | 13:00 |
| achudnovets | hello everybody | 13:00 |
| isviridov | achudnovets, hello alex | 13:00 |
| *** SpyRay has joined #magnetodb | 13:00 | |
| rushiagr | hello! | 13:00 |
| rushiagr | ajaya should be around too. Wait, I'll poke him | 13:01 |
| isviridov | SpyRay, hello | 13:01 |
| SpyRay | Hi All! | 13:01 |
| isviridov | rushiagr, great. He has several items in agenda | 13:01 |
| *** ajayaa has joined #magnetodb | 13:01 | |
| isviridov | Hello ajayaa | 13:02 |
| ajayaa | Hi isviridov. | 13:02 |
| isviridov | Ok, I think we can start | 13:02 |
| isviridov | Here is today agenda #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Agenda | 13:03 |
| isviridov | The AIs from last meeting #link http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-10-02-13.00.html | 13:03 |
| isviridov | #topic Go through action items | 13:03 |
| *** SpyRay has left #magnetodb | 13:03 | |
| *** SpyRay has joined #magnetodb | 13:03 | |
| isviridov | dukhlov ikhudoshyn review spec for https://blueprints.launchpad.net/magnetodb/+spec/monitoring-health-check | 13:04 |
| isviridov | dukhlov, ikhudoshyn any success with it? | 13:04 |
| ikhudoshyn | yup | 13:04 |
| *** keith_newstadt has joined #magnetodb | 13:04 | |
| ikhudoshyn | in fact there was only one open question for me | 13:04 |
| ikhudoshyn | response in case of unhealthy state | 13:05 |
| dukhlov | yes | 13:05 |
| dukhlov | now it is returned 503 | 13:05 |
| ikhudoshyn | i would really like errcode other than 200 in the case | 13:05 |
| aostapenko | ikhudoshyn 503 | 13:05 |
| dukhlov | and json response | 13:05 |
| ikhudoshyn | aostapenko, is it official? | 13:05 |
| dukhlov | with detailes | 13:05 |
| aostapenko | ikhudoshyn, yes. and text/plain body | 13:06 |
| ikhudoshyn | aostapenko, great if so | 13:06 |
| ikhudoshyn | no objections from my side than | 13:06 |
| dukhlov | but if we decided that it is "simple" healthcheck | 13:06 |
| isviridov | ikhudoshyn, dukhlov please add your 'approved' to spec, just to keep it consistent | 13:07 |
| dukhlov | and we have no plans to parse json to get detailes | 13:07 |
| aostapenko | there is simple healthcheck, and healthcheck that checks subsystems. see specs please | 13:07 |
| ikhudoshyn | isviridov, where to? | 13:07 |
| aostapenko | https://wiki.openstack.org/wiki/MagnetoDB/specs/monitoring-health-check | 13:07 |
| ikhudoshyn | isviridov, i mean approve? | 13:07 |
| dukhlov | maybe it is reasonable to return more detailed status via status code? | 13:07 |
| isviridov | ikhudoshyn, https://wiki.openstack.org/wiki/MagnetoDB/specs/monitoring-health-check#Specification_status | 13:08 |
| dukhlov | I mean define a few codes for different cases | 13:08 |
| ikhudoshyn | isviridov, tnx | 13:08 |
| isviridov | dukhlov, for example? | 13:09 |
| ikhudoshyn | dukhlov, are we to provide automatic recovery? if no then I don't see a usecase for that | 13:09 |
| aostapenko | I think 200 and 503 are enough | 13:10 |
| dukhlov | that is ok, but In this case It is not clear for me why are we sending json with detailes? | 13:10 |
| ikhudoshyn | aostapenko, +1 | 13:11 |
| aostapenko | dukhlov, plain/text. Just to provide additional info for administrator | 13:12 |
| dukhlov | aostapenko: ah, ok, I fogot that it is not REST call now | 13:12 |
| isviridov | Ok, let us move on | 13:13 |
| isviridov | dukhlov, ok? | 13:13 |
| ikhudoshyn | isviridov, +1 | 13:13 |
| dukhlov | ok | 13:13 |
| isviridov | ikhudoshyn dukhlov review https://wiki.openstack.org/wiki/MagnetoDB/specs/rbac | 13:13 |
| isviridov | Let me share my feedback also | 13:14 |
| ikhudoshyn | as for that, I'd love to see full list of permissions | 13:14 |
| * isviridov ikhudoshyn is faster | 13:14 | |
| isviridov | yeap | 13:14 |
| ajayaa | Apart from permission based on roles and projects(tenants) do we need anythin else? | 13:14 |
| ikhudoshyn | ajayaa, I dont see any | 13:15 |
| ikhudoshyn | * anything | 13:15 |
| isviridov | ajayaa, could you enumerate the list of actions we are going to restrict | 13:15 |
| ajayaa | Then the permission listed in the spec are enough. | 13:15 |
| ajayaa | Okay. | 13:15 |
| dukhlov | LGTM in general, but i have seen there some kind of definition of simple language for rights | 13:16 |
| ajayaa | We can restrict all actions. | 13:16 |
| ajayaa | If you want to make an api public then just don't put any rule for it policy.json file. | 13:16 |
| *** charlesw has joined #magnetodb | 13:16 | |
| ajayaa | I will provide an example of that in the commit log. | 13:16 |
| dukhlov | role:admin and project_id:(project_id)s | 13:16 |
| dukhlov | now we have "AND" | 13:17 |
| *** SpyRay has quit IRC | 13:17 | |
| dukhlov | Do we plan to have "OR" | 13:17 |
| ajayaa | dukhlov, yes. | 13:17 |
| ajayaa | It is already there in policy. | 13:17 |
| ajayaa | The openstack common code provided already does this. | 13:17 |
| *** avinogradov has joined #magnetodb | 13:18 | |
| isviridov | ajayaa, yes. But the actions will be coded, so having a list will help to document exact maning | 13:18 |
| isviridov | *naming | 13:18 |
| ajayaa | Okay. I will modify the spec to reflect the same. | 13:18 |
| isviridov | Thank you | 13:18 |
| dukhlov | ajayaa: openstack common code? which library? where can I find it? | 13:19 |
| ajayaa | If you see my patch there itself, magnetodb/openstack/common/policy.py | 13:20 |
| ajayaa | That is the common code shared by every project which does role based policy checking. | 13:21 |
| isviridov | ajayaa, another think could you please keep the template structure. I mean https://wiki.openstack.org/wiki/MagnetoDB/specs/template | 13:21 |
| ajayaa | isviridov, I have missed some points in the template, I think. | 13:22 |
| ajayaa | I will update the spec. :) | 13:22 |
| ikhudoshyn | ajayaa, we're trying to get rid of *.openstack.common when possible | 13:22 |
| dukhlov | ajayaa: cool, thank you | 13:23 |
| ikhudoshyn | if u know a library where this stuff resides could u pls use it? | 13:23 |
| ajayaa | ikhudoshyn, There is no library for it as of now. | 13:23 |
| ikhudoshyn | ajayaa, ok ic | 13:23 |
| ajayaa | In future oslo people could include it, but I am sure. | 13:23 |
| achudnovets | ikhudoshyn: https://github.com/openstack/oslo-incubator/blob/master/openstack/common/policy.py | 13:23 |
| * isviridov came back | 13:24 | |
| isviridov | dukhlov, ikhudoshyn next point? | 13:24 |
| dukhlov | +1 | 13:24 |
| ikhudoshyn | achudnovets, are we to see oslo.incubator on pypi? | 13:24 |
| ikhudoshyn | achudnovets, in some future? | 13:24 |
| achudnovets | It may become a library some day :) | 13:25 |
| ikhudoshyn | :) tnx | 13:25 |
| ikhudoshyn | ikhudoshyn, lets move on | 13:25 |
| isviridov | isviridov start create spec repo like https://github.com/openstack/nova-specs | 13:25 |
| ajayaa | ikhudoshyn, Before becoming library common code go thorough oslo.incubator. | 13:25 |
| ikhudoshyn | s/ikhudoshyn/isviridov | 13:25 |
| isviridov | It is for me. So no progress here yet | 13:26 |
| ikhudoshyn | ajayaa, that makes sense, i just dont really like copypased code | 13:26 |
| isviridov | But we will have it for kilo | 13:26 |
| ikhudoshyn | isviridov, we're ;looking forward )) | 13:27 |
| isviridov | ikhudoshyn, :) | 13:27 |
| isviridov | ominakov describe security impact here https://wiki.openstack.org/wiki/MagnetoDB/specs/monitoring-api | 13:27 |
| isviridov | ominakov, around? | 13:27 |
| isviridov | Ok.We have other point to discuss | 13:28 |
| ajayaa | ikhudoshyn, If everybody feels like we should wait for policies to become a library, then I am fine with it. :) | 13:28 |
| ikhudoshyn | ajayaa, no way) | 13:28 |
| achudnovets | isviridov: +1 :) | 13:28 |
| isviridov | ajayaa, how long it can take? | 13:29 |
| ajayaa | isviridov, I have no idea. | 13:29 |
| isviridov | We had the same with notifications, I don't think that it should stop us. | 13:30 |
| isviridov | Or even more, it is a greate chance to contribute to oslo | 13:30 |
| ajayaa | Yes. besides every other project is reusing that piece of code. | 13:31 |
| isviridov | ajayaa, yeap | 13:31 |
| isviridov | Ok next big topic looks like from you | 13:31 |
| isviridov | #topic Decide how to do metering. Define a clear boundary between monitoring api and Ceilometer metering through Magnetodb notifications. | 13:31 |
| isviridov | #topic Decide how to do metering | 13:32 |
| ajayaa | Do we have a basic idea of what to meter? | 13:32 |
| ajayaa | besides byte usage and #rows in a table | 13:32 |
| keith_newstadt | we have docs describing key metrics | 13:33 |
| keith_newstadt | have that info been shared with the community? | 13:33 |
| ajayaa | I don't see it. | 13:33 |
| keith_newstadt | we should put it in the blueprint | 13:34 |
| isviridov | keith_newstadt, 1 sec | 13:34 |
| isviridov | Here it is #link https://docs.google.com/a/mirantis.com/spreadsheets/d/1tYvgCSvkcOVED46MX8qSlUyrhNhHlyTrVkX7AXP-XR4/edit#gid=0 | 13:34 |
| isviridov | Here is the list | 13:35 |
| isviridov | ajayaa, does it work for you? | 13:35 |
| ajayaa | yep. I can see it. | 13:35 |
| isviridov | So the data with Source API==KVaaS API is expected to be collected with monitoring API | 13:37 |
| ikhudoshyn | isviridov, and everything other is left for ceilometer? | 13:38 |
| ajayaa | Ceilometer would only consume notifications as of now. | 13:38 |
| isviridov | ajayaa, what about pooling data? | 13:39 |
| ajayaa | If we are going to do metering through ceilometer then we should emit notifications containing these information. | 13:39 |
| ajayaa | I talked with ceilometer devs and they are okay with notifications but not polling. | 13:39 |
| isviridov | ajayaa, I mean pollster http://docs.openstack.org/developer/ceilometer/contributing/plugins.html#pollster | 13:39 |
| isviridov | What the reasoning to work only with notifications? | 13:40 |
| isviridov | ikhudoshyn, actually all can be sent to celiometer, the question is how and if it is needed there at all | 13:41 |
| ajayaa | isviridov, no dependency on code of other modules. | 13:42 |
| ajayaa | services* | 13:42 |
| isviridov | ajayaa, got you | 13:42 |
| isviridov | ajayaa, yeap it is a big question for us as non integrated project. We have to figure out how we can go here | 13:43 |
| isviridov | Ok, let us summarize | 13:43 |
| ajayaa | We could have some code running periodically which would send notifications. | 13:43 |
| isviridov | #info celiometer team prefers notifications | 13:44 |
| isviridov | ajayaa, are you ok with a list of metrics or have ideas what we can add? | 13:45 |
| ajayaa | isviridov, I will go through the list in detail and let you know. | 13:45 |
| isviridov | #action ajayaa review current list of metrics | 13:46 |
| isviridov | Anything else> | 13:46 |
| isviridov | ? | 13:46 |
| ikhudoshyn | isviridov, move on? | 13:46 |
| isviridov | ajayaa, keith_newstadt move on? | 13:46 |
| ajayaa | okay. | 13:46 |
| isviridov | #topic UUID for a table | 13:47 |
| ajayaa | The need for this right now is in ceilometer which needs a field resource_id. | 13:47 |
| isviridov | ajayaa, I believe celiometer is a big topic, let us continue offline. But very appreciate your work! | 13:47 |
| ajayaa | which should be unique per resouce which is being measured. | 13:48 |
| ajayaa | okay. | 13:48 |
| ajayaa | Also UUID would help in making our apis more openstack way. | 13:49 |
| isviridov | I personally would like to see UUID for table | 13:49 |
| isviridov | dukhlov, ikhudoshyn, charlesw any thoughts? | 13:49 |
| ajayaa | isviridov, yes. | 13:49 |
| ajayaa | +1 | 13:49 |
| ikhudoshyn | isviridov, where exactly u want to see them? | 13:49 |
| isviridov | As table attribute | 13:50 |
| ikhudoshyn | is it only about haivng them in table_info or u expect to expose it? | 13:50 |
| ikhudoshyn | like in resource url? | 13:50 |
| ajayaa | ikhudoshyn, unless exposed what value would it add? | 13:50 |
| ikhudoshyn | ajayaa, that's what I tey to figure out) | 13:51 |
| charlesw | table name + project id is already unique. What's the purpose for uuid for table? | 13:51 |
| ikhudoshyn | charlesw, +1 | 13:52 |
| keith_newstadt | charlesw +1 | 13:52 |
| aostapenko | charlesw, table can be recreated | 13:52 |
| ajayaa | aostapenko +1 | 13:52 |
| aostapenko | and it will be another resource | 13:52 |
| ajayaa | I was waiting for you to tell this. :) | 13:52 |
| keith_newstadt | how would the user use the uuid? | 13:53 |
| dukhlov | table name + project id is already unique in scope of magnetodb | 13:53 |
| keith_newstadt | i'm trying to understand the use case we'd be solving for | 13:53 |
| aostapenko | dukhlov, but not in scope of OpenStack. If we consider a table as a resource | 13:53 |
| dukhlov | sould this ID be unique resoure for monitoring in scope of all ceilometer resoures being monitored | 13:54 |
| dukhlov | ? | 13:54 |
| ajayaa | dukhlov, yes. At least for one service. | 13:54 |
| aostapenko | It's not a problem to add uuid just for ceilometer. but it will be openstack style if we expose it | 13:57 |
| isviridov | HEAT has similar story. Implementing AWS CloudFormation API they have as stack name as identifier, but added UUID as well | 13:58 |
| isviridov | http://developer.openstack.org/api-ref-orchestration-v1.html | 13:58 |
| isviridov | It looks like we don't have an agreement here. Let us return back to it offline or in ML | 13:59 |
| ikhudoshyn | so for ceilometer we could have table name + uuid as a resource id | 13:59 |
| charlesw | Then we need to change MDB resource url to use uuid instead of table name. Different than Dynamo | 13:59 |
| ikhudoshyn | charlesw, OS REST API already differs from Dynamo one | 13:59 |
| ikhudoshyn | but this is a topic to discuss anyway | 14:00 |
| isviridov | We are run out of time | 14:00 |
| isviridov | #topic Juno delivery status overview | 14:00 |
| isviridov | The current rc1 is the last version before juno release | 14:01 |
| isviridov | I've created kilo and we can start with suggesting BPs there https://launchpad.net/magnetodb/kilo | 14:01 |
| isviridov | Thank you for attending the meeting. | 14:02 |
| isviridov | #stopmeeting | 14:02 |
| rushiagr | thanks all | 14:02 |
| rushiagr | isviridov: endmeeting :) | 14:02 |
| isviridov | #endmeeting | 14:02 |
| openstack | Meeting ended Thu Oct 9 14:02:41 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-10-09-13.00.html | 14:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-10-09-13.00.txt | 14:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-10-09-13.00.log.html | 14:02 |
| isviridov | rushiagr, thanks | 14:02 |
| isviridov | :)) | 14:02 |
| rushiagr | :) | 14:02 |
| *** ajayaa has quit IRC | 14:24 | |
| *** ajayaa has joined #magnetodb | 14:27 | |
| *** avinogradov has quit IRC | 14:32 | |
| *** vivekd has quit IRC | 14:35 | |
| openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: Changes logic of table cleanup in tempest https://review.openstack.org/127216 | 14:39 |
| *** k4n0 has quit IRC | 14:42 | |
| *** isviridov is now known as isviridov_meet | 14:43 | |
| *** jeromatron has joined #magnetodb | 14:53 | |
| *** romainh has left #magnetodb | 14:59 | |
| openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: Changes logic of table cleanup in tempest https://review.openstack.org/127216 | 15:08 |
| *** jeromatron has quit IRC | 15:12 | |
| *** jeromatron has joined #magnetodb | 15:15 | |
| *** keith_newstadt has quit IRC | 15:33 | |
| *** isviridov_meet is now known as isviridov_away | 15:34 | |
| openstackgerrit | Andrei V. Ostapenko proposed a change to stackforge/magnetodb: Changes logic of table cleanup in tempest https://review.openstack.org/127216 | 15:44 |
| *** jeromatron has quit IRC | 16:38 | |
| *** jeromatron has joined #magnetodb | 16:42 | |
| *** jeromatron has quit IRC | 17:08 | |
| *** jeromatron has joined #magnetodb | 17:09 | |
| *** jeromatron has quit IRC | 17:52 | |
| *** jeromatron has joined #magnetodb | 18:22 | |
| *** jeromatron has quit IRC | 18:57 | |
| *** rushiagr is now known as rushiagr_away | 19:00 | |
| *** jeromatron has joined #magnetodb | 19:01 | |
| *** jeromatron has quit IRC | 19:06 | |
| *** jeromatron has joined #magnetodb | 19:09 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Use oslo.notify for notifications https://review.openstack.org/126489 | 19:12 |
| *** jeromatron has quit IRC | 19:33 | |
| *** jeromatron has joined #magnetodb | 19:41 | |
| *** ajayaa has quit IRC | 19:45 | |
| openstackgerrit | Nuno Santos proposed a change to stackforge/magnetodb: Additional validation on keyspace, index, table, and attribute names https://review.openstack.org/125445 | 21:35 |
| openstackgerrit | Nuno Santos proposed a change to stackforge/magnetodb: Additional validation on keyspace, index, table, and attribute names https://review.openstack.org/125445 | 21:43 |
| *** charlesw has quit IRC | 22:36 | |
| *** jeromatron has quit IRC | 23:17 | |
| *** jeromatron has joined #magnetodb | 23:49 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!