| *** chlong has quit IRC | 00:05 | |
| *** ge has quit IRC | 00:47 | |
| *** toddjohn_ has joined #openstack-mistral | 00:55 | |
| *** bobh has quit IRC | 00:57 | |
| *** rena9067 has joined #openstack-mistral | 01:03 | |
| *** gyee has quit IRC | 01:03 | |
| *** rena9067 has quit IRC | 01:09 | |
| *** bobh has joined #openstack-mistral | 01:15 | |
| *** chlong has joined #openstack-mistral | 01:30 | |
| *** toddjohn_ has quit IRC | 01:31 | |
| *** rena9067 has joined #openstack-mistral | 02:03 | |
| *** tonytan4ever has quit IRC | 02:09 | |
| *** rena9067 has quit IRC | 02:11 | |
| *** ge has joined #openstack-mistral | 02:12 | |
| ge | Hi, one quick question.. | 02:12 |
|---|---|---|
| ge | i added an Ad-hoc action for send_email (following instructions on the DSL v2 manual) | 02:13 |
| ge | when i use it in my workflow, i get an error that says "STARTTLS extension not supported by server." | 02:13 |
| ge | on SO, i see people recommending removing the smtp.ehlo() call preceding smtp.starttls() http://stackoverflow.com/questions/6355456/starttls-extension-not-supported-by-server | 02:15 |
| ge | does this https://github.com/openstack/mistral/blob/master/mistral/actions/std_actions.py need fixing | 02:15 |
| ge | or did i miss something here in my test here | 02:15 |
| *** bobh has quit IRC | 02:50 | |
| ge | and, one more: when i click on an available "Action" so i can see the code behind it, i get a response like this: Error: Unable to get action "429a27ea-f15e-457c-a08a-fe0d1dde8af1". | 02:52 |
| ge | (while clicking on an "workflow" displays the code) | 02:53 |
| *** bobh has joined #openstack-mistral | 02:54 | |
| *** bobh has quit IRC | 03:04 | |
| *** rena9067 has joined #openstack-mistral | 04:01 | |
| *** rena9067 has quit IRC | 04:08 | |
| rakhmerov | ge, evgenyl: I'm aware of installations with ~30 nodes | 04:38 |
| rakhmerov | ge: as far as customers, there are several that I'm aware of | 04:38 |
| rakhmerov | ge: on std.email, I'm actually now aware of this problem, it may really exist. You can either file a bug or just fix it, test it, and send us a patch | 04:40 |
| rakhmerov | as far as action code, I'm not sure what you mean | 04:41 |
| rakhmerov | what do you mean by code? | 04:41 |
| rakhmerov | please give a list of steps to reproduce it | 04:41 |
| ge | rakhmerov: thanks for the answers | 04:48 |
| rakhmerov | ge: so what about code? | 04:48 |
| rakhmerov | can you explain it? | 04:48 |
| ge | as for "actions"...from the left pane, where we click to navigate to different screens for workbooks, workflows, tasks, executions | 04:48 |
| rakhmerov | ooh, you mean it happens in dashboard? | 04:49 |
| ge | when i am on the "actions" screen, when i click on a particular "action" (say my ad-hoc action called "send_mail"...) i end up with this Error i posted above | 04:49 |
| rakhmerov | ok, got it | 04:49 |
| ge | when clicking on any other action, be it mistral.tasks_list or std.ssh, i get the same error | 04:50 |
| rakhmerov | I see | 04:50 |
| ge | (there is nothing in the logs..i see the GET requests coming in and no exceptions otehrwise) | 04:50 |
| ge | ok... | 04:50 |
| rakhmerov | yeah, Mistral Dashboard is actually still under heavy development | 04:50 |
| rakhmerov | ok, we'll fix it. We're about to get a UI engineer for significant time specifically to eliminate this kind of issues | 04:51 |
| rakhmerov | stay tuned | 04:51 |
| ge | ok thanks, that will be great | 04:51 |
| ge | btw the ~30 nodes deployment you mentioned is all production/ live environment that customers use...? | 04:51 |
| ge | i spent quite a bit of time going over several other alternatives before zero-ing in on mistral | 04:52 |
| ge | (particularly liked the design of things here...with the DSL/ yaml, yaql etc) | 04:53 |
| ge | i do know some python, so will look to contribute (i haven't gone the devstack way yet...but will look into it) | 04:53 |
| ge | will you have little time for couple of more questions..(not much, just quick ones) | 04:54 |
| ge | i am trying to see how i can have stdout/ stderr captured/ published for a task... | 04:55 |
| ge | publish: stdout = <% $.task(task_nm).result.stdout %> <<<<<< will this get me the task_nm's stdout | 04:56 |
| rakhmerov | ge: if you join our team that would be great, we're looking for more contributors | 05:02 |
| rakhmerov | yes, it's all live customer environments | 05:02 |
| rakhmerov | on your last question | 05:03 |
| rakhmerov | 1. Slightly invalid syntax, you can't use it as "stdout =", it should be hierarchical | 05:04 |
| rakhmerov | publish: | 05:04 |
| rakhmerov | stdout: <% %> | 05:04 |
| rakhmerov | as far as stdout, it depends on what you task "task_nm" returns | 05:05 |
| rakhmerov | remember that task is associated with either an action or another workflow | 05:05 |
| rakhmerov | both can be treated as a regular function with parameters and return value | 05:05 |
| rakhmerov | so let's say if corresponding action returns a JSON like {"stdout": "my stdout goes here"} then yes, it will work | 05:06 |
| rakhmerov | but there's no ant magic built-in stdout and stderror by default | 05:06 |
| ge | oh ok... yes i was imagining some default stdout/stderr attached to capture these on cmds | 05:08 |
| ge | normally, say for the std.ssh action, how can i capture stdout/stderr | 05:08 |
| rakhmerov | yes, I know | 05:10 |
| rakhmerov | we actually thought about it but it's not done yet | 05:10 |
| rakhmerov | I don't mean that what you're saying is wrong, it's just how it's implemented now | 05:10 |
| rakhmerov | providing stdout/stderror is a good idea | 05:10 |
| ge | ok...but it can be supported at some point later basically (the current approach will not restrict enabling these things later...) | 05:11 |
| rakhmerov | it's not that hard to implement it btw | 05:11 |
| rakhmerov | yes, I agree with you | 05:11 |
| rakhmerov | no restrictions | 05:11 |
| rakhmerov | we just need more hands to implement all that stuff | 05:12 |
| ge | ok...so until then we can provide a wrapper action ourselves to the std.ssh etc? | 05:12 |
| rakhmerov | so you're very welcome to contribute, we'll help you get up to speed | 05:12 |
| rakhmerov | ge: yes, that's what's available now | 05:12 |
| ge | ok sure i am in some sense eager to contribute (mistral is one of the things i am involved in...so need to see whats the best way to go about it..) | 05:13 |
| ge | things like calendar, which can in theory be supported by writing some custom logic etc | 05:13 |
| ge | also will be interested in putting in some role based access control so the operations and the admins can stay separate etc | 05:14 |
| ge | the dry-run that some one mentioned is useful in a way ( i had a similar idea, but not exactly puppet style noop... | 05:15 |
| ge | but more like a new step in on-boarding a new workflow/ task, so whatever people submit gets first eye-balled by another person/ approved before it is effective) | 05:15 |
| ge | dry-run sounds good but even for a little complex workflow (with status checking and conditional branching and things..with tasks dependencies and results being queried) its difficult to see how things can proceed | 05:17 |
| ge | think the hardwork (design..) is already done, so rest all are just patching up on top | 05:18 |
| ge | should be easy in some sense, lets see | 05:18 |
| rakhmerov | yes | 05:19 |
| rakhmerov | agree on dry-run | 05:19 |
| rakhmerov | btw, we already have BPs for both dry-run and RBAC | 05:19 |
| ge | oh ok great then | 05:20 |
| ge | normally we don't have to wait for the next release (newton/ october..) in theory right...we can just pull in stuff anytime and apply to prod here if we think something is good enough for us etc | 05:21 |
| ge | (thanks, will check the RBAC blueprint..) | 05:21 |
| rakhmerov | sure | 05:22 |
| rakhmerov | some people do exactly that | 05:22 |
| ge | ok great | 05:22 |
| ge | for this std_actions.py ehlo/starttls), if i just want to live patch this (simply edit the mistral files i already deployed and restart the mistral-server, i should pick up the changes...?) | 05:23 |
| ge | as opposed to changing the code and redeploying... | 05:23 |
| ge | (i mean just clearing the .pyc/ .pyo files from the install location will pick up any changes to .py ?) | 05:24 |
| ge | mine is installed under: /usr/lib/python2.7/site-packages/mistral | 05:25 |
| ge | so to quickly check (in my local dev environment), i just edit the .py here and test it (after clearing .pyc/.pyo...) | 05:25 |
| ge | will that do...or will i be messing up my env by doing that | 05:26 |
| ge | btw for task rerun and resuming of the workflow, i should say: | 06:37 |
| ge | >> mistral task-rerun <the-failed-task-id> --resume | 06:37 |
| ge | is that right...? | 06:37 |
| *** ge has quit IRC | 06:54 | |
| *** toddjohn_ has joined #openstack-mistral | 06:55 | |
| *** toddjohn_ has quit IRC | 06:59 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: Fixing engine facade hierarchy https://review.openstack.org/313257 | 07:30 |
| *** chlong has quit IRC | 07:54 | |
| *** dmk0202 has joined #openstack-mistral | 08:08 | |
| *** shardy has joined #openstack-mistral | 08:28 | |
| rakhmerov | ge: yes | 08:35 |
| *** nmakhotkin has joined #openstack-mistral | 08:41 | |
| *** ge has joined #openstack-mistral | 08:44 | |
| openstackgerrit | hardik proposed openstack/mistral: Fixing engine facade hierarchy https://review.openstack.org/313257 | 09:55 |
| *** penchal has joined #openstack-mistral | 10:32 | |
| *** hparekh has quit IRC | 10:50 | |
| *** dmk0202 has quit IRC | 10:57 | |
| *** dmk0202 has joined #openstack-mistral | 10:57 | |
| *** jtomasek has quit IRC | 10:59 | |
| *** hparekh has joined #openstack-mistral | 11:03 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: Refactoring exception hierarchy https://review.openstack.org/313509 | 11:22 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: Refactoring exception hierarchy https://review.openstack.org/313509 | 11:35 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: Refactoring exception hierarchy https://review.openstack.org/313509 | 11:42 |
| *** bobh has joined #openstack-mistral | 11:49 | |
| *** bobh has quit IRC | 11:49 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: Refactoring exception hierarchy https://review.openstack.org/313509 | 11:55 |
| *** bobh has joined #openstack-mistral | 12:07 | |
| *** dprince has joined #openstack-mistral | 12:11 | |
| *** bobh has quit IRC | 12:13 | |
| *** toddjohn_ has joined #openstack-mistral | 12:18 | |
| *** toddjohn_ has quit IRC | 12:32 | |
| *** ninag has joined #openstack-mistral | 12:39 | |
| *** toddjohn_ has joined #openstack-mistral | 12:50 | |
| *** alejandrito has joined #openstack-mistral | 12:52 | |
| *** bobh has joined #openstack-mistral | 13:15 | |
| *** bobh has quit IRC | 13:15 | |
| *** bobh has joined #openstack-mistral | 13:15 | |
| *** tonytan4ever has joined #openstack-mistral | 13:28 | |
| *** penchal has quit IRC | 13:33 | |
| *** toddjohn_ has quit IRC | 13:50 | |
| *** alejandrito has quit IRC | 14:05 | |
| *** catintheroof has joined #openstack-mistral | 14:05 | |
| *** toddjohn_ has joined #openstack-mistral | 14:07 | |
| *** catintheroof has quit IRC | 14:15 | |
| *** catintheroof has joined #openstack-mistral | 14:27 | |
| *** dprince has quit IRC | 14:37 | |
| *** rena9067 has joined #openstack-mistral | 14:54 | |
| *** rena9067_ has joined #openstack-mistral | 14:56 | |
| *** rena9067 has quit IRC | 14:59 | |
| *** rbrady has quit IRC | 15:11 | |
| *** rbrady has joined #openstack-mistral | 15:24 | |
| *** toddjohn_ has quit IRC | 15:26 | |
| *** dmk0202 has quit IRC | 15:33 | |
| *** dmk0202 has joined #openstack-mistral | 15:34 | |
| *** catintheroof has quit IRC | 15:36 | |
| *** dmk0202 has quit IRC | 15:39 | |
| *** toddjohn_ has joined #openstack-mistral | 15:40 | |
| *** rena9067_ has quit IRC | 15:53 | |
| *** rena9067 has joined #openstack-mistral | 15:54 | |
| *** ruhe has quit IRC | 16:24 | |
| *** dprince has joined #openstack-mistral | 16:25 | |
| *** catintheroof has joined #openstack-mistral | 16:27 | |
| *** ruhe has joined #openstack-mistral | 16:31 | |
| *** dmk0202 has joined #openstack-mistral | 16:40 | |
| *** gyee has joined #openstack-mistral | 16:52 | |
| *** toddjohn_ has quit IRC | 16:53 | |
| *** dmk0202 has quit IRC | 16:55 | |
| *** dmk0202 has joined #openstack-mistral | 16:57 | |
| *** dmk0202 has quit IRC | 17:01 | |
| *** shardy has quit IRC | 17:02 | |
| openstackgerrit | Todd Johnson proposed openstack/mistral-specs: Add support for mistral notification event triggers https://review.openstack.org/308664 | 17:09 |
| *** toddjohn_ has joined #openstack-mistral | 17:13 | |
| *** jtomasek has joined #openstack-mistral | 17:21 | |
| *** rena9067 has quit IRC | 17:57 | |
| *** rena9067 has joined #openstack-mistral | 18:18 | |
| *** tonytan4ever has quit IRC | 18:22 | |
| *** toddjohn_ has quit IRC | 18:32 | |
| *** catintheroof has quit IRC | 18:41 | |
| *** toddjohn_ has joined #openstack-mistral | 18:45 | |
| *** tonytan4ever has joined #openstack-mistral | 19:07 | |
| *** toddjohn_ has quit IRC | 19:12 | |
| *** toddjohn_ has joined #openstack-mistral | 19:24 | |
| *** ninag has quit IRC | 19:47 | |
| *** dprince has quit IRC | 19:59 | |
| *** toddjohn_ has quit IRC | 20:04 | |
| *** dmk0202 has joined #openstack-mistral | 20:05 | |
| *** openstackgerrit has quit IRC | 20:32 | |
| *** openstackgerrit has joined #openstack-mistral | 20:33 | |
| *** ge has quit IRC | 20:49 | |
| *** dmk0202 has quit IRC | 20:58 | |
| *** bobh has quit IRC | 22:04 | |
| *** tonytan4ever has quit IRC | 22:24 | |
| *** rbrady_ has joined #openstack-mistral | 22:37 | |
| *** rbrady has quit IRC | 22:37 | |
| *** rena9067 has quit IRC | 23:18 | |
| *** rena9067 has joined #openstack-mistral | 23:21 | |
| *** rena9067 has quit IRC | 23:32 | |
| *** gyee has quit IRC | 23:53 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!