Wednesday, 2018-03-21

*** itlinux has joined #openstack-mistral00:12
*** AlexeyAbashkin has joined #openstack-mistral00:18
*** AlexeyAbashkin has quit IRC00:22
*** harlowja has quit IRC01:07
*** AlexeyAbashkin has joined #openstack-mistral01:18
*** AlexeyAbashkin has quit IRC01:22
*** pengdake has joined #openstack-mistral01:29
*** AlexeyAbashkin has joined #openstack-mistral02:18
*** AlexeyAbashkin has quit IRC02:23
*** zhurong has joined #openstack-mistral02:40
*** zhurong has quit IRC03:44
rakhmerovd0ugal: hi04:34
rakhmerovsorry, missed your last message04:34
*** harlowja has joined #openstack-mistral04:39
*** openstackgerrit has joined #openstack-mistral04:45
openstackgerritRenat Akhmerov proposed openstack/mistral master: Add a release note for the 'pause' command fix  https://review.openstack.org/55479404:45
*** harlowja has quit IRC04:56
*** hardikjasani has joined #openstack-mistral04:57
*** zhurong has joined #openstack-mistral06:05
*** gkadam has joined #openstack-mistral06:50
*** jaosorior has quit IRC07:05
apetrichrakhmerov, thanks for the release note07:12
rakhmerovnp )07:12
*** jaosorior has joined #openstack-mistral07:44
*** AlexeyAbashkin has joined #openstack-mistral07:55
d0ugalrakhmerov: np08:14
d0ugalrakhmerov: I was just going to show you a small tool I made08:14
d0ugalrakhmerov: http://paste.openstack.org/show/706040/08:14
d0ugalAllows you to easily see a execution and it's tasks, actions and sub-workflows08:14
d0ugalThe formatting isn't perfect, but I have found it really useful08:15
d0ugalIt just uses mistralclient08:15
*** danpawlik has joined #openstack-mistral08:15
danpawlikGood morning, I was checking puppet integration manifests and as I see in my PS https://review.openstack.org/#/c/552833/ package mistral-event-engine is partialy installed because of mistral-engine package is installed (im talking about Ubuntu). Is this a bug or not? I see that in RDO they doesn't have any error08:18
danpawlikand http://logs.openstack.org/33/552833/2/check/puppet-openstack-integration-4-scenario003-tempest-ubuntu-xenial/f480d58/logs/dpkg-l.txt.gz package has flags iF08:18
danpawlikzigo: maybe you know more details08:18
d0ugaldanpawlik: I believe it is an optional component, so that is probably why08:19
d0ugalbut honestly I am not that familiar with the mistral-event-engine. I have been asked about it a couple of times recently, so I guess I should learn :)08:20
rakhmerovd0ugal: aah, cool. Reminds me about one BP that's been in progress for a while now ;)08:21
d0ugalrakhmerov: indeed, I needed something sooner08:21
rakhmerovI see08:21
rakhmerovd0ugal: can you share it somewhere?08:22
d0ugalrakhmerov: https://github.com/d0ugal/tripleo-util/blob/master/scripts/wf-report08:22
rakhmerovok, thanks08:22
d0ugalrakhmerov: it is quite hacky, I'd like to tidy it up. I wonder if it would make sense as an addition to mistralclient08:22
d0ugalrakhmerov: I am not convinced we really need API changes for something like this - at least not for a first version08:22
d0ugal(we can change the API if we find some parts are too slow etc.)08:22
rakhmerovwell, yeah, I think we wanted API changed because we predicted performance problems mostly08:24
rakhmerovas far I as I remember08:24
rakhmerovbut as a prototype something like this would be enough for now08:24
pgaxatteo/ danpawlik, I asked recently about the event-engine :)08:24
d0ugalrakhmerov: right, but I don't think we need to add a new API endpoint - probably just add some options to what we have08:25
rakhmerovd0ugal: also, just letting you know that I won't be too active till the end of the week. Have to focus on some internal things for now08:25
d0ugalrakhmerov: sure08:25
*** mcdoker181818 has joined #openstack-mistral08:25
danpawlikgood :)08:27
danpawlikpgaxatte: I guess zigo is one of the person who can make some modification in debianization :P08:27
danpawlikpgaxatte: he is a master of Debian and debian packages08:28
zigodanpawlik: I can.08:44
zigodanpawlik: How may I help?08:45
zigodanpawlik: What you reported looks like an error in *Ubuntu*.08:46
zigoI do Debian ...08:47
zigoMy package switched to Python 3, they didn't in Ubuntu.08:47
zigoSo it becomes quite different these days.08:47
danpawlikzigo: wow, I was thinking that Canonical takes debianization from debian :P08:49
danpawlikzigo:08:49
zigodanpawlik: They did, but not for Queens, since I switched all to Python 3.08:50
danpawlikzigo: there is small change in package debianization, pgaxatte will send you08:50
zigodanpawlik: By all means, please do, I'd love to have more contribs ! :)08:50
zigoBTW, switching to Py3 was mostly painless, I'm happy I did that.08:50
zigoOnly manila-ui is completely broken, everything else just work ...08:51
pgaxattedanpawlik, zigo: actually my problem was about the event-engine which is not present on Debian08:52
danpawlikzigo: congrats !08:53
*** milind has joined #openstack-mistral08:58
openstackgerritMerged openstack/mistral master: Ensure workflow check is retried on DB error  https://review.openstack.org/54706908:59
milindhello, i am using openstack mistral for execution of workflows. The workflow consists of few actions. I have observed that the actions are taking time to invoke once the previous action execution completes. This is causing my project to slow down. Any idea how to troubleshoot this? Googled many things but didn09:00
*** jpich has joined #openstack-mistral09:02
*** zhurong has quit IRC09:04
zigopgaxatte: So, I should add a new mistral-event-engine package, together with init/systemd script and all?09:12
*** zhurong has joined #openstack-mistral09:13
pgaxattezigo: that would be nice :) I'm not sure I can submit anything with a guest account on salsa09:14
zigopgaxatte: I don't see any console-script with event-engine in setup.cfg09:14
zigopgaxatte: You can, you just do a pull request.09:15
pgaxattealright, I'll try to do that and report back09:15
zigopgaxatte: You can also join the openstack-team on Salsa, and I'll approve it, but then it's best if you do that on a branch.09:16
zigopgaxatte: Also join the packaging list here: https://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel/09:16
pgaxattezigo: no problem, for now I'll just stick with making a branch and once I'm done i'll ping you09:16
zigoCheers.09:17
*** mcdoker181818 has quit IRC09:18
d0ugalmilind: Which version of Mistral are you using?09:51
milindhow to check that ? is there any command.. i am using the mistral on docker container which i pulled from repo10:12
milind root@54582b021ef5:/# mistral --version mistral 3.1.210:13
milind3.1.210:13
d0ugalmilind: That is the python-mistralclient version. How did you install Mistral? You will need to check with the packaging you use10:20
d0ugalpip freeze | grep mistral10:20
d0ugalrpm -qa | grep mistral10:20
d0ugalor some debian command I forget :)10:21
rakhmerovd0ugal, apetrich, anyone else: who knows much about Python memory management?10:25
*** pengdake has quit IRC10:25
d0ugalrakhmerov: a bit, what is the question?10:25
rakhmerovsec..10:25
rakhmerovwe see the problem in production: Mistral processes take more and more memory over time reaching some really gigantic values like 20G10:26
d0ugalouch10:26
rakhmerovwe did a lot of tests in the past and concluded that Python objects are deallocated correctly10:26
rakhmerovit just seems like Python doesn't release memory correctly for some reason10:27
pgaxatterakhmerov: did you try with different python versions?10:27
rakhmerovand we didn't find any ways to limit its memory consumption (like Xmax parameter in Java)10:27
rakhmerovpgaxatte: yes, seems like Python 3 doesn't have this problem )10:27
d0ugalInteresting.10:27
rakhmerovat the first glance10:27
rakhmerovyeah10:27
rakhmerovMistral itself doesn't seem to leak10:28
d0ugalI think that could suggest we have some reference cycles - and Python 3 is smarter about detecting them10:28
d0ugalrakhmerov: oh, if mistral doesn't leak - what does?10:28
rakhmerovPython10:28
d0ugalHow do you know it isn't Mistral?10:28
rakhmerovI did tests that showed that a number of objects in Heap didn't grow over time (on similar API operations, for example) but the overall resident memory for the Python process was consistently growing10:29
d0ugalInteresting10:30
d0ugalrakhmerov: do you have your findings you can share somewhere?10:30
rakhmerovlocally on my Mac it was ok, the memory was freed up after it reached a certain value (~1G) but on our production it doesn't seem to happen10:30
rakhmerovd0ugal: no, I didn't keep them, it was about a year ago10:31
d0ugalrakhmerov: oh, a long time :)10:31
d0ugalrakhmerov: Is the mistral under heavy load? or how long has it been running?10:31
rakhmerovd0ugal: so the fundamental question: is there any way to limit memory consumption for a python process?10:31
d0ugalrakhmerov: I am trying to see how I can reproduce it10:31
d0ugalrakhmerov: I have never needed to put limits on a Python process before - so I am not sure.10:32
rakhmerovd0ugal: well, by repeating highly memory consuming operations (e.g. task-list when there's a lot of tasks)10:33
*** vienin has joined #openstack-mistral10:33
d0ugalEvery memory issue I have had has been in the user code - not Python itself :)10:33
rakhmerovok10:33
d0ugalrakhmerov: how many tasks would you consider lots? (just so I can test something similar)10:33
rakhmerovI'm not sure if that matters10:34
d0ugalok10:34
*** mcdoker181818 has joined #openstack-mistral10:34
rakhmerovas far as I remember, I was just doing something simple in the loop10:34
d0ugalI'll try that10:34
rakhmerov:)10:34
d0ugalrakhmerov: btw, I have had success with this in the past: https://mg.pov.lt/objgraph/10:34
milindok let me check10:34
d0ugalbut it has been a while.10:34
rakhmerovok, I thought may be you or some of your colleagues encountered something similar in the past10:35
rakhmerovd0ugal: yes, I used this lib too10:35
apetrichI've hit that before10:35
rakhmerovand some others10:35
apetrichbut never able to get a satisfying solution10:35
rakhmerovapetrich: ooh really?10:35
rakhmerovapetrich: what did you observe?10:36
apetrichpretty much that. we would release objects but python would keep memory10:36
rakhmerovyeah10:37
apetrichin the end we did what things like phusion would do that limit a run of a worker for that many tasks, kill and respawn it10:37
rakhmerovright10:37
vieninHi mistral team ! I'm just figuring out that "scope" property is not available for workbook creation, only for workflows. Is it requisite, or just missing ? Thanks for your pointers !10:37
rakhmerovwhat was the operating system?10:37
rakhmerovapetrich: ^10:37
apetrichlinux10:38
rakhmerovok, yep10:38
apetrichit was on our data gathering servers so ubuntu if I'm not mistaken10:38
rakhmerovI've read that on Win Python memory management works differently: it frees up memory immediately after gc.collect()10:38
apetrichI spent a silly amount of time drilling down that10:38
rakhmerovok10:38
rakhmerovme too )10:38
rakhmerovand now we're facing it again..10:39
rakhmerovvienin: I believe this is a bug, can you file it pls so that we don't lose it?10:39
apetrichI didn't test on win10:39
vienin(in way to create "public" workbooks through the api)10:39
rakhmerovvienin: gotcha10:39
vieninOk, you want I create the issue in launchpad, right ?10:40
rakhmerovvienin: you may also want to check our LP first, it seems to me that a similar bug may already exist10:40
rakhmerovvienin: yes10:40
d0ugalmilind: the versions you sent me are not for mistral-server - how did you install mistral?10:40
vieninOk, I found this issue https://bugs.launchpad.net/python-mistralclient/+bug/1746681 that can be related, but at all, do you have any other existing ticket in mind ?10:41
openstackLaunchpad bug 1746681 in python-mistralclient "Scope attribute not shown in List, Get operations" [Undecided,New] - Assigned to Theodoros Tsioutsias (ttsiouts)10:41
d0ugalvienin: I am not aware of a way to make a public workbook.10:42
d0ugalvienin: workbooks are not very useful in the API, having access to them doesn't give you anything really10:42
vieninOK my bad :) So do you recommend to do use the workbook api to register workflows ? No pb for us to do that, workbook are just used to gather workflow in a single file10:44
vienin*to not use10:44
milindd0ugal, i am using mistral via docker.. it was already present in the docker image. There are 3 docker images i am using for mistral. one is having mistral-api, one is hosting mistral-executor and one is having mistral-engine.10:44
d0ugalmilind: aha, are you using the docker config in mistral's git repo? if so, then you are using the git master version of mistral10:45
d0ugalvienin: we use workbooks to create our workflows, but we never really use the workbook api after that - we do everything with the workflow api10:45
d0ugalvienin: I guess the question I have is: what is it that you want to use the workbook api for?10:45
d0ugalvienin: when you create the workbook, is the scope for the workflow correct?10:46
rakhmerovd0ugal: yes but I see no reason why "scope" shouldn't be available at workbook creation10:46
d0ugalvienin: it does sound like you have spotted a bug - we should correct the scope for the workbooks10:46
d0ugalrakhmerov: agreed10:46
rakhmerovthe corresponding workflows could naturally inherit that scope10:46
vienin<d0ugal> We are using the worbook api for register all our workflows, but we want those workflow public, as we want they "exists" in all domains/projects10:47
vieninOk, make sens for us, can I report the issue and propose a fix ?10:48
rakhmerovvienin: sure, go ahead10:49
milindd0ugal: yes , i am using the docker config. The base repo listed is "mistral_base"10:49
rakhmerovwe'd appreciate that10:49
rakhmerovvienin: https://bugs.launchpad.net/python-mistralclient/+bug/1746681 is not exactly about this, so please file a new one10:50
openstackLaunchpad bug 1746681 in python-mistralclient "Scope attribute not shown in List, Get operations" [Undecided,New] - Assigned to Theodoros Tsioutsias (ttsiouts)10:50
vienin<rakhmerov> Ok10:51
d0ugalvienin: thanks!10:52
vienin<d0ugal> <rakhmerov> Thanks for your reactivity, see you !10:52
rakhmerovnp10:52
*** zhurong has quit IRC10:55
*** vienin has quit IRC11:00
*** katkapilatova has joined #openstack-mistral11:21
*** milind has quit IRC11:33
*** pengdake has joined #openstack-mistral11:58
*** dprince has joined #openstack-mistral12:06
d0ugalrakhmerov: I am trying hard, but failing to see my memory usage increase :)12:18
*** pengdake has quit IRC12:18
d0ugalI am running this, in 4 tmux panes....12:18
d0ugalwhile true; do mistral task-list --limit=-1 | wc -l; done12:18
d0ugaland I have almost 6k tasks now12:18
d0ugalI also have a loop creating new executions12:19
d0ugaleverything is getting quite slow :)12:19
*** dprince has quit IRC12:29
*** dprince has joined #openstack-mistral13:05
*** mcdoker181818 has quit IRC13:48
*** bobh has joined #openstack-mistral14:03
openstackgerritDougal Matthews proposed openstack/mistral master: [WIP] Experimental work adding a Zaqar event publisher  https://review.openstack.org/54766614:03
*** itlinux has quit IRC14:16
*** itlinux has joined #openstack-mistral14:17
*** gkadam_ has joined #openstack-mistral14:18
*** gkadam has quit IRC14:20
*** itlinux has quit IRC14:22
*** pengdake has joined #openstack-mistral14:45
*** pengdake has quit IRC15:00
*** thrash is now known as thrash|biab15:13
*** gkadam_ has quit IRC15:15
*** thrash|biab is now known as thrash15:43
*** itlinux has joined #openstack-mistral16:07
*** katkapilatova has quit IRC16:07
*** danpawlik has quit IRC16:11
*** itlinux has quit IRC16:15
*** AlexeyAbashkin has quit IRC16:29
*** danpawlik has joined #openstack-mistral16:37
*** thrash is now known as thrash|biab16:40
*** danpawlik has quit IRC16:42
*** itlinux has joined #openstack-mistral16:50
openstackgerritVitalii Solodilov proposed openstack/mistral master: Fixed the Mistral build job  https://review.openstack.org/55498716:52
openstackgerritVitalii Solodilov proposed openstack/mistral master: Fixed the Mistral Docker build job  https://review.openstack.org/55498716:56
*** bradjones has quit IRC17:03
*** danpawlik has joined #openstack-mistral17:07
*** danpawlik has quit IRC17:11
*** danpawlik has joined #openstack-mistral17:20
*** danpawlik has quit IRC17:25
*** jpich has quit IRC17:33
*** danpawlik has joined #openstack-mistral17:41
*** danpawlik has quit IRC17:45
*** thrash|biab is now known as thrash17:49
*** AlexeyAbashkin has joined #openstack-mistral18:03
*** danpawlik has joined #openstack-mistral18:12
*** danpawlik has quit IRC18:17
*** AlexeyAbashkin has quit IRC18:21
*** EmilienM is now known as mimi18:21
*** mimi is now known as EmilienM18:21
*** harlowja has joined #openstack-mistral18:24
*** hardikjasani has quit IRC18:28
*** danpawlik has joined #openstack-mistral18:52
*** danpawlik has quit IRC18:56
*** AlexeyAbashkin has joined #openstack-mistral19:17
*** AlexeyAbashkin has quit IRC19:21
*** dprince has quit IRC19:23
*** jaosorior has quit IRC19:23
*** dprince has joined #openstack-mistral19:23
*** danpawlik has joined #openstack-mistral19:29
*** danpawlik has quit IRC19:33
*** dprince has quit IRC19:43
*** jaosorior has joined #openstack-mistral19:44
openstackgerritKevin Pouget proposed openstack/mistral master: Add missing query paramater `scope` to the workbook api  https://review.openstack.org/55503019:47
*** danpawlik has joined #openstack-mistral20:02
*** danpawlik has quit IRC20:06
*** AlexeyAbashkin has joined #openstack-mistral20:18
*** AlexeyAbashkin has quit IRC20:22
*** jaosorior_ has joined #openstack-mistral20:33
*** danpawlik has joined #openstack-mistral20:33
*** jaosorior has quit IRC20:37
*** danpawlik has quit IRC20:38
*** danpawlik has joined #openstack-mistral21:07
*** danpawlik has quit IRC21:12
*** AlexeyAbashkin has joined #openstack-mistral21:17
*** AlexeyAbashkin has quit IRC21:21
openstackgerritVitalii Solodilov proposed openstack/mistral master: Add new indexes to optimize `task().result` expression function  https://review.openstack.org/55506621:41
*** fultonj has joined #openstack-mistral21:44
*** danpawlik has joined #openstack-mistral21:45
fultonjmy execution contains a task which runs a command, the command has returned 0 and i'd like my workflow to move on, however, task seems to be stuck in the running state21:45
*** rbrady is now known as rbrady-afk21:46
fultonjas my task is the last task, i tried telling the execution that everything is ok21:46
fultonjmistral execution-update -s SUCCESS $UUID21:46
fultonjthere's a longer story here, but i'm basically wondering if i can tell my workflow to move on21:49
*** danpawlik has quit IRC21:50
*** itlinux has quit IRC21:51
*** danpawlik has joined #openstack-mistral21:53
*** danpawlik has quit IRC21:57
*** danpawlik has joined #openstack-mistral22:24
*** danpawlik has quit IRC22:28
*** threestrands has joined #openstack-mistral22:29
*** threestrands has quit IRC22:30
*** threestrands has joined #openstack-mistral22:30
*** threestrands has quit IRC22:30
*** threestrands has joined #openstack-mistral22:30
*** bobh has quit IRC22:30
*** d0ugal has quit IRC22:34
*** d0ugal has joined #openstack-mistral22:37
*** thrash is now known as thrash|g0ne22:39
*** danpawlik has joined #openstack-mistral23:04
*** jtomasek has quit IRC23:08
*** danpawlik has quit IRC23:08
*** itlinux has joined #openstack-mistral23:20
*** danpawlik has joined #openstack-mistral23:39
*** danpawlik has quit IRC23:44

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