16:00:43 <rakhmerov> #startmeeting Mistral
16:00:43 <openstack> Meeting started Mon Jan 11 16:00:43 2016 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:46 <openstack> The meeting name has been set to 'mistral'
16:00:53 <NikolayM> hi!
16:01:07 <LimorStotland> Hi
16:01:07 <rakhmerov> hi )
16:01:11 <dzimine> Hi all
16:01:18 <rakhmerov> hi!
16:01:25 <ninag> hi
16:01:44 <hparekh_> hi
16:01:53 <dprince> hello
16:02:17 <rakhmerov> hi
16:02:22 <rakhmerov> ok, let's start
16:03:03 <rakhmerov> since we haven't had meetings for a long time due to NY holidays let's skip "Review Action Items" topic
16:04:00 <rakhmerov> so let's quickly sync up on our status
16:04:06 <rakhmerov> #topic Current status (progress, issues, roadblocks, further plans)
16:05:16 <rakhmerov> my status: haven't done much, reviewed several patches today and was trying to understand why a dead-lock can happen as Winson reported
16:05:40 <hparekh_> Completed Mistral support in kolla, Mistral docker image, Submitted patches for mistral-tempest-plugin, Solved some issue due to tempest code change.
16:05:56 <rakhmerov> planning to work on a bug assigned to me with wrong WF state
16:06:20 <NikolayM> my status: catching up reviewing missing patches, reviewing a lot. It seems our unit tests are failing quite often
16:06:50 <NikolayM> tried to merge fixes for devstack today but tests are failing again and again
16:07:05 <rakhmerov> yes
16:07:33 <rakhmerov> has anybody tried to investigate why it's failing?
16:08:29 <rakhmerov> NikolayM: is it always the same resume tests that fails?
16:08:38 <NikolayM> no
16:08:39 <rakhmerov> or we have different tests failing?
16:09:06 <NikolayM> I saw not only resume tests - also test on workbook_create
16:09:43 <dzimine> For Winson: hunting deadlocks that pop up in our prod mistral deployment, blocked on review on Reatart workflow BP implementation
16:09:52 <rakhmerov> hm.. ok
16:09:56 <NikolayM> it tries to get associated triggers for wf and don't find that wf
16:10:58 <rakhmerov> dzimine: I reviewed the first and most and most important patch for env update for resume, looks good to me, just a couple of minor things from Lingxian
16:11:14 <hparekh_> Further Planning to work on https://blueprints.launchpad.net/mistral/+spec/mistral-items-filtering rakhmerov Can you please assigned this to me? so I can start  work on spec
16:11:27 <rakhmerov> ok
16:11:52 <dzimine> I began to look at Making YAQL extensions pluggable but won't have time to work on it till next week.
16:12:10 <rakhmerov> dzimine: ok, that would be a nice thing to have
16:12:16 <rakhmerov> not only nice, very useful
16:12:24 <ninag> dmowrer could not make the meeting. He is working on bp: https://blueprints.launchpad.net/mistral/+spec/mistral-mistral-actions. Can you assign to him?
16:12:38 <rakhmerov> hparekh_: as far as that BP, do you need it yourself?
16:12:40 <NikolayM> dzimine: do you mean pluggable YAQL functions?
16:12:48 <rakhmerov> I mean this kind of functionality
16:12:55 <ninag> Also, does that need a spec or can he directly start contributing code?
16:13:04 <hparekh_> rakhmerov, no
16:13:07 <rakhmerov> I'm asking because I would hold it for now
16:13:20 <rakhmerov> because we have a bigger task: API v3
16:13:27 <rakhmerov> and that BP could be a part of it
16:14:23 <rakhmerov> ninag: IMO, it doesn't require a spec because it is functionally 100% clear
16:14:34 <ninag> sounds good, thanks
16:14:55 <rakhmerov> however, if you think it will have some pitfalls you can create a spec too
16:15:16 <rakhmerov> but at the first glance it's not needed
16:15:20 <ninag> seems straighforward right now..if we hit anything will look at a spec
16:15:32 <rakhmerov> yeah
16:15:41 <dprince> rakhmerov: ++ for not requiring specs if things are very clear cut
16:15:58 <rakhmerov> actually, I remember that NikolayM already tried to do that but stumbled upon something
16:16:02 <rakhmerov> he can tell better
16:16:10 <NikolayM> yep
16:16:38 <NikolayM> I can't do request to mistral from mistral
16:16:40 <dzimine> @NikolayM: use stevedore to add custom YAQL functions on the fly
16:16:53 <rakhmerov> dprince: yes, if the functionality can be trivially understood and the patch implementing it is straightforward I would not require a spec
16:17:04 <dzimine> There is a BP somewhere I'll look up
16:17:15 <NikolayM> if do it synchronously
16:17:37 <rakhmerov> hparekh_: as far as that BP, can we talk in IRC tomorrow about it?
16:18:06 <hparekh_> rakhmerov ok sounds good
16:18:19 <ninag> NikolayM: dmowrer is aware of it, anyways, will ask him to get with you on irc if needed
16:18:52 <dzimine> I'll do a spec if needed once prototype is ready
16:19:24 <rakhmerov> #action rakhmerov, hparekh_: discuss https://blueprints.launchpad.net/mistral/+spec/mistral-items-filtering
16:19:46 <NikolayM> ninag: sure. anyway, it works fine if do async (or from workflow)
16:19:54 <rakhmerov> ninag: just curious, is this BP needed for your work?
16:20:11 <ninag> rakhmerov: yes
16:20:20 <rakhmerov> interesting
16:20:36 <rakhmerov> ok
16:20:53 <rakhmerov> LimorStotland: Limor, anything from ALU side today?
16:20:59 <LimorStotland> i am
16:21:21 <LimorStotland> gal and liat working on the UI
16:21:36 <rakhmerov> yep
16:21:37 <rakhmerov> ok
16:21:54 <LimorStotland> and the rest of us are working on internal alcatel tasks
16:22:06 <rakhmerov> ok
16:22:34 <LimorStotland> i know that liat finished with the action pagination and gal working on the cron trigger screen
16:22:44 <rakhmerov> I'm just wondering if you guys have other critical bugs in Mistral that block your work
16:23:04 <rakhmerov> yeah, I saw patches but didn't review them yet
16:23:19 <rakhmerov> ok
16:23:24 <rakhmerov> #topic Open Discussion
16:23:33 <ninag> I have one item
16:23:39 <rakhmerov> sure
16:23:51 <ninag> we thought it would be good to get Mistral workflows published in the OpenStack Application Catalog, so talked with docaedo the App Catalog ptl
16:24:04 <ninag> He thought it was a good idea..
16:24:14 <rakhmerov> we just came back from our long holidays here so don't have probably much to discuss, my goal was mostly to catch up on the current activities
16:24:18 <ninag> It will be an agenda item in this week’s App Catalog meeting ( Jan 14th, 2016 1700 UTC)
16:24:43 <ninag> So a heads up if anyone is interested as well
16:24:58 <rakhmerov> ninag: yes, I actually already discussed that with Kirill
16:25:04 <ninag> Cool
16:25:09 <rakhmerov> I think it is a good idea
16:25:26 <dprince> rakhmerov: when there is time I have one item to bring up from TripleO
16:25:48 <rakhmerov> the only thing is: WFs getting into App Catalog should be really well-written and designed
16:25:59 <rakhmerov> I mean quality and applicability
16:26:09 <rakhmerov> dprince: sure
16:26:17 <ninag> rakhmerov: +1
16:26:44 <rakhmerov> ninag: preliminarily, I can attend that meeting
16:26:53 <rakhmerov> will now put it on my cal
16:27:38 <ninag> ok, thx
16:28:07 <rakhmerov> dprince: you can go ahead and tell about your item
16:28:39 <dprince> rakhmerov: ack, thanks
16:29:25 <dprince> I've been tinkering w/ Mistral as a workflow tool for TripleO
16:29:46 <dprince> thus some of my patches for actions around Ironic, inspector, and just recently swift too
16:29:53 <dprince> thanks for all of the reviews on those things
16:30:25 <dprince> Today I started a [TripleO] thread on "what if" we were to use Mistral instead of another idea around building our own API (called TripleO API)
16:30:27 <rakhmerov> ok
16:30:45 <dprince> if any Mistral devs have feedback into my thoughts I would love to have them
16:30:46 <rakhmerov> actually I apologize for not reviewing actively in the last month or so
16:31:13 <dprince> upstream thread is called [TripleO] Driving workflows with Mistral
16:31:15 <rakhmerov> ok
16:31:48 <rakhmerov> ok, I'll participate
16:32:02 <rakhmerov> #action rakhmerov: participate in [TripleO] Driving workflows with Mistral
16:32:08 <dprince> There is still some debate... some from the TripleO team prefer to build our own API I think. But I think Mistral as a workflow tool looks to have a lot of merit
16:32:35 <rakhmerov> ok, interesting
16:32:44 <dprince> we can now use Mistral as part of our "undercloud". So \o/
16:33:01 <rakhmerov> I personally don't know much about TripleO though, only general idea. But I'll try to digg into that
16:33:09 <dprince> And from a Red Hat angle... the packages are in RDO trunk repositories
16:33:10 <rakhmerov> ok
16:33:46 <dprince> I based those off or a Bugzilla from Mirantis so I think they should be good for all
16:34:10 <dprince> anyways, that is all. Just wanted to introduce some of these ideas when I have been tinkering with since before the break
16:34:13 <dprince> thanks :)
16:34:13 <rakhmerov> dprince: do you now see what's missing in Mistral except what you've been working on? I mean different kinds of actions
16:34:16 <rakhmerov> OpenStack APIs
16:34:40 <dprince> rakhmerov: well, I did try a few things that didn't work
16:34:48 <rakhmerov> really?
16:34:53 <dprince> rakhmerov: "reverse" workflow didn't quite work for me
16:34:58 <rakhmerov> could you share please?
16:35:03 <dprince> rakhmerov: but "direct" was working quite well
16:35:18 <dprince> rakhmerov: I will dig into the "reverse" workflow issue I had and try to file a bug on it this week
16:35:26 <rakhmerov> I'd very appreciate if you could share some details or report bugs
16:35:27 <dprince> rakhmerov: could have totally been user error on my part
16:35:37 <rakhmerov> yes, thanks a lot
16:36:03 <rakhmerov> well, speaking honestly, reverse WF is tested much much worse
16:36:13 <dprince> rakhmerov: in general I think Mistral works quite well for some things
16:36:15 <rakhmerov> even though it is much simpler in implementation
16:36:22 <rakhmerov> ok
16:36:28 <dprince> one question I had today was how many people write their own actions
16:36:46 <rakhmerov> dzimine can tell you much about it :)
16:36:51 <dprince> I like the idea of "pure" OpenSTack workflows that just use core OpenStack actions
16:36:55 <rakhmerov> they write thousands actions
16:37:05 <dprince> but for TripleO I think we would also require some custom actions (I mention these in my thread)
16:37:09 <dprince> good to know
16:37:28 <rakhmerov> yeah, you can look at StackStorm github
16:37:43 <dprince> rakhmerov: ack, thanks. I will look for the actions there
16:37:57 <rakhmerov> ok
16:38:29 * dprince keeps quiet now
16:38:33 <rakhmerov> alright
16:38:34 <dprince> thanks for letting me give updates
16:38:47 <rakhmerov> no problem, you're very welcome
16:38:52 <rakhmerov> always :)
16:39:32 <rakhmerov> guys, I actually don't have anything from my side
16:39:56 <rakhmerov> Like I said my personal goal was just to sync up with the team on the current activities
16:40:00 <rakhmerov> this is done
16:40:31 <rakhmerov> tomorrow, I'm planning to review as many patches as possible since we already have a long queue (relatively long)
16:40:45 <rakhmerov> and evaluate our progress on M-2
16:40:49 <dzimine> Thanks rakhmerov for doing a pitch for StackStorm. It's Apache 2.0 and adds triggers and actions to Mistral, with integration of everything mostly ready on community
16:41:05 <rakhmerov> yep
16:41:08 <dzimine> Check out github/st2contrib
16:41:49 <rakhmerov> ok, is there anything else you'd like to discuss?
16:42:28 <rakhmerov> sadly, we don't have a number of folks today for different reasons. Hopefully, next time we'll gather the entire team
16:42:29 <rakhmerov> :)
16:42:53 <rakhmerov> ok, counting to 10 and shutting down the meeting
16:42:54 <rakhmerov> 1
16:42:56 <rakhmerov> 2
16:42:57 <rakhmerov> 3
16:42:58 <rakhmerov> 4
16:42:59 <rakhmerov> 5
16:43:01 <rakhmerov> 6
16:43:03 <rakhmerov> 7
16:43:05 <rakhmerov> 8
16:43:07 <rakhmerov> 9
16:43:09 <rakhmerov> 10
16:43:11 <rakhmerov> ok, bye guys!
16:43:16 <rakhmerov> thanks for joining!
16:43:24 <ninag> thanks, bye
16:43:44 <rakhmerov> all: feel free to reach out to us in IRC
16:43:49 <rakhmerov> openstack-mistral
16:44:02 <rakhmerov> there's someone in there nearly all the time
16:44:09 <NikolayM> bye!
16:44:12 <rakhmerov> #endmeeting