| *** gyee has quit IRC | 00:10 | |
| *** toddjohn has quit IRC | 00:14 | |
| *** d0ugal has joined #openstack-mistral | 00:20 | |
| *** bobh has quit IRC | 00:25 | |
| *** rena9067_ has quit IRC | 00:27 | |
| *** bobh has joined #openstack-mistral | 00:38 | |
| *** vishwanathj has quit IRC | 00:50 | |
| *** Qiming has joined #openstack-mistral | 00:52 | |
| *** rbrady has quit IRC | 00:55 | |
| *** cheneydc has joined #openstack-mistral | 00:59 | |
| *** rena9067 has joined #openstack-mistral | 01:08 | |
| *** toddjohn has joined #openstack-mistral | 01:08 | |
| *** rena9067_ has joined #openstack-mistral | 01:09 | |
| *** rena9067 has quit IRC | 01:12 | |
| *** toddjohn has quit IRC | 01:22 | |
| *** toddjohn has joined #openstack-mistral | 01:22 | |
| *** toddjohn has quit IRC | 01:28 | |
| *** bobh has quit IRC | 01:59 | |
| *** Qiming has quit IRC | 02:18 | |
| *** Qiming has joined #openstack-mistral | 02:19 | |
| *** toddjohn has joined #openstack-mistral | 02:24 | |
| *** toddjohn has quit IRC | 02:29 | |
| *** Qiming has quit IRC | 02:30 | |
| *** bobh has joined #openstack-mistral | 02:41 | |
| *** Qiming has joined #openstack-mistral | 02:46 | |
| *** bobh has quit IRC | 02:55 | |
| *** Qiming has quit IRC | 02:56 | |
| *** Qiming has joined #openstack-mistral | 03:07 | |
| *** toddjohn has joined #openstack-mistral | 03:26 | |
| *** toddjohn has quit IRC | 03:32 | |
| *** rena9067_ has quit IRC | 04:39 | |
| rakhmerov | kong: hi Lingxian | 04:43 |
|---|---|---|
| rakhmerov | kong: can you please look at https://review.openstack.org/#/c/319861/ ? It's a backport of your patch to stable/mitaka | 04:43 |
| rakhmerov | docs gate is failing for some reason | 04:43 |
| rakhmerov | maybe you still need to do some tweaks in tox.ini | 04:44 |
| openstackgerrit | Merged openstack/mistral: Updated from global requirements https://review.openstack.org/319884 | 04:58 |
| openstackgerrit | Merged openstack/mistral: Remove unnecessary executable permissions https://review.openstack.org/320006 | 05:08 |
| *** toddjohn has joined #openstack-mistral | 05:29 | |
| *** toddjohn has quit IRC | 05:34 | |
| *** lkannan has quit IRC | 06:14 | |
| *** evgenyl has quit IRC | 06:15 | |
| *** lkannan has joined #openstack-mistral | 06:15 | |
| *** zhenguo_ has quit IRC | 06:16 | |
| *** evgenyl has joined #openstack-mistral | 06:18 | |
| *** doriftoshoes has quit IRC | 06:18 | |
| *** zhenguo_ has joined #openstack-mistral | 06:18 | |
| *** doriftoshoes has joined #openstack-mistral | 06:20 | |
| *** harlowja has quit IRC | 06:28 | |
| *** rwsu has quit IRC | 06:30 | |
| *** jtomasek has quit IRC | 07:10 | |
| *** Ravikiran_K has joined #openstack-mistral | 07:25 | |
| *** shardy has joined #openstack-mistral | 08:12 | |
| *** dmk0202 has joined #openstack-mistral | 08:16 | |
| *** venkat has joined #openstack-mistral | 08:23 | |
| *** _mgershen is now known as mgershen | 08:24 | |
| *** ig0r_ has joined #openstack-mistral | 08:40 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 08:41 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 08:42 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 08:46 |
| d0ugal | Does Mistral support Python 3? | 08:51 |
| d0ugal | It looks like it does based on the tests. | 08:52 |
| *** ak has joined #openstack-mistral | 08:55 | |
| ak | Hi In mistral can i have looping in tasks . | 08:56 |
| ak | mistral does allow it but is this the write way to use it | 08:57 |
| mgershen | ak: did you read http://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#policies | 09:00 |
| ak | taking a look at it | 09:00 |
| ak | i though retry is only done in error cases | 09:01 |
| ak | can retry happen even when http status code is 200 ? | 09:02 |
| ak | I remember trying this | 09:02 |
| mgershen | ak: I used it to re-run failed task, but it says there you can add continue-on rule | 09:02 |
| ak | here the basic issue is mistral wont retry anything until u have http response code more than 400 | 09:04 |
| ak | will it retry for 200 too , i dont think so last time i tried it did not work | 09:05 |
| ak | retry Defines a pattern how task should be repeated in case of an error. | 09:05 |
| ak | mistral documentation ... | 09:06 |
| ak | Basically I have a task which has to be run infinitely, two ways to solve this problem keep looping or throw some know error and keep a very high retry count | 09:07 |
| mgershen | you can wrap your wf with another one and make sure the inner one fails when needed | 09:13 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 09:19 |
| mgershen | ak: ^ | 09:22 |
| ak | thats something we are doing | 09:28 |
| mgershen | ak: did you consider using cron-trigger to run a workflow4+ | 09:29 |
| mgershen | ak: sorry5 | 09:30 |
| openstackgerrit | Andras Kovi proposed openstack/mistral-specs: Execute workflows on targeted cloud https://review.openstack.org/319868 | 09:30 |
| mgershen | 66666641 | 09:31 |
| mgershen | ak: sorry, someone at work found the other half of my keyboard and played with it | 09:32 |
| mgershen | https://www.google.com/search?q=Microsoft+Sculpt+wireless+ergonomic+desktop&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjc46CBtPLMAhUMIMAKHbz1CsIQ_AUICSgD&biw=1920&bih=965#imgrc=ECw6-lwyVUcioM%3A | 09:34 |
| mgershen | ak: I have to step out for a while | 09:34 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral: Add Python 3.4 to the classifiers https://review.openstack.org/320326 | 09:38 |
| *** cheneydc has quit IRC | 10:01 | |
| ak | sure not a problem | 10:05 |
| mgershen | ak: I'm back | 10:15 |
| ak | hi | 10:15 |
| ak | do we have an api which start it and stop when ever we want ? | 10:16 |
| mgershen | ak: are you referencing cron-triggers? you can create and delete them when ever you like via API or cli | 10:17 |
| ak | ohk cool | 10:18 |
| ak | need to check it .. | 10:18 |
| openstackgerrit | Merged openstack/mistral: Add Python 3.4 to the classifiers https://review.openstack.org/320326 | 10:18 |
| ak | The problem here is i want to retry a task even though it succeded and i think mistral doest do that :( | 10:19 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 10:21 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 10:28 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 10:30 |
| mgershen | ak: I don't understand, didn't you say using nested workflows solved your problem? | 10:33 |
| ak | it did | 10:33 |
| ak | but nested have a bug in them | 10:33 |
| mgershen | ak: what bug? | 10:34 |
| ak | for example i try to publish a variable .. and try to republish again in one particular scenario it doest work. | 10:34 |
| ak | Lets consider this particular scenario | 10:35 |
| mgershen | ak: do we have a bug open on launchpad for this? | 10:35 |
| ak | T1 on-success call T2 on Failure calls T3 , T3 on success call T1 again | 10:36 |
| ak | in T1 I am trying to publish a variable X | 10:36 |
| ak | T1 task is done it was an error so it published X as null which is valid scenario | 10:37 |
| ak | now T3 will call T1 again | 10:37 |
| ak | T1 is success this time and published X as 2 | 10:38 |
| ak | now T2 is called which is correct again. But when i try to use the $.X ( it should give me 2 instead it gives me null ) | 10:39 |
| ak | @mgershen let me know if need any clarification | 10:39 |
| ak | @mgershen let me know if need any clarification | 10:40 |
| ak | thats why I was worried if mistral supports looping in tasks | 10:46 |
| mgershen | ak: please clarify the first line "T1 on-success call T2 on Failure calls T3 , T3 on success call T1 again " | 10:46 |
| mgershen | ak: mainly "T1 on-success call T2 on Failure calls T3" | 10:47 |
| ak | T1 is a task. It has on-success and on-failure | 10:47 |
| *** dmowrer has joined #openstack-mistral | 10:57 | |
| *** hparekh has quit IRC | 10:59 | |
| *** dprince has joined #openstack-mistral | 11:02 | |
| *** Qiming has quit IRC | 11:06 | |
| *** Ravikiran_K has quit IRC | 11:08 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 11:10 |
| *** hparekh has joined #openstack-mistral | 11:13 | |
| *** venkat has quit IRC | 11:15 | |
| *** ak has quit IRC | 11:20 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 11:30 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 11:30 |
| *** ig0r_ has quit IRC | 11:34 | |
| rakhmerov | ak: I think that but really exists | 11:37 |
| rakhmerov | we even had something like this filed in LP | 11:38 |
| rakhmerov | btw, one more way to loop is using "with-items" but it's inside a task, not for building loops out of tasks.. | 11:38 |
| rakhmerov | ak: there's an ambiguity in workflow semantics whenever we encounter loops and tasks not marked as "join" | 11:39 |
| rakhmerov | one of our team members is now working on a blueprint that will help eliminate those ambiguities | 11:40 |
| rakhmerov | https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-execution-graph | 11:40 |
| rakhmerov | so you can subscribe to it and track its progress | 11:40 |
| rakhmerov | I'm expecting that it will be solved in N-2 or the worst case N-3 | 11:41 |
| mgershen | rakhmerov: ak: I tried using nested workflows, but I couldn't get any info from the inner workflow when it failed. | 11:42 |
| rakhmerov | the only way is to access corresponding task in the parent workflow | 11:43 |
| rakhmerov | task(task_name).result | 11:43 |
| mgershen | does not work | 11:43 |
| rakhmerov | or task(task_name).state_info | 11:43 |
| rakhmerov | what exactly doesn't work? | 11:43 |
| rakhmerov | well, if a nested workflow failed you should rather look at state_info | 11:44 |
| rakhmerov | it should be in result as well but there's a small bug in master now, I already fixed it locally | 11:44 |
| mgershen | I wanted to retry the task containing the nested workflow, so it didn't technically failed yet. I wanted to use "break-on" with info from the nested workflow | 11:45 |
| mgershen | http://paste.openstack.org/show/498586/ | 11:46 |
| rakhmerov | hm.. | 11:49 |
| mgershen | at the end state info has this in its value: | 11:49 |
| rakhmerov | ok | 11:49 |
| mgershen | Can not evaluate YAQL expression: task(l ... A LOT OF TEXT ... error: u'loop_result' | 11:49 |
| rakhmerov | yeah, I see | 11:49 |
| rakhmerov | btw, "task(loop).loop_result" should not work | 11:50 |
| mgershen | why? | 11:50 |
| rakhmerov | because only properties of task are accessible with task(loop) | 11:50 |
| rakhmerov | loop_result is a published variable | 11:50 |
| mgershen | also an output | 11:50 |
| mgershen | sorry for the messy workflow... | 11:51 |
| rakhmerov | you can try this: task(loop).published.loop_result | 11:51 |
| rakhmerov | np | 11:51 |
| mgershen | nothing gets published | 11:52 |
| rakhmerov | ooh, yes, if it fails | 11:52 |
| rakhmerov | true | 11:52 |
| rakhmerov | ok, maybe I don't understand what you're trying to achieve here | 11:53 |
| mgershen | I couldn't think of a way to pull information from the nested workflow when it fails | 11:53 |
| rakhmerov | what kind of information? | 11:53 |
| mgershen | I wanted to use info from the failed workflow in order to decide to retry or ont | 11:53 |
| rakhmerov | you can only detect that it failed and see an error message | 11:53 |
| mgershen | /s/ont/not | 11:54 |
| rakhmerov | yes, but what info? | 11:54 |
| rakhmerov | if something failed it doesn't necessarily have any structured output or something we could rely on | 11:54 |
| mgershen | anything I can control from the nested workflow | 11:54 |
| rakhmerov | it's just ERROR state and state_info that explains what happened | 11:54 |
| mgershen | the real reason I tried this is to find a way to loop on a task | 11:55 |
| rakhmerov | well, theoretically we can have yaql functions (we discussed it before) that can peek at other workflow executions and tasks | 11:55 |
| rakhmerov | mgershen: ok, understood | 11:55 |
| rakhmerov | so that, for example, from parent wf we could see how many executions of task1 in the nested wf | 11:56 |
| rakhmerov | but those functions are still to be implemented | 11:56 |
| rakhmerov | as far as publishing issue, it's true that it exists in case of looping | 11:56 |
| *** ig0r_ has joined #openstack-mistral | 11:57 | |
| rakhmerov | I would try to avoid it till we fix it | 11:57 |
| rakhmerov | sorry, have to run. Will be back later ) | 11:58 |
| *** Qiming has joined #openstack-mistral | 11:58 | |
| mgershen | cool | 11:58 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral: WIP: engine refactoring https://review.openstack.org/317879 | 11:58 |
| mgershen | I think we should consider adding the option to publish things add save outputs even if the workflow fails. | 11:59 |
| rakhmerov | yes, needs to be discussed | 12:08 |
| *** bobh has joined #openstack-mistral | 12:09 | |
| *** rbrady has joined #openstack-mistral | 12:13 | |
| *** Qiming has quit IRC | 12:15 | |
| *** Ravikiran_K has joined #openstack-mistral | 12:16 | |
| *** Qiming has joined #openstack-mistral | 12:17 | |
| *** bobh has quit IRC | 12:28 | |
| *** dprince has quit IRC | 12:38 | |
| *** catintheroof has joined #openstack-mistral | 12:49 | |
| openstackgerrit | hardik proposed openstack/mistral: Fail/Success/Pause transition message https://review.openstack.org/276625 | 12:56 |
| *** Qiming has quit IRC | 13:01 | |
| *** toddjohn has joined #openstack-mistral | 13:11 | |
| mflobo | Question about Mistral and workflow with several tasks | 13:12 |
| mflobo | What happen if I have a workflow with 3 actions, and the second one fails? How mistral behaves with that? | 13:13 |
| *** bobh has joined #openstack-mistral | 13:16 | |
| openstackgerrit | Michal Gershenzon proposed openstack/python-mistralclient: Validate ad-hoc action via cli https://review.openstack.org/318152 | 13:47 |
| *** Qiming has joined #openstack-mistral | 14:02 | |
| *** toddjohn has quit IRC | 14:42 | |
| openstackgerrit | Daryl Mowrer proposed openstack/mistral: [WIP] Implement event-notification-trigger spec This is part 1 of 5 patch sets which implement the Mistral event-notification-trigger spec. This is a work in progress. https://review.openstack.org/320497 | 14:46 |
| openstackgerrit | Daryl Mowrer proposed openstack/mistral: [WIP] Implement event-notification-trigger spec This is part 2 of 5 patch sets which implement the Mistral event-notification-trigger spec. This is a work in progress. https://review.openstack.org/320500 | 14:52 |
| *** rena9067 has joined #openstack-mistral | 14:54 | |
| openstackgerrit | Daryl Mowrer proposed openstack/mistral: [WIP] Implement event-notification-trigger spec This is part 3 of 5 patch sets which implement the Mistral event-notification-trigger spec. This is a work in progress. https://review.openstack.org/320509 | 14:57 |
| openstackgerrit | Daryl Mowrer proposed openstack/python-mistralclient: [WIP] Implement event-notification-trigger spec This is part 4 of 5 patch sets which implement the Mistral event-notification-trigger spec. This is a work in progress. https://review.openstack.org/320510 | 15:01 |
| *** Qiming has quit IRC | 15:04 | |
| openstackgerrit | Daryl Mowrer proposed openstack/mistral: [WIP] Implement event-notification-trigger spec This is part 5 of 5 patch sets which implement the Mistral event-notification-trigger spec. This is a work in progress. https://review.openstack.org/320514 | 15:08 |
| *** tonytan4ever has joined #openstack-mistral | 15:31 | |
| *** dmk0202 has quit IRC | 15:38 | |
| *** dmk0202 has joined #openstack-mistral | 15:38 | |
| *** toddjohn has joined #openstack-mistral | 15:45 | |
| *** gyee has joined #openstack-mistral | 15:53 | |
| *** toddjohn has quit IRC | 15:57 | |
| *** rena9067_ has joined #openstack-mistral | 15:58 | |
| *** rena9067 has quit IRC | 16:01 | |
| *** toddjohn has joined #openstack-mistral | 16:02 | |
| *** dmk0202 has quit IRC | 16:24 | |
| *** ig0r_ has quit IRC | 16:24 | |
| *** catintheroof has quit IRC | 16:28 | |
| *** harlowja has joined #openstack-mistral | 16:51 | |
| *** tonytan4ever has quit IRC | 16:55 | |
| *** Ravikiran_K has quit IRC | 17:34 | |
| *** dmowrer has quit IRC | 17:46 | |
| *** dmowrer has joined #openstack-mistral | 18:11 | |
| *** ig0r_ has joined #openstack-mistral | 18:23 | |
| *** dmowrer has quit IRC | 18:41 | |
| *** dmowrer has joined #openstack-mistral | 18:43 | |
| *** toddjohn has quit IRC | 18:55 | |
| *** tonytan4ever has joined #openstack-mistral | 19:01 | |
| *** ig0r_ has quit IRC | 19:39 | |
| *** tonytan4ever has quit IRC | 19:46 | |
| *** gyee has quit IRC | 19:47 | |
| *** dmk0202 has joined #openstack-mistral | 19:54 | |
| *** shardy has quit IRC | 20:06 | |
| *** tonytan4ever has joined #openstack-mistral | 20:10 | |
| *** dmowrer has quit IRC | 20:24 | |
| *** dmowrer has joined #openstack-mistral | 20:25 | |
| *** dmowrer has quit IRC | 20:30 | |
| *** dmowrer has joined #openstack-mistral | 20:44 | |
| *** gyee has joined #openstack-mistral | 20:45 | |
| *** vishwanathj has joined #openstack-mistral | 21:20 | |
| *** dmk0202 has quit IRC | 21:32 | |
| *** dmk0202 has joined #openstack-mistral | 21:37 | |
| *** stevebak` is now known as stevebaker | 21:46 | |
| *** dmk0202 has quit IRC | 22:09 | |
| *** dmowrer has quit IRC | 22:26 | |
| *** dmowrer has joined #openstack-mistral | 22:27 | |
| *** dmowrer has quit IRC | 22:31 | |
| *** openstackgerrit has quit IRC | 23:03 | |
| *** vishwanathj has quit IRC | 23:03 | |
| *** openstackgerrit has joined #openstack-mistral | 23:03 | |
| *** Qiming has joined #openstack-mistral | 23:37 | |
| *** rbrady has quit IRC | 23:41 | |
| *** bobh has quit IRC | 23:53 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!