| *** d0ugal__ has quit IRC | 00:58 | |
| *** harlowja has quit IRC | 00:58 | |
| *** d0ugal__ has joined #openstack-mistral | 01:00 | |
| *** EmilienM_ has joined #openstack-mistral | 03:43 | |
| *** rbrady has quit IRC | 03:44 | |
| *** doriftoshoes____ has quit IRC | 03:44 | |
| *** EmilienM has quit IRC | 03:44 | |
| *** EmilienM_ is now known as EmilienM | 03:44 | |
| *** EmilienM has quit IRC | 03:46 | |
| *** EmilienM has joined #openstack-mistral | 03:46 | |
| *** d0ugal__ has quit IRC | 03:52 | |
| *** d0ugal__ has joined #openstack-mistral | 04:14 | |
| *** harlowja has joined #openstack-mistral | 04:17 | |
| *** harlowja has quit IRC | 04:20 | |
| *** hardikjasani has joined #openstack-mistral | 04:26 | |
| *** d0ugal__ has quit IRC | 04:49 | |
| *** AlexeyAbashkin has joined #openstack-mistral | 04:49 | |
| *** Alexey_Abashkin has joined #openstack-mistral | 04:52 | |
| *** AlexeyAbashkin has quit IRC | 04:53 | |
| *** Alexey_Abashkin is now known as AlexeyAbashkin | 04:53 | |
| *** d0ugal__ has joined #openstack-mistral | 04:58 | |
| *** AlexeyAbashkin has quit IRC | 05:22 | |
| *** mcdoker181818 has joined #openstack-mistral | 06:06 | |
| rakhmerov | d0ugal__: hi | 06:17 |
|---|---|---|
| rakhmerov | https://review.openstack.org/#/c/477816 again failed on the TripleO gate | 06:18 |
| rakhmerov | what is the algorithm that I need to use to see what failed and where? | 06:18 |
| rakhmerov | what log files do I need to look at? | 06:18 |
| *** d0ugal__ has quit IRC | 06:26 | |
| rakhmerov | apetrich: hi, may be you can help understand that | 06:28 |
| rakhmerov | what exactly failed in http://logs.openstack.org/16/477816/8/check/tripleo-ci-centos-7-scenario003-multinode-oooq-container/e1abb77/ | 06:28 |
| apetrich | rakhmerov, looking | 06:29 |
| rakhmerov | apetrich: thanks! | 06:29 |
| rakhmerov | I seem to have fixed the previous problem (and added a test for it) but I'm surprised that something else failed now | 06:30 |
| apetrich | rakhmerov, what I usually do is first look at logs/undercloud/home/zuul/ and see if there's a overcloud_deploy.log.txt.gz if that file is there means that we had a successful undercloud deploy | 06:32 |
| rakhmerov | ok | 06:32 |
| apetrich | then I scroll down that file. if it succeeded that means that the overcloud deployed | 06:32 |
| apetrich | as it did | 06:32 |
| apetrich | so it might have been a tempest issue | 06:32 |
| rakhmerov | I rechecked anyway, may be it will help | 06:33 |
| rakhmerov | btw, I don't see this file in there | 06:34 |
| rakhmerov | apetrich: ^ | 06:34 |
| apetrich | so that's not a tempest gate so I'm now my system failed and now I'm looking all over the place to find what it failed :) | 06:34 |
| rakhmerov | oh, sorry, I do see it ) | 06:34 |
| apetrich | but those are usually my first steps on tripleo gates | 06:34 |
| rakhmerov | got it | 06:35 |
| rakhmerov | apetrich: so those mistral workflows run when the overcloud is being deployed, right? | 06:36 |
| rakhmerov | which means that the error is different now, not related to Mistral workflows? | 06:36 |
| apetrich | it says that the overcloud failed http://logs.openstack.org/16/477816/8/check/tripleo-ci-centos-7-scenario003-multinode-oooq-container/e1abb77/job-output.txt.gz#_2018-05-31_15_55_57_164641 | 06:37 |
| rakhmerov | aha | 06:37 |
| rakhmerov | I see | 06:37 |
| apetrich | not really | 06:37 |
| apetrich | yeah => so those mistral workflows run when the overcloud is being deployed | 06:38 |
| rakhmerov | ok | 06:39 |
| rakhmerov | apetrich: where can I see a log from Mistral? | 06:40 |
| apetrich | logs/undercloud/var/log/mistral/executor.log.txt.gz | 06:40 |
| rakhmerov | if it has errors they will tell me something I think | 06:40 |
| rakhmerov | ok | 06:40 |
| apetrich | i'm not seeing anything obvious | 06:43 |
| apetrich | another interesting place to look is logs/undercloud/var/log/extra/ specially errors.txt.gz | 06:43 |
| apetrich | that's where all ERROR logs from the system are collected | 06:44 |
| rakhmerov | ok | 06:45 |
| apetrich | it might be this Can not evaluate YAQL expression [expression=yaml_dump($.swift_message), error=cannot represent an object: {u'status': | 06:45 |
| apetrich | from here http://logs.openstack.org/16/477816/8/check/tripleo-ci-centos-7-scenario003-multinode-oooq-container/e1abb77/logs/undercloud/var/log/extra/errors.txt.gz#_2018-05-31_14_48_17_357 | 06:46 |
| rakhmerov | I see for sure that the previous error has gone | 06:47 |
| rakhmerov | which is good | 06:47 |
| rakhmerov | ooh | 06:47 |
| rakhmerov | nope, it's similar actually.. | 06:48 |
| rakhmerov | hah | 06:48 |
| *** d0ugal__ has joined #openstack-mistral | 06:48 | |
| rakhmerov | apetrich: yeah, thanks | 06:49 |
| apetrich | no worries. glad to be helpful :) | 06:49 |
| rakhmerov | interesting, it means I didn't fully fix the problem | 06:49 |
| apetrich | it looks like it is trying to do a yaml_dump on a python string of json object. is that it? | 06:55 |
| apetrich | not on. off* | 06:55 |
| apetrich | of* | 06:55 |
| * apetrich cna't type today | 06:55 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral master: Add YAQL engine options https://review.openstack.org/477816 | 07:00 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral master: Release note for adding YAQL engine options https://review.openstack.org/571481 | 07:00 |
| rakhmerov | apetrich: not sure exactly, I added a debug line to see what it is | 07:02 |
| *** jaewook_oh has joined #openstack-mistral | 07:09 | |
| rakhmerov | apetrich: according to the error message it can be either a dict or FrozenDict from YAQL. Both should be handled.. So I'm a little confused why this is happeninng | 07:17 |
| apetrich | it looks like a string from a converted dict | 07:18 |
| rakhmerov | apetrich: hm.. why a string? | 07:34 |
| rakhmerov | well, with strings there shouldn't be any problems too | 07:34 |
| apetrich | no. I'm wrong. It is an object | 07:35 |
| *** hardikjasani has quit IRC | 07:36 | |
| rakhmerov | apetrich: ok, I'll look at the debug and we'll see | 07:42 |
| rakhmerov | apetrich: btw, just a crazy thought.. Is it possible that the gate somehow took a older version of this YAQL function somehow? | 07:43 |
| rakhmerov | I understand it's not likely but who knows.. | 07:43 |
| rakhmerov | I remember something like that in the past.. Not sure though what it was exactly | 07:43 |
| *** rbrady has joined #openstack-mistral | 07:47 | |
| *** doriftoshoes____ has joined #openstack-mistral | 07:47 | |
| *** jpich has joined #openstack-mistral | 08:00 | |
| *** d0ugal__ has quit IRC | 08:03 | |
| *** AlexeyAbashkin has joined #openstack-mistral | 08:03 | |
| *** d0ugal has joined #openstack-mistral | 08:03 | |
| d0ugal | Morning folks | 08:04 |
| d0ugal | #startmeeting mistral | 08:04 |
| openstack | Meeting started Fri Jun 1 08:04:35 2018 UTC and is due to finish in 60 minutes. The chair is d0ugal. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:04 |
| *** openstack changes topic to " (Meeting topic: mistral)" | 08:04 | |
| openstack | The meeting name has been set to 'mistral' | 08:04 |
| d0ugal | Friday office hour! | 08:05 |
| d0ugal | Hows everyone doing? | 08:05 |
| d0ugal | rakhmerov, apetrich, bobh, mcdoker181818: PING | 08:05 |
| rakhmerov | I'm here | 08:05 |
| d0ugal | https://etherpad.openstack.org/p/mistral-office-hours | 08:05 |
| rakhmerov | but don't have much to update with ) | 08:05 |
| d0ugal | As usual, add your name to the ping list on line 16 if you want reminders ^ | 08:05 |
| rakhmerov | btw, I'm on vacation next week | 08:06 |
| d0ugal | rakhmerov: sure, that is fine :) | 08:06 |
| d0ugal | Nice :) | 08:06 |
| d0ugal | Are you going away somewher? | 08:06 |
| rakhmerov | yeah | 08:07 |
| rakhmerov | Turkey | 08:07 |
| d0ugal | oh, nice and warm I bet. | 08:07 |
| d0ugal | rakhmerov: did you manage to resolve the tripleo gate failure? | 08:08 |
| rakhmerov | not yet | 08:08 |
| rakhmerov | I added a debug line to see what I'm dealing with | 08:08 |
| rakhmerov | I thought I fixed it but it occurred again | 08:08 |
| rakhmerov | d0ugal: but it seems as if TripleO took an old yaml_dump() function | 08:10 |
| d0ugal | oh, strange | 08:10 |
| rakhmerov | not likely, I understand though.. | 08:10 |
| rakhmerov | yeah | 08:10 |
| d0ugal | Could be possible, but I'm not sure how :) | 08:10 |
| apetrich | o/ | 08:13 |
| d0ugal | rakhmerov: Can you set the Importance on https://bugs.launchpad.net/mistral/+bug/1774164 ? | 08:13 |
| openstack | Launchpad bug 1774164 in Mistral ""Create execution" API request may lead to creation of more than one workflow execution object" [Undecided,Confirmed] | 08:13 |
| rakhmerov | yes | 08:14 |
| d0ugal | It is our only untriaged bug :) | 08:14 |
| d0ugal | opetrenko_: Are you around? Did you want to chat about EBNF? | 08:14 |
| opetrenko_ | yes, want to chat about all the staff that can help newcomers quickly take apart mistral | 08:16 |
| d0ugal | staff? do you mean stuff? | 08:16 |
| rakhmerov | :)) | 08:17 |
| d0ugal | I am not very familiar with EBNF. I have never written it before at least, just read it a few times. | 08:18 |
| opetrenko_ | Yeah, stuff :) | 08:19 |
| opetrenko_ | I would like to document mistral dsl as detailed as possible | 08:20 |
| d0ugal | Yeah, that makes sense | 08:21 |
| rakhmerov | opetrenko_: usually EBNF is requested by someone who wants to write a parser for a language | 08:21 |
| rakhmerov | why do you think you need EBNF to understand the Mistral workflow language? | 08:21 |
| d0ugal | I wonder if we could generate something | 08:22 |
| rakhmerov | I think the spec is pretty detailed. Although I agree that there are some gaps | 08:22 |
| mcdoker181818 | Hi, all. Please take a look https://review.openstack.org/#/c/499790/ and https://review.openstack.org/#/c/569643/ | 08:22 |
| opetrenko_ | Probably, if we describe our dsl, adding new abilities to it will become much easier I guess | 08:23 |
| d0ugal | It does change sometimes, but not very often now. | 08:23 |
| opetrenko_ | Well, if you think it's not needed it's ok. We can just skip this topic. | 08:25 |
| d0ugal | I'm not sure we need EBNF exactly | 08:26 |
| d0ugal | However I do think a better description of the syntax would be useful. | 08:26 |
| d0ugal | I found it difficult originally and relied on looking at examples. | 08:26 |
| rakhmerov | opetrenko_: well it's kind of nice to have it (and I thought about adding it at some point) but haven't seen strong reasons so far | 08:26 |
| rakhmerov | d0ugal: yes | 08:26 |
| rakhmerov | agree | 08:26 |
| *** shardy has joined #openstack-mistral | 08:27 | |
| opetrenko_ | So we can discuss what should be documented | 08:27 |
| d0ugal | EBNF has a very specific purpose and it is good for that, but I don't think it will be easy for most new users to understand. | 08:28 |
| d0ugal | Are there any alternatives? | 08:28 |
| rakhmerov | d0ugal: yes, I think you're right :) From what I've seen, only computer science guru ever look at it ) | 08:31 |
| rakhmerov | so generally, we have a task to improve our doc and it also includes improving the language spec | 08:32 |
| d0ugal | Yeah | 08:32 |
| rakhmerov | we know that it has a number of issues: gaps, not the same style everywhere, not the best structure etc. | 08:32 |
| rakhmerov | but someone needs to volunteer to fix it at the end of the day ) | 08:33 |
| d0ugal | Indeed | 08:33 |
| opetrenko_ | agree | 08:33 |
| opetrenko_ | We can restructure our docs to make them more structured and verbose | 08:34 |
| d0ugal | Fixing the documentation is difficult. | 08:34 |
| rakhmerov | yeah | 08:34 |
| d0ugal | I have been trying to think of a prgamatic way to start working through it, but I don't have any great ideas. | 08:35 |
| d0ugal | We have a legacy documentation problem, it is hard to refactor :) | 08:35 |
| rakhmerov | the challenge is that it doesn't make a lot of sense to fix individual sections, we rather need to look at the docs as a whole and restructure it first | 08:35 |
| rakhmerov | and come up with the unified style etc. | 08:35 |
| d0ugal | rakhmerov: You were going to write a guideline for that style. | 08:35 |
| opetrenko_ | We would rather not refactor our docs but write new one | 08:35 |
| d0ugal | :) | 08:35 |
| rakhmerov | no, not for that style :) | 08:36 |
| rakhmerov | I was going to write a guideline for coding style ) | 08:36 |
| opetrenko_ | We can discuss the structure of docs, than create skeleton and after that fill out everything as verbose as possible | 08:36 |
| d0ugal | opetrenko_: true, do you want to propose a structure? :) | 08:37 |
| rakhmerov | opetrenko_: that may be a good idea. Write a structure of the new doc first, then start moving individual sections into it step by step applying the new rules | 08:37 |
| opetrenko_ | Wow, not so fast) | 08:37 |
| d0ugal | rakhmerov: for code style, I wish we just used Black https://pypi.org/project/black/) and then didn't have to worry about code style! | 08:37 |
| d0ugal | lol | 08:37 |
| rakhmerov | opetrenko_: what do you mean by "as verbose as possible"? | 08:37 |
| d0ugal | brb | 08:38 |
| d0ugal | "as detailed as possible" perhaps | 08:38 |
| rakhmerov | I mean "can you give an example where our docs are not verbose enough"? | 08:38 |
| opetrenko_ | I mean that we should write our docs the way that student of 3rd year comes looks at it and will understand how he can use it | 08:39 |
| opetrenko_ | afk for 5 mins | 08:39 |
| rakhmerov | d0ugal: I'll look at Black, may be it's ok | 08:39 |
| rakhmerov | opetrenko_: the goal is good, yes. Agree. I just found that the idea of the project itself is often hard to explain | 08:40 |
| rakhmerov | not even to students | 08:40 |
| rakhmerov | anyway, we've always had this idea in mind too. And we've actually improved docs significantly over the last 1-1.5 years | 08:41 |
| rakhmerov | so we keep improving it but yes, I agree, we need to restructure it soon | 08:41 |
| d0ugal | I keep wanting to propose a new documentation structure | 08:42 |
| d0ugal | but never get to doing it | 08:42 |
| opetrenko_ | I have an idea | 08:47 |
| opetrenko_ | Lets keep the structure of documentation that way | 08:47 |
| opetrenko_ | The first topic is quick overview of the project. Idea, purpose of the project. Some examples of what can you do with mistral, with some aka screenshots of results. | 08:49 |
| opetrenko_ | Next, we provide topics for each group of users. For devs, operators etc | 08:49 |
| d0ugal | Yup | 08:50 |
| d0ugal | We have talked about this a few times - we just need somebody with the time and motivation to do it :) | 08:50 |
| opetrenko_ | The first thing we should describe it the overview of the project. It can help encourage new user, devs to participate in life of mistral | 08:50 |
| opetrenko_ | IMO, the second thing should be dev guide. It's the crucial part to devs | 08:51 |
| opetrenko_ | If you come to project and cant get an idea of what's going on there, you are 50% to leave the idea to join | 08:52 |
| d0ugal | Sure | 08:52 |
| d0ugal | I think we all agree the documentation can and should be better. | 08:52 |
| d0ugal | The question is, how do we start working on it instead of just talking about it? | 08:53 |
| opetrenko_ | The dev guide should contain architecture of the project, explanation of project structure | 08:53 |
| d0ugal | and who can do the work? | 08:53 |
| opetrenko_ | I can try, but I'll need a lot of help, because I'm not familiar with mistral yet :) | 08:53 |
| d0ugal | Right | 08:53 |
| d0ugal | but being new also gives you a better insight into the problems. | 08:54 |
| opetrenko_ | Yeah, that's why I started doc topic | 08:54 |
| d0ugal | I think the first step is for somebody to try writing a documentation outline | 08:54 |
| d0ugal | What sections there should be and what should be in them | 08:55 |
| d0ugal | Then we can discuss that and hopefully agree on a structure | 08:55 |
| opetrenko_ | Yeah I can try do this, but still need some help from you guys | 08:55 |
| d0ugal | Sure | 08:55 |
| opetrenko_ | So where should I start describing skeleton? | 08:56 |
| opetrenko_ | probably some visualization feature can help in that | 08:56 |
| opetrenko_ | maybe we can try out some conference tool with ability to speak, make remarks and draw | 09:01 |
| d0ugal | opetrenko_: usually when we want to propose larger ideas like this we would propose a patch to the mistral-specs repo | 09:02 |
| d0ugal | https://github.com/openstack/mistral-specs | 09:02 |
| d0ugal | and then the discussion would happen via gerrit and code review. | 09:02 |
| opetrenko_ | ok | 09:03 |
| d0ugal | #endmeeting | 09:06 |
| *** openstack changes topic to " (Meeting topic: test)" | 09:06 | |
| openstack | Meeting ended Fri Jun 1 09:06:33 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:06 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/mistral/2018/mistral.2018-06-01-08.04.html | 09:06 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/mistral/2018/mistral.2018-06-01-08.04.txt | 09:06 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/mistral/2018/mistral.2018-06-01-08.04.log.html | 09:06 |
| d0ugal | That is the end of the office hour - I'll be around for the rest of the day however | 09:06 |
| d0ugal | openstack: if you want something less formal, you could start writing notes in a etherpad. | 09:14 |
| d0ugal | http://etherpad.openstack.org/ | 09:14 |
| opetrenko_ | And I have some ideas of what should better be done | 09:28 |
| *** d0ugal has quit IRC | 09:33 | |
| *** d0ugal has joined #openstack-mistral | 09:53 | |
| rakhmerov | apetrich, d0ugal: mistery :) http://logs.openstack.org/16/477816/9/check/tripleo-ci-centos-7-scenario003-multinode-oooq-container/7beaf58/logs/undercloud/var/log/mistral/engine.log.txt.gz#_2018-06-01_08_27_19_962 | 09:56 |
| rakhmerov | so it's a FrozenDict that I specifically check and transform | 09:56 |
| rakhmerov | but it still fails | 09:56 |
| rakhmerov | maybe it's wrapped in a different way somehow.. ok, will be looking at it | 09:57 |
| apetrich | damn | 09:57 |
| rakhmerov | yeah | 09:58 |
| rakhmerov | I was getting the same type in the unit test that I created | 09:58 |
| rakhmerov | after I added sanitizing it worked fine | 09:58 |
| rakhmerov | another theory is that it needs to be done recursively | 09:59 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral master: Add YAQL engine options https://review.openstack.org/477816 | 10:07 |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral master: Release note for adding YAQL engine options https://review.openstack.org/571481 | 10:07 |
| *** d0ugal has quit IRC | 10:16 | |
| *** d0ugal has joined #openstack-mistral | 10:25 | |
| *** thrash|g0ne is now known as thrash | 10:33 | |
| d0ugal | rakhmerov: That is interesting. | 10:43 |
| d0ugal | I'm starting to get curious enough to look :-D | 10:43 |
| *** hardikjasani has joined #openstack-mistral | 10:46 | |
| apetrich | it is very odd. I did a test and didn't get that | 10:52 |
| *** d0ugal has quit IRC | 11:06 | |
| *** d0ugal has joined #openstack-mistral | 11:23 | |
| *** apetrich has quit IRC | 11:29 | |
| *** apetrich has joined #openstack-mistral | 11:31 | |
| thrash | d0ugal: apetrich https://review.openstack.org/#/c/569876/ is ready | 11:35 |
| apetrich | thrash, thanks! I will look in a bit when I come back from lunch | 11:36 |
| thrash | apetrich: ack. thanks. | 11:36 |
| *** d0ugal has quit IRC | 11:53 | |
| *** d0ugal has joined #openstack-mistral | 11:59 | |
| *** d0ugal has quit IRC | 12:16 | |
| openstackgerrit | Oleksiy Petrenko proposed openstack/mistral-specs master: New more user friendly documentation for Mistral https://review.openstack.org/571710 | 12:26 |
| *** d0ugal has joined #openstack-mistral | 12:35 | |
| apetrich | thrash, you doing lisp now? $(($(cat .stestr/next-stream) - 1)) | 12:54 |
| apetrich | lgtm | 12:54 |
| * toure thinks lisp is cool | 12:54 | |
| thrash | apetrich: I didn't like the 3 lines... :D | 13:01 |
| opetrenko_ | d0ugal, rakhmerov: Well, some skeleton of skeleton of new documentation is ready | 13:24 |
| d0ugal | opetrenko_: That was fast! | 13:31 |
| d0ugal | thrash: Thanks! | 13:32 |
| opetrenko_ | it is just skeleton of skeleton | 13:32 |
| d0ugal | :) | 13:32 |
| d0ugal | Skeletons all the way down. | 13:32 |
| opetrenko_ | and it should be modified a lot | 13:32 |
| opetrenko_ | where should I publish it? | 13:33 |
| d0ugal | Sure, but it is a strating point. That is important. | 13:33 |
| d0ugal | opetrenko_: What format is it in? | 13:33 |
| d0ugal | opetrenko_: etherpad? email to openstack-dev? WIP patch to mistral-specs? | 13:33 |
| opetrenko_ | rst like that I can add on review to the main spec description | 13:34 |
| d0ugal | opetrenko_: sure, that works | 13:48 |
| rakhmerov | d0ugal, apetrich: so, I applied another fix, and it worked. The problem was that the structure that goes to YAQL functions can have nested internal types | 13:51 |
| apetrich | oh | 13:52 |
| rakhmerov | so registering another presenter in the YAML library helps | 13:52 |
| rakhmerov | yeah | 13:52 |
| rakhmerov | so please review and let me know if that's ok | 13:52 |
| *** hardikjasani has quit IRC | 13:59 | |
| apetrich | lgtm | 13:59 |
| d0ugal | rakhmerov: great, I'll take a look in a moment. | 14:02 |
| rakhmerov | ok, thanks | 14:03 |
| *** d0ugal has quit IRC | 14:31 | |
| *** d0ugal has joined #openstack-mistral | 14:35 | |
| d0ugal | rakhmerov: still here? | 14:41 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral stable/queens: Fix the README formatting https://review.openstack.org/571746 | 14:41 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral stable/pike: Fix the README formatting https://review.openstack.org/571747 | 14:41 |
| d0ugal | ^ we need these fixes to do releases. | 14:42 |
| d0ugal | I might just land them because they are so trivial | 14:42 |
| d0ugal | apetrich: ^ fancy doing a sanity check? | 14:42 |
| apetrich | d0ugal, looking | 14:43 |
| apetrich | too big of a change I might need until tuesday to test and +1 it | 14:44 |
| apetrich | :) | 14:44 |
| d0ugal | lol | 14:44 |
| d0ugal | apetrich: just updating the commit message. | 14:44 |
| apetrich | dang the pike change is twice as big as the queens one | 14:45 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral stable/pike: Fix the README formatting https://review.openstack.org/571747 | 14:46 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral stable/queens: Fix the README formatting https://review.openstack.org/571746 | 14:47 |
| apetrich | yeah it works | 14:48 |
| *** d0ugal has quit IRC | 14:49 | |
| *** d0ugal has joined #openstack-mistral | 14:57 | |
| *** gkadam has joined #openstack-mistral | 15:05 | |
| openstackgerrit | Kupai József proposed openstack/mistral master: A mechanism to close stuck running action executions https://review.openstack.org/527085 | 15:16 |
| *** gkadam_ has joined #openstack-mistral | 15:20 | |
| *** gkadam has quit IRC | 15:24 | |
| *** d0ugal has quit IRC | 15:34 | |
| *** jaosorior has quit IRC | 15:41 | |
| *** d0ugal has joined #openstack-mistral | 15:41 | |
| *** gkadam__ has joined #openstack-mistral | 15:46 | |
| *** d0ugal has quit IRC | 15:48 | |
| *** gkadam_ has quit IRC | 15:49 | |
| *** d0ugal has joined #openstack-mistral | 15:51 | |
| *** gkadam_ has joined #openstack-mistral | 15:52 | |
| *** gkadam__ has quit IRC | 15:55 | |
| *** jrist has quit IRC | 16:08 | |
| *** harlowja has joined #openstack-mistral | 16:11 | |
| *** jrist has joined #openstack-mistral | 16:25 | |
| *** gkadam__ has joined #openstack-mistral | 16:33 | |
| *** gkadam_ has quit IRC | 16:36 | |
| *** gkadam_ has joined #openstack-mistral | 16:37 | |
| *** EmilienM is now known as EvilienM | 16:40 | |
| *** gkadam__ has quit IRC | 16:40 | |
| *** gkadam__ has joined #openstack-mistral | 16:57 | |
| *** gkadam has joined #openstack-mistral | 17:00 | |
| *** gkadam_ has quit IRC | 17:00 | |
| *** AlexeyAbashkin has quit IRC | 17:02 | |
| *** jpich has quit IRC | 17:02 | |
| *** gkadam__ has quit IRC | 17:02 | |
| openstackgerrit | Merged openstack/mistral master: Add YAQL engine options https://review.openstack.org/477816 | 17:04 |
| openstackgerrit | Merged openstack/mistral stable/queens: Fix the README formatting https://review.openstack.org/571746 | 17:04 |
| openstackgerrit | Merged openstack/mistral stable/pike: Fix the README formatting https://review.openstack.org/571747 | 17:04 |
| *** gkadam has quit IRC | 17:18 | |
| *** thrash is now known as thrash|biab | 17:21 | |
| *** harlowja has quit IRC | 17:22 | |
| *** harlowja has joined #openstack-mistral | 18:14 | |
| *** thrash|biab is now known as thrash | 18:57 | |
| *** openstackgerrit has quit IRC | 19:04 | |
| *** d0ugal has quit IRC | 19:47 | |
| *** d0ugal has joined #openstack-mistral | 20:05 | |
| *** d0ugal has quit IRC | 21:08 | |
| *** d0ugal has joined #openstack-mistral | 21:15 | |
| *** EvilienM has quit IRC | 21:18 | |
| *** EmilienM has joined #openstack-mistral | 21:19 | |
| *** EmilienM is now known as EvilienM | 21:19 | |
| *** harlowja has quit IRC | 23:18 | |
| *** openstackgerrit has joined #openstack-mistral | 23:51 | |
| openstackgerrit | Merged openstack/mistral master: Switch to using stestr https://review.openstack.org/569876 | 23:51 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!