| *** charlesw has joined #magnetodb | 01:22 | |
| *** achanda has quit IRC | 02:42 | |
| openstackgerrit | Charles Wang proposed stackforge/magnetodb: Adds detailed response body to success healthcheck request https://review.openstack.org/144774 | 02:49 |
|---|---|---|
| *** rushiagr_away is now known as rushiagr | 02:52 | |
| *** rushiagr is now known as rushiagr_away | 02:54 | |
| *** rushiagr_away is now known as rushiagr | 02:55 | |
| *** rushiagr is now known as rushiagr_away | 03:12 | |
| *** rushiagr_away is now known as rushiagr | 03:53 | |
| *** achanda has joined #magnetodb | 04:31 | |
| *** charlesw has quit IRC | 04:35 | |
| *** achanda has quit IRC | 05:04 | |
| *** rushiagr is now known as rushiagr_away | 05:14 | |
| *** achanda has joined #magnetodb | 05:28 | |
| *** rushiagr_away is now known as rushiagr | 05:58 | |
| *** achanda has quit IRC | 07:11 | |
| *** achanda has joined #magnetodb | 07:24 | |
| *** achanda has quit IRC | 07:44 | |
| *** rushiagr is now known as rushiagr_away | 08:11 | |
| *** idegtiarov has left #magnetodb | 08:47 | |
| *** ygbo has joined #magnetodb | 08:51 | |
| *** ominakov_ has joined #magnetodb | 09:19 | |
| *** ominakov_ has quit IRC | 10:38 | |
| *** ominakov_ has joined #magnetodb | 11:13 | |
| *** ominakov_ has quit IRC | 11:22 | |
| *** ominakov_ has joined #magnetodb | 11:37 | |
| *** ominakov_ has quit IRC | 11:42 | |
| *** isviridov_vction is now known as isviridov | 11:54 | |
| *** aostapenko has left #magnetodb | 11:56 | |
| *** aostapenko has joined #magnetodb | 11:57 | |
| *** rushiagr_away is now known as rushiagr | 12:28 | |
| isviridov | Hello everyone | 13:54 |
| *** ChanServ sets mode: +o isviridov | 13:57 | |
| *** isviridov changes topic to "MagnetoDB - key-value store for OpenStack (https://wiki.openstack.org/wiki/MagnetoDB, logs @ https://botbot.me/freenode/magnetodb/) | Kilo roadmap http://goo.gl/XHXIpg | ask isviridov is any Qs" | 13:58 | |
| isviridov | dukhlov: aostapenko? | 13:59 |
| *** charlesw has joined #magnetodb | 13:59 | |
| isviridov | charlesw: hello | 13:59 |
| dukhlov | isviridov: Hello | 14:00 |
| charlesw | Hi isviridov, you are back :) | 14:00 |
| isviridov | dukhlov: hey | 14:00 |
| dukhlov | aostapenko seems busy | 14:00 |
| isviridov | charlesw: yeap and missed all of you | 14:00 |
| isviridov | dukhlov: clear | 14:00 |
| isviridov | We have a meeting scheduled, let us start | 14:01 |
| isviridov | #startmeeting magnetodb | 14:01 |
| openstack | Meeting started Thu Mar 12 14:01:18 2015 UTC and is due to finish in 60 minutes. The chair is isviridov. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
| openstack | The meeting name has been set to 'magnetodb' | 14:01 |
| isviridov | #link https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda#12_Mar.2C_2015.2C_14:00_UTC | 14:01 |
| isviridov | Agenda | 14:01 |
| isviridov | Not too many topics | 14:02 |
| isviridov | Not sure I know what action items left from previous meeting | 14:02 |
| isviridov | #topic Go through action items | 14:03 |
| isviridov | Guys? anything from your side? | 14:03 |
| charlesw | maybe a round of status | 14:03 |
| dukhlov | yes | 14:03 |
| charlesw | I'll go first | 14:03 |
| aostapenko | Hi, guys | 14:04 |
| isviridov | charlesw: please | 14:04 |
| isviridov | aostapenko: hey man | 14:04 |
| charlesw | Working on the health check metrics, https://review.openstack.org/#/c/144774/7, https://review.openstack.org/#/c/159325/, https://review.openstack.org/#/c/161743/ | 14:04 |
| charlesw | I'm picking up this one https://review.openstack.org/#/c/144774/9 since Andrei seems tied up with something else | 14:05 |
| charlesw | And I have a dependency on it | 14:06 |
| charlesw | Also working with dukhlov to merge refactor notification https://review.openstack.org/#/c/143115/ | 14:07 |
| * isviridov thinks it is a lot of items | 14:07 | |
| dukhlov | I picked up refactor notification. | 14:08 |
| dukhlov | When I started work on it and dig deeper I faced with a few problems | 14:09 |
| dukhlov | and now I'm thinking how to implement it better | 14:09 |
| charlesw | dukhlov, can you explain what problems you encountered? | 14:10 |
| dukhlov | but nothing serious | 14:10 |
| isviridov | charlesw: +1 | 14:10 |
| isviridov | #topic Round of status | 14:11 |
| dukhlov | should we notify requests only passed authentification? | 14:11 |
| charlesw | I wouldn't think so. Unauthenticated req should also be logged so we can understand what percentage of reqs are failing because of authn issue | 14:14 |
| dukhlov | if no, in this case of authorization get failed we haven't parsed request yet | 14:14 |
| dukhlov | and have no information for notification | 14:14 |
| charlesw | at the end, admin should be able to tell the percentage of each response status code | 14:14 |
| *** rushiagr is now known as rushiagr_away | 14:14 | |
| charlesw | That's why I implemented that part | 14:14 |
| dukhlov | but at authorization stage we haven't parsed request and don't know what is this request exactly | 14:15 |
| dukhlov | we could sent notification like - some request was anauthorized | 14:16 |
| charlesw | we know the req, so we know the API url | 14:16 |
| charlesw | API url + HTTP method maps to our API one-to-one | 14:16 |
| dukhlov | no, we don't know we should duplicate parsing logic and parse it to get this infrmation | 14:17 |
| charlesw | No this is not duplicate parsing since the req is rejected for failing to pass authn | 14:17 |
| dukhlov | ok, duplicating code I ment | 14:18 |
| charlesw | well, the mapping code I added in is much simpler than WSGI mapper | 14:19 |
| dukhlov | we do it only once but if all fine using one code and if something wrong - using another | 14:19 |
| charlesw | we need to handle that one way or the other | 14:19 |
| dukhlov | it is simple, but it is a mess | 14:19 |
| *** ominakov_ has joined #magnetodb | 14:21 | |
| charlesw | unless we have a better solution. | 14:21 |
| dukhlov | exactly | 14:21 |
| isviridov | I think that we have to produce event on un authorized request, because it is important information for security auditing | 14:22 |
| dukhlov | so I'm thinking how to do this better | 14:22 |
| isviridov | Another question how to code it better | 14:22 |
| isviridov | dukhlov: does shared code help? | 14:22 |
| dukhlov | no | 14:23 |
| dukhlov | mmm | 14:23 |
| dukhlov | maybe | 14:23 |
| dukhlov | but not in current implementation | 14:23 |
| charlesw | ominakov, welcome back | 14:23 |
| dukhlov | requres some more efforts for refactoring | 14:24 |
| charlesw | dukhlov, we need to speed up this one. It has a business impact | 14:25 |
| dukhlov | clear | 14:25 |
| charlesw | maybe we can leave it for future. The functionality needs to be in first. | 14:25 |
| *** ominakov_ has quit IRC | 14:25 | |
| *** ominakov_ has joined #magnetodb | 14:26 | |
| isviridov | dukhlov: charlesw moving on? | 14:26 |
| dukhlov | I am afraid that in future it will require much more efforts to refactor it and it can remain as is, but you are right | 14:28 |
| isviridov | #topic Open discussion | 14:28 |
| isviridov | Do you think that scheduled regular meeting is needed? | 14:29 |
| isviridov | I mean we can have it ad-hoc and announce day before when it is needed. | 14:30 |
| isviridov | What do you think? | 14:30 |
| charlesw | ad-hoc seems more appropriate now since much less activities hence less topics. Or switch to bi-weekly. | 14:31 |
| isviridov | I also think so. Every second week looks also good for me. | 14:33 |
| isviridov | dukhlov: aostapenko? | 14:33 |
| dukhlov | sounds reasonable because of decreasing contribution activity | 14:34 |
| isviridov | Ok, I'll update wiki, and next meeting will take place 26 of March | 14:35 |
| isviridov | #action isviridov update weekly meeting schedule | 14:35 |
| *** achanda has joined #magnetodb | 14:36 | |
| isviridov | Any other topics? | 14:36 |
| aostapenko | isviridov: agree | 14:37 |
| isviridov | aostapenko :) | 14:37 |
| isviridov | aostapenko thx for sharing your view | 14:37 |
| isviridov | dukhlov charlesw aostapenko finishing the meeting | 14:38 |
| charlesw | isviridov, thanks for organizing | 14:39 |
| isviridov | Thank you for comming | 14:39 |
| isviridov | #endmeeting | 14:39 |
| openstack | Meeting ended Thu Mar 12 14:39:38 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:39 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-03-12-14.01.html | 14:39 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-03-12-14.01.txt | 14:39 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/magnetodb/2015/magnetodb.2015-03-12-14.01.log.html | 14:39 |
| *** achanda has quit IRC | 14:44 | |
| *** igormarnat is now known as imarnat | 14:47 | |
| *** imarnat is now known as igormarnat | 14:52 | |
| *** ominakov_ has quit IRC | 14:59 | |
| *** rushiagr_away is now known as rushiagr | 15:30 | |
| *** igormarnat is now known as imarnat | 15:30 | |
| *** imarnat is now known as igormarnat | 15:45 | |
| *** ygbo has quit IRC | 17:17 | |
| *** achanda has joined #magnetodb | 17:32 | |
| *** achanda has quit IRC | 18:17 | |
| *** igormarnat is now known as imarnat | 18:20 | |
| *** achanda has joined #magnetodb | 18:23 | |
| *** achanda has quit IRC | 18:23 | |
| *** achanda has joined #magnetodb | 18:24 | |
| *** imarnat is now known as igormarnat | 18:50 | |
| *** igormarnat is now known as imarnat | 18:51 | |
| *** rushiagr is now known as rushiagr_away | 19:20 | |
| *** imarnat is now known as igormarnat | 19:34 | |
| *** openstackgerrit has quit IRC | 19:40 | |
| *** openstackgerrit has joined #magnetodb | 19:41 | |
| openstackgerrit | Charles Wang proposed stackforge/magnetodb: Add detailed response body to healthcheck request and fix messaging https://review.openstack.org/144774 | 20:15 |
| openstackgerrit | Charles Wang proposed stackforge/magnetodb: Add periodic tasks to send health check metrics https://review.openstack.org/161743 | 20:20 |
| openstackgerrit | Charles Wang proposed stackforge/magnetodb: Add periodic tasks to send health check metrics https://review.openstack.org/161743 | 20:59 |
| openstackgerrit | Charles Wang proposed stackforge/magnetodb: Add detailed response body to healthcheck request and fix messaging https://review.openstack.org/144774 | 21:43 |
| openstackgerrit | Charles Wang proposed stackforge/magnetodb: Add detailed healthcheck response body and fix messaging config https://review.openstack.org/144774 | 21:45 |
| *** charlesw has quit IRC | 22:22 | |
| *** achanda has quit IRC | 22:52 | |
| *** achanda has joined #magnetodb | 22:53 | |
| *** achanda_ has joined #magnetodb | 22:56 | |
| *** achanda_ has quit IRC | 22:56 | |
| *** achanda_ has joined #magnetodb | 22:56 | |
| *** achanda has quit IRC | 22:57 | |
| *** achanda has joined #magnetodb | 23:08 | |
| *** achanda_ has quit IRC | 23:11 | |
| *** achanda has quit IRC | 23:32 | |
| *** achanda has joined #magnetodb | 23:32 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!