Thursday, 2017-01-19

*** catintheroof has joined #openstack-mistral00:23
*** bobh has quit IRC00:28
*** jamielennox|away is now known as jamielennox00:37
*** harlowja has joined #openstack-mistral00:52
*** catintheroof has quit IRC01:13
*** gongysh has joined #openstack-mistral01:14
*** catintheroof has joined #openstack-mistral01:14
*** catintheroof has quit IRC01:14
*** gongysh has quit IRC01:40
*** gongysh has joined #openstack-mistral01:42
*** gongysh has quit IRC01:42
*** gongysh has joined #openstack-mistral01:50
*** gongysh has quit IRC01:53
*** mgershen1 has joined #openstack-mistral02:34
*** Kiall has joined #openstack-mistral02:37
*** mgershen has quit IRC02:41
*** Guest87200 has quit IRC02:41
*** jamielennox has quit IRC02:41
*** thrash is now known as thrash|g0ne02:57
*** bobh has joined #openstack-mistral03:01
openstackgerritLingxian Kong proposed openstack/mistral-specs: Support openstack context for workflow execution  https://review.openstack.org/41450803:03
konghi, mfisch, a new version of python-mistralclient has been released03:05
kongmfisch: https://pypi.python.org/pypi/python-mistralclient/3.0.003:05
*** jamielennox|away has joined #openstack-mistral03:12
*** jamielennox|away is now known as jamielennox03:12
kongddeja, 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
mfischkong: thanks03:36
kongmfisch: np03:37
*** bobh has quit IRC04:09
*** gongysh has joined #openstack-mistral04:33
*** gongysh has quit IRC04:42
*** sharatss has joined #openstack-mistral05:00
*** gongysh has joined #openstack-mistral05:31
*** ist has joined #openstack-mistral05:56
*** ist has quit IRC06:23
*** ist has joined #openstack-mistral06:41
*** sharatss has quit IRC06:55
*** tuan_ has joined #openstack-mistral07:19
*** tuan_ has quit IRC07:28
*** tuan_ has joined #openstack-mistral07:30
*** sharatss has joined #openstack-mistral08:21
*** sharatss has quit IRC08:25
*** openstackgerrit has quit IRC08:33
*** jpich has joined #openstack-mistral08:46
*** shardy_afk is now known as shardy09:03
*** sharatss has joined #openstack-mistral09:18
ddejakong: looking09:43
*** akuznetsova has quit IRC09:44
*** akuznetsova has joined #openstack-mistral09:48
*** openstackgerrit has joined #openstack-mistral10:01
openstackgerritRenat Akhmerov proposed openstack/mistral: Make 'task' function work w/o a task name  https://review.openstack.org/42251810:01
tuan_Hey10:11
tuan_could somebody say something about this problem10:12
tuan_when we run workflow with 30 tasks10:12
openstackgerritRenat Akhmerov proposed openstack/mistral-specs: Adding workflow global context spec  https://review.openstack.org/42065010:20
*** sharat has joined #openstack-mistral10:26
openstackgerritSharat Sharma proposed openstack/mistral: Added the command to execute reverse workflow  https://review.openstack.org/42253510:27
*** gongysh has quit IRC10:30
*** sharatss has quit IRC10:41
openstackgerritSharat Sharma proposed openstack/mistral: Changed the README.rst and added debug guide  https://review.openstack.org/42068710:46
openstackgerritRenat Akhmerov proposed openstack/mistral: Make 'task' function work w/o a task name  https://review.openstack.org/42251810:48
*** sharatss has joined #openstack-mistral10:48
*** sharatss has quit IRC11:16
*** sharatss has joined #openstack-mistral11:18
openstackgerritMerged openstack/mistral: Role based resource access control - update workflows  https://review.openstack.org/42119011:35
tuan_Hi guys, another stupid question from me12:06
tuan_:(12:06
tuan_we have 1 delayed call in db12:06
tuan_and scheduler checks that delayed call and runs the target_method which is _check_and_complete() in workflow_handler12:07
tuan_and then this _check_and_complete() triggers schedule_call in scheduler.py and this whole process loops forever12:08
tuan_therefore mistral engine could not delete the delayed_call in the db12:09
tuan_what happens here?12:09
rakhmerovtuan_: hi12:19
rakhmerovtheoretically, if everything is working normally this shouldn't happen12:19
rakhmerovI guess that bug with expiration policy that Jozsef described in the email is related to exactly this12:20
rakhmerovbut it needs to be investigated12:20
rakhmerovprobably, something like this can happen on engine restart12:21
rakhmerovthe job itself checks workflow completion conditions12:21
rakhmerovit's implemented as a delayed call for a reason, I can explain separately if needed12:21
tuan_ok12:22
rakhmerovtuan_: also, if you fail a corresponding workflow manually this job should destroy itself12:22
rakhmerovso this job is for some WF stuck in RUNNING state12:22
tuan_let's talk in separately12:23
rakhmerovok12:23
rakhmerovddeja: ping12:24
ddejarakhmerov: pong12:25
rakhmerovddeja: yes, looking at https://review.openstack.org/#/c/419888/2/mistral/engine/rpc_backend/kombu/kombu_server.py12:28
rakhmerovquestion: what is this thread pool?12:28
rakhmerovI didn't come across it before12:29
rakhmerovspecifically, futurist:ThreadPoolExecutor12:29
*** thrash|g0ne is now known as thrash12:30
ddejarakhmerov: 1) it is something used also by oslo_messaging12:31
ddeja2) from my very limited knowledge, it is responsible for menaging the pool of threads and for giving jobs to them12:31
ddejain this example, processing of meesage is a job12:32
ddejaand it is developed as an OpenStack project/library http://docs.openstack.org/developer/futurist/api.html12:32
rakhmerovwhat kind of threads is it responsible for?12:33
rakhmerovgreen threads? regular python threads?12:33
rakhmerovsomething else?12:33
ddejahttp://docs.openstack.org/developer/futurist/features.html12:33
ddejait depends on configuration12:33
rakhmerovreading..12:33
ddejaright now it can be 'blocking'12:33
rakhmerovohh, I see12:33
ddejawhich is just running it in a same thread - a wrapper for compatibility reasons12:34
rakhmerovso it can be even ProcessPoolExecutor12:34
ddejaand can be 'threading' - wich uses threading12:34
*** shardy is now known as shardy_lunch12:34
rakhmerovI guess it spawns separate processes in OS12:34
rakhmerovok12:34
rakhmerovddeja: so, seems ok to me12:35
rakhmerovI don't see any issues with your patch12:35
ddejacool, thanks :)12:36
ddejaWe can also try to add greenThread pool to it12:36
ddejabut in oslo they need to monkey-patch something to make it work12:36
ddejaand I didin't want to make it too complicated12:36
rakhmerovddeja: don't we already monkey patch all they need?12:37
ddejarakhmerov: I'm not sure12:38
ddejamaybe12:38
rakhmerovor there's something besides our patched modules?12:38
rakhmerovok12:38
ddejabut after all, we don't use 'eventlet' executor anywhere in a code12:38
ddejawe only have 'blocking' and 'threading'12:38
rakhmerovyeah, I know..12:39
rakhmerovok12:39
rakhmerovddeja: btw, I fix my spec12:39
rakhmerovtried to put the info you suggested12:39
rakhmerovnot "tried", just "put" :)12:39
ddejaOK12:40
ddejaI've just went through my 'review' folder in evolution and got a buch of tabs with reviews, looking on them right now12:40
rakhmerovok12:42
rakhmerovddeja: also please look at https://review.openstack.org/#/c/421686/12:42
rakhmerovI left my honest comment on it12:43
rakhmerov:)12:43
rakhmerovbut I really found useful to have something like this right in "std."12:43
rakhmerovfor testing12:43
rakhmerovI'm not insisting though to include it into "std."12:43
*** catintheroof has joined #openstack-mistral12:43
ddejaOK12:43
ddejarakhmerov: hm, can you provide an example when it can be useful>12:46
ddeja?12:46
ddejapatch itself seems OK, but I'm a little bit confused when it may be usefull12:46
ddejarakhmerov: 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 project12:49
*** rbrady has quit IRC12:51
rakhmerovddeja: yeah, I guess so (on PTLship)12:55
ddeja\o/12:55
rakhmerovunless someone else wants to be12:55
rakhmerovddeja: you can apply to12:55
rakhmerovas far as an example, what do you mean?12:56
rakhmerovglobal context?12:56
ddejarakhmerov: nope, I do not want to ;)12:56
rakhmerovddeja: bad :)12:56
ddejarakhmerov: why?12:56
rakhmerov:)12:56
ddejarakhmerov: as far as example, I just can't think when I would like to use such action12:57
rakhmerovsometimes I think that I need to step down at least for sometime12:57
ddejaor maybe I just understand it wrong12:57
rakhmerov(although it also depends on my management and company)12:57
rakhmerovno, I mean, maybe it could be useful for the project12:57
ddejabut I understand that this action would produce something like: {'foo1': 'abc', 'foo2': 'abc', ... , 'fooXXX': 'abc'}12:57
ddejaam I wright?12:58
*** sharat has quit IRC12:58
rakhmerovif someone else play the role of PTL12:58
rakhmerovooh, you're talking about an action?12:58
rakhmerovok12:58
rakhmerovsec12:58
ddejaright now yes :D12:58
ddeja(it's different to talk about to subjects at a same time on IRC :/ )12:58
rakhmerovddeja: I forgot I have a meeting right now13:00
*** sharatss has quit IRC13:00
ddejano problem, I also have one now ;)13:00
rakhmerovso, essentially if I want to perform tests with big data published into a context13:01
rakhmerovin order to test performance13:01
rakhmerov(I'm really doing it)13:01
*** sharatss has joined #openstack-mistral13:01
ddejaOh13:02
ddejaso you are using it to produce really big dicts13:02
ddejawhere the problem is the ammount of data, am I right?13:02
rakhmerovyes13:03
ddeja(my wife is also working on Big Data :D, so I heard something about it everyday)13:04
ddejarakhmerov: ok, thanks. +2 +W13:08
rakhmerov:)13:08
*** bobh has joined #openstack-mistral13:08
ddejaoh, sorry, only +213:08
ddejasomeone else needs to give second ;)13:08
rakhmerovyes13:10
rakhmerovddeja: how about this tiny one? https://review.openstack.org/#/c/421223/113:10
rakhmerovit just follows ahead of that one13:10
ddeja*poof* +2 +W ;)13:11
rakhmerovthnx13:13
ddejano problem ;)13:14
*** shardy_lunch is now known as shardy13:20
rakhmerovd0ugal: hi, what do you think about it ? https://review.openstack.org/#/c/421686/13:24
rakhmerovcan we let it in?13:25
rakhmerovbased on my reasoning here (see above)13:25
d0ugalrakhmerov: can we add it to the docs?13:26
rakhmerovhm...13:26
rakhmerovwhy not13:26
d0ugalJust a quick mention would do :)13:26
rakhmerovyep13:26
rakhmerovwe could say "useful for testing and try outs)13:26
d0ugalI don't think I understand when it would be useful lol13:27
* d0ugal reads up13:28
*** bobh has quit IRC13:28
d0ugalrakhmerov: how long have you been PTL?13:29
rakhmerov3 years13:29
d0ugallong time :)13:30
rakhmerovfrom the very beginning13:30
rakhmerovyes13:30
rakhmerov:)13:30
d0ugalrakhmerov: are you going to update that patch with docs now or should I merge it?13:31
rakhmerovI'd prefere separately13:31
rakhmerovI'll do it13:32
rakhmerovif it's ok13:32
d0ugalok13:32
d0ugalbut please do :)13:32
d0ugalI 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 good13:33
rakhmerovd0ugal: I have to agree with you13:56
rakhmerovyes13:56
rakhmerovalthough there can be a different point of view on this13:57
rakhmerove.g., I implemented a new feature but I don't want to expose it broadly yet13:57
rakhmerovsay I treat it experimental for the time being13:58
rakhmerovddeja: does this tell anything to you? http://logs.openstack.org/18/422518/2/check/gate-mistral-devstack-dsvm-ubuntu-xenial-nv/a154e88/console.html13:58
ddejarakhmerov: let me take a look13:59
rakhmerovif you have time13:59
rakhmerovjust thought maybe you saw a similar thing13:59
ddejarakhmerov: I've never seen something similar14:00
rakhmerovok14:02
rakhmerovI wonder if it's something worth rechecking..14:02
*** dprince has joined #openstack-mistral14:05
openstackgerritMerged openstack/mistral: Register Javascript action additionally as 'js' action  https://review.openstack.org/42122314:08
ddejarakhmerov: I'd say that every gate failure is worth checking14:11
ddejabut this one seems weird14:11
rakhmerovI rechecked14:11
rakhmerovwanna see if it helps14:11
ddejawell, it seems unrelated with the change itself14:12
ddejatestr return 2, instead of 0, when listing tests14:12
openstackgerritMerged openstack/mistral: Add action "std.test_dict"  https://review.openstack.org/42168614:31
d0ugalrakhmerov: then we should have an experimental part of the documentation for features we might change14:39
d0ugalrakhmerov: just releasing them and hoping people don't find them isn't a great idea14:40
*** ist has quit IRC14:45
*** sharatss has quit IRC14:53
*** dprince has quit IRC14:59
*** thrash is now known as thrash|biab15:01
*** bobh has joined #openstack-mistral15:05
*** rbrady has joined #openstack-mistral15:28
*** rbrady has quit IRC15:28
*** rbrady has joined #openstack-mistral15:28
*** jaosorior has joined #openstack-mistral15:31
*** dprince has joined #openstack-mistral15:47
*** tuan_ has quit IRC15:54
*** thrash|biab is now known as thrash15:55
*** bobh has quit IRC15:59
*** shardy has quit IRC16:00
*** shardy has joined #openstack-mistral16:01
thrashgot 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
thrashtrying 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
thrashI've also tried 'task(my_task).result[$.stack_name = $.stack].len() > 0' to no avail.16:14
thrashi get 'Can not evalutate YAQL expression'16:15
thrashI'm pretty sure it's because of the $.stack part of it.16:25
*** hrybacki is now known as hrybacki|afkish16:32
thrashnm..,16:33
thrashI think I have it. Went about it a different way. Testing...16:33
*** bobh has joined #openstack-mistral16:35
thrashok.. got it... $.stack in task(my_task).result.select($.stack_name)16:40
openstackgerritMerged openstack/mistral: using utcnow instead of now in expiration policy  https://review.openstack.org/42184216:53
openstackgerritMerged openstack/mistral: Make 'task' function work w/o a task name  https://review.openstack.org/42251816:56
*** jistr is now known as jistr|afk16:57
*** rbrady has quit IRC17:03
*** rbrady has joined #openstack-mistral17:15
*** shardy has quit IRC17:29
*** dturner has joined #openstack-mistral17:37
*** rbrady has quit IRC17:52
openstackgerritCorey Bryant proposed openstack/python-mistralclient: Fix doc build if git is absent  https://review.openstack.org/42278417:56
*** jistr|afk is now known as jistr18:01
*** bobh has quit IRC18:17
*** catinthe_ has joined #openstack-mistral18:18
*** catintheroof has quit IRC18:18
*** jpich has quit IRC18:22
*** weshay is now known as weshay_afk18:31
*** hrybacki|afkish is now known as hrybacki|sick18:40
*** rbrady has joined #openstack-mistral18:44
d0ugalthrash: nice18:52
d0ugalthrash: YAQL is a strange thing :)18:52
thrashd0ugal: yeah.. Just had to come at it from a different angle.18:53
*** bobh has joined #openstack-mistral18:56
*** thrash is now known as thrash|biab19:11
*** bobh has quit IRC19:28
*** dprince has quit IRC19:32
*** openstackgerrit has quit IRC19:33
*** rbrady has quit IRC19:46
*** rbrady has joined #openstack-mistral19:51
*** rbrady has quit IRC19:51
*** rbrady has joined #openstack-mistral19:51
*** rbrady has quit IRC20:03
*** thrash|biab is now known as thrash20:16
*** dprince has joined #openstack-mistral20:17
*** bobh has joined #openstack-mistral20:28
*** bobh has quit IRC20:33
*** bobh has joined #openstack-mistral21:22
*** dprince has quit IRC21:28
*** dprince has joined #openstack-mistral21:28
*** thrash is now known as thrash|g0ne21:37
*** bobh has quit IRC22:53
*** gyee has joined #openstack-mistral23:22
*** gyee has quit IRC23:36
*** jaosorior has quit IRC23:38
*** gyee has joined #openstack-mistral23:39

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!