08:14:00 <takashi> #startmeeting storlets
08:14:01 <openstack> Meeting started Tue Oct  4 08:14:00 2016 UTC and is due to finish in 60 minutes.  The chair is takashi. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:14:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:14:04 <openstack> The meeting name has been set to 'storlets'
08:14:05 <kota_> takashi: nice
08:14:12 <takashi> kota_: :-)
08:14:45 <takashi> I updated agenda a little: https://wiki.openstack.org/wiki/Meetings/Storlets
08:15:01 <takashi> kota_: feel free to add any topics
08:15:05 <kota_> takashi: tbh, I've been hit another meeting so that i could response with delay
08:15:33 <takashi> kota_: ok
08:16:46 <takashi> Can we proceed base on the agenda?
08:17:15 <takashi> kota_: I think it does not take so mach time, so we can take time about your topic after that
08:17:20 <takashi> I think
08:19:31 <kota_> ok
08:20:18 <takashi> #topic Design Summit planning
08:21:04 <takashi> I just started to write down my idea about discussion point in design summit, based on eranrom's first draft
08:21:26 <takashi> kota_: I found that you already added some of your ideas
08:21:51 <kota_> takahshi: yea
08:22:24 <takashi> will add mine soon
08:22:31 <kota_> with quick view, it looks like there are awesome topics
08:22:52 <takashi> kota_: yes :-)
08:23:31 <takashi> I think I need to pick up some topics from python storlet related works, and also I think there are something we need to highlight in our design summit
08:23:43 <takashi> about big-tent work
08:24:06 <kota_> thinking of the conflicted session with Swift's, could we move our slotst to sort of Wed?
08:24:38 <kota_> but basically, Wed is addressed for cross-project work
08:24:40 <kota_> hmmm
08:24:43 <takashi> kota_: maybe
08:25:19 <takashi> kota_: the reason why thursday morning is listed there is that there are available room at that time slot
08:25:45 <kota_> but if it's difficult to move them to Wed, current schedule looks not so bad because the morning time is for fb of Swift sessions.
08:26:32 <kota_> ah
08:27:20 <kota_> if we could address some sessions for implementations (e.g. python work) in the Thu fb, I'm happy because, I have to be abasent in Fri.
08:27:57 <takashi> kota_: agree
08:28:27 <takashi> kota_: Talking about myself, there are still some sessions not scheduled yet, but as far it seems that I'm available at Thursday morning (9:00-9:40) and on Wednesday
08:29:00 <kota_> ah, you mean, we could make mini-hackathon in Wed with ourselvs.
08:29:09 <kota_> sounds great
08:30:27 <kota_> wrote down at the bottom of etherpad.
08:32:05 <takashi_> kota_: sorry. I got disconnected for a while. maybe there are something wrong with the wifi network in my office... :-(
08:32:13 <takashi_> and back
08:32:15 <kota_> it looks takashi's line is unstable.
08:32:23 <kota_> takashi: np
08:33:33 <takashi_> kota_: I'll add my available time on the etherpad, as we discussed last week
08:34:02 <takashi_> but currently Thursday morning and Wednesday seems possible options for us
08:35:20 <takashi_> kota_: Can we move to the next topic?
08:35:52 <kota_> yes
08:36:08 <takashi_> #topic Big tent updates
08:37:16 <takashi> #topic Big tent updates
08:37:24 <takashi> now it works
08:37:27 <kota_> no updates from my side, do you have something?
08:37:39 <takashi> kota_: not so big updates
08:37:43 <kota_> but, I'd like to confirm the remaining tasks, though
08:38:03 <takashi> about python packaging, I found some problems caused by updated dependency packages
08:38:35 <takashi> I still need to find the root cause. Maybe I need to build clean environment to test that
08:40:16 <takashi> kota_: I think the thing should come for next is, bumping up keystone or replace nostests by testr in functest
08:40:27 <takashi> kota_: or... copyright stuff is another possible one
08:40:44 <takashi> I know eranrom is workin about using testr in functests
08:40:50 <takashi> s/workin/working/
08:41:40 <takashi> about python storlet works, we currently have awesome doc patch by eranrom
08:42:02 <kota_> takashi: yey, I've looked at
08:42:55 <takashi> It covers all things together with my previous patch. We still have some remaining work items, but that is the last thing we need to release the feature at least in beta status
08:43:28 <kota_> takashi: k, thanks.
08:43:59 <kota_> summrize that, we're now working, docs, packaging for big tent.
08:44:25 <kota_> plus testing
08:44:28 <kota_> gotcha
08:44:35 <takashi> kota_: yes
08:44:45 <takashi> kota_: I think it is great if we can talk with tc member directly at Barcelona
08:45:22 <kota_> takashi: nice idea!
08:45:24 <takashi> we can check remaining things there.
08:45:36 <kota_> ok, will do
08:45:43 <takashi> It seems that another project, Tricircle is requresing to have some time for dicsussion with tc members
08:45:51 <kota_> Is acoles comming?
08:46:23 <kota_> jk
08:47:03 <kota_> ok, Barcelona summit seems good place to get face to face conversion with tc
08:47:36 <takashi> kota_: yes. Let's talk about that plan with eranrom later
08:47:41 <kota_> k
08:47:43 <kota_> moving on?
08:47:44 <acoles> kota_: hello, what happened?
08:47:55 <takashi> kota_: yes
08:48:51 <kota_> what's topic on the next?
08:49:26 <takashi> #topic Release planning
08:49:29 <kota_> ok
08:49:43 <takashi> I think we don't have so much about this topic
08:50:08 <kota_> yes, docs will land soon, and we can cut the release, doesn't it?
08:50:17 <takashi> we agreed to include doc patch about python storlet works in the next release, and they are now ready for review (and hopefully ready for landing)
08:50:21 <takashi> kota_: yes
08:50:33 <kota_> k
08:50:55 <takashi> Tha's all from my side
08:51:01 <kota_> ok
08:51:04 <takashi> #topic Open discussion
08:51:26 <takashi> I think you have some topics, right?
08:51:31 <takashi> kota_: ^^^
08:51:40 <kota_> i think the logger change is really good one but I didn't get all for that, right now.
08:52:14 <takashi> kota_: you mean patch 380207
08:52:21 <kota_> I think, you know my traial and the status, we cannot get the actual log from python storlets if it fails by some reasons.
08:52:35 <kota_> https://review.openstack.org/#/c/380207
08:52:38 <kota_> yes
08:52:43 <takashi> kota_: yes
08:53:25 <kota_> I hope it could address A. dump a log correctly, B. we can look at the status in the gerrit log
08:53:59 <kota_> takashi: Q. does the newest patch set enable that?
08:54:25 <kota_> we have last 5 minutes :/
08:54:29 <takashi> kota_: Currently the patch can be a help for A, but there are something not covered yet
08:54:42 <takashi> kota_: ok
08:54:49 <kota_> ok, that means, it's still working.
08:54:57 <kota_> will look at to help something
08:55:13 <takashi> kota_: It captures stdio/stdout of daemon process, but it assume that the daemon process started properly
08:55:25 <kota_> yeah,
08:55:42 <takashi> kota_: I mean, for example No such file case, it generates stdout output before setting that captureing
08:55:44 <kota_> hopefully, I'd avoid the "logger" command, if possible
08:55:59 <kota_> though :/
08:56:08 <takashi> kota_: In my first idea, I passed our logger to popen to get rid of logger command
08:56:47 <takashi> kota_: However, after some testing, I noticed that popen requires fd related to that logger, which I still need to thin the way
08:57:01 <takashi> kota_: it tries to get logger.fileno()
08:57:46 <takashi> kota_: Maybe we need to open new pipe, and fork some process listening that fd and record the coming message to the log
08:58:16 <kota_> takashi: hmm...
08:58:38 <kota_> anyway, we're running out of time.
08:58:45 <kota_> will discuss later
08:58:49 <takashi> kota_: ok
08:59:39 <takashi> feel free to add your comment on the patch, or catch me at openstack-storlets
08:59:48 <kota_> takashi: could you please make the end command?
08:59:52 <takashi> #endmeeting