08:00:28 #startmeeting storlets 08:00:29 Meeting started Tue Mar 14 08:00:28 2017 UTC and is due to finish in 60 minutes. The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:33 The meeting name has been set to 'storlets' 08:00:35 hey-yo 08:00:40 hi 08:00:43 Hi 08:01:31 Let's start. 08:01:42 Hi 08:02:20 akihito: Hi 08:02:28 I did not add anything to the agenda 08:02:51 There is something on stopping unused containers 08:02:59 which I am looking at 08:03:04 hi 08:03:11 takashi: !!!! 08:03:14 takashi: Hi! 08:03:40 we missed you takashi at the PTG 08:03:43 all: hi 08:04:11 kota_: sorry about that :-( I'll check your great discussion result... 08:04:54 takashi: Hi! 08:05:00 There are no big topics from my side today. I think I should review some of the patches about agent refactoring 08:05:05 eranrom: o/ 08:05:22 takashi: great to see you here! 08:05:38 eranrom: me too :-) 08:05:52 it would be great if I can ask some review about https://review.openstack.org/#/c/426586/ 08:05:58 especially from kota_ :-P 08:06:09 what's that? 08:06:23 about range handling 08:06:28 #topic: Patches priority reviews 08:06:35 oic 08:06:37 eranrom: thx 08:07:05 :-) 08:07:14 I'm afraid this is very affective bug, so I'll backport it to stable later. 08:07:18 after we land the fix 08:07:35 I think we also need to backport the patch to fix breaking unit test to stable 08:07:40 takashi: yep, good point. 08:08:06 takashi: I think I did that. 08:08:07 which is submitted by kota_ and already merged to master 08:08:22 eranrom: I'm afraid that I overlooked that. thx! 08:08:26 if no big topic here, can we look at the patch together? 08:08:47 what's the difference after the version i reviewed 08:08:48 ? 08:09:07 sorry, I have to re-install the change in my head :/ 08:09:22 I have 'stopping unused containers' topic. 08:09:27 kota_: added some unit tests to assert my change 08:09:31 I have resource limiting topic, but now I am writing that to etherpad. 08:09:47 #link: https://etherpad.openstack.org/p/storlets-rate-resource-limiting-design 08:10:06 kota_: in tests/unit/swift_middleware/handlers/test_obj.py and tests/unit/swift_middleware/handlers/test_proxy.py 08:10:13 ok lets spend few minutes on the patch, and then proceed with Sagara's and Akihito's topics 08:10:19 eranrom: +1 08:10:24 thanks 08:10:45 Thank you! I wrote my topic in etherpad. 08:10:49 <> 08:10:53 No. 10 - 12 08:11:03 kota_: takashi: we want to go over this one https://review.openstack.org/#/c/426586/ right? 08:11:14 takashi: quick question, current *file* object range shouldbe [start, end] but http range [start, end), right? 08:11:19 akihito: yes, I saw good topic! 08:11:21 eranrom: yes 08:11:26 kota_: yes 08:11:49 k and the middleware (which in http layer) resolves (translates) to file 08:11:51 make sense. 08:13:41 takashi: can you make sure https://review.openstack.org/#/c/426586/2..4/tests/unit/swift_middleware/handlers/test_obj.py@258 08:13:41 ? 08:14:02 the http range calls 1-6 there 08:14:14 kota_: oh, sorry 08:14:22 and http range should be [1, 6) so that 1, 2, 3, 4, 5 08:14:22 In http rfc, range should include end 08:14:38 so http deals range as [start, end] 08:14:45 that means, opposite? 08:14:52 kota_: yes 08:15:00 current file object deals range as [start, end) 08:15:08 so we need some translation between them 08:15:24 more precisely, current python file object 08:15:50 ah, ok, the docs in middleware says, general range as (include start, and exclude end) 08:16:37 kota_: I believe that is general range diffinition :-P 08:16:52 definition 08:19:41 done 08:20:03 kota_: Thanks! 08:20:22 kota_: thx! 08:20:25 anything else on reviews? 08:20:38 I still like clear cleanup for convert http range <-> general range (class or functions) 08:20:40 though 08:21:10 kota_: My understanding is that the translation between http and files requires adding +1 to the end. 08:21:26 eranrom: correct 08:21:42 previously that +1 was in the SBus layer, and Takashi changes that to happen in the middleware level 08:22:20 eranrom: previously that +1 was done in Java SDaemon 08:22:35 and not done in Python SDaemon (storlet-daemon) 08:22:35 oh, even worse... 08:22:47 takashi: right! 08:22:47 with my patch, +1 is done in gateway side 08:22:49 takashi: that means, Java SDaemon is now +2 for the range? 08:22:59 kota_: I removed that +1 in my patch 08:23:03 ok 08:23:27 all range execution case python/java proxy/object is now tested in functional tests 08:24:55 anything else on ramges? 08:24:58 ranges? 08:25:19 nothing more from me 08:25:34 I'll submit backport patch to stable/ocata later, and ping you after that 08:26:18 takashi: sure. thanks! 08:26:48 anything else on patches before we continue? 08:29:09 please go ahead eranrom 08:29:16 let's move to the next topic 08:29:55 Since I have already read, lets continue with Akihito's topic. 08:30:18 #topic: Stopping unused containers / storlet demons 08:30:21 Thank you! 08:30:42 I like the suggestion, I have two comments so far: 08:31:33 1. We need to add a configurable timeouts for all 3 (I think you mention a timeout only for the third, which is the storlet app) 08:32:34 2. I would like to understand how you plan to enforce the storlet app timeout. for the factory and storlet daemon it seems pretty streight forward 08:33:19 sorry one more comment: 08:33:55 Regarding file deletions. Have we agreed on having a storlet create a file? 08:35:20 sorry, I'm missing the etherpad which we reffers right now 08:35:33 eranrom: Thank you comments. first. Why we need to set Timeout for daemon_factory and agent process? 08:35:34 https://etherpad.openstack.org/p/storlets-pike-design-summit 08:35:52 No. 10-12 :-) 08:36:19 akihito: ah, you added to that one, ok thx 08:36:47 please continue 08:36:50 akihito: because when we, e.g. start the container, and hence the daemon_factory there may be some time passing before any storlet_daemon is started 08:37:47 Oh. I understand! OK. fix it. 08:37:49 similarly, there may pass some time after we start a storlet_daemon and before we get a storlet request 08:39:00 for No2 comments. I want to add timeout for storlet app in agent_process. 08:39:10 https:/In /github.com/openstack/storlets/blob/master/storlets/agent/daemon/manager.py#L223-L224 08:39:29 sorry <> 08:40:24 refer to <> 08:40:49 oh. sorry.. 08:40:57 https://review.openstack.org/#/c/410296/5/storlets/agent/common/server.py 08:43:15 Making a suggestion: 08:43:56 sorry.. 08:44:23 np 08:44:56 How about writing comments on the etherpads, and use the time now for questions. 08:45:14 i support that idea 08:45:28 akihito: I will comment on the Etherpad regarding your answer to comment 2. 08:46:59 eranrom: I see. Thank you. 08:49:11 eranrom: on the question for you 08:49:27 kota_: yep 08:49:39 eranrom: meaning "should we support that storlet app can write some files into the local in the container" 08:49:51 eranrom: I strongly recommend to support that option 08:50:15 kota_: right, we started this discussion. and I think takashi also wanted to ask on this. 08:50:19 eranrom: I know, we *don't* want such in-effective use case for our storlet streaming apps 08:51:15 eranrom: however, from my experience with my custormers, absolutely we will have a clif (might be wall) when translating leagcy app to the storlet one. 08:51:55 i'm calling *legacy* app is something like which can run on file system 08:52:09 kota_: I see. 08:52:50 eranrom: i can manage the translation with my custormer but almost case for our poc starts with just running legacy app in the storlet container 08:53:03 that is enabled to write the files to read 08:53:21 ffmpeg? 08:53:34 no? 08:53:56 i have certain cases for now, 08:54:05 not only oss 08:54:11 kota_: I was asking because I had the same problem with ffmpeg for which I found a solution 08:54:20 kota_: got it 08:54:54 ok, note that cleaning up those files is as simple as restarting the container (and deleting the older instance) 08:55:14 eranrom: maybe it's one of them. espically, a kind of hard-coded 'path-forced' input format. 08:55:29 kota_: yep 08:55:29 like "progam -i file_to_path" 08:55:38 right 08:56:07 Will you be interested to setup another time this week to discuss the comments for Sagara's and Akihito's suggestions? 08:56:17 we can read it all and comment by then 08:56:28 we can meet in #openstack-storlets 08:56:34 +1 08:56:49 yes, I would like you to review resource limiting design. 08:57:02 OK. 08:57:23 Tomorrow same time? 08:58:07 i could have 08:58:44 I'll join if possible 08:59:17 I had some local discussions about the topics with sagara-san and akihito, so I think you can have the discussion without me. 08:59:18 just a wait 08:59:56 takashi: ok, sure! 09:00:11 I can join tomorrow meeting at same time. 09:00:18 sagara: greate thanks 09:00:22 I must end here. 09:00:32 eranrom: thanks 09:00:34 Lets go to #openstack-storlets 09:00:37 #endmeeting