15:00:12 #startmeeting Mistral 15:00:13 Meeting started Mon May 15 15:00:12 2017 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'mistral' 15:00:23 hi all 15:00:30 Hey 15:00:34 I'm inviting to join https://nokiameetings.webex.com/nokiameetings/j.php?MTID=ma568fbd65db98eeb7b927ec96a14a018 15:00:37 :) 15:00:50 we'll wait a few more minutes if you need to install something 15:00:51 ah 15:01:17 try to connect pls 15:01:31 I'm not sure Linux is supported, which might be more of an issue 15:01:47 I'm just assuming it isn't... I'm using my phone 15:01:53 lol 15:01:57 good idea 15:02:39 I think I am in 15:02:42 but I can't hear anything 15:03:03 d0ugal: but do you see the screen? 15:03:16 no :) 15:03:28 I see toure! 15:04:00 We're still havent shared a screen 15:04:09 Waiting for all to join 15:05:12 d0ugal: now? 15:05:17 we're sharing it 15:05:23 rakhmerov: Yeah, I can see it - should I have sound? 15:05:33 yes ) 15:05:39 you can probably call in ) 15:05:44 from your phone 15:05:54 got it working 15:05:59 this is more confusing that bluejeans :P 15:06:26 i will continue to try... go on without me. 15:07:30 thrash: no man will be left beind! 15:07:45 oh.. I'm in. :) 15:07:47 in chrome. 15:07:50 \o/ 15:08:03 thrash: mute please 15:08:07 thrash: can you mute? 15:20:58 feel free to ask questions! :) 15:21:06 You just answered mine :) 15:21:15 I was going to ask about writing workflows. 15:22:25 :)) ok 15:23:42 what is the GUI written with? 15:26:40 they look cool :) 15:28:29 I do want to see what our workflows look like... 15:29:45 I think we probably all just want to try it out :) 15:30:10 d0ugal: +1 15:30:20 d0ugal +1 15:30:51 :)) 15:30:52 yeah 15:31:10 hrm, I should have asked - is there a backend component? or is it just front-end javascript? 15:31:11 but it's a POC, and we're going to open source it to make it more production ready 15:31:19 but I think even now it's usable for much 15:31:32 front-end javascript for now 15:31:48 rakhmerov would this tie into my work? 15:31:58 in regards to the backend 15:32:28 For tripleo to use it, for example, we would need it to be packaged up etc. - that could be quite a big job (javascript projects generally have many deps). However, if it was front-end only and we could just quickly use it without much setup it would be useful. 15:32:31 toure: I'd say this is going to serve the same general goal "Usability" but I think it's orthogola to what you're doing 15:32:54 toure: your work is needed anyway, no matter if CloudFlow is ever released and used by someone 15:33:05 ack 15:33:48 d0ugal: yes, right 15:34:34 rakhmerov: I think I need to use it a bit to see how useful it is. 15:35:01 I really believe that we now need to make it a little more usable for large workflows (filters, some topological sorting) and it can be really used in your work 15:35:07 rbrady_: yes 15:35:21 we'll try to make it available sooner 15:35:31 rakhmerov: I think it's probably a good start, but possibly starting to develop it in an open source way might help bring/refine additional requirements 15:35:53 yes 15:36:41 the thing is that what you saw today was made during a very short period of time (1.5-2 months). Once Guy started working on it (before him it was a different Guy :) ) he made a good progress 15:36:50 rakhmerov: I joined late so I might have missed this - is the intent to keep it standalone or incorporate it into horizon via plugin? 15:37:09 so I believe in a month those things that are not 100% ready now can be fixed 15:37:13 rakhmerov: standalone I think 15:37:29 rbrady_: ^ 15:37:31 yes, I think it's not going to fit into Horizon 15:37:53 It needs to work without Horizon/Keystone too. 15:38:06 we'll probably place it at github, not in OpenStack community 15:38:11 yes 15:38:29 and it doesn't have to be installed along with Horizon 15:38:40 for some who don't want to deal with Horizon 15:38:52 this is going to be much lighter 15:38:55 We would really need keystone auth :) 15:39:04 sure, understandable 15:39:17 we'll have to implement it 15:39:55 so, most of the meeting was about CloudFlow, would you like to discuss anything else? 15:40:11 I thought the demo would take about 1 hour so we have some extra time 15:40:30 rbrady_, thrash: maybe you could share what happened at the summit? 15:40:52 how your sessions went, what interesting you saw etc ) 15:41:20 I'm also wondering about project onboarding session 15:41:55 rakhmerov: project update talk had maybe 10 - 15 people in it. I had a couple of questions from TripleO project with respect to rolling upgrades and a question from an engineer at CERN about a specific use case 15:42:15 ooh, ok 15:42:29 I think I know this engineer from CERN ) 15:42:29 rakhmerov: the project onboarding started with 3 people, one left when he found out we were not discussing containers and kubernetes 15:42:40 :)) haha 15:43:00 but even 2 is ok ) 15:43:12 despite the extremely low turnout at the onboarding, I think we had a great conversation with bobh (nokia) 15:43:25 yeah? 15:43:34 any details that you can share? 15:43:47 rbrady_: Definitely the best 1.5 hours at the summit 15:43:59 woow, interesting 15:44:16 once in a while we communicate with him but I don't know much about what he's doing 15:44:29 he reports problems sometimes and I try to help him 15:44:36 we discussed a little bit about the internals of mistral, deployment strategies and performance, jinja vs yaql (performance and lack of docs) 15:44:48 yep 15:44:56 cool 15:45:31 we also discussed different places where the docs could be improved, examples needed and possible features 15:45:58 I think bobh filed a couple of bugs while we were in the session too :) 15:45:59 ooh yeah 15:46:01 I'll have a couple of patchsets ready this week 15:46:04 +2000 15:46:30 bobh: ooh, I just realized you're here ) 15:46:31 hi 15:46:41 I was interested to hear that he had the same usage of messaging and error handling in a workflow, even though we both use a different backend for the message transport 15:46:52 rakhmerov: hello 15:47:41 rbrady_: what messaging do you mean? Mistral transport itself or something that you use as part of your worklflows? 15:47:47 rakhmerov: I'm almost ready to push a change to the AdHoc Actions to allow access to the env() in YAQL/Jinja expressions 15:48:11 rakhmerov: I'd appreciate any feedback - not sure if its the right way to implement or not 15:48:13 ok 15:48:23 rakhmerov: we both have a send_message task, tripleo uses zaqar actions, bobh uses redis 15:48:37 np, please push them, we'll review and think how to make it the right way 15:48:49 rbrady_: ooh, got it 15:48:52 yes 15:48:56 rakhmerov: I also talked to many people at the summit randomly, in between sessions, at lunch, etc and asked them if they had ever heard of or used mistral. most people did not 15:49:18 on Mistral messaging, there are also options, I'm going to write a big section in the docs about it 15:49:56 I have a redis custom action that I can push into mistra-extra if there is any interest 15:51:07 rbrady_: it's ok, it's normal. I can say that the number of those who know about it is still pretty big. I attended a session in Atlanta in Feb with people from all kind of teams (Nova, Heat, Magnum etc.) 15:51:20 there were 50 people of so of core contributors 15:51:37 and all of them knew Mistral and lots of them used it 15:52:19 bobh: yes, we are interested. The whole thing is that we're now reworking our actions significantly 15:52:48 part of it is that we're moving OpenStack and other actions to a separate repo, mistral-extra 15:52:52 rakhmerov: I felt it confirmed the goal in the readme about improving the docs and helping people with ideas of how to use mistral 15:52:56 with some refactoring 15:53:13 rakhmerov: ok, will do 15:53:21 I guess that redis action could go there two. We also have other candidates for it, like Ansible etc. 15:53:44 That would be cool 15:53:56 rbrady_: absolutely, that's why I keep emphasizing: we're now doing the best job on docs yet 15:54:00 sorry...took longer than I expected and then the meeting popped up 15:54:11 rakhmerov: I think setuptools supports optional requirements, so that if you don't want redis installed you can still install the package 15:54:47 ok 15:55:44 bobh: so please join our discussions if you can/want, it's usually fun and will help you stay tuned ) 15:56:06 rakhmerov: will do - I added it to my reminders :-) 15:56:20 ok, great, thank you 15:56:42 ok, guys, time to end the meeting? 15:56:53 3 mins left 15:57:00 nothing more from me :) 15:57:09 if there's nothing else let's wrap up 15:57:22 thanks for coming, see you in a week as usually 15:57:37 we'll share updates etc. as we usually do 15:57:39 see you next week :) 15:57:43 thanks see ya later 15:57:49 yeah, have a great week 15:57:54 #endmeeting