| *** openstackgerrit has quit IRC | 00:16 | |
| *** openstackgerrit has joined #magnetodb | 00:18 | |
| *** vnaboychenko has quit IRC | 01:35 | |
| *** vnaboychenko has joined #magnetodb | 01:36 | |
| *** vnaboychenko has quit IRC | 01:40 | |
| *** vnaboychenko has joined #magnetodb | 02:25 | |
| *** jeromatron has quit IRC | 02:30 | |
| *** vivekd has joined #magnetodb | 03:23 | |
| openstackgerrit | Charles Wang proposed a change to stackforge/magnetodb: Closes-Bug: #1373627 https://review.openstack.org/123927 | 03:54 |
|---|---|---|
| *** vivekd has quit IRC | 03:54 | |
| *** vivekd has joined #magnetodb | 04:04 | |
| *** vnaboychenko has quit IRC | 05:13 | |
| *** vnaboychenko has joined #magnetodb | 05:13 | |
| *** vnaboychenko has quit IRC | 05:18 | |
| *** jeromatron has joined #magnetodb | 05:51 | |
| *** ajayaa has joined #magnetodb | 05:57 | |
| *** jeromatron has quit IRC | 06:01 | |
| *** jeromatron has joined #magnetodb | 06:06 | |
| *** jeromatron has quit IRC | 06:14 | |
| *** ajayaa has quit IRC | 06:14 | |
| *** jeromatron has joined #magnetodb | 06:19 | |
| *** ajayaa has joined #magnetodb | 06:34 | |
| *** k4n0 has joined #magnetodb | 06:37 | |
| *** vnaboychenko has joined #magnetodb | 06:37 | |
| *** ajayaa has quit IRC | 07:12 | |
| *** jeromatron has quit IRC | 07:16 | |
| *** romainh has joined #magnetodb | 07:18 | |
| *** ajayaa has joined #magnetodb | 07:20 | |
| *** ajayaa has quit IRC | 07:32 | |
| *** ajayaa has joined #magnetodb | 07:34 | |
| *** vnaboychenko has quit IRC | 07:57 | |
| *** vnaboychenko has joined #magnetodb | 07:58 | |
| openstackgerrit | Christian Berendt proposed a change to stackforge/magnetodb: Stop using intersphinx https://review.openstack.org/123962 | 08:00 |
| *** rushiagr_away is now known as rushiagr | 08:00 | |
| *** vnaboychenko has quit IRC | 08:02 | |
| *** openstackgerrit has quit IRC | 08:48 | |
| *** rushiagr is now known as rushiagr_away | 08:52 | |
| *** rushiagr_away is now known as rushiagr | 09:56 | |
| *** vnaboychenko has joined #magnetodb | 10:58 | |
| *** vnaboychenko has quit IRC | 11:02 | |
| *** rushiagr is now known as rushiagr_away | 12:26 | |
| *** vivekd_ has joined #magnetodb | 12:26 | |
| *** rushiagr_away is now known as rushiagr | 12:28 | |
| *** isviridov_meetin is now known as isviridov | 12:29 | |
| *** vivekd has quit IRC | 12:29 | |
| *** vivekd_ is now known as vivekd | 12:29 | |
| isviridov | Hello everybody | 12:29 |
| isviridov | #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda today meeting agenda | 12:29 |
| isviridov | Feel free to add items | 12:29 |
| isviridov | Please pay attention that we have meeting here, but not in #openstack-meeting | 12:30 |
| isviridov | achudnovets, ikhudoshyn ominakov aostapenko achuprin the meeting time | 12:59 |
| aostapenko | Hello, everybody | 12:59 |
| isviridov | Let us start | 13:00 |
| ominakov | Hello, guys | 13:00 |
| isviridov | #startmeeting magnetodb | 13:00 |
| openstack | Meeting started Thu Sep 25 13:00:24 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 | o/ | 13:00 |
| isviridov | Anybody here? | 13:00 |
| ajayaa | o/ | 13:01 |
| ajayaa | Hi isviridov. | 13:01 |
| isviridov | Hello ajayaa | 13:01 |
| aostapenko | Hi, guys | 13:01 |
| ikhudoshyn | o/ | 13:01 |
| isviridov | #link from last meeting http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-09-18-13.01.html | 13:02 |
| isviridov | Today agenda #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#Sep25.2C_2014.2C_13:00_UTC | 13:02 |
| isviridov | #topic Go through action items | 13:02 |
| isviridov | ikhudoshyn write spec | 13:02 |
| ikhudoshyn | done | 13:03 |
| isviridov | I've seen that it exists :) | 13:03 |
| ikhudoshyn | just a sec, i'll find the link | 13:03 |
| ikhudoshyn | https://wiki.openstack.org/wiki/MagnetoDB/specs/async-schema-operations | 13:03 |
| *** vivekd has quit IRC | 13:03 | |
| *** charlesw has joined #magnetodb | 13:03 | |
| ajayaa | Please link it to the blueprint. | 13:04 |
| * isviridov going through spec quickly | 13:04 | |
| *** SpyRay has joined #magnetodb | 13:04 | |
| ikhudoshyn | ajayaa, it is already linked | 13:04 |
| isviridov | ikhudoshyn, looks serios | 13:05 |
| isviridov | I like it. Any questions? | 13:05 |
| ikhudoshyn | did my best | 13:05 |
| isviridov | Ok, looking forward for your patch | 13:06 |
| isviridov | Another AI is: | 13:06 |
| ikhudoshyn | it's green in gerrit | 13:06 |
| ajayaa | Looks nice. I will have some questions after reading through it. | 13:07 |
| ikhudoshyn | everybody are welcome to review | 13:07 |
| ikhudoshyn | https://review.openstack.org/#/c/122404/ | 13:07 |
| isviridov | Great! | 13:07 |
| isviridov | achudnovets provide numbers about performance impact from big PKI token in ML | 13:07 |
| isviridov | achudnovets, around? | 13:07 |
| achudnovets | yes | 13:07 |
| achudnovets | Hmm, I'll send an email today. With numbers. | 13:08 |
| isviridov | achudnovets, cool! | 13:08 |
| isviridov | #action provide numbers about performance impact from big PKI token in ML | 13:09 |
| isviridov | #topic Asynchronous table creation and removal | 13:09 |
| isviridov | Seems we have spec and patch to review. | 13:09 |
| isviridov | ikhudoshyn, anything else to add? | 13:10 |
| achudnovets | for lightweight requests, like list_tables, we can get 5% - 8% performance boost using tokens without service catalog | 13:10 |
| *** achuprin_ has joined #magnetodb | 13:10 | |
| ikhudoshyn | isviridov, nothing from my side | 13:11 |
| charlesw | Hi ikhudoshyn, if you can add a section about the pros/cons of alternative approaches, it will be even better :) | 13:11 |
| isviridov | Welcome charlesw | 13:11 |
| ikhudoshyn | charlesw, sounds good. I'll do it.. eventually | 13:11 |
| ikhudoshyn | ,) | 13:12 |
| isviridov | achudnovets, I see, let us return back to it later or in ML | 13:12 |
| isviridov | charlesw, what alternatives do you mean? | 13:12 |
| * isviridov thinks that we have lost charlesw | 13:14 | |
| charlesw | I put some comments in the patch review. I think what we need there is a distributed lock. Some alternative approach can be, for example, using Cassandra itself as a global lock. | 13:14 |
| isviridov | Move on? | 13:14 |
| rushiagr | Hi all! Sorry, I am late.. | 13:14 |
| isviridov | rushiagr, welcome | 13:15 |
| rushiagr | isviridov: thanks | 13:15 |
| isviridov | charlesw, I see | 13:15 |
| isviridov | Next topic? | 13:15 |
| isviridov | #topic Monitoring API | 13:16 |
| isviridov | ominakov, will you update us with latest status? | 13:16 |
| ominakov | yes, sure | 13:17 |
| ominakov | i've pushed new patch set with implemented size of table in bytes and item counts | 13:18 |
| isviridov | #link https://blueprints.launchpad.net/magnetodb/+spec/monitoring-api | 13:18 |
| isviridov | ominakov, great! | 13:18 |
| ominakov | welcome to review #link https://review.openstack.org/#/c/122330/4 | 13:18 |
| isviridov | ominakov, I believe we have to update the deployment as well | 13:19 |
| ominakov | yep, we should add Jolokia to our C* deployment | 13:20 |
| ajayaa | A bit off-topic but we are starting ceiliometer integration work. So currently we have plans to catch notifications and process them in ceilometer. | 13:21 |
| ajayaa | Do we plan to consume monitoring-api from ceilometer? | 13:21 |
| isviridov | ajayaa, are you working on this part? | 13:22 |
| isviridov | ajayaa, yes, it can be done by celio. But it is not in prior for now. | 13:22 |
| ajayaa | isviridov, Yes. I have started working on ceilometer integration. | 13:23 |
| isviridov | ajayaa, great to know! Let us discuss it in details out of this topic. | 13:23 |
| isviridov | Moving on? | 13:23 |
| ikhudoshyn | isviridov, yep | 13:24 |
| ajayaa | isviridov, okay. | 13:24 |
| rushiagr | isviridov: ceilometer work is important to us :) | 13:24 |
| isviridov | rushiagr, I see :) | 13:24 |
| isviridov | #topic Light weight session for authorization | 13:24 |
| isviridov | achudnovets, do you have a conclusion about this BP? | 13:25 |
| achudnovets | I think we can just use PKI tokens without service catalog | 13:26 |
| isviridov | I like the approach 'to leave all as is' :) | 13:26 |
| achudnovets | I'm not sure we need to provide some custom mechanism right now | 13:26 |
| ikhudoshyn | achudnovets, did you do any measurements? | 13:26 |
| charlesw | where is the BP? | 13:27 |
| isviridov | charlesw, #link https://blueprints.launchpad.net/magnetodb/+spec/light-weight-session | 13:27 |
| romainh | hi guys, just a notice. Would it possible to have longer commit messages? It would allow easier understanding of code changes :) | 13:27 |
| * rushiagr looks around to see if any Symantec folks are present | 13:28 | |
| rushiagr | romainh: +1000 | 13:28 |
| achudnovets | ikhudoshyn: yep, and I'll send an email with some conlusions | 13:28 |
| isviridov | romainh, +2 | 13:28 |
| ikhudoshyn | achudnovets, yep, sry I missed yu answer before | 13:28 |
| rushiagr | romainh: completely agree with you. Also, I see some commits without any blueprints, or bugs included in them.. | 13:28 |
| ikhudoshyn | romainh, u r right, all of us should work on it)) | 13:28 |
| isviridov | romainh, rushiagr feel free to -1 | 13:28 |
| ajayaa | achudnovets, How did you measure performance hit with PKI tokens? | 13:29 |
| ajayaa | Did you use size of PKI token? | 13:29 |
| charlesw | Maybe we should say authN instead of authZ? | 13:30 |
| achudnovets | ajayaa: I sent a lot of requests with PIK token with enabled service catalog and without service catalog. And measure responce time and rps | 13:31 |
| isviridov | charlesw, not sure. authentication is done by keystone | 13:32 |
| ajayaa | achudnovets, We all agree that PKI tokens without service catalogs are nice and less in size. | 13:32 |
| ikhudoshyn | move on? | 13:33 |
| isviridov | achudnovets, ajayaa moving on? | 13:33 |
| achudnovets | +1 | 13:33 |
| ajayaa | But can't we use UUID token and subtract the keystone request time from it to measure real performance impact of PKI? | 13:33 |
| isviridov | #topic Review tempest tests and move to stable test dir | 13:33 |
| isviridov | achudnovets, will you answer or next topic? | 13:34 |
| ajayaa | we can take it offline. | 13:34 |
| isviridov | Ok | 13:35 |
| isviridov | #link https://blueprints.launchpad.net/magnetodb/+spec/review-tempest-tests | 13:35 |
| aostapenko | I've started to review in_progress tempest tests and move some of them to stable dir, so they will affect dvsm job results | 13:35 |
| isviridov | aostapenko, good job! QA is really important | 13:35 |
| aostapenko | isviridov: thanks | 13:36 |
| isviridov | The next one? | 13:36 |
| charlesw | I noticed updateItem is missing from tempest, any reason? | 13:36 |
| ikhudoshyn | charlesw, nothing but the lack of resources)) | 13:37 |
| ikhudoshyn | fell free to join | 13:37 |
| charlesw | sure | 13:37 |
| isviridov | charlesw, could you please track it as a bug? | 13:37 |
| aostapenko | charlesw, could you register a blueprint | 13:38 |
| ikhudoshyn | there are several areas that are not covered yet | 13:38 |
| charlesw | will do | 13:38 |
| rushiagr | charlesw: ikhudoshyn: I think it is high time we should start filing bugs , or writing blueprints for that matter, for such things | 13:38 |
| isviridov | aostapenko, not sure that BP is need for this. But we can add work item to current one. | 13:38 |
| ikhudoshyn | rushiagr, definitely. They are not bugs, I think. BPs are good for that | 13:38 |
| charlesw | rushiagr, good point | 13:39 |
| isviridov | charlesw, great! | 13:39 |
| ikhudoshyn | ikhudoshyn, do u want one huge pending BP? | 13:39 |
| rushiagr | ikhudoshyn: I'm fine with either way, but we should not let someone 'discover' these things out.. | 13:39 |
| ikhudoshyn | s/ikhudoshyn/isvyrydov/ | 13:39 |
| isviridov | rushiagr, ikhudoshyn can't say right now. Bug sounds easier to track. BP is more topic for discussion or long term effort. | 13:40 |
| ikhudoshyn | rushiagr, sry , I sort of missed ur point | 13:40 |
| isviridov | Let us file it as a bug and move on | 13:40 |
| isviridov | #topic Monitoring - healthcheck http request | 13:41 |
| rushiagr | if tempest test is missing, it should be given due importance IMO, whether bug or blueprint | 13:41 |
| ikhudoshyn | ok, let them be bugs | 13:41 |
| isviridov | aostapenko, it is you again | 13:41 |
| rushiagr | personally it is a bug, but blueprints will do too if somoene feels like it :) | 13:41 |
| isviridov | #agreed file missed tests as bugs | 13:42 |
| aostapenko | Now we are looking for lightweight tool to check magnetodb health | 13:42 |
| aostapenko | here is a bp https://blueprints.launchpad.net/magnetodb/+spec/monitoring-health-check | 13:42 |
| aostapenko | I suppose it should be http request to magnetodb that will initiate checking of keystone and cassandra availability | 13:44 |
| isviridov | aostapenko, i like it. Could you please write short spec with path, request, response | 13:44 |
| aostapenko | yes. sure | 13:44 |
| isviridov | dukhlov ikhudoshyn charlesw are you ok with idea? | 13:44 |
| ikhudoshyn | isviridov, LGTM | 13:45 |
| charlesw | sounds good | 13:45 |
| isviridov | aostapenko, please go ahead with it | 13:45 |
| isviridov | #action aostapenko write a spec about healthcheck | 13:46 |
| isviridov | #topic Log management | 13:46 |
| ajayaa | sounds good to me, but this should not be exposed to public. | 13:46 |
| isviridov | #link https://blueprints.launchpad.net/magnetodb/+spec/log-rotating | 13:46 |
| isviridov | I've heard about it from achuprin | 13:46 |
| ikhudoshyn | isviridov, ' move out whole logging configuration file' in the spec, do you mean 'to have a separate conf file for the logging subsystem'? | 13:47 |
| isviridov | Yeap, it is one of ideas. But let me first describe the problem | 13:48 |
| charlesw | ajayaa, I think a ping like service can be exposed, or make it optional at deployment | 13:48 |
| ikhudoshyn | isviridov, sure go ahead | 13:48 |
| isviridov | We have too much logs on disk and usage of standard log rotate is not always helpful | 13:48 |
| isviridov | I mean we can wrote several Gbs of logs before cron start and rotate the file | 13:49 |
| rushiagr | charlesw: can you expand on the idea? | 13:49 |
| aostapenko | Now we are looking for ability to use log rotating by python logging lib, or make proper config for logrotate tool | 13:50 |
| isviridov | So, suggested approach is have log rotation by size on application level | 13:50 |
| charlesw | let's follow meeting agenda and discuss a little later maybe. | 13:50 |
| ikhudoshyn | my 2cents, having just one conf for all mdb executables does not sound like a good idea for me | 13:51 |
| isviridov | charlesw, thx | 13:51 |
| ikhudoshyn | do we have any numbers on the topic? Could disabling 'debug' msgs help us in any way? | 13:52 |
| isviridov | ikhudoshyn, I thought about it, because rotating in standard functionality and probably it is not needed to duplicate the configuration in mdb config, but keep the standard format for logging framework | 13:52 |
| isviridov | ikhudoshyn, on big deployment doesn | 13:52 |
| isviridov | t help. The audit messages could fill all disk :) | 13:53 |
| ikhudoshyn | isviridov, in fact we have 3 (for now) possibly separate deployables, I'd really prefer them to have their own CONFs | 13:53 |
| isviridov | ikhudoshyn, agree | 13:53 |
| charlesw | I'm with ikhudoshyn | 13:53 |
| ikhudoshyn | so even if we gonna have a couple more conf params, lets just have them in service's personal CONFs | 13:54 |
| isviridov | #agreed put log rotation configs in mdb config. No separate logging config | 13:54 |
| isviridov | aostapenko, anything to add from your side? | 13:54 |
| aostapenko | isviridov no. i've done | 13:55 |
| isviridov | #topic Open discussion | 13:56 |
| ikhudoshyn | i'd like to announce one more thing I gonna do | 13:56 |
| isviridov | ikhudoshyn, please | 13:57 |
| ikhudoshyn | most of OS projects already moved to oslo.messaging.notify | 13:57 |
| ikhudoshyn | I plan to do the same for MDB once I finish with current activities | 13:57 |
| isviridov | ikhudoshyn, is it released already? | 13:58 |
| ikhudoshyn | yes, afaik | 13:59 |
| isviridov | ikhudoshyn, as far as I remember it was not, that is why we have just grabbed some code. | 13:59 |
| ikhudoshyn | anyway, nova, sfift, keystone ant lots more use it | 13:59 |
| ikhudoshyn | isviridov, that was at the time when we implemented it in MDB | 14:00 |
| isviridov | Nice to know, ikhudoshyn please file a bp for that forst | 14:00 |
| ikhudoshyn | https://blueprints.launchpad.net/magnetodb/+spec/oslo-notify | 14:00 |
| isviridov | WOW | 14:00 |
| isviridov | Ok, spec is needed | 14:00 |
| isviridov | #action ikhudoshyn write a spec for migration to oslo.messaging.notify | 14:01 |
| ajayaa | I have a working implementation of RBAC in magnetodb. I will push it once I am done with unit tests. | 14:01 |
| isviridov | ajayaa, WOW! | 14:01 |
| rushiagr | isviridov: do you think it is a good time to move to using magnetodb-specs as a place for tracking blueprints? | 14:01 |
| charlesw | yes we should move to oslo messaging. Hopefully MDb code will be minimally impacted if any | 14:01 |
| isviridov | rushiagr, yes. I agree | 14:01 |
| ikhudoshyn | ajayaa, is there any spec for that? | 14:01 |
| isviridov | #action isviridov look how to created magentodb-spec repo | 14:02 |
| rushiagr | isviridov: let's follow it starting from Kilo | 14:02 |
| isviridov | rushiagr, +1 | 14:02 |
| ajayaa | There is a blueprint. I am yet to write a spec. https://blueprints.launchpad.net/magnetodb/+spec/enforce-acls | 14:02 |
| ajayaa | ikhudoshyn ^^ | 14:03 |
| ikhudoshyn | ajayaa, cool | 14:03 |
| isviridov | ajayaa, cool! | 14:03 |
| rushiagr | isviridov: a spec repo will be very useful for asking questions on the spec, and also make sure that specs are written comprehensively before any spec is targetted | 14:03 |
| isviridov | #action ajayaa write spec for RBAC | 14:03 |
| rushiagr | another suggestion: we can discuss more about 'ideas' here in the meeting, rather than discuss about status updates of blueprints | 14:04 |
| isviridov | rushiagr, agree | 14:04 |
| rushiagr | I find that we are spending a lot of time tracking updates only, which leaves us with very less time to debate on important ideas/discussions | 14:05 |
| *** SpyRay has quit IRC | 14:05 | |
| isviridov | rushiagr, just add an items to meeting agenda and we will discuss it | 14:05 |
| rushiagr | it is partly my fault too. I should have added to agenda, the items I had to discuss :) | 14:05 |
| isviridov | Ok, guys we are out of time. | 14:06 |
| charlesw | also please announce meeting agenda some time before meeting so we can look into issues to be discussed | 14:06 |
| isviridov | charlesw, got you | 14:06 |
| rushiagr | is anyone from Symantec present here? | 14:06 |
| charlesw | me | 14:06 |
| rushiagr | charlesw: I wanted to discuss about cassandra provisioning | 14:06 |
| isviridov | The official part of meeting is finished | 14:06 |
| isviridov | #endmeeting | 14:07 |
| openstack | Meeting ended Thu Sep 25 14:07:00 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:07 |
| rushiagr | isviridov: thanks | 14:07 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-09-25-13.00.html | 14:07 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-09-25-13.00.txt | 14:07 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/magnetodb/2014/magnetodb.2014-09-25-13.00.log.html | 14:07 |
| charlesw | sure | 14:07 |
| rushiagr | charlesw: last meeting I heard you people are using heat for provisioning Cassandra nodes in cloud | 14:07 |
| rushiagr | charlesw: do you have any idea about that? | 14:07 |
| charlesw | I only heard using heat for API and leaving C* out, correct me if I heard it wrong | 14:08 |
| isviridov | rushiagr, we have a deployment of mdb together with C* by heat. As several clicks way. Let me found the link | 14:09 |
| isviridov | rushiagr, https://github.com/stackforge/magnetodb/tree/master/deployment/heat_templates | 14:10 |
| rushiagr | isviridov: oh cool! | 14:11 |
| rushiagr | isviridov: I completely missed that! | 14:11 |
| rushiagr | isviridov: I'll have a look, and comment | 14:11 |
| rushiagr | isviridov: also, probably, I'll also add documentation on how to use them (after I get to use them) :P | 14:11 |
| charlesw | even I missed that :) | 14:11 |
| rushiagr | charlesw: I wanted to know if what symantec is doing with heat is open sourced or not | 14:12 |
| charlesw | I'll check with Keith and get back to you. Keith is out today | 14:13 |
| rushiagr | isviridov: charlesw: very soon, we'll start to look into it too. So was curious that if many parties are interested in it, we can as well create a repository for it and work together :) | 14:13 |
| isviridov | rushiagr, here it is documentation about it https://github.com/stackforge/magnetodb/blob/master/doc/deploy_magnetodb_howto.rst | 14:13 |
| rushiagr | isviridov: oh, mirantis openstack. We are an ubuntu shop :( | 14:14 |
| isviridov | rushiagr, please note it was done half a year ago and has dependencies on some very early version of Mirantis OpenStack | 14:14 |
| rushiagr | I just started to look at the provisioning aspect. I was going to put stuff here: https://github.com/rushiagr/cloud-cassandra . Please don't have a look yet, it is embarassingly crude and has not a single bit of heat :( | 14:15 |
| isviridov | rushiagr, it is all about dependencies, nothing special. I believe it is possible to recove it for ubunntu | 14:15 |
| rushiagr | isviridov: okay. I'll see how we can consume that | 14:15 |
| rushiagr | that repo was worth an hour of work actually :/ | 14:16 |
| isviridov | rushiagr, I believe achuprin is also interested in it | 14:16 |
| rushiagr | charlesw: sure | 14:16 |
| *** openstackgerrit has joined #magnetodb | 14:16 | |
| rushiagr | isviridov: cool! | 14:16 |
| charlesw | rushiagr, please post back how you go with the doc, thx | 14:17 |
| rushiagr | charlesw: yes, sure | 14:17 |
| isviridov | Guys, one more clarification from my side. | 14:19 |
| isviridov | There is a schedule conflict with celiometer team, that is why we have meeting in this channel. | 14:20 |
| charlesw | thx for clarification | 14:21 |
| charlesw | Found the bug already registered for updateItem tempest coverage: https://bugs.launchpad.net/magnetodb/+bug/1332056 | 14:24 |
| isviridov | charlesw, could you give +2 and approve now? I've updated project config | 14:24 |
| ikhudoshyn | charlesw, isviridov, dukhlov https://review.openstack.org/#/c/122404/ guys pls approve | 14:25 |
| isviridov | charlesw, added to juno-rc1 | 14:25 |
| charlesw | great, I'll try :) | 14:25 |
| charlesw | yes, +2 | 14:27 |
| ikhudoshyn | charlesw, tnx | 14:29 |
| isviridov | ikhudoshyn, I have to look on it closer. Will do today. | 14:30 |
| ikhudoshyn | isviridov, sure, pls do | 14:30 |
| rushiagr | isviridov: just curious, are we not doing i18n yet? | 14:31 |
| ikhudoshyn | rushiagr, haven't started yet | 14:34 |
| rushiagr | ikhudoshyn: okay. I'll have a proper look at the patch soon, but not today. Too tired :( | 14:34 |
| ikhudoshyn | rushiagr, sure | 14:35 |
| *** openstackgerrit has quit IRC | 14:40 | |
| *** openstackgerrit has joined #magnetodb | 14:42 | |
| ajayaa | isviridov, ikhudoshyn https://wiki.openstack.org/wiki/MagnetoDB/specs/rbac | 15:08 |
| ajayaa | Please let me know if something is not clear. | 15:09 |
| ikhudoshyn | ajayaa, Great, thanks, I'll take a look on that. | 15:10 |
| ikhudoshyn | will look closer, but there is one question I already get | 15:12 |
| openstackgerrit | Alexei Vinogradov proposed a change to stackforge/magnetodb: fixed: Cleanup MagnetoDB specific data from Cassandra https://review.openstack.org/124078 | 15:12 |
| ikhudoshyn | "The above rule could be made stricter by "mdb:create_table":"role:admin and project_id:(project_id)s"." -- I think we should not have this in a json file. | 15:12 |
| ikhudoshyn | All configurations are the matter of deployment. | 15:13 |
| ikhudoshyn | But project ids are usually defined in runtime | 15:13 |
| ajayaa | Hi ikhudoshyn, Yes. But project_ids can be passed during run time to policy engine. | 15:21 |
| ajayaa | That's how it works. While calling function from policy engine we pass a dictionary containing the project_id and the policy engine checks for project_id against this dictionary. | 15:23 |
| ikhudoshyn | it would be great to have a somewhat more detailed API description for that | 15:24 |
| ikhudoshyn | i'm afraid I don't follow it | 15:25 |
| ikhudoshyn | It's late for me here. Will try to look closer tomorrow | 15:25 |
| ikhudoshyn | btw, have you looked at how this done in other OS projects? | 15:25 |
| ikhudoshyn | if u have some links pls sare | 15:26 |
| ikhudoshyn | s/sare/share | 15:26 |
| ajayaa | I will do and update the specs as well. | 15:27 |
| ajayaa | Similarly I will upload my working POC for you to have a look. | 15:28 |
| ajayaa | ikhudoshyn ^^ | 15:28 |
| ikhudoshyn | ajayaa, great | 15:29 |
| *** k4n0 has quit IRC | 15:43 | |
| *** ajayaa has quit IRC | 16:03 | |
| *** rushiagr is now known as rushiagr_away | 16:11 | |
| *** romainh has left #magnetodb | 16:20 | |
| openstackgerrit | Nuno Santos proposed a change to stackforge/magnetodb: Typo in table name https://review.openstack.org/124100 | 16:21 |
| *** openstackgerrit has quit IRC | 16:33 | |
| *** rushiagr_away is now known as rushiagr | 16:48 | |
| *** openstackgerrit has joined #magnetodb | 16:54 | |
| *** jeromatron has joined #magnetodb | 16:58 | |
| *** vnaboychenko has joined #magnetodb | 17:11 | |
| *** openstackgerrit has quit IRC | 17:33 | |
| *** openstackgerrit has joined #magnetodb | 17:41 | |
| *** jeromatron has quit IRC | 17:50 | |
| openstackgerrit | Alexei Vinogradov proposed a change to stackforge/magnetodb: fixed: Cleanup MagnetoDB specific data from Cassandra https://review.openstack.org/124078 | 18:03 |
| *** rushiagr is now known as rushiagr_away | 18:20 | |
| *** jeromatron has joined #magnetodb | 18:21 | |
| *** jeromatron has quit IRC | 18:26 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Add queued storage manager https://review.openstack.org/122404 | 18:28 |
| *** jeromatron has joined #magnetodb | 18:33 | |
| *** jeromatron has quit IRC | 18:36 | |
| *** jeromatron has joined #magnetodb | 19:42 | |
| *** jeromatron has quit IRC | 20:01 | |
| *** jeromatron has joined #magnetodb | 20:03 | |
| *** jeromatron has quit IRC | 20:08 | |
| *** jeromatron has joined #magnetodb | 20:24 | |
| openstackgerrit | Charles Wang proposed a change to stackforge/magnetodb: Handle non existent item when calling update_item Closes-Bug: #1373627 https://review.openstack.org/123927 | 21:30 |
| *** charlesw has quit IRC | 21:58 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Improve json schema validation for requests left https://review.openstack.org/122445 | 23:02 |
| *** jeromatron has quit IRC | 23:06 | |
| *** boris-42 has quit IRC | 23:47 | |
| *** boris-42 has joined #magnetodb | 23:48 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!