*** catintheroof has joined #openstack-mistral | 00:23 | |
*** bobh has quit IRC | 00:28 | |
*** jamielennox|away is now known as jamielennox | 00:37 | |
*** harlowja has joined #openstack-mistral | 00:52 | |
*** catintheroof has quit IRC | 01:13 | |
*** gongysh has joined #openstack-mistral | 01:14 | |
*** catintheroof has joined #openstack-mistral | 01:14 | |
*** catintheroof has quit IRC | 01:14 | |
*** gongysh has quit IRC | 01:40 | |
*** gongysh has joined #openstack-mistral | 01:42 | |
*** gongysh has quit IRC | 01:42 | |
*** gongysh has joined #openstack-mistral | 01:50 | |
*** gongysh has quit IRC | 01:53 | |
*** mgershen1 has joined #openstack-mistral | 02:34 | |
*** Kiall has joined #openstack-mistral | 02:37 | |
*** mgershen has quit IRC | 02:41 | |
*** Guest87200 has quit IRC | 02:41 | |
*** jamielennox has quit IRC | 02:41 | |
*** thrash is now known as thrash|g0ne | 02:57 | |
*** bobh has joined #openstack-mistral | 03:01 | |
openstackgerrit | Lingxian Kong proposed openstack/mistral-specs: Support openstack context for workflow execution https://review.openstack.org/414508 | 03:03 |
---|---|---|
kong | hi, mfisch, a new version of python-mistralclient has been released | 03:05 |
kong | mfisch: https://pypi.python.org/pypi/python-mistralclient/3.0.0 | 03:05 |
*** jamielennox|away has joined #openstack-mistral | 03:12 | |
*** jamielennox|away is now known as jamielennox | 03:12 | |
kong | ddeja, d0ugal, hi, guys, could you please take a look at the simple patch for role based resource operation feature https://review.openstack.org/#/c/421190/ | 03:36 |
mfisch | kong: thanks | 03:36 |
kong | mfisch: np | 03:37 |
*** bobh has quit IRC | 04:09 | |
*** gongysh has joined #openstack-mistral | 04:33 | |
*** gongysh has quit IRC | 04:42 | |
*** sharatss has joined #openstack-mistral | 05:00 | |
*** gongysh has joined #openstack-mistral | 05:31 | |
*** ist has joined #openstack-mistral | 05:56 | |
*** ist has quit IRC | 06:23 | |
*** ist has joined #openstack-mistral | 06:41 | |
*** sharatss has quit IRC | 06:55 | |
*** tuan_ has joined #openstack-mistral | 07:19 | |
*** tuan_ has quit IRC | 07:28 | |
*** tuan_ has joined #openstack-mistral | 07:30 | |
*** sharatss has joined #openstack-mistral | 08:21 | |
*** sharatss has quit IRC | 08:25 | |
*** openstackgerrit has quit IRC | 08:33 | |
*** jpich has joined #openstack-mistral | 08:46 | |
*** shardy_afk is now known as shardy | 09:03 | |
*** sharatss has joined #openstack-mistral | 09:18 | |
ddeja | kong: looking | 09:43 |
*** akuznetsova has quit IRC | 09:44 | |
*** akuznetsova has joined #openstack-mistral | 09:48 | |
*** openstackgerrit has joined #openstack-mistral | 10:01 | |
openstackgerrit | Renat Akhmerov proposed openstack/mistral: Make 'task' function work w/o a task name https://review.openstack.org/422518 | 10:01 |
tuan_ | Hey | 10:11 |
tuan_ | could somebody say something about this problem | 10:12 |
tuan_ | when we run workflow with 30 tasks | 10:12 |
openstackgerrit | Renat Akhmerov proposed openstack/mistral-specs: Adding workflow global context spec https://review.openstack.org/420650 | 10:20 |
*** sharat has joined #openstack-mistral | 10:26 | |
openstackgerrit | Sharat Sharma proposed openstack/mistral: Added the command to execute reverse workflow https://review.openstack.org/422535 | 10:27 |
*** gongysh has quit IRC | 10:30 | |
*** sharatss has quit IRC | 10:41 | |
openstackgerrit | Sharat Sharma proposed openstack/mistral: Changed the README.rst and added debug guide https://review.openstack.org/420687 | 10:46 |
openstackgerrit | Renat Akhmerov proposed openstack/mistral: Make 'task' function work w/o a task name https://review.openstack.org/422518 | 10:48 |
*** sharatss has joined #openstack-mistral | 10:48 | |
*** sharatss has quit IRC | 11:16 | |
*** sharatss has joined #openstack-mistral | 11:18 | |
openstackgerrit | Merged openstack/mistral: Role based resource access control - update workflows https://review.openstack.org/421190 | 11:35 |
tuan_ | Hi guys, another stupid question from me | 12:06 |
tuan_ | :( | 12:06 |
tuan_ | we have 1 delayed call in db | 12:06 |
tuan_ | and scheduler checks that delayed call and runs the target_method which is _check_and_complete() in workflow_handler | 12:07 |
tuan_ | and then this _check_and_complete() triggers schedule_call in scheduler.py and this whole process loops forever | 12:08 |
tuan_ | therefore mistral engine could not delete the delayed_call in the db | 12:09 |
tuan_ | what happens here? | 12:09 |
rakhmerov | tuan_: hi | 12:19 |
rakhmerov | theoretically, if everything is working normally this shouldn't happen | 12:19 |
rakhmerov | I guess that bug with expiration policy that Jozsef described in the email is related to exactly this | 12:20 |
rakhmerov | but it needs to be investigated | 12:20 |
rakhmerov | probably, something like this can happen on engine restart | 12:21 |
rakhmerov | the job itself checks workflow completion conditions | 12:21 |
rakhmerov | it's implemented as a delayed call for a reason, I can explain separately if needed | 12:21 |
tuan_ | ok | 12:22 |
rakhmerov | tuan_: also, if you fail a corresponding workflow manually this job should destroy itself | 12:22 |
rakhmerov | so this job is for some WF stuck in RUNNING state | 12:22 |
tuan_ | let's talk in separately | 12:23 |
rakhmerov | ok | 12:23 |
rakhmerov | ddeja: ping | 12:24 |
ddeja | rakhmerov: pong | 12:25 |
rakhmerov | ddeja: yes, looking at https://review.openstack.org/#/c/419888/2/mistral/engine/rpc_backend/kombu/kombu_server.py | 12:28 |
rakhmerov | question: what is this thread pool? | 12:28 |
rakhmerov | I didn't come across it before | 12:29 |
rakhmerov | specifically, futurist:ThreadPoolExecutor | 12:29 |
*** thrash|g0ne is now known as thrash | 12:30 | |
ddeja | rakhmerov: 1) it is something used also by oslo_messaging | 12:31 |
ddeja | 2) from my very limited knowledge, it is responsible for menaging the pool of threads and for giving jobs to them | 12:31 |
ddeja | in this example, processing of meesage is a job | 12:32 |
ddeja | and it is developed as an OpenStack project/library http://docs.openstack.org/developer/futurist/api.html | 12:32 |
rakhmerov | what kind of threads is it responsible for? | 12:33 |
rakhmerov | green threads? regular python threads? | 12:33 |
rakhmerov | something else? | 12:33 |
ddeja | http://docs.openstack.org/developer/futurist/features.html | 12:33 |
ddeja | it depends on configuration | 12:33 |
rakhmerov | reading.. | 12:33 |
ddeja | right now it can be 'blocking' | 12:33 |
rakhmerov | ohh, I see | 12:33 |
ddeja | which is just running it in a same thread - a wrapper for compatibility reasons | 12:34 |
rakhmerov | so it can be even ProcessPoolExecutor | 12:34 |
ddeja | and can be 'threading' - wich uses threading | 12:34 |
*** shardy is now known as shardy_lunch | 12:34 | |
rakhmerov | I guess it spawns separate processes in OS | 12:34 |
rakhmerov | ok | 12:34 |
rakhmerov | ddeja: so, seems ok to me | 12:35 |
rakhmerov | I don't see any issues with your patch | 12:35 |
ddeja | cool, thanks :) | 12:36 |
ddeja | We can also try to add greenThread pool to it | 12:36 |
ddeja | but in oslo they need to monkey-patch something to make it work | 12:36 |
ddeja | and I didin't want to make it too complicated | 12:36 |
rakhmerov | ddeja: don't we already monkey patch all they need? | 12:37 |
ddeja | rakhmerov: I'm not sure | 12:38 |
ddeja | maybe | 12:38 |
rakhmerov | or there's something besides our patched modules? | 12:38 |
rakhmerov | ok | 12:38 |
ddeja | but after all, we don't use 'eventlet' executor anywhere in a code | 12:38 |
ddeja | we only have 'blocking' and 'threading' | 12:38 |
rakhmerov | yeah, I know.. | 12:39 |
rakhmerov | ok | 12:39 |
rakhmerov | ddeja: btw, I fix my spec | 12:39 |
rakhmerov | tried to put the info you suggested | 12:39 |
rakhmerov | not "tried", just "put" :) | 12:39 |
ddeja | OK | 12:40 |
ddeja | I've just went through my 'review' folder in evolution and got a buch of tabs with reviews, looking on them right now | 12:40 |
rakhmerov | ok | 12:42 |
rakhmerov | ddeja: also please look at https://review.openstack.org/#/c/421686/ | 12:42 |
rakhmerov | I left my honest comment on it | 12:43 |
rakhmerov | :) | 12:43 |
rakhmerov | but I really found useful to have something like this right in "std." | 12:43 |
rakhmerov | for testing | 12:43 |
rakhmerov | I'm not insisting though to include it into "std." | 12:43 |
*** catintheroof has joined #openstack-mistral | 12:43 | |
ddeja | OK | 12:43 |
ddeja | rakhmerov: hm, can you provide an example when it can be useful> | 12:46 |
ddeja | ? | 12:46 |
ddeja | patch itself seems OK, but I'm a little bit confused when it may be usefull | 12:46 |
ddeja | rakhmerov: and BTW, you will be a PTL for Pike, won't you? | 12:48 |
* ddeja just read an email about someone not going to candidate in another project | 12:49 | |
*** rbrady has quit IRC | 12:51 | |
rakhmerov | ddeja: yeah, I guess so (on PTLship) | 12:55 |
ddeja | \o/ | 12:55 |
rakhmerov | unless someone else wants to be | 12:55 |
rakhmerov | ddeja: you can apply to | 12:55 |
rakhmerov | as far as an example, what do you mean? | 12:56 |
rakhmerov | global context? | 12:56 |
ddeja | rakhmerov: nope, I do not want to ;) | 12:56 |
rakhmerov | ddeja: bad :) | 12:56 |
ddeja | rakhmerov: why? | 12:56 |
rakhmerov | :) | 12:56 |
ddeja | rakhmerov: as far as example, I just can't think when I would like to use such action | 12:57 |
rakhmerov | sometimes I think that I need to step down at least for sometime | 12:57 |
ddeja | or maybe I just understand it wrong | 12:57 |
rakhmerov | (although it also depends on my management and company) | 12:57 |
rakhmerov | no, I mean, maybe it could be useful for the project | 12:57 |
ddeja | but I understand that this action would produce something like: {'foo1': 'abc', 'foo2': 'abc', ... , 'fooXXX': 'abc'} | 12:57 |
ddeja | am I wright? | 12:58 |
*** sharat has quit IRC | 12:58 | |
rakhmerov | if someone else play the role of PTL | 12:58 |
rakhmerov | ooh, you're talking about an action? | 12:58 |
rakhmerov | ok | 12:58 |
rakhmerov | sec | 12:58 |
ddeja | right now yes :D | 12:58 |
ddeja | (it's different to talk about to subjects at a same time on IRC :/ ) | 12:58 |
rakhmerov | ddeja: I forgot I have a meeting right now | 13:00 |
*** sharatss has quit IRC | 13:00 | |
ddeja | no problem, I also have one now ;) | 13:00 |
rakhmerov | so, essentially if I want to perform tests with big data published into a context | 13:01 |
rakhmerov | in order to test performance | 13:01 |
rakhmerov | (I'm really doing it) | 13:01 |
*** sharatss has joined #openstack-mistral | 13:01 | |
ddeja | Oh | 13:02 |
ddeja | so you are using it to produce really big dicts | 13:02 |
ddeja | where the problem is the ammount of data, am I right? | 13:02 |
rakhmerov | yes | 13:03 |
ddeja | (my wife is also working on Big Data :D, so I heard something about it everyday) | 13:04 |
ddeja | rakhmerov: ok, thanks. +2 +W | 13:08 |
rakhmerov | :) | 13:08 |
*** bobh has joined #openstack-mistral | 13:08 | |
ddeja | oh, sorry, only +2 | 13:08 |
ddeja | someone else needs to give second ;) | 13:08 |
rakhmerov | yes | 13:10 |
rakhmerov | ddeja: how about this tiny one? https://review.openstack.org/#/c/421223/1 | 13:10 |
rakhmerov | it just follows ahead of that one | 13:10 |
ddeja | *poof* +2 +W ;) | 13:11 |
rakhmerov | thnx | 13:13 |
ddeja | no problem ;) | 13:14 |
*** shardy_lunch is now known as shardy | 13:20 | |
rakhmerov | d0ugal: hi, what do you think about it ? https://review.openstack.org/#/c/421686/ | 13:24 |
rakhmerov | can we let it in? | 13:25 |
rakhmerov | based on my reasoning here (see above) | 13:25 |
d0ugal | rakhmerov: can we add it to the docs? | 13:26 |
rakhmerov | hm... | 13:26 |
rakhmerov | why not | 13:26 |
d0ugal | Just a quick mention would do :) | 13:26 |
rakhmerov | yep | 13:26 |
rakhmerov | we could say "useful for testing and try outs) | 13:26 |
d0ugal | I don't think I understand when it would be useful lol | 13:27 |
* d0ugal reads up | 13:28 | |
*** bobh has quit IRC | 13:28 | |
d0ugal | rakhmerov: how long have you been PTL? | 13:29 |
rakhmerov | 3 years | 13:29 |
d0ugal | long time :) | 13:30 |
rakhmerov | from the very beginning | 13:30 |
rakhmerov | yes | 13:30 |
rakhmerov | :) | 13:30 |
d0ugal | rakhmerov: are you going to update that patch with docs now or should I merge it? | 13:31 |
rakhmerov | I'd prefere separately | 13:31 |
rakhmerov | I'll do it | 13:32 |
rakhmerov | if it's ok | 13:32 |
d0ugal | ok | 13:32 |
d0ugal | but please do :) | 13:32 |
d0ugal | I think eventually we should have a policy that all features need documentation to be merged, it is the only way we will make our docs good | 13:33 |
rakhmerov | d0ugal: I have to agree with you | 13:56 |
rakhmerov | yes | 13:56 |
rakhmerov | although there can be a different point of view on this | 13:57 |
rakhmerov | e.g., I implemented a new feature but I don't want to expose it broadly yet | 13:57 |
rakhmerov | say I treat it experimental for the time being | 13:58 |
rakhmerov | ddeja: does this tell anything to you? http://logs.openstack.org/18/422518/2/check/gate-mistral-devstack-dsvm-ubuntu-xenial-nv/a154e88/console.html | 13:58 |
ddeja | rakhmerov: let me take a look | 13:59 |
rakhmerov | if you have time | 13:59 |
rakhmerov | just thought maybe you saw a similar thing | 13:59 |
ddeja | rakhmerov: I've never seen something similar | 14:00 |
rakhmerov | ok | 14:02 |
rakhmerov | I wonder if it's something worth rechecking.. | 14:02 |
*** dprince has joined #openstack-mistral | 14:05 | |
openstackgerrit | Merged openstack/mistral: Register Javascript action additionally as 'js' action https://review.openstack.org/421223 | 14:08 |
ddeja | rakhmerov: I'd say that every gate failure is worth checking | 14:11 |
ddeja | but this one seems weird | 14:11 |
rakhmerov | I rechecked | 14:11 |
rakhmerov | wanna see if it helps | 14:11 |
ddeja | well, it seems unrelated with the change itself | 14:12 |
ddeja | testr return 2, instead of 0, when listing tests | 14:12 |
openstackgerrit | Merged openstack/mistral: Add action "std.test_dict" https://review.openstack.org/421686 | 14:31 |
d0ugal | rakhmerov: then we should have an experimental part of the documentation for features we might change | 14:39 |
d0ugal | rakhmerov: just releasing them and hoping people don't find them isn't a great idea | 14:40 |
*** ist has quit IRC | 14:45 | |
*** sharatss has quit IRC | 14:53 | |
*** dprince has quit IRC | 14:59 | |
*** thrash is now known as thrash|biab | 15:01 | |
*** bobh has joined #openstack-mistral | 15:05 | |
*** rbrady has joined #openstack-mistral | 15:28 | |
*** rbrady has quit IRC | 15:28 | |
*** rbrady has joined #openstack-mistral | 15:28 | |
*** jaosorior has joined #openstack-mistral | 15:31 | |
*** dprince has joined #openstack-mistral | 15:47 | |
*** tuan_ has quit IRC | 15:54 | |
*** thrash|biab is now known as thrash | 15:55 | |
*** bobh has quit IRC | 15:59 | |
*** shardy has quit IRC | 16:00 | |
*** shardy has joined #openstack-mistral | 16:01 | |
thrash | got a yaql question... trying to filter down a list (specifically, output from heat.stacks_list), and want to see if a specific entry exists... Not having a whole lot of luck with it. | 16:09 |
thrash | trying to use 'task(my_task).result.where($.stack_name = $.stack).len() > 0' did not work. | 16:10 |
thrash | $.stack is an input to the workflow. | 16:10 |
thrash | I've also tried 'task(my_task).result[$.stack_name = $.stack].len() > 0' to no avail. | 16:14 |
thrash | i get 'Can not evalutate YAQL expression' | 16:15 |
thrash | I'm pretty sure it's because of the $.stack part of it. | 16:25 |
*** hrybacki is now known as hrybacki|afkish | 16:32 | |
thrash | nm.., | 16:33 |
thrash | I think I have it. Went about it a different way. Testing... | 16:33 |
*** bobh has joined #openstack-mistral | 16:35 | |
thrash | ok.. got it... $.stack in task(my_task).result.select($.stack_name) | 16:40 |
openstackgerrit | Merged openstack/mistral: using utcnow instead of now in expiration policy https://review.openstack.org/421842 | 16:53 |
openstackgerrit | Merged openstack/mistral: Make 'task' function work w/o a task name https://review.openstack.org/422518 | 16:56 |
*** jistr is now known as jistr|afk | 16:57 | |
*** rbrady has quit IRC | 17:03 | |
*** rbrady has joined #openstack-mistral | 17:15 | |
*** shardy has quit IRC | 17:29 | |
*** dturner has joined #openstack-mistral | 17:37 | |
*** rbrady has quit IRC | 17:52 | |
openstackgerrit | Corey Bryant proposed openstack/python-mistralclient: Fix doc build if git is absent https://review.openstack.org/422784 | 17:56 |
*** jistr|afk is now known as jistr | 18:01 | |
*** bobh has quit IRC | 18:17 | |
*** catinthe_ has joined #openstack-mistral | 18:18 | |
*** catintheroof has quit IRC | 18:18 | |
*** jpich has quit IRC | 18:22 | |
*** weshay is now known as weshay_afk | 18:31 | |
*** hrybacki|afkish is now known as hrybacki|sick | 18:40 | |
*** rbrady has joined #openstack-mistral | 18:44 | |
d0ugal | thrash: nice | 18:52 |
d0ugal | thrash: YAQL is a strange thing :) | 18:52 |
thrash | d0ugal: yeah.. Just had to come at it from a different angle. | 18:53 |
*** bobh has joined #openstack-mistral | 18:56 | |
*** thrash is now known as thrash|biab | 19:11 | |
*** bobh has quit IRC | 19:28 | |
*** dprince has quit IRC | 19:32 | |
*** openstackgerrit has quit IRC | 19:33 | |
*** rbrady has quit IRC | 19:46 | |
*** rbrady has joined #openstack-mistral | 19:51 | |
*** rbrady has quit IRC | 19:51 | |
*** rbrady has joined #openstack-mistral | 19:51 | |
*** rbrady has quit IRC | 20:03 | |
*** thrash|biab is now known as thrash | 20:16 | |
*** dprince has joined #openstack-mistral | 20:17 | |
*** bobh has joined #openstack-mistral | 20:28 | |
*** bobh has quit IRC | 20:33 | |
*** bobh has joined #openstack-mistral | 21:22 | |
*** dprince has quit IRC | 21:28 | |
*** dprince has joined #openstack-mistral | 21:28 | |
*** thrash is now known as thrash|g0ne | 21:37 | |
*** bobh has quit IRC | 22:53 | |
*** gyee has joined #openstack-mistral | 23:22 | |
*** gyee has quit IRC | 23:36 | |
*** jaosorior has quit IRC | 23:38 | |
*** gyee has joined #openstack-mistral | 23:39 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!