Thursday, 2016-05-19

*** rena9067 has quit IRC00:05
*** bobh has quit IRC00:07
*** gyee has quit IRC00:08
*** gyee has joined #openstack-mistral00:08
*** harlowja_ has joined #openstack-mistral00:11
*** rbrady has quit IRC00:12
*** harlowja has quit IRC00:15
*** bobh has joined #openstack-mistral00:33
*** gyee has quit IRC00:34
*** gyee has joined #openstack-mistral00:34
openstackgerritWinson Chan proposed openstack/mistral: Fix get task list on YAQL error in with-items  https://review.openstack.org/31839100:43
*** ninag has joined #openstack-mistral00:57
*** cheneydc has joined #openstack-mistral00:59
*** ninag has quit IRC01:02
openstackgerritWinson Chan proposed openstack/mistral: Fix get task list on YAQL error in with-items  https://review.openstack.org/31839101:42
*** toddjohn_ has joined #openstack-mistral01:45
*** toddjohn_ has quit IRC01:50
*** bobh has quit IRC01:57
*** ge has joined #openstack-mistral02:01
*** bobh has joined #openstack-mistral02:35
*** toddjohn_ has joined #openstack-mistral02:46
*** toddjohn_ has quit IRC02:51
*** bobh has quit IRC02:58
*** bobh has joined #openstack-mistral02:58
*** bobh has quit IRC03:04
*** chlong has joined #openstack-mistral04:04
*** ninag has joined #openstack-mistral04:06
*** ninag has quit IRC04:10
*** toddjohn_ has joined #openstack-mistral04:48
*** toddjohn_ has quit IRC04:52
*** cheneydc has quit IRC05:07
*** cheneydc has joined #openstack-mistral05:10
*** chlong has quit IRC05:17
*** chlong has joined #openstack-mistral05:31
*** gyee has quit IRC05:56
*** Ravikiran_K has joined #openstack-mistral06:02
*** chlong has quit IRC06:05
*** chlong has joined #openstack-mistral06:22
*** toddjohn_ has joined #openstack-mistral06:49
*** toddjohn_ has quit IRC06:54
*** chlong has quit IRC06:54
openstackgerritMerged openstack/mistral: Fix get task list on YAQL error in with-items  https://review.openstack.org/31839107:16
*** ak_ has joined #openstack-mistral07:18
*** ninag has joined #openstack-mistral07:32
*** ninag has quit IRC07:37
hparekhmflobo, rakhmerov, Hi we have  BP for including policy. json file https://blueprints.launchpad.net/mistral/+spec/mistral-customize-authorization07:38
*** toddjohn_ has joined #openstack-mistral07:50
*** dmk0202 has joined #openstack-mistral07:50
*** toddjohn_ has quit IRC07:54
*** shm_ has joined #openstack-mistral08:01
*** shardy has joined #openstack-mistral08:05
rakhmerovhparekh: ok08:09
mflobohparekh, thanks for the link08:34
*** shm_ has quit IRC09:01
*** venkat has joined #openstack-mistral09:05
*** shm_ has joined #openstack-mistral09:08
*** Qiming has joined #openstack-mistral09:18
mfloborakhmerov, please let me know when is ok for you to ask about Mistral, thanks in advance09:18
*** shm_ has quit IRC09:19
ak_a09:40
rakhmerovmflobo: ok, what would you like to know?09:44
mfloborakhmerov, I have a set of questions, I don't if you'd prefer send them to you via email09:44
rakhmerovmflobo: whatever you prefer09:45
rakhmerovyou can send them by email, I'll answer then and then we can talk about details here09:45
rakhmerovor directly here )09:46
rakhmerovI'm ok with everything09:46
*** Ravikiran_K has quit IRC09:46
kongrakhmerov: did you sort out how to config upper-constraints.txt in CI?09:47
rakhmerovkong: well, readme in openstack/requirements repo says that enforcing upper constraints in tox based jobs is not completed yet09:48
kong...09:48
mflobohere is faster, so, there I go09:48
kongrakhmerov: so, this is community...09:48
kongopen source09:48
rakhmerovkong: I guess we can do it ourselves by just configuring tox jobs to use "pip install" with -c option09:49
rakhmerovbut we need to fetch right upper-constraints.txt, I mean from a right branch (stable, master etc.)09:49
mfloborakhmerov, Mistral has a lot of cool things, I'd like to know the "not cool" things of Mistral. Things to be careful we I want to put this service in production09:49
rakhmerovkong: I doubt about how exactly we should do it09:49
kongrakhmerov: I noticed upper-constraints.txt also has different stable branches, shouldn't it already been used in CI?09:50
rakhmerovI don't think that fetching upper-constraints.txt from github every time we run tox is a good idea09:50
rakhmerovkong: that's what I'm talking about, it's not implemented yet09:50
rakhmerovthose jobs are out of our control09:50
kongrakhmerov: ok09:50
rakhmerovkong: but somehow we need to enforce them09:51
rakhmerovkong: I asked Doug about it in ML, let's wait for his answer09:51
kongmy colleague also met with this kind of problem :-)09:51
rakhmerovyeah09:51
*** toddjohn_ has joined #openstack-mistral09:51
ak_@rakhmerov https://blueprints.launchpad.net/mistral/+spec/exponential-retry-strategy09:51
ak_Create a blue print as u asked me09:52
ak_let me know if you me to change anything09:52
rakhmerovmflobo: Mistral is obviously mostly cool! :)09:52
rakhmerovmflobo: but you're right09:52
ak_*if you want me to change*09:52
rakhmerovthe biggest thing that we need to improve is working with multiple engine instances09:52
rakhmerovHA09:52
kongmflobo: hi, if mistral is cool or not, depends on your requirement to it09:52
rakhmerovand varios kinds of recovery scenarios, aka failover09:52
rakhmerovkong: good point, yes09:53
rakhmerovak_: thanks!09:53
mfloborakhmerov, I see. What is the problem right now about HA of engine instances?09:54
kongmflobo: so, let talk about your requirments09:54
kongmflobo :-)09:54
rakhmerovak_: BP looks good09:54
ak_ok cool09:54
mflobokong, good HA is a requirement for me :)09:54
ak_@mflobo if engine gets killed there is a possibility that task is stuck in running state :(09:55
kongmflobo hah09:55
rakhmerovmflobo: there's a number of dangerous windows and so if something crashes while in them it may be hard to recover09:55
rakhmerovak_: true, we discussed it, recently09:55
rakhmerovthe good news is that we're working hard to improve that09:56
*** toddjohn_ has quit IRC09:56
rakhmerovmyself and other people in the team09:56
rakhmerovexcuse me, have to step out for 20-30 min09:56
mfloborakhmerov, I see. Could you please give and example of those "dangerous windows" if something crashes?09:57
mfloborakhmerov, np09:57
rakhmerovmflobo: I will when I'm back..09:57
ak_cool09:57
*** cheneydc has quit IRC10:00
*** mgershen has quit IRC10:07
*** mgershen has joined #openstack-mistral10:21
rakhmerovmflobo: an example of a bad situation: Mistral engine sent an action to Mistral Executor and executor is running it but it crashed in the middle10:22
rakhmerovone thing that we can do is to use message acknowledgements in rabbit so that such messages would be returned to queue10:22
rakhmerovbut oslo.messaging that we rely on does not support that, it has only at-most-once delivery10:23
rakhmerovwe need at-least-once10:23
rakhmerovddeja from our team is about to start working to fix that10:23
rakhmerovby just using direct access to rabbit10:24
*** d0ugal has quit IRC10:24
rakhmerovif that's solved it may not be a silver bullet as well because such actions ideally need to be idempotent10:24
rakhmerovso that they can be relaunched repeatedly in a safe manner10:25
rakhmerovbut that's a matter of how users write actions10:25
rakhmerovsimilar thing may happen when executor sends an action result back to engine10:25
rakhmerovengine may poll the message from queue but when it starts updating all persistent stuff in DB (workflow execution, task executions, action executions) then transaction may roll back or just crash due to DB inaccessitility10:26
rakhmerovthen we'll get a situation when message doesn't exist in the queue already but it's not effectively processed by engine10:27
*** d0ugal has joined #openstack-mistral10:28
rakhmerovso these two situations are bad ones that we're aware of10:28
*** Qiming has quit IRC10:29
rakhmerovthere's also a number of places where we need to improve performance10:30
rakhmerove.g. in API layer there are some unnecessary object conversions10:30
rakhmerovour DB transactions could made shorter as well (this is being currently worked on)10:30
rakhmerovmflobo: any questions on that?10:31
*** d0ugal has quit IRC10:31
*** d0ugal has joined #openstack-mistral10:31
*** mgershen2 has joined #openstack-mistral10:53
*** mgershen3 has joined #openstack-mistral11:13
*** mgershen2 has quit IRC11:15
*** mgershen2 has joined #openstack-mistral11:16
*** mgershen2 has quit IRC11:17
*** mgershen2 has joined #openstack-mistral11:18
*** mgershen4 has joined #openstack-mistral11:21
*** mgershen4 has quit IRC11:22
*** Qiming has joined #openstack-mistral11:23
*** mgershen3 has quit IRC11:29
mfloborakhmerov, I see11:30
*** michal_ has joined #openstack-mistral11:31
mfloborakhmerov, about the engine and HA. Does it work fine?11:31
mfloboI mean, Does the engine scales fine?11:31
rakhmerovyes11:33
mflobook11:33
rakhmerovit's stateless11:33
mfloboSo, the engine sounds like a important key in the mistral infra, right?11:34
*** ninag has joined #openstack-mistral11:34
rakhmerovyes, it's a core of the system11:34
rakhmerovwhere all complicated stuff happens11:34
rakhmerovso, overall, I would put it this way: Mistral doesn't have serious design issue but there's a number of places and corner cases where we need to improve it11:35
*** michal_ is now known as mgershen511:35
rakhmerovI would say you should try to use it and see how to configure it for your particular case11:36
rakhmerovdepending on what you need11:36
rakhmerovand it'll be improving consistently all the time11:36
mfloborakhmerov, I see11:36
mfloborakhmerov, Ok, I think my question about "not cool things" and HA is solved11:37
*** ninag has quit IRC11:38
rakhmerovok11:38
mfloborakhmerov, now, about asynchronous/synchronous executions. asynchronous/synchronous are for Workflows or for actions?11:38
rakhmerovI hope I didn't disappoint you too much11:38
mflobosorry, for workflows or for tasks?11:38
mfloborakhmerov, not at all :)11:39
rakhmerovcan you pls explain what you mean by sync/async?11:39
rakhmerovfor workflows and tasks11:39
rakhmerovthere are sync and async actions, true11:39
mfloboin this presentation http://www.slideshare.net/RenatAkhmerov/mistral-openstack-meetup-feb-5 slide 811:40
mfloboyou mean sync and async is possible for tasks only, right?11:41
rakhmerovooh11:45
rakhmerovsec..11:45
rakhmerovok, I was just trying to recall what I told in that presentation11:46
rakhmerovso technically, task is an action + a little bit more (managing transitions, workflow context state etc.)11:47
rakhmerovso yes, tasks may both async and sync depending on its action11:47
*** mgershen3 has joined #openstack-mistral11:47
rakhmerovsync action is that one that executor sends a result for immediately after its completion11:48
*** mgershen5 has quit IRC11:48
*** mgershen has quit IRC11:48
rakhmerovif an action is async then executor doesn't send a result back to engine and let a 3rd party do it later via Mistral API11:48
rakhmerovthat's the whole difference11:48
rakhmerovfrom engine perspective all tasks are asynchronous11:49
rakhmerovengine doesn't care who sends action result, Mistral Executor or something else11:49
rakhmerovas far as workflows, they are always asynchronous, meaning that there isn't any component in the system that waits for workflow completion11:50
*** toddjohn_ has joined #openstack-mistral11:53
*** mgershen2 has left #openstack-mistral11:54
*** mgershen has joined #openstack-mistral11:56
*** mgershen has left #openstack-mistral11:56
*** mgershen has joined #openstack-mistral11:56
*** mgershen3 has quit IRC11:57
*** toddjohn_ has quit IRC11:57
*** mgershen4 has joined #openstack-mistral11:59
mfloborakhmerov, understood12:02
mfloborakhmerov, last question,12:02
mfloborakhmerov, mistral has a lot of built-in actions... Is there any webpage with the full action list?12:03
*** mgershen has left #openstack-mistral12:03
*** mgershen has joined #openstack-mistral12:03
*** mgershen2 has joined #openstack-mistral12:10
*** mgershen has left #openstack-mistral12:11
*** mgershen2 has left #openstack-mistral12:11
*** mgershen4 has quit IRC12:11
rakhmerovmflobo: it's http://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#system-actions12:13
rakhmerov+ a bunch of OpenStack related actions12:14
rakhmerov~ a thousand12:14
rakhmerovfor Nova, Neutron, Heat etc.12:14
mfloborakhmerov, yea, I know that link. But I was looking for "the full" list, the same result of "$mistral action-list" command12:15
*** mgershen2 has joined #openstack-mistral12:18
*** mgershen has joined #openstack-mistral12:18
*** mgershen2 has left #openstack-mistral12:19
*** mgershen has left #openstack-mistral12:19
*** mgershen has joined #openstack-mistral12:19
*** mgershen has left #openstack-mistral12:19
*** mgershen has joined #openstack-mistral12:19
*** dprince has joined #openstack-mistral12:20
*** mgershen has left #openstack-mistral12:21
*** mgershen has joined #openstack-mistral12:21
rakhmerovit's not published anywhere, sorry12:21
mfloborakhmerov, ok, thank you very much for you time and attention :)12:22
rakhmerovyou're welcome12:22
*** mgershen has left #openstack-mistral12:23
*** mgershen has joined #openstack-mistral12:23
*** SAshish___ has joined #openstack-mistral12:29
SAshish___Hi All12:29
SAshish___Need help in running mistral tempest12:29
SAshish___can some one tell me how to run mistral FTs with tempest12:29
SAshish___I have checked the tempest code is with mistral repo12:29
*** Ravikiran_K has joined #openstack-mistral12:33
SAshish___Need help in running mistral tempest12:34
*** toddjohn_ has joined #openstack-mistral12:34
*** ninag has joined #openstack-mistral12:38
*** venkat has quit IRC12:42
mgershenSAshish: I didn't have a chance to run tempest tests.12:43
mgershenSAshish: Did you read instructions here: https://github.com/openstack/mistral/blob/master/mistral_tempest_tests/README.rst12:43
*** ninag has quit IRC12:43
*** ninag_ has joined #openstack-mistral12:47
mfloboI have a question about this workflow http://paste.openstack.org/show/497705/ and the "find_given_vm" action12:49
mfloboIn "find_given_vm" action, the "on-error" event points to "succeed" task... but "succeed" does not exists in the workflow? is it correct?12:50
mgershenmflobo: yes. This is the blueprint that added this option: https://blueprints.launchpad.net/mistral/+spec/mistral-engine-instructions12:57
mflobomgershen, but the "suceed" task does not exist in the YAML file12:58
mflobos/suceed/succeed12:58
mgershenthis is a reserved word to mark the workflow as successful. I think "fail" to fail the workflow is more commonly used12:58
*** toddjohn_ has quit IRC12:58
mflobomgershen, I see12:58
mgershenyou can use the validate workflow to see if the workflow is legal. /v2/workflows/validate12:59
mgershenfor your WF the result is:13:00
mgershen{ "valid": true}13:00
mgershenif you change the key word to "notkeyword" the result of validation will be:13:01
mgershen{  "valid": false,  "error": "Task 'notkeyword' not found."}13:01
mfloboBTW, this YAML example in official documentation http://docs.openstack.org/developer/mistral/terminology/workflows.html#yaml-example does not pass the validation...13:02
*** ak_ has quit IRC13:04
*** LimorStotland has joined #openstack-mistral13:11
mgershenwhat is the response? what version are you using? it passes on my devstack on master branch...13:16
*** bobh has joined #openstack-mistral13:19
mflobomgershen, sorry, you are right, I got my example from other place (probably old)13:21
mgershennp :)13:21
*** rbrady has joined #openstack-mistral13:22
mfloboMore questions (today I'm on fire :) )13:25
mflobothe mistralclient syntax for create an execution13:26
mflobois like: $ mistral execution-create workflow_identifier [workflow_input] [params]13:26
mgershengive me 2 minutes, I need to restart IRC13:26
*** mgershen has quit IRC13:26
*** mgershen has joined #openstack-mistral13:27
mflobomgershen, np13:27
mgershenI'm back13:27
mflobook13:27
mfloboso13:27
mfloboUsually I do: $mistral execution-create my_workflow my_workflow_parameters.json13:27
mfloboand ir works, but I was wondering which is [params] in the CLI syntax13:28
mflobos/ir/it13:28
mgershenare you using an empty file?13:29
mflobono, I don't13:29
mfloboso, for my  [workflow_input] means the JSON file with parameters13:30
mflobobut [params] I don't know what it means?13:30
mgershenyou mean the 3d positional parameter in the cli?13:31
mfloboyes13:32
mgershenThe main feature for that file is using it as a place for more parameters, usually more environment related.13:35
mflobomgershen, ok13:35
mflobomgershen, I guess it's not possible to do something like: $mistral execution-create my_worflow "{"param1": "valueparam1"}", right?13:36
mgershenin the file you can define under "env" anything you like and then you can read it from the workflow using yaql "<% env() %>"13:36
mgershenparams is a positional, so it has to be 3d...13:37
mgershenI will show you an example of the content13:37
mgershenhttp://paste.openstack.org/show/497712/13:39
mgershenand if you want to use the url from the params file inside the workflow you can use yaql: "<% env().url %>"13:41
mflobomgershen, ok, I see, thanks13:42
*** toddjohn_ has joined #openstack-mistral13:42
mfloboIs there any git repo or something where people share their YAML workflows? it'd be nice :)13:46
*** toddjoh__ has joined #openstack-mistral13:46
*** toddjohn_ has quit IRC13:47
openstackgerrithardik proposed openstack/mistral-specs: Meaningful message for fail/success/pause transition  https://review.openstack.org/27550113:49
openstackgerrithardik proposed openstack/mistral: Fail/Success/Pause transition message  https://review.openstack.org/27662513:49
openstackgerrithardik proposed openstack/mistral: Fail/Success/Pause transition message  https://review.openstack.org/27662513:52
mflobomgershen, do you know any issue about execute a workflow that is always in RUNNING state? I have this workflow http://paste.openstack.org/show/497716/. when I execute the workflow, no errors in the logs and the VM is created, but the execution created is always in RUNNING state13:54
mgershenyou can see some document mistral examples in the mistral wiki page here: http://docs.openstack.org/developer/mistral/dsl/dsl_v2.html13:54
mgershenalso there are some examples in this git repo that is manages by StackStorm: https://github.com/StackStorm/st2/tree/master/contrib/examples/actions/workflows13:54
mgershenwhat is the response when you do mistral task-list <EXECUTION_ID>13:59
mgershen?13:59
*** ninag_ has quit IRC14:02
*** ninag has joined #openstack-mistral14:03
*** ninag_ has joined #openstack-mistral14:05
*** ninag has quit IRC14:07
*** toddjoh__ has quit IRC14:16
*** toddjohn_ has joined #openstack-mistral14:17
*** toddjohn_ has quit IRC14:21
*** ninag_ has quit IRC14:32
mflobothe response is the task info, with State to RUNNING14:34
mflobomgershen, actually, I have an error log file related to mistral-engine http://paste.openstack.org/show/497730/14:48
*** tonytan4ever has joined #openstack-mistral14:49
*** toddjohn_ has joined #openstack-mistral14:50
*** rena9067 has joined #openstack-mistral14:55
*** dprince has quit IRC14:56
*** rena9067_ has joined #openstack-mistral14:56
*** dprince has joined #openstack-mistral14:56
*** ninag_ has joined #openstack-mistral14:56
*** rena9067 has quit IRC14:59
*** shardy has quit IRC15:07
rbradyI'm looking for any info / assistance with running mistral api with apache+wsgi instead of eventlet.  https://bugs.launchpad.net/mistral/+bug/158164915:18
openstackLaunchpad bug 1581649 in Mistral "Action Execution Response Timeout" [High,New]15:18
*** zaneb has joined #openstack-mistral15:18
*** ninag_ has quit IRC15:21
*** dmk0202 has quit IRC15:33
mgershenrbrady: if you don't find someone to answer you by next week, you can join the mistral weekly meeting and raise this issue there. IRC meetings on #openstack-meeting weekly on Mondays at 16:00 UTC.15:37
*** toddjohn_ has quit IRC15:37
*** ninag has joined #openstack-mistral15:37
mgershenrbrady: more info on meetings: https://wiki.openstack.org/wiki/Meetings/MistralAgenda15:37
mgershenmflobo: sorry, I had to step away. However I try running the WF on my devstack and it finished. can you do mistral action-list?15:39
*** dprince has quit IRC15:40
*** toddjohn_ has joined #openstack-mistral15:41
*** dprince has joined #openstack-mistral15:41
rbradymgershen: thanks.  I have been attending meetings.  Brought up this issue in last weeks meeting.  http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-05-16-16.01.html15:43
rena9067_i have a general workflow question: is it possible to have a conditional beyond just on-success/on-error? I.e. If task a publishes x, then do task b.15:47
mgershenrbrady: Right totally forgot, sorry.15:49
mgershenrena9067_: yes, it is possible.15:50
mgershenrena9067_: see here - http://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#transitions-with-yaql-expressions15:52
rena9067_wonderful, thank you mgershen!15:53
mgershennp :)15:53
*** xenthree3 has joined #openstack-mistral15:54
*** xenthree3 has left #openstack-mistral15:54
*** Qiming has quit IRC15:54
*** dprince has quit IRC15:58
*** dprince has joined #openstack-mistral15:59
*** shadow has joined #openstack-mistral16:01
*** shadow is now known as Guest5528516:01
*** Guest55285 is now known as shadow1216:02
*** ninag has quit IRC16:11
*** ninag has joined #openstack-mistral16:12
*** toddjohn_ has quit IRC16:15
*** toddjohn_ has joined #openstack-mistral16:15
*** dprince has quit IRC16:16
*** ninag has quit IRC16:16
shadow12test16:17
*** toddjohn_ has quit IRC16:20
*** vishwanathj has joined #openstack-mistral16:22
*** ninag has joined #openstack-mistral16:26
*** tonytan4ever has quit IRC16:28
*** tonytan4ever has joined #openstack-mistral16:33
*** ninag has quit IRC16:35
*** dprince has joined #openstack-mistral16:36
*** ninag has joined #openstack-mistral16:36
*** ninag has quit IRC16:36
*** ninag has joined #openstack-mistral16:36
*** ninag has quit IRC16:41
*** ninag has joined #openstack-mistral16:54
*** ninag has quit IRC16:59
*** ninag_ has joined #openstack-mistral17:02
*** ninag_ has quit IRC17:05
*** ninag has joined #openstack-mistral17:05
*** toddjohn_ has joined #openstack-mistral17:37
*** tonytan4ever has quit IRC17:45
vgnbkrHi Guys.  I'm trying to get Trove working with Mistral and am running into a problem.  The "trove list" api returns an object which implements the builtin methods to support interation; mistral complains that the result is not of type "List".  Is this expected?  I ask because "glance list" returns a generator which is supported.17:53
vgnbkrDid you intend to support any iterable, or just collections that are lists?17:54
*** tonytan4ever has joined #openstack-mistral17:57
*** rena9067_ has quit IRC18:02
*** toddjohn_ has quit IRC18:09
*** toddjohn_ has joined #openstack-mistral18:10
*** ninag has quit IRC18:15
*** ninag has joined #openstack-mistral18:16
*** ninag has quit IRC18:17
*** ninag has joined #openstack-mistral18:18
*** dprince has quit IRC18:18
*** ninag has quit IRC18:24
*** ninag has joined #openstack-mistral18:25
*** zaneb has quit IRC18:26
*** ninag has quit IRC18:27
*** ninag has joined #openstack-mistral18:28
*** rena9067 has joined #openstack-mistral18:28
*** zaneb has joined #openstack-mistral18:29
*** zhenguo_ has quit IRC18:30
*** zhenguo_ has joined #openstack-mistral18:34
*** ninag has quit IRC18:42
*** toddjohn_ has quit IRC18:58
*** toddjohn_ has joined #openstack-mistral19:00
*** ninag has joined #openstack-mistral19:01
*** toddjohn_ has quit IRC19:04
*** ninag has quit IRC19:37
*** ninag has joined #openstack-mistral19:38
*** ninag has quit IRC19:42
*** gyee has joined #openstack-mistral20:02
*** Ravikiran_K has quit IRC20:30
*** ninag has joined #openstack-mistral20:39
*** dmk0202 has joined #openstack-mistral20:39
*** tonytan4ever has quit IRC20:51
*** ninag has quit IRC21:14
*** dmk0202 has quit IRC21:22
*** bobh has quit IRC22:37
*** ninag has joined #openstack-mistral22:38
*** ninag has quit IRC22:41
*** Qiming has joined #openstack-mistral23:11
*** toddjohn_ has joined #openstack-mistral23:42
*** toddjohn_ has quit IRC23:47

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