| *** takashi has joined #openstack-storlets | 06:46 | |
| *** openstackgerrit has quit IRC | 06:48 | |
| *** openstackgerrit has joined #openstack-storlets | 06:49 | |
| takashi | eranrom_: sorry for my late reply. I just want to make sure that some of us submit talks planned, because we do not have so long time before deadline comes. | 06:50 |
|---|---|---|
| eranrom_ | no problem. So you will be submitting - right? | 06:50 |
| takashi | eranrom_: can I ask you to submit it? I'm afraid I can't make time for that today... :-( | 06:52 |
| eranrom_ | no problem. sec. | 06:52 |
| takashi | eranrom_: thank you. please let me know when you create the submittion. I'll have a look about that. | 06:52 |
| takashi | eranrom_: I think you can select my and kota_'s account using e-mail address, when adding speakers. | 06:53 |
| takashi | eranrom_: please make sure to use my company e-mail. | 06:53 |
| takashi | (not gmail or other | 06:54 |
| eranrom_ | sure. | 06:54 |
| takashi | eranrom_: thank you again for working about that | 06:54 |
| *** takashi_ has joined #openstack-storlets | 07:03 | |
| *** takashi has quit IRC | 07:03 | |
| eranrom_ | takashi_, kota_: I have just submitted the 101 talk, please review and chance as you see fit. | 07:27 |
| takashi_ | eranrom_: thank you for submitting the talk. Now I can see the detail! | 07:52 |
| eranrom_ | sure. Please review :-) | 07:53 |
| takashi_ | eranrom_: I have one question. When we choose "Developers" as summit categories, we can choose "big data" as generic topic. | 07:53 |
| eranrom_ | I am not sure. Seems like there is one checkbox there... but if you find a way that would be great. An alternative is to choose the category with 'big data'... | 07:54 |
| takashi_ | eranrom_: Is it reasonable for you to change category from Architecture & Operations to Developers? | 07:55 |
| eranrom_ | sure. I think you can also do that. | 07:56 |
| eranrom_ | I am good this it. | 07:56 |
| takashi_ | eranrom_: thanks | 07:56 |
| takashi_ | eranrom: I just updated it | 07:58 |
| takashi_ | IMO, "Big Data" topic can be more attractive for people than "Storage" topic, and also shows clearly that we are doing more that Storage. | 07:58 |
| takashi_ | s/that/than/ | 07:59 |
| takashi_ | eranrom_: I updated the titol of the talk, as I mentioned in my e-mail. (I think current topic is a little different from 101) If you have any thought about it, please let me know. | 08:53 |
| eranrom_ | takashi_: I am good with the change to big data. Regarding the title, it sounds to me too specific and poeple may think it will be of less interest if they are not involved in the project | 09:08 |
| eranrom_ | This is not to say that 101 is the right title... | 09:08 |
| takashi_ | eranrom_: I'm open for changing the title, but currently I think 101 is not good if we try to choose Developers category, to select big data topic. | 09:14 |
| takashi_ | eranrom_: I think it is a temporal one. In my current thought, we should include two things in the title. (1) We'll explain what is storlet (2) We'll also describe technical detail | 09:15 |
| eranrom_ | How about: Storlets deep dive | 09:16 |
| eranrom_ | or storlets technical deep dive | 09:17 |
| takashi_ | eranrom_: makes sense | 09:23 |
| takashi_ | "Storlets deep dive" looks better to me, because we also have some topics for app developers | 09:25 |
| eranrom_ | ok. great. | 09:35 |
| *** takashi_ has quit IRC | 10:26 | |
| *** takashi has joined #openstack-storlets | 12:56 | |
| eranrom_ | Hi | 12:57 |
| takashi | eranrom_: hello | 12:58 |
| eranrom_ | I guess Kota is in the Hackathon, so its only us. | 12:58 |
| eranrom_ | ? | 12:58 |
| takashi | eranrom_: I suppose so | 12:58 |
| eranrom_ | ok. I have only 30 minutes today. | 12:58 |
| eranrom_ | I can update on: | 12:59 |
| eranrom_ | 1. I will send soon a plan for the security feature | 12:59 |
| eranrom_ | 2. I am making progress on the Spark code, will have more updates soon | 13:00 |
| takashi | eranrom_: looking forward to see them! | 13:00 |
| eranrom_ | Otherwise, regarding the openstack talk, did you update the subject? Should I? | 13:01 |
| takashi | eranrom_: I just did it | 13:01 |
| eranrom_ | great | 13:01 |
| takashi | thank you for your lot of working about it | 13:01 |
| takashi | I'll update if I find any possible improvoments, but IMO now our proposal is ready | 13:02 |
| takashi | :-) | 13:02 |
| eranrom_ | alright, cool. | 13:02 |
| takashi | eranrom_: I don't have so big update today. I'm still working about copy fix and python application support | 13:02 |
| eranrom_ | ok, I still see -1 on the recent refactoring work. Want me to have a look? | 13:03 |
| eranrom_ | Gerrit seems down so I do not have the patch is | 13:04 |
| eranrom_ | id | 13:04 |
| takashi | eranrom_: That is the last one of refactoring work. I saw some error in storlet range execution, but need some more time to find the cause | 13:04 |
| eranrom_ | I see. | 13:04 |
| eranrom_ | I will try to have a look | 13:04 |
| takashi | eranrom_: thx | 13:05 |
| takashi | I saw two kinds of failure in functional testing | 13:05 |
| takashi | 1. input range is ignored | 13:05 |
| takashi | 2. timeout happens in storlet execution | 13:05 |
| eranrom_ | I had 1 many times during the development of the feature. | 13:06 |
| eranrom_ | I will have a look | 13:06 |
| takashi | I suppose there are some wrong handling about range parameters, and I'll have a deep look in this week, or at least in the early next week | 13:06 |
| eranrom_ | sure, np | 13:06 |
| takashi | eranrom_: thanks you for your help | 13:06 |
| eranrom_ | yw (you welcome:-) | 13:07 |
| eranrom_ | anything else for today? | 13:07 |
| takashi | one update about copy fix | 13:07 |
| takashi | I'll inform you detailed information later, but I found current swift does not allow copy with chunked get | 13:07 |
| eranrom_ | interesting | 13:08 |
| takashi | that's because they do not want to allow copy of the large object, which has more objects than the listing limit of container | 13:08 |
| takashi | (I found the patch introduced that limitation, and it says so | 13:09 |
| eranrom_ | Does this happen when you place storlet_handler to the left of copy? | 13:09 |
| eranrom_ | actually it does not make sense | 13:09 |
| takashi | to the right of copy | 13:09 |
| eranrom_ | right :-) | 13:09 |
| takashi | I'm doing a PoC about the idea you wrote in the previous e-mail (detect PUT/GET caused by copy in storlet_handler, and invoke storlet in one side) | 13:10 |
| eranrom_ | ok, so when do we encounter the Swift limitation... | 13:11 |
| eranrom_ | ? | 13:11 |
| takashi | eranrom_: In my first idea, I tried to execute storlet in GET request, when processing copy | 13:11 |
| takashi | but if we invoke storlet copy, we loose content-length in that response right? | 13:12 |
| eranrom_ | right. | 13:12 |
| eranrom_ | gotcha | 13:12 |
| takashi | then copy middleware tried to use that GET request, to put the retrieved content to the destination, but It notice that GET response is a chunked one, and raise 4xx error. | 13:12 |
| eranrom_ | and then the copy middleware cannot do the put - right? | 13:13 |
| takashi | eranrom_: yes | 13:13 |
| eranrom_ | ok now I get it. | 13:13 |
| eranrom_ | I guess we can still invoke the storlet on the put... | 13:13 |
| takashi | That logic is already introduced when copy was implemented inside swift. In previous architecture, we handle put by ourselves inside storlet_handler, and we didn't implement that limitation | 13:14 |
| eranrom_ | right | 13:14 |
| takashi | eranrom_: you are right, but I think we should make sure about the pros/cons of that change | 13:14 |
| eranrom_ | yeah. so the alternative is to put the storlet_handler to the left of the middleware. | 13:14 |
| eranrom_ | or perhaps fix Swift... | 13:14 |
| takashi | yes | 13:15 |
| eranrom_ | ok, do you have any thoughts as to the cons of invoking the storlet during the put part of the copy? | 13:15 |
| takashi | I'll have a deep look, and would like ask some thoughts about it by people who worked about copy_middleware | 13:15 |
| eranrom_ | sounds great\ | 13:15 |
| eranrom_ | ! | 13:15 |
| takashi | if we can reduce data size by invoking storlet, execution on proxy requires heavier traffic in GET than execution on object side | 13:16 |
| eranrom_ | right! | 13:16 |
| takashi | ex. if you put your image and execute strlet copy to extract tag information to create json object | 13:17 |
| takashi | if we can execute on object, we only need transfer json | 13:17 |
| takashi | if we execute on proxy, we need to transfer image file from object to proxy | 13:18 |
| eranrom_ | in such a case doing the put is really worse... | 13:18 |
| takashi | eranrom_: yes | 13:18 |
| eranrom_ | I guess it will be interesting to get the Swift community view on fixing that limitation... | 13:18 |
| eranrom_ | well a limitation for us... | 13:19 |
| takashi | eranrom_: that limitations is introduced in very old time, so there are some possible change in their opinion | 13:19 |
| eranrom_ | right. | 13:19 |
| eranrom_ | I mean good point. | 13:20 |
| takashi | At some point I'll show for swift community what is happening for use | 13:20 |
| takashi | about copy | 13:20 |
| eranrom_ | That would be great. | 13:21 |
| takashi | I'll let you inform if I get updates about this topic | 13:21 |
| eranrom_ | Thanks! | 13:21 |
| takashi | that's all from my side today | 13:21 |
| eranrom_ | ok thanks very much. One last thing: | 13:21 |
| eranrom_ | Are you ok with moving the IRC to Tuesdays, at a much earlier time? | 13:22 |
| eranrom_ | say my morning - your noon | 13:22 |
| takashi | eramrom_: I have a weekly meeting until around noon JST | 13:23 |
| eranrom_ | ok, so you prefer not to have yet another one right away I guess... | 13:24 |
| takashi | eranrom_: If we can have a meeting after 13:00, I think it works for me | 13:24 |
| eranrom_ | ok, great. I think this is also ok for Kota. I will send a mail to the list. | 13:25 |
| takashi | I'll wait your e-mail, and give me some time for checking my schedule (I can't check it from my house | 13:25 |
| eranrom_ | sure. thanks | 13:25 |
| takashi | :-) | 13:26 |
| takashi | Did we talk all topics for today? | 13:27 |
| eranrom_ | yes. Thanks for joining. | 13:27 |
| takashi | eranrom_: thank you | 13:28 |
| *** takashi has quit IRC | 13:31 | |
| *** openstackgerrit has quit IRC | 16:03 | |
| *** openstackgerrit has joined #openstack-storlets | 16:04 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!