Wednesday, 2015-11-11

*** achanda has joined #openstack-mistral00:36
*** enykeev has quit IRC00:40
*** enykeev has joined #openstack-mistral00:41
*** tej has joined #openstack-mistral00:43
*** gyee has joined #openstack-mistral00:56
*** bobh has joined #openstack-mistral01:22
*** zhenguo has joined #openstack-mistral01:23
*** harlowja has quit IRC01:38
*** harlowja_ has joined #openstack-mistral01:38
xylan_kongRavikiran_K: hi, are you sure your token info is correct?02:13
openstackgerritMerged openstack/mistral: Fixing wf execution creation at initial stage  https://review.openstack.org/23963803:08
*** gyee has quit IRC03:23
*** bobh has quit IRC03:30
openstackgerritMerged openstack/mistral: Do not use len() in log_exec decorator  https://review.openstack.org/24369003:59
*** dmowrer has joined #openstack-mistral04:18
*** dmowrer has quit IRC04:23
*** achanda has quit IRC05:54
*** achanda has joined #openstack-mistral06:34
LimorStotlandHi all.06:40
LimorStotlandcan any one pleas review https://review.openstack.org/#/c/242996/ Thanks06:41
*** dmowrer has joined #openstack-mistral06:45
*** ^Gal^ has quit IRC06:45
*** ^Gal^ has joined #openstack-mistral06:49
*** dmowrer has quit IRC06:49
*** tshtilma has joined #openstack-mistral07:15
*** sergmelikyan has joined #openstack-mistral07:17
tshtilmahi ,  need another +2 for the bug fix https://review.openstack.org/#/c/240705/07:22
tshtilmaplease review07:22
^Gal^got you covered with the +2 thing07:29
^Gal^(just kidding)07:33
*** ninag has joined #openstack-mistral07:35
*** sergmelikyan has quit IRC07:39
*** ninag has quit IRC07:40
*** achanda has quit IRC07:51
*** LiatFried has joined #openstack-mistral07:54
*** achanda has joined #openstack-mistral07:57
*** ^Gal^ has quit IRC08:27
*** achanda has quit IRC08:36
*** achanda has joined #openstack-mistral08:39
openstackgerritGal Margalit proposed openstack/mistral-dashboard: UI: Task & Execution screen refactored  https://review.openstack.org/24366508:46
*** ^Gal^ has joined #openstack-mistral08:46
*** achanda has quit IRC08:57
*** dmowrer has joined #openstack-mistral09:13
*** dmowrer has quit IRC09:17
*** zhenguo has quit IRC09:56
*** LiatFried has quit IRC10:00
openstackgerritLingxian Kong proposed openstack/mistral: Add db model for resource sharing  https://review.openstack.org/24403010:00
rakhmerovmelisha, nmakhotkin, akuznetsova: hi guys, give me 2 mins and we'll start our bug review10:01
LimorStotlandHi all, is there a bug meeting now?10:01
nkoffmanHi10:01
nmakhotkinhi everyone10:01
*** [1]melisha has joined #openstack-mistral10:01
*** nastya has joined #openstack-mistral10:01
nastyahi there10:02
[1]melishanastya: Hi10:03
^Gal^hello10:03
rakhmerovhi again10:04
rakhmerovmy mac crashed unexpectedly ) Got scared of the bug meeting probably10:04
nastyaare we ready to start meeting?10:04
rakhmerovyes10:05
[1]melisha:-)10:05
rakhmerovlet me just forward a letter from Moshe that he sent me yesterday10:05
rakhmerovit has a list of bugs important for ALU10:05
rakhmerovdone10:07
rakhmerovyou all should have it now10:07
[1]melisharakhmerov: Thanks.10:07
nkoffmangot it, thx :)10:08
rakhmerovso before we start actually discussing bugs we need decide how we track bugs that need to be backported into stable/liberty10:08
rakhmerovis there a standard way of doing this you'd be aware of?10:08
rakhmerovI just thought we could create a wiki page for that, not sure we can do it well in Launchpad10:09
nastya@rakhmerov: yes10:09
[1]melisharakhmerov: I am not aware of any process. WIKI is fine by me. Maybe a tag in launchpad?10:09
rakhmerovwoow, melisha, great idea10:09
rakhmerovlet's try tags first10:10
rakhmerovok10:10
nastyaneed to create tag : liberty-backport-potential10:10
rakhmerovyes10:10
rakhmerovwhy potential?10:10
nastyaother project did it in this way10:10
rakhmerovooh, ok10:10
[1]melishaall: Just to put a context to our discussion. We have some customers that will use Mistral Liberty in production on live deployments in the next few months10:11
rakhmerovyes10:11
[1]melishaOur customers are very demanding in regard to stability and performance10:11
[1]melishaWe see it in our current live deployments and the tickets they open on Heat10:12
rakhmerovtrying to create a tag and for some reason I can't do it10:12
rakhmerovgive me a sec10:12
*** LiatFried has joined #openstack-mistral10:12
[1]melishaThey have huge huge stacks (>2500 nested stacks in one top level stack) and they are constantly working with the OpenStack APIs for querying and modifying10:13
rakhmerovok, done10:13
[1]melishaWe are still backporting important fixes into Kilo for them from time to time10:13
rakhmerov> 2500 staks?????!10:13
rakhmerovthat sounds scary10:14
[1]melishaYes. Crazy things. and we expect similar behaviors in Mistral :-)10:14
*** nastya_ has joined #openstack-mistral10:14
rakhmerovyeah, ok10:14
rakhmerovSo I created a new tag: liberty-backport-potential10:14
rakhmerovlet's use it10:14
*** nastya_ has quit IRC10:14
rakhmerovso let's quickly go over the list of bugs10:14
rakhmerovin the email10:15
rakhmerov1. Mistral stops responding after a few days that we haven't investigated / opened yet10:15
*** nastya_ has joined #openstack-mistral10:15
rakhmerov[1]melisha: any comments on that? What exactly stops responding?10:15
rakhmerovbtw, let's try to use regular meeting commands, they are supposed to work now10:16
[1]melisharakhmerov: Not much to do here yet. mistral-api is not responding to any request. The logs are not being written into10:16
rakhmerov#startmeeting Mistral Bug Review10:16
openstackMeeting started Wed Nov 11 10:16:18 2015 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot.10:16
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.10:16
openstackThe meeting name has been set to 'mistral_bug_review'10:16
rakhmerov1. Mistral stops responding after a few days that we haven't investigated / opened yet10:16
rakhmerovok10:16
*** nastya has quit IRC10:16
rakhmerovthen let's at least file a bug10:17
[1]melishaWe need to investigate further.10:17
rakhmerov#action melisha: File a bug for "Mistral stops responding after a few days that we haven't investigated / opened yet"10:17
[1]melishaCool10:17
rakhmerovok10:17
rakhmerov2. task stuck in RUNNING state when all action executions are finished - https://bugs.launchpad.net/mistral/+bug/151345610:17
openstackLaunchpad bug 1513456 in Mistral "task stuck in RUNNING state when all action executions are finished" [Critical,Triaged]10:17
rakhmerovOn this one, we came across it a number of times10:18
nkoffmanwe get this a lot, specifically when ruuning in HA mode, we see that all action-executions were sucessfull but the task doesn't en10:18
nkoffmanend10:18
nmakhotkinyes, I investigated that a little bit10:19
rakhmerovhave you done any investigation? Any assumption where the problem is?10:19
nastya_we also got it10:19
rakhmerovyes10:19
nmakhotkinthe potential problem is our transactions10:19
rakhmerovI assume that the issue is in transactions10:20
rakhmerovyes10:20
rakhmerovWinson also observed this behavior but in a different context10:20
rakhmerovnkoffman: do you know a reliable way of reproducing it?10:20
rakhmerovor at least increasing conditions that increase chances or reproducing it10:21
nkoffmanI saw it using a workflow with a task using with_items on HA,10:21
rakhmerovok10:21
nkoffmanI can try to reproduce on our node, haven't seen it on devstack though10:21
rakhmerovplease try to fill all info you have in bugs' comments10:21
rakhmerovok10:21
nkoffmanok10:21
nastya_nkoffman: I saw it in devsatck installation without any ha10:21
rakhmerovI can try to dig this task myself since I have a couple of thoughts how to track it down10:22
rakhmerovok10:22
nkoffmannastya_: I assume the HA might only bring it up more often10:22
rakhmerovyes, I guess so10:23
nastya_nkoffman: yeah, agree10:23
rakhmerovok, I assigned it to myself10:23
rakhmerovwill try to fix it10:23
rakhmerovsoon10:23
rakhmerovlet's continue10:23
rakhmerov2. Running WFs fail on failed to find system actions / workflows if DB sync is running in parallel - https://bugs.launchpad.net/mistral/+bug/150837910:24
openstackLaunchpad bug 1508379 in Mistral "Running WFs fail on failed to find system actions / workflows if DB sync is running in parallel" [Medium,In progress] - Assigned to Tomer Shtilman (tomer-shtilman)10:24
nastya_rakhmerov: you can use my env to debug where this problem was occured10:24
rakhmerovooh, sorry, it was #310:24
rakhmerovnastya_: ok, will talk to you once I get to working on it, thanks10:24
nmakhotkinthis one is being fixed in https://review.openstack.org/#/c/240705/10:25
rakhmerov[1]melisha, LimorStotland, nkoffman: so this happens if you need to reinstall one of Mistral instances?10:25
[1]melisharakhmerov: We all know the reason for this and Tomer is working on a fix with very responsive reviews from you all so that's OK10:26
nmakhotkinbut I'm not sure on 100%10:26
rakhmerovnmakhotkin: yes, this seems to be the right patch10:26
[1]melisharakhmerov: On production setups, there is a puppet agent that always makes sure that the VM is up-to-date10:27
rakhmerov#action: rakhmerov, nmakhotkin: review https://review.openstack.org/#/c/240705/10:27
rakhmerov[1]melisha: ok10:27
[1]melishaThis puppet agent runs every X minutes and compares conf files, etc. and also runs mistral syn db10:27
rakhmerovI see10:27
rakhmerovI'm just wondering.. Maybe we should change the whole algorithm of updating actions in DB10:28
rakhmerovw/o deleting them10:28
rakhmerovbut on the other hand, if we use transactions properly it should fix the problem10:28
rakhmerovok, let's move on10:28
[1]melishaIt will fix the problem10:28
rakhmerov4. Workflow executed more than once when using cron-trigger with multiple engines - https://bugs.launchpad.net/mistral/+bug/151354810:29
openstackLaunchpad bug 1513548 in Mistral "Workflow executed more than once when using cron-trigger with multiple engines" [High,In progress] - Assigned to Moshe Elisha (melisha)10:29
rakhmerovthis is being worked on10:29
rakhmerov[1]melisha: I still owe you a review, sorry10:29
[1]melishaYes10:29
[1]melishanp10:29
rakhmerov#action: rakhmerov: Review https://review.openstack.org/243234 ASAP10:30
rakhmerovok, guys, btw, just for the same of time saving I'm not tagging these tickets with the new tag10:30
rakhmerovI'll do it once we finish the meeting10:31
rakhmerov.. for the sake ...10:31
rakhmerovthe next one10:31
rakhmerov5. Some DB queries are reported slow as no indices are used - https://bugs.launchpad.net/mistral/+bug/150566410:31
openstackLaunchpad bug 1505664 in Mistral "Some DB queries are reported slow as no indices are used" [High,Confirmed] - Assigned to Winson Chan (winson-c-chan)10:31
rakhmerovthis one is assigned to Winson10:31
rakhmerovI'll help him fix that, it's pretty straightforward thing to do10:32
[1]melishaCool. Do you have an easy way to know the indexes that are needed?10:32
rakhmerov#action rakhmerov: tag all needed bugs with liberty-backport-potential10:32
[1]melishaor the queries that are executed?10:32
rakhmerov[1]melisha: yes, it's mostly in my head )10:33
rakhmerovIf I look at DB model I'll say exactly what should be indexed and what should not10:33
[1]melishaGreat10:33
rakhmerovof course, this doesn't cancel the need of some testing10:33
[1]melisha:-) Sure. We will help with that10:34
rakhmerov#action rakhmerov: put info into https://bugs.launchpad.net/mistral/+bug/1505664 about what exact indexes need to be created10:34
openstackLaunchpad bug 1505664 in Mistral "Some DB queries are reported slow as no indices are used" [High,Confirmed] - Assigned to Winson Chan (winson-c-chan)10:34
rakhmerov6. WF execution is not created if input preparation of initial task fails - https://bugs.launchpad.net/mistral/+bug/150647010:35
openstackLaunchpad bug 1506470 in Mistral "WF execution is not created if input preparation of initial task fails" [High,Fix committed] - Assigned to Nikolay Makhotkin (nmakhotkin)10:35
rakhmerovso here my question is: is this a bug at all?10:35
rakhmerovopinions?10:36
nmakhotkinthe fix is already commited10:36
nmakhotkinIMO, yes, it is a bug10:36
[1]melishaI think it is a bug. As I see it an execution should always be created10:36
nkoffmanI agree10:36
LimorStotlandme 210:36
rakhmerovalready committed? or merged?10:37
rakhmerovcan you please help me to find it?10:37
nastya_merged10:37
nmakhotkinfix commited in LP means that it is merged :)10:38
nastya_rakhmerov: https://review.openstack.org/#/c/239638/10:38
rakhmerovok, I can find it via the ticket10:38
rakhmerovyep, thanks10:38
rakhmerovok, great!10:39
rakhmerov#action rakhmerov: take a look at https://review.openstack.org/#/c/239638/ and backport it10:39
rakhmerov7. HTTP connection issues on simple load testing - https://bugs.launchpad.net/mistral/+bug/142305410:40
openstackLaunchpad bug 1423054 in Mistral mitaka "HTTP connection issues on simple load testing" [High,Triaged]10:40
[1]melishaIf the bug description is true - this will surely be an issue for our customers10:40
rakhmerovok, I'll just share what I know quickly10:41
rakhmerovwe discussed it a lot with StackStorm about 8 months ago and particularly with Winson10:41
rakhmerovnote that latest comment was made on 2015-02-1810:42
rakhmerovso, I'm almost sure this is not really a bug if we just consider Mistral codebase10:42
_gryf110:43
rakhmerovWinson told me that once they put Mistral behind Apache server or Nginx this issue stopped appearing completely10:43
rakhmerovthe thing is that if we use just an http server provided out of the box it's mostly intended to be used for development, not for production10:43
rakhmerovin other words, it can't really server a lot of parallel requests well and dies under even modest load10:44
[1]melishaOK. I see10:44
rakhmerovApache or Nginx help exactly with a big number of requests coming in in parallel10:44
[1]melishaso no need to backport10:45
rakhmerovjust in case, I'd suggest we talk to Winson again and clarify this information10:45
rakhmerov#action rakhmerov, [1]melisha: talk to Winson about https://bugs.launchpad.net/mistral/+bug/1423054 and confirm that this can be solved with putting Apache or Nginx in front of Mistral API server10:46
openstackLaunchpad bug 1423054 in Mistral mitaka "HTTP connection issues on simple load testing" [High,Triaged]10:46
rakhmerov8. execution-get truncates "State info" - https://bugs.launchpad.net/mistral/+bug/150945610:47
openstackLaunchpad bug 1509456 in Mistral "execution-get truncates "State info"" [Medium,Confirmed] - Assigned to hardik (hardik-parekh047)10:47
rakhmerov[1]melisha: can you confirm this bug too?10:48
rakhmerovor anyone else?10:48
rakhmerovI didn't see it myself10:48
nkoffmanwe didn10:48
nkoffman't10:48
nkoffmansee it either, but based on the description, it looks like it could be an issue, if it does happen10:49
rakhmerovI'm ready to bet that Mistral server doesn't truncate anything. If the problem exists it might be something on a client side10:49
nkoffmannmakhotkin:I see it is confirmed by10:49
rakhmerovooh, yes, nmakhotkin confirmed it10:50
nmakhotkinyep, I confirmed that10:50
rakhmerovok, then it should be something simple to fix10:50
nmakhotkinstate_info is really truncated10:50
rakhmerovlet's not spend time on that now, we just need to fix it10:50
rakhmerov9.   wait-before and retry policies directly call task_handler.run_existing_task() method via RPC - https://bugs.launchpad.net/mistral/+bug/148452110:51
openstackLaunchpad bug 1484521 in Mistral "wait-before and retry policies directly call task_handler.run_existing_task() method via RPC" [High,In progress] - Assigned to Renat Akhmerov (rakhmerov)10:51
rakhmerovYes, this is definitely a bug but it's more like an architectural bug10:51
nkoffmanwhat are the consequences of this bug to users?10:52
rakhmerovwe've discovered it with Limor together while improving Scheduler10:52
rakhmerovno consequences I'd be able to tell about actually10:52
rakhmerovit's rather an ugly design10:52
rakhmerovand it requires some serious refactoring in engine and policies10:53
rakhmerovnot sure we need to backport it actually10:53
LimorStotlandyes, we have a bp on  improving Scheduler:https://blueprints.launchpad.net/mistral/+spec/fallback-mechanism-for-scheduler10:53
nkoffmanok, so in that case, probably unnecessary to backport10:53
rakhmerovyes, I think we need to make a design improvement for Mitaka10:54
rakhmerovit'll require I think a couple of weeks for me to fix it properly10:54
nkoffmanok10:54
LimorStotlandI think if it doesn't have any effect on the user and its risky we shouldn't backport10:54
rakhmerovI assigned to myself to M-2 for now10:55
rakhmerovyes, it is risky a little bit because, as I said, it's not just a simple change, it's rather a refactoring10:55
rakhmerovof engine and policies10:55
rakhmerovwhich I'd love to do personally but it's pretty time consuming10:56
rakhmerov10.  Wrong execution state with conditional transitions - https://bugs.launchpad.net/mistral/+bug/151093610:56
openstackLaunchpad bug 1510936 in Mistral "Wrong execution state with conditional transitions" [High,Fix committed] - Assigned to Nikolay Makhotkin (nmakhotkin)10:56
nmakhotkinthis one is fixed already10:57
rakhmerovok, cool10:57
nkoffmanwe haven't tried to reproduce it on our set up yet, but again based on description, we will need the fix10:57
rakhmerovneeds to be backported I think10:57
nmakhotkinone thing, this bug is not completely fixed (case of on-complete is uncovered)10:58
rakhmerovyes, it was definitely a bug, we discussed it with Nikolay before10:58
nkoffmanok, so we need to backport it10:58
rakhmerov#action nmakhotkin: fix https://bugs.launchpad.net/mistral/+bug/1510936 completely and backport all related patches10:58
openstackLaunchpad bug 1510936 in Mistral "Wrong execution state with conditional transitions" [High,Fix committed] - Assigned to Nikolay Makhotkin (nmakhotkin)10:58
rakhmerov:)10:58
rakhmerov11. create pagination for the mistral client (This should be treated like a bug) - https://blueprints.launchpad.net/python-mistralclient/+spec/pagination-execution-mitralclient (This is mandatory as after a few days of work there is no way to get the execution list anymore).10:59
LimorStotlandi am missing one more +2 : https://review.openstack.org/#/c/242996/11:00
rakhmerov#action rakhmerov: review https://review.openstack.org/#/c/242996/ and backport it into stable/liberty11:01
rakhmerovno questions on that, this is really a bad thing11:01
LimorStotlandand then i think we need to backported  it because users with croon-trigers can use execution-list without it11:01
rakhmerovI wish we could spend more time polishing such things11:01
rakhmerovLimorStotland: sure, agree on 100%11:01
LimorStotlandcool :-)11:02
rakhmerov12. Add ceilometer apis as mistral actions - https://blueprints.launchpad.net/mistral/+spec/mistral-ceilometer-actions (This is not mandatory but we have some use cases that require this).11:02
rakhmerovas we discussed at the team meeting this is pretty easy to implement11:03
rakhmerovnmakhotkin can do it in 10 mins ;)11:03
nkoffmanyes, I did it on our installation as a POC,11:03
nmakhotkin:D11:03
[1]melishain 11 mins11:03
nkoffman:)11:03
rakhmerov:)11:03
[1]melishaor was it 9 mins?11:03
rakhmerovok, a serious question: who will be working on it? nmakhotkin or nkoffman?11:04
nkoffmanI can take it11:04
rakhmerovok11:04
nkoffmanis it ok for backporting?11:05
nmakhotkinok11:05
rakhmerovthen I'll tag it properly as well to backport it11:05
rakhmerovalright, we ran out of time already actually11:05
nkoffmangreat :)11:05
nastya_do we really need to backport it? it is not so critical bug11:05
rakhmerovvery productive meeting I think11:05
rakhmerovnastya_: good question11:06
rakhmerov[1]melisha, nkoffman: what do you think guys?11:06
nastya_actually it ia a new feature11:06
[1]melishanastya_: You are right. It is not even a bug11:06
nkoffmanthis is indeed not critical, however since this is a low risk, and usefull for our customers, it would be helpfull if backported11:06
[1]melishaYes. But so easy impl will make some really cool use cases possible11:06
LimorStotlandI don't think it mandatory for backport but it can be nice11:06
[1]melishaBut up to you to decide11:07
rakhmerovmy perspective: it's pretty easy to backport and if it brings some comfort for your customers then let's do this11:07
rakhmerov[1]melisha: completely agree11:07
rakhmerovcustomers' happiness first11:07
[1]melisha:-)11:07
LimorStotlandit have no risk and it can be very useful no way not?11:07
rakhmerovyes11:07
rakhmerovok, are we good now?11:08
nastya_ok, if it is not risky, then let's do it11:08
nkoffmanyes11:08
rakhmerovany other questions?11:08
LimorStotlandyep11:08
nkoffmanI have a request,11:08
nkoffmannot regarding the meeting though..11:08
rakhmerovlet me end the meeting then11:09
rakhmerovand we'll continue to talk11:09
rakhmerov#endmeeting11:09
openstackMeeting ended Wed Nov 11 11:09:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)11:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/mistral_bug_review/2015/mistral_bug_review.2015-11-11-10.16.html11:09
nkoffmansure11:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/mistral_bug_review/2015/mistral_bug_review.2015-11-11-10.16.txt11:09
openstackLog:            http://eavesdrop.openstack.org/meetings/mistral_bug_review/2015/mistral_bug_review.2015-11-11-10.16.log.html11:09
nkoffmanI created a blueprint in heat to improve the mistral workflow type and how it is signaled, if you guys can take a look and review it would be very helpful. https://blueprints.launchpad.net/heat/+spec/mistral-wf-signal-json-format11:10
rakhmerovok11:11
rakhmerovjust add us as reviewers11:12
rakhmerovat least myself and nmakhotkin11:12
nkoffmanok, will do, thanks11:12
rakhmerovwe'll look at it and, if needed, will add someone else who knows Heat better11:12
nkoffmanthat would be great11:14
rakhmerovnkoffman: yeah, actually Heat's PTL is now a guy from Mirantis ;)11:16
rakhmerovSerkey Kraynev )11:17
rakhmerovSergey11:17
rakhmerovmelisha, nkoffman, LimorStotland: here's a list of bugs we need to backport: https://bugs.launchpad.net/mistral/+bugs?field.tag=liberty-backport-potential11:20
[1]melisharakhmerov: That's great! Thanks!11:22
[1]melishaShould we also tag the 2 BPs?11:22
nastya_afaik, bps do not have tags11:24
rakhmerov[1]melisha: looks like there's no tags for BPs :(11:24
rakhmerovyes11:24
rakhmerovI added comments in them to do so11:25
[1]melishaOh. OK.11:25
[1]melishaThanks11:25
rakhmerovM-1 now looks like: https://launchpad.net/mistral/+milestone/mitaka-111:28
rakhmerovneed to try hard to get this all done11:28
[1]melisha:-) Yes.11:29
rakhmerovall, I added a link at https://wiki.openstack.org/wiki/Meetings/MistralAgenda (at the bottom) to our today's meeting log/minutes11:30
rakhmerovjust in case11:30
rakhmerovwe need to have these meetings regularly I think11:30
[1]melisharakhmerov: Yes. It was very helpful and productive11:33
rakhmerov[1]melisha: agree )11:33
*** nitzikow has joined #openstack-mistral11:35
openstackgerritMerged openstack/python-mistralclient: Create pagination for the mistral client  https://review.openstack.org/24299611:36
*** nitzikow_ has joined #openstack-mistral11:38
*** nitzikow has quit IRC11:38
*** nitzikow_ has quit IRC11:39
*** nitzikow has joined #openstack-mistral11:39
*** tej has joined #openstack-mistral11:48
*** nitzikow has quit IRC11:49
*** nitzikow has joined #openstack-mistral11:49
*** nitzikow has quit IRC11:51
*** nitzikow has joined #openstack-mistral11:51
*** nitzikow has quit IRC11:52
*** nitzikow has joined #openstack-mistral11:53
*** nastya_ has quit IRC11:55
*** tej has quit IRC11:58
*** dmowrer has joined #openstack-mistral12:08
openstackgerritGal Margalit proposed openstack/mistral-dashboard: UI: Task & Execution screen refactored  https://review.openstack.org/24366512:24
*** nitzikow has quit IRC12:27
*** nitzikow has joined #openstack-mistral12:27
openstackgerritGal Margalit proposed openstack/mistral-dashboard: UI: Task & Execution screen refactored  https://review.openstack.org/24366512:30
*** openstackgerrit has quit IRC12:31
*** openstackgerrit has joined #openstack-mistral12:32
*** nitzikow has quit IRC12:44
*** nitzikow has joined #openstack-mistral12:45
openstackgerritTomer Shtilman proposed openstack/mistral: Wrap sync_db operations in transactions  https://review.openstack.org/24070512:46
openstackgerritTomer Shtilman proposed openstack/mistral: Wrap sync_db operations in transactions  https://review.openstack.org/24070512:46
openstackgerritTomer Shtilman proposed openstack/mistral: Wrap sync_db operations in transactions  https://review.openstack.org/24070512:48
openstackgerritTomer Shtilman proposed openstack/mistral: Wrap sync_db operations in transactions  https://review.openstack.org/24070512:50
openstackgerritTomer Shtilman proposed openstack/mistral: Wrap sync_db operations in transactions  https://review.openstack.org/24070512:50
*** bobh has joined #openstack-mistral12:53
*** bobh has quit IRC12:59
*** ^Gal^ has quit IRC13:00
*** ^Gal^ has joined #openstack-mistral13:03
*** tshtilma has quit IRC13:13
*** achanda has joined #openstack-mistral13:15
openstackgerritGal Margalit proposed openstack/mistral-dashboard: UI: Task & Execution screen refactored  https://review.openstack.org/24366513:16
*** achanda has quit IRC13:19
*** ninag has joined #openstack-mistral13:37
*** nitzikow has quit IRC13:52
*** LiatFried has quit IRC13:55
*** ^Gal^ has quit IRC14:08
*** melisha has quit IRC14:08
*** [1]melisha is now known as melisha14:08
*** melisha is now known as 16WAAQN4M14:15
*** ^Gal^ has joined #openstack-mistral14:15
*** melisha has joined #openstack-mistral14:15
*** Piet has quit IRC14:17
*** dmowrer has quit IRC14:19
*** Piet has joined #openstack-mistral14:25
*** Piet has quit IRC14:40
*** bradjones|away is now known as bradjones14:40
*** dmowrer has joined #openstack-mistral14:44
*** bobh has joined #openstack-mistral14:46
*** tej has joined #openstack-mistral14:52
*** [1]melisha has joined #openstack-mistral14:52
*** ^Gal^ has quit IRC14:55
*** melisha has quit IRC14:55
*** [1]melisha is now known as melisha14:55
*** tej has quit IRC14:55
*** tej has joined #openstack-mistral14:57
*** ^Gal^ has joined #openstack-mistral14:59
*** tej has quit IRC15:00
*** LiatFried_ has joined #openstack-mistral15:05
*** tshtilma has joined #openstack-mistral15:15
openstackgerritLingxian Kong proposed openstack/mistral: Add db operations for resource members  https://review.openstack.org/24415415:18
openstackgerritLingxian Kong proposed openstack/mistral: [WIP] Support workflow sharing  https://review.openstack.org/24415515:18
nkoffmanHi everyone, I proposed a blueprint and implementation regarding signaling os::mistral::workflow type, to make it compatible with other systems. if anyone could review it would be great. https://blueprints.launchpad.net/heat/+spec/mistral-wf-signal-json-format15:34
*** tonytan4ever has joined #openstack-mistral15:44
*** tej has joined #openstack-mistral15:50
*** tej has quit IRC15:51
*** ninag has quit IRC16:00
*** ninag has joined #openstack-mistral16:00
*** Piet has joined #openstack-mistral16:01
*** openstackgerrit has quit IRC16:02
*** openstackgerrit has joined #openstack-mistral16:02
*** LiatFried_ has quit IRC16:03
*** LiatFried_ has joined #openstack-mistral16:03
*** tonytan4ever has quit IRC16:04
*** ninag has quit IRC16:05
*** ninag has joined #openstack-mistral16:06
*** ninag has quit IRC16:08
*** ninag has joined #openstack-mistral16:08
*** 16WAAQN4M has quit IRC16:17
*** gyee has joined #openstack-mistral16:28
*** tshtilma has quit IRC16:32
*** tej has joined #openstack-mistral16:34
*** LiatFried_ has quit IRC16:37
openstackgerritLingxian Kong proposed openstack/mistral: Removing wait() when initializing notification listener  https://review.openstack.org/24314616:38
*** tonytan4ever has joined #openstack-mistral17:01
*** dmowrer has quit IRC17:10
*** dmowrer has joined #openstack-mistral17:28
*** tshtilma has joined #openstack-mistral17:40
*** nitzikow has joined #openstack-mistral17:43
*** tshtilma has quit IRC17:44
*** tej has quit IRC17:45
*** Ravikiran_K has quit IRC17:45
*** tej has joined #openstack-mistral17:48
*** achanda has joined #openstack-mistral17:54
*** achanda has quit IRC17:58
*** tonytan4ever has quit IRC17:58
*** achanda has joined #openstack-mistral18:00
*** ninag has quit IRC18:02
*** ninag has joined #openstack-mistral18:02
*** ninag_ has joined #openstack-mistral18:04
*** ninag has quit IRC18:06
*** harlowja_ has quit IRC18:08
*** ninag_ has quit IRC18:09
*** ninag has joined #openstack-mistral18:18
*** nitzikow has quit IRC18:20
*** harlowja has joined #openstack-mistral18:42
*** harlowja_ has joined #openstack-mistral18:44
*** harlowja has quit IRC18:44
*** dmowrer has quit IRC18:49
*** dmowrer has joined #openstack-mistral18:50
*** LiatFried_ has joined #openstack-mistral18:53
*** dmowrer has quit IRC18:54
*** Piet has quit IRC19:01
*** tonytan4ever has joined #openstack-mistral19:06
*** achanda has quit IRC19:16
*** Piet has joined #openstack-mistral19:33
*** achanda has joined #openstack-mistral19:34
*** LiatFried_ has quit IRC19:35
*** LiatFried_ has joined #openstack-mistral19:38
*** dmowrer has joined #openstack-mistral19:41
*** achanda has quit IRC19:42
*** tonytan4ever has quit IRC20:26
*** LiatFried_ has quit IRC20:38
*** nitzikow has joined #openstack-mistral20:42
*** dmowrer has quit IRC20:42
*** tej has quit IRC20:42
*** dmowrer has joined #openstack-mistral20:42
*** tej has joined #openstack-mistral20:43
*** tonytan4ever has joined #openstack-mistral20:46
*** nitzikow has quit IRC20:46
*** tej has quit IRC20:46
*** dmowrer has quit IRC20:47
*** dmowrer has joined #openstack-mistral21:00
*** dmowrer has quit IRC21:02
*** dmowrer has joined #openstack-mistral21:03
*** tej has joined #openstack-mistral21:24
*** bobh has quit IRC21:47
*** bobh has joined #openstack-mistral21:48
*** bobh has quit IRC21:53
*** achanda has joined #openstack-mistral21:53
*** achanda has quit IRC22:05
*** ninag has quit IRC22:08
*** ninag has joined #openstack-mistral22:08
*** ninag has quit IRC22:13
*** bobh has joined #openstack-mistral22:20
*** achanda has joined #openstack-mistral22:33
*** dmowrer has quit IRC22:36
*** dmowrer has joined #openstack-mistral22:37
*** ninag has joined #openstack-mistral22:38
*** tej has quit IRC22:38
*** dmowrer has quit IRC22:41
*** achanda has quit IRC22:42
*** tej has joined #openstack-mistral22:50
*** tej has quit IRC22:53
*** ninag has quit IRC22:57
*** ninag has joined #openstack-mistral22:57
*** ninag has quit IRC23:02
*** Piet has quit IRC23:06
*** Piet has joined #openstack-mistral23:25
*** tej has joined #openstack-mistral23:38
*** tej has quit IRC23:50

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