16:00:03 <rakhmerov> #startmeeting Mistral
16:00:10 <openstack> Meeting started Mon Jan 26 16:00:03 2015 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:13 <openstack> The meeting name has been set to 'mistral'
16:00:38 <rakhmerov> hi
16:00:55 <NikolayM> hi!
16:01:31 <rakhmerov> let's wait for others
16:04:02 <rakhmerov> ok
16:04:09 <rakhmerov> #topic Review Action Items
16:04:14 <rakhmerov> 1. rakhmerov, dzimine, create necessary BPs/bugs for the upcoming "cleaning up" work
16:04:25 <rakhmerov> mostly done
16:04:49 <rakhmerov> 2. rakhmerov, NikolayM: reply to Winson on action providers design
16:04:50 <rakhmerov> done
16:05:06 <rakhmerov> dzimine, clarify https://blueprints.launchpad.net/mistral/+spec/mistral-runtime-context definition with Winson
16:05:07 <dzimine> Hi all
16:05:11 <rakhmerov> that was 3
16:05:13 <rakhmerov> hi dzimine
16:05:21 <dzimine> right on time :) but no
16:05:23 <rakhmerov> it's done as well
16:05:29 <rakhmerov> :)
16:05:39 <rakhmerov> 4. rakhmerov, add a couple of unit tests checking "updated_at population
16:06:07 <rakhmerov> it's done as well, Nastya also fixed functional tests to verify updated_at
16:06:26 <rakhmerov> #topic Current Status (by team members)
16:07:36 <rakhmerov> my status: last week finished with Secure Data Access BP, participated lots of design discussions etc. Today I finished fixing the bug https://bugs.launchpad.net/mistral/+bug/1412635
16:07:50 <rakhmerov> there was a lot of unit test to fix
16:08:27 <rakhmerov> plans: look at with-items and result/output thing
16:08:31 <rakhmerov> already started
16:09:05 <NikolayM> my status: worked and fixed patches on with-items and concurrency, fixed some bugs. Today began to work on JavaScript action (some research about what JS engine we will use exactly)
16:09:34 <rakhmerov> NikolayM, do you see any roadblocks?
16:09:40 <rakhmerov> with script action
16:09:48 <dzimine> my status: I was discovering and investigating bugs, and discussed with renat and others how to fix them. Small fix re task error output. More on the way.
16:10:56 <rakhmerov> NikolayM, we assumed script action BP would take 7 days, do you still think it's the right estimation?
16:11:19 <rakhmerov> dzimine, yeah, your fix has already been merged in
16:11:51 <dzimine> NikolayM, do you have cycles to look at https://bugs.launchpad.net/mistral/+bug/1413535
16:12:16 <NikolayM> no, I just found the right JS engine and try to emulate some JS lines
16:12:17 <dzimine> looks like you know testr stuff the best of us
16:13:09 <dzimine> re JavaScript task - than we need to flash out the sytax of communicating data in and out (especially out).
16:13:28 <rakhmerov> yep
16:13:36 <rakhmerov> as usually, "test first"
16:13:54 <NikolayM> yes
16:14:04 <rakhmerov> I think we can agree on the syntax pretty quickly
16:14:16 <rakhmerov> don't think there will be serious problems
16:14:39 <NikolayM> will the JS action work with our data context?
16:14:54 <rakhmerov> that's the part of the task
16:15:09 <NikolayM> or it will just work in its separate ctx?
16:15:15 <rakhmerov> somehow we need to be able to pass context data into a script
16:15:25 <rakhmerov> nope, not a separate ctx
16:15:28 <rakhmerov> same
16:15:36 <NikolayM> ok
16:16:07 <rakhmerov> so our assumption was that in that JS we should implicitly have function to access external context and pass data back to it
16:16:21 <rakhmerov> I think there was some info about that in the BP itself
16:16:25 <rakhmerov> let me check
16:17:01 <rakhmerov> yes, please look at it again carefully
16:17:15 <rakhmerov> for example, there's a syntax "v = read_from_context("param")"
16:17:24 <rakhmerov> https://blueprints.launchpad.net/mistral/+spec/mistral-javascript-action
16:17:25 <dzimine> in_context and input parameters will come in and somehow (how syntaxically?) will be available within the script. Than there gotta be syntax to make internal parameters available for the outer context so that they can be used in publish and on-success etc.
16:17:42 <rakhmerov> yes
16:17:58 <rakhmerov> it might be pretty challenging though
16:18:03 <dzimine> but this ‘syntax’ is exactly what we need to flash out
16:18:09 <rakhmerov> we just need to research this first
16:18:14 <rakhmerov> yes
16:19:01 <rakhmerov> as far as heavy_init(), NikolayM already looked at it and it looks like it's not that easy to fix
16:19:05 <rakhmerov> unfortunately
16:19:13 <rakhmerov> so we need to think more
16:19:28 <rakhmerov> but my suggestion is to postpone it for a couple of weeks
16:19:35 <rakhmerov> unless you think it's a blocker
16:20:25 <rakhmerov> thoughts?
16:20:28 <dzimine> ok.
16:21:00 <rakhmerov> so guys, I don't actually have much else today for the agenda
16:21:01 <dzimine> w4dcoder found a concurrency bug that he’ll file about today.
16:21:08 <rakhmerov> ooh, really?
16:21:17 <rakhmerov> well, it can be actually...
16:21:20 <rakhmerov> ok
16:21:27 <rakhmerov> I wonder where exactly
16:21:51 <dzimine> I am quite concerned and let us get him on htis to repro and add all the logs.
16:22:02 <rakhmerov> ok
16:22:08 <rakhmerov> somewhere in engine?
16:22:54 <rakhmerov> #topic Open discussion
16:23:14 <dzimine> don’t know. Too bad the meeting time is such that Winson can’t make it. But I asked him to file once he repro it.
16:23:24 <rakhmerov> ok
16:23:34 <rakhmerov> guys, I suggest we shut down the meeting for today
16:23:39 <rakhmerov> looks like we know what to do
16:23:45 <dzimine> yes.
16:23:48 <dzimine> cheers!
16:23:57 <rakhmerov> Dmitri, I sent you an invitation to talk about result/output
16:24:01 <rakhmerov> can you make it?
16:24:01 <dzimine> ok.
16:24:05 <rakhmerov> your 10pm
16:24:29 <NikolayM> bye!
16:24:37 <dzimine> ok.
16:24:37 <rakhmerov> ok, bye
16:24:40 <rakhmerov> thank you )
16:24:46 <rakhmerov> #endmeeting