*** bobh has joined #openstack-mistral | 00:31 | |
*** bobh has quit IRC | 00:53 | |
*** bobh has joined #openstack-mistral | 00:55 | |
*** bobh has quit IRC | 01:04 | |
*** thrash is now known as thrash|g0ne | 01:34 | |
*** bobh has joined #openstack-mistral | 01:36 | |
*** bobh has quit IRC | 02:09 | |
*** bobh has joined #openstack-mistral | 02:24 | |
*** gfidente has quit IRC | 02:51 | |
*** bobh has quit IRC | 03:26 | |
*** sharatss has joined #openstack-mistral | 05:41 | |
*** sharatss has quit IRC | 05:55 | |
*** sharatss has joined #openstack-mistral | 06:11 | |
*** sharat has joined #openstack-mistral | 06:31 | |
*** shardy has joined #openstack-mistral | 07:06 | |
*** jpich has joined #openstack-mistral | 07:20 | |
d0ugal | rakhmerov: yay https://review.openstack.org/#/c/477450/ | 07:31 |
---|---|---|
d0ugal | :) | 07:31 |
rakhmerov | d0ugal: excellent! | 07:32 |
rakhmerov | no need to change the release model then ) | 07:32 |
d0ugal | Indeed | 07:32 |
d0ugal | Unless you want to change it :) | 07:32 |
*** jkilpatr has quit IRC | 07:33 | |
*** sharatss_ has joined #openstack-mistral | 07:37 | |
*** sharatss has quit IRC | 07:37 | |
*** amoralej|off is now known as amoralej | 07:38 | |
*** openstackgerrit has quit IRC | 07:47 | |
*** sharatss_ has quit IRC | 07:49 | |
rakhmerov | d0ugal: no, I don't for now ) | 07:53 |
apetrich | d0ugal, woot! | 07:56 |
*** sharat has quit IRC | 08:10 | |
*** dtantsur|afk is now known as dtantsur | 08:11 | |
rakhmerov | kong: hi | 08:16 |
rakhmerov | you here? | 08:16 |
*** mgershen has joined #openstack-mistral | 08:32 | |
d0ugal | rakhmerov: do you understand the "--filter" option on the CLI? | 08:38 |
d0ugal | How can I find the list of valid names. | 08:38 |
d0ugal | rakhmerov: Foudn it, it seems you can't do "mistral task-list --filter execution_id=ID" - that would be useful. | 08:42 |
* d0ugal might write a quick patch. | 08:42 | |
rakhmerov | yep, right | 08:44 |
rakhmerov | d0ugal: but in case of task-list you don't even need to use --filter | 08:45 |
rakhmerov | just do: mistral task-list <execution_id> | 08:45 |
d0ugal | oh, wow | 08:45 |
rakhmerov | yep | 08:45 |
d0ugal | TIL! | 08:45 |
rakhmerov | same with action-execution-list | 08:45 |
rakhmerov | you can pass it with a task execution ID | 08:45 |
d0ugal | amazing | 08:46 |
d0ugal | thanks | 08:46 |
rakhmerov | but yes, --filter can be used for all other fields | 08:46 |
rakhmerov | name, state etc. | 08:46 |
d0ugal | right, I have used it before and thought it was weird that it didn't allow execution_id | 08:46 |
d0ugal | Now I know why :) | 08:47 |
d0ugal | Until now I have just grepped | 08:47 |
*** sharat has joined #openstack-mistral | 08:49 | |
rakhmerov | haha :) | 08:51 |
rakhmerov | you suffered, it's bad ) | 08:52 |
rakhmerov | documentation!! We need a good documentation! | 08:52 |
d0ugal | haha, yeah | 09:00 |
d0ugal | rakhmerov: I would like "mistral execution-list EXECUTION_ID" | 09:16 |
d0ugal | to get the execution and it's sub-workflow executions | 09:17 |
d0ugal | Is there a relation in the db for sub-workflow to parent workflow? | 09:17 |
d0ugal | I don't see one :( | 09:18 |
rakhmerov | d0ugal: actually it's a good idea | 09:18 |
rakhmerov | but we can't use EXECUTION_ID | 09:18 |
rakhmerov | we rather have to use TASK_EXECUTION_ID | 09:18 |
d0ugal | oh | 09:18 |
rakhmerov | because workflow may have multiple subworkflows | 09:18 |
d0ugal | right | 09:19 |
rakhmerov | yes, the relation is "task_execution_id" | 09:19 |
rakhmerov | in workflow execution | 09:19 |
d0ugal | but they also might have multiple task executions with sub-workflows? | 09:19 |
d0ugal | hmm | 09:19 |
d0ugal | This would be hard to do with one db query :) | 09:19 |
rakhmerov | not sure I understood your last question.. | 09:21 |
d0ugal | rakhmerov: so, given this example: http://paste.openstack.org/show/614015/ | 09:22 |
rakhmerov | yep | 09:22 |
d0ugal | I only started one workflow, the others were started by it | 09:22 |
rakhmerov | yes | 09:22 |
rakhmerov | ooh, you just want to list ALL subworkflows of your original workflow? | 09:22 |
d0ugal | if there were other workflow executions, how would I find only the executions related to 03fcdef4-1701-4661-9049-c944b8a87760 | 09:22 |
d0ugal | rakhmerov: yeah | 09:22 |
rakhmerov | yep, I see | 09:23 |
rakhmerov | it'd be good | 09:23 |
d0ugal | so at the moment I only have that workflow, because I delete all executions before running to make it easier | 09:23 |
d0ugal | but it would be really useful if I could say "mistral execution-list 03fcdef4-1701-4661-9049-c944b8a87760" and it gave me all the sub-workflows (and the sub-sub-workflows etc) | 09:23 |
rakhmerov | we can probably have some pseudo filter for this | 09:23 |
d0ugal | yeah | 09:23 |
mgershen | d0ugal: you can try and run a workflow that gets all tasks of the execution recursively and them get the execution_id from there distinctly using yaql. | 09:24 |
d0ugal | mgershen: oh, that is a cool idea. | 09:24 |
d0ugal | it also sounds fun :) | 09:24 |
rakhmerov | yes, it is there now | 09:24 |
d0ugal | Okay, I'll try this! | 09:24 |
rakhmerov | we can expose it in the API too somehow | 09:24 |
rakhmerov | that would be nice | 09:24 |
rakhmerov | btw, what Toure is doing can probably help with this too | 09:25 |
rakhmerov | it should show the structure of workflow/subworkflows | 09:25 |
d0ugal | yeah, I was just reviewing his patch which is what made me think of it :) | 09:25 |
rakhmerov | aha | 09:25 |
mgershen | it will take work to get it done. | 09:26 |
mgershen | I mean even with the workflow | 09:27 |
d0ugal | yup | 09:29 |
mgershen | I belive something like this will get you the execution IDs: <% tasks(TOP_LVL_EXEC, true).workflow_execution_id.distinct() %> | 09:31 |
mgershen | d0ugal: you using the http://yaqluator.com/ ? | 09:34 |
d0ugal | mgershen: no, I use the YAQL repl sometimes. | 09:34 |
d0ugal | mgershen: I did try it once but it has an old version of YAQL and didn't have the features I wanted | 09:35 |
mgershen | ok, it now has yaql 1.1.0 if you want to try it again. I like it because of the auto-completion based on content. | 09:39 |
d0ugal | mgershen: oh cool, I don't remember auto-completion. I'll try it again. | 09:41 |
mgershen | d0ugal: maybe you are typing too fast haha. see here: https://pasteboard.co/1PfMFMUd.png | 09:55 |
d0ugal | mgershen: very cool :) | 09:56 |
*** shardy has quit IRC | 10:49 | |
*** openstackgerrit has joined #openstack-mistral | 10:54 | |
openstackgerrit | Sharat Sharma proposed openstack/python-mistralclient master: Add pagination options for workflows and actions https://review.openstack.org/458515 | 10:54 |
*** jkilpatr has joined #openstack-mistral | 10:56 | |
*** jkilpatr has quit IRC | 10:56 | |
*** jkilpatr has joined #openstack-mistral | 10:57 | |
openstackgerrit | bhavani proposed openstack/mistral-specs master: Remove pbr warnerrors in favor of sphinx check https://review.openstack.org/478886 | 11:45 |
*** amoralej is now known as amoralej|lunch | 11:56 | |
*** thrash|g0ne is now known as thrash | 11:57 | |
openstackgerrit | bhavani proposed openstack/mistral-specs master: Remove pbr warnerrors in favor of sphinx check https://review.openstack.org/478886 | 12:03 |
*** abhishekk has quit IRC | 12:28 | |
*** bobh has joined #openstack-mistral | 12:29 | |
*** bobh has quit IRC | 12:32 | |
*** chlong_ has joined #openstack-mistral | 12:35 | |
*** dmellado has quit IRC | 12:39 | |
*** amoralej|lunch has quit IRC | 12:39 | |
*** dmellado has joined #openstack-mistral | 12:42 | |
*** bobh has joined #openstack-mistral | 12:43 | |
openstackgerrit | Sharat Sharma proposed openstack/python-mistralclient master: Add pagination options for workflows and actions https://review.openstack.org/458515 | 12:44 |
*** thrash is now known as thrash|biab | 12:46 | |
*** dprince has joined #openstack-mistral | 12:47 | |
*** jkilpatr has quit IRC | 12:49 | |
*** jkilpatr has joined #openstack-mistral | 12:49 | |
*** bobh has quit IRC | 12:53 | |
*** shardy has joined #openstack-mistral | 12:54 | |
*** sharat has quit IRC | 12:58 | |
*** brunograz has joined #openstack-mistral | 12:59 | |
*** jkilpatr has quit IRC | 13:26 | |
*** jkilpatr has joined #openstack-mistral | 13:28 | |
*** toure|gone is now known as toure | 13:30 | |
*** jkilpatr_ has joined #openstack-mistral | 13:34 | |
*** jkilpatr_ has quit IRC | 13:36 | |
*** jkilpatr_ has joined #openstack-mistral | 13:36 | |
*** jkilpatr has quit IRC | 13:37 | |
*** bobh has joined #openstack-mistral | 13:39 | |
*** livelace has joined #openstack-mistral | 13:46 | |
*** mgershen has quit IRC | 13:58 | |
toure | d0ugal ping | 14:01 |
*** mgershen has joined #openstack-mistral | 14:01 | |
d0ugal | toure: hey | 14:02 |
toure | question in regards to the sqlalchemy structure in my proposal | 14:02 |
toure | d0ugal would a join solve that problem | 14:03 |
toure | combined with the filter | 14:03 |
d0ugal | toure: with sub workflows? | 14:03 |
d0ugal | no, I don't think do | 14:03 |
toure | yeah | 14:03 |
toure | what did you have in mind in regards? | 14:03 |
d0ugal | I don't have a solution :) | 14:03 |
toure | hehe | 14:03 |
toure | ok, I will play around with the database and see if I can come up with something | 14:04 |
toure | d0ugal would each sub_workflow be considered a unique workflow_Execution with a parent? | 14:06 |
d0ugal | toure: I don't think it will be possible with one query | 14:06 |
d0ugal | toure: yes | 14:06 |
* toure accepts d0ugal's challenge | 14:07 | |
toure | :) | 14:07 |
d0ugal | haha, good luck | 14:07 |
* toure will bend sqlalchemy to his will | 14:07 | |
toure | lol | 14:07 |
d0ugal | toure: the workflow has a reference to the current task exectution, that task execution links back to the execution of the sub-workflow | 14:07 |
d0ugal | IIUC | 14:07 |
toure | do you have a quick example of a sub_workflow yaml | 14:08 |
d0ugal | toure: baremetal.yaml? | 14:08 |
d0ugal | in tripleo-common | 14:08 |
d0ugal | but there it isn't really a feature of the workflow language | 14:09 |
toure | ah | 14:09 |
d0ugal | any workflow can call any other workflow | 14:09 |
toure | k | 14:09 |
*** thrash|biab is now known as thrash | 14:09 | |
toure | d0ugal I think I got it figured out in my mind at least, so if we take the approach of starting with the parent workflow query then extract the execution id(s) we should capture everything | 14:15 |
toure | so we can get a count from the parent in regards to execution_id then traverse each id | 14:16 |
d0ugal | right | 14:16 |
d0ugal | Having to do N queries is a pain, but getting that working is a good starting point. | 14:16 |
* toure sqlalchemy-Fu will be raised a notch | 14:16 | |
toure | well you wouldn't have to do N queries as the count returned can load a loop to perform the task | 14:17 |
toure | if I am thinking clearly :) | 14:18 |
d0ugal | I'm not sure | 14:18 |
d0ugal | I'd have to try it and see | 14:18 |
toure | I am working on it | 14:19 |
*** jkilpatr_ has quit IRC | 14:26 | |
*** jkilpatr has joined #openstack-mistral | 14:27 | |
*** zhurong has joined #openstack-mistral | 14:31 | |
*** zhurong has quit IRC | 14:40 | |
*** brunograz has quit IRC | 15:07 | |
openstackgerrit | Andras Kovi proposed openstack/mistral master: Update docker build https://review.openstack.org/473876 | 15:10 |
*** jkilpatr has quit IRC | 15:16 | |
d0ugal | 15:16 | |
*** jistr is now known as jistr|afk | 15:20 | |
*** jkilpatr has joined #openstack-mistral | 15:29 | |
*** jistr|afk is now known as jistr | 16:07 | |
*** jpich has quit IRC | 16:28 | |
*** dtantsur is now known as dtantsur|afk | 16:50 | |
*** bobh has quit IRC | 17:04 | |
*** dprince has quit IRC | 18:32 | |
*** dprince has joined #openstack-mistral | 18:48 | |
*** livelace has quit IRC | 18:59 | |
*** bobh has joined #openstack-mistral | 19:04 | |
*** bobh has quit IRC | 19:25 | |
*** bobh has joined #openstack-mistral | 19:33 | |
openstackgerrit | Toure Dunnon proposed openstack/mistral master: Workflow Error Analysis https://review.openstack.org/455447 | 19:54 |
*** bobh has quit IRC | 19:55 | |
*** toure is now known as toure|gone | 20:03 | |
*** dprince has quit IRC | 20:44 | |
openstackgerrit | Michal Gershenzon proposed openstack/mistral-specs master: Create and run workflows within a namespace https://review.openstack.org/470996 | 21:41 |
*** shardy has quit IRC | 22:09 | |
*** jamielennox has quit IRC | 22:57 | |
*** jamielennox has joined #openstack-mistral | 23:03 | |
*** dougshelley66 has quit IRC | 23:50 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!