| *** catintheroof has joined #openstack-mistral | 00:00 | |
| *** catintheroof has quit IRC | 00:01 | |
| *** harlowja has quit IRC | 00:04 | |
| *** catintheroof has joined #openstack-mistral | 00:04 | |
| *** bobh has quit IRC | 00:09 | |
| *** bobh has joined #openstack-mistral | 00:13 | |
| *** bobh has quit IRC | 00:21 | |
| *** bobh has joined #openstack-mistral | 00:24 | |
| *** bobh has quit IRC | 00:30 | |
| *** catintheroof has quit IRC | 00:33 | |
| *** catintheroof has joined #openstack-mistral | 00:39 | |
| *** bobh has joined #openstack-mistral | 00:56 | |
| *** bobh has quit IRC | 00:58 | |
| *** catintheroof has quit IRC | 01:09 | |
| *** thrash is now known as thrash|g0ne | 01:10 | |
| *** zhurong has joined #openstack-mistral | 01:50 | |
| *** jamielennox is now known as jamielennox|away | 02:03 | |
| *** zhurong has quit IRC | 02:07 | |
| *** openstackgerrit has joined #openstack-mistral | 02:14 | |
| openstackgerrit | Merged openstack/mistral master: Refactor Kombu-based RPC https://review.openstack.org/457123 | 02:14 |
|---|---|---|
| *** jamielennox|away is now known as jamielennox | 02:17 | |
| *** bobh has joined #openstack-mistral | 03:13 | |
| openstackgerrit | Lingxian Kong proposed openstack/mistral master: Add "running_region" param for OpenStack actions https://review.openstack.org/460351 | 03:14 |
| *** bobh has quit IRC | 03:16 | |
| *** bobh has joined #openstack-mistral | 03:21 | |
| rakhmerov | rbrady: yes, sure | 03:29 |
| *** zhurong has joined #openstack-mistral | 03:37 | |
| *** zhurong has quit IRC | 03:40 | |
| *** bobh has quit IRC | 03:41 | |
| *** chlong has joined #openstack-mistral | 04:23 | |
| openstackgerrit | Renat Akhmerov proposed openstack/mistral-lib master: Update serialization from 'mistral' repo with latest changes https://review.openstack.org/461986 | 04:32 |
| *** zhurong has joined #openstack-mistral | 04:37 | |
| openstackgerrit | Merged openstack/mistral master: Add support for mistral-lib to Mistral https://review.openstack.org/453517 | 04:40 |
| *** sharatss_ has joined #openstack-mistral | 04:55 | |
| openstackgerrit | Sharat Sharma proposed openstack/python-mistralclient master: Use keystoneauth plugins and session instead of keystoneclient https://review.openstack.org/455174 | 05:21 |
| *** jaosorior_away is now known as jaosorior | 06:19 | |
| *** gongysh has joined #openstack-mistral | 06:21 | |
| openstackgerrit | luong tuan proposed openstack/mistral master: Refactor mistral context using oslo_context https://review.openstack.org/455407 | 06:38 |
| *** shardy has joined #openstack-mistral | 07:00 | |
| *** brunograz has quit IRC | 07:12 | |
| *** zhurong has quit IRC | 07:24 | |
| *** brunograz has joined #openstack-mistral | 07:27 | |
| *** Qiming has quit IRC | 07:36 | |
| *** Qiming has joined #openstack-mistral | 07:42 | |
| *** zhurong has joined #openstack-mistral | 07:43 | |
| *** gongysh has quit IRC | 07:55 | |
| *** zhurong has quit IRC | 08:47 | |
| *** zhurong has joined #openstack-mistral | 09:01 | |
| *** sharatss_ has quit IRC | 09:17 | |
| *** sharatss_ has joined #openstack-mistral | 09:18 | |
| kong | rakhmerov, d0ugal, hi guys, please take a look at region support feature implementation https://review.openstack.org/460351 when you're available. (although I know it may not be an ideal time for the people who are preparing Boston summit) | 09:32 |
| d0ugal | kong: sure thing, I'll take a look this week | 09:33 |
| d0ugal | kong: neither I or rakhmerov are going to Boston :( | 09:33 |
| kong | d0ugal: thanks and sorry to here that :) | 09:34 |
| kong | s/here/hear | 09:34 |
| d0ugal | kong: are you going? | 09:34 |
| kong | d0ugal: nope, we have not enough budget | 09:34 |
| kong | maybe next time | 09:34 |
| rakhmerov | kong: yes, I was going to review it within an hour | 09:35 |
| d0ugal | kong: Where in the world are you? | 09:35 |
| kong | and one possibility for developers to attend summit is we get the chance to give presentation | 09:35 |
| kong | d0ugal: New Zealand | 09:35 |
| d0ugal | kong: oh, cool - so the next summit is closer! | 09:36 |
| kong | d0ugal: yeah! | 09:36 |
| kong | that's reason I said 'maybe next time' :-) | 09:36 |
| *** zhurong has quit IRC | 09:41 | |
| openstackgerrit | luong tuan proposed openstack/mistral master: Refactor mistral context using oslo_context https://review.openstack.org/455407 | 09:43 |
| openstackgerrit | luong tuan proposed openstack/mistral master: Add user creds trusts to db https://review.openstack.org/462056 | 09:43 |
| *** zhurong has joined #openstack-mistral | 10:18 | |
| d0ugal | rakhmerov: is there a way to have a task called for each completion of an with-items? | 10:30 |
| d0ugal | i.e. I want on-complete for each with-items item | 10:30 |
| *** zhurong has quit IRC | 10:30 | |
| *** jkilpatr has quit IRC | 10:31 | |
| *** sharat has quit IRC | 10:34 | |
| rakhmerov | d0ugal: only if the task that has "with-items" calls workflows instead of actions | 10:35 |
| rakhmerov | then in a subworkflow you can do that | 10:35 |
| d0ugal | rakhmerov: oh, of course! | 10:35 |
| rakhmerov | but not in the parent workflow | 10:35 |
| d0ugal | perfect | 10:36 |
| rakhmerov | yeah ) | 10:36 |
| rakhmerov | because from the parent workflow perspective all iterations if 'with-items' are still one task (but its result is a collection) | 10:36 |
| d0ugal | right, that makes sense | 10:37 |
| d0ugal | I had hoped for a handy trick, but calling a workflow is better. | 10:37 |
| *** jkilpatr has joined #openstack-mistral | 10:49 | |
| d0ugal | rakhmerov: how do I make sure that task().result is the same? when moving from an action call to a workflow call? if that doesn't make sense I might need to make an example :) | 10:59 |
| *** thrash|g0ne is now known as thrash | 10:59 | |
| rakhmerov | hm.. | 11:00 |
| * rakhmerov is trying to get an idea.. | 11:00 | |
| d0ugal | :) | 11:00 |
| d0ugal | basically I want to control the "result" of a workflow | 11:01 |
| rakhmerov | yep | 11:01 |
| d0ugal | rakhmerov: https://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#id1 | 11:02 |
| d0ugal | rakhmerov: in that example; output: result: <% %> | 11:02 |
| d0ugal | I guess that would do it? | 11:02 |
| rakhmerov | ooh, so | 11:03 |
| d0ugal | I have not used "output" yet :) | 11:03 |
| rakhmerov | all you need to do is just to save an action result so that it's accessible as a result of the workflow? | 11:03 |
| d0ugal | rakhmerov: yeah | 11:03 |
| rakhmerov | ok | 11:03 |
| d0ugal | rakhmerov: so I can replace an action call, with a workflow call but it work the same | 11:04 |
| rakhmerov | yes, so what "output" does is it just calculates an expression and saves it as a workflow result (accessible as wf_ex.output in the API), in the expression you can use any data published into the context | 11:04 |
| rakhmerov | although "context" here is slightly tricky | 11:05 |
| d0ugal | rakhmerov: and can I access the output with task().result? or does that need to change to task().output? | 11:05 |
| rakhmerov | because, as you know, workflow context is always bound to a workflow branch (if we're not talking about global publishing that I added recently) | 11:06 |
| rakhmerov | yes, you can use task(task_name).result | 11:06 |
| rakhmerov | absolutely | 11:06 |
| d0ugal | great | 11:06 |
| d0ugal | there shouldn't be any branching here :) | 11:06 |
| d0ugal | This is going to be a very simple 2 task workflow. | 11:07 |
| rakhmerov | just one thing to remember: there may be ambiguity if you have many instances (executions) of the same task | 11:07 |
| d0ugal | maybe 3 tasks :) | 11:07 |
| rakhmerov | e.g. in case of loops | 11:07 |
| d0ugal | rakhmerov: ambiguity? where? :) | 11:07 |
| rakhmerov | example: taskA -> TaskB -> TaskC -> (on condition) TaskB | 11:08 |
| rakhmerov | this may lead to creating many executions for TaskB | 11:08 |
| rakhmerov | because there's a loop here | 11:08 |
| *** sharatss_ has quit IRC | 11:09 | |
| rakhmerov | and if you use task(TaskB).result it's pretty much undefined what exact execution you will take | 11:09 |
| *** sharat has joined #openstack-mistral | 11:09 | |
| rakhmerov | makes sense? | 11:09 |
| d0ugal | rakhmerov: right, I see | 11:09 |
| d0ugal | rakhmerov: we wont have any loops like that | 11:10 |
| d0ugal | only a with-items | 11:10 |
| rakhmerov | ok, then it's fine | 11:10 |
| rakhmerov | so, one more thing: getting back to the branches.. | 11:10 |
| d0ugal | yup :) | 11:10 |
| rakhmerov | when a workflow completes it always finds so-called "end tasks", basically those tasks that led to completing the workflow | 11:11 |
| rakhmerov | and then it merges all contexts associated with their branches | 11:11 |
| rakhmerov | that way it calculates the final workflow context | 11:11 |
| rakhmerov | that is used when evaluating "output" | 11:11 |
| rakhmerov | a little bit tricky but that's what we came up with | 11:12 |
| d0ugal | right | 11:13 |
| rakhmerov | or btw, now we can also do global publishing | 11:13 |
| rakhmerov | if we want to make it more explicit | 11:13 |
| d0ugal | rakhmerov: yeah, I'll need to try that when it is ready :) | 11:13 |
| rakhmerov | :) | 11:13 |
| d0ugal | rakhmerov: this is what I came up with, just about to test it: https://review.openstack.org/#/c/462078/1/workbooks/baremetal.yaml | 11:13 |
| rakhmerov | yes, but you don't even need "publish" here at all | 11:15 |
| rakhmerov | you can do "result: <% task(start_introspection).result %>" in "output" | 11:15 |
| d0ugal | oh, good point | 11:15 |
| d0ugal | updated, even neater :) | 11:17 |
| d0ugal | rakhmerov: thanks! | 11:17 |
| rakhmerov | :) | 11:18 |
| rakhmerov | np | 11:18 |
| d0ugal | rakhmerov: btw, could you look at https://review.openstack.org/#/c/461026/ | 11:26 |
| d0ugal | rakhmerov: thrash noticed a difference when using on-complete and on-success/on-error - does that seem correct to you? | 11:26 |
| d0ugal | it seems like a bug in Mistral to me | 11:27 |
| rakhmerov | no! | 11:28 |
| rakhmerov | it's not a bug | 11:28 |
| d0ugal | rakhmerov: haha, okay | 11:28 |
| rakhmerov | sec | 11:28 |
| d0ugal | rakhmerov: but if on-complete is like "finally" in Python, I wouldn't expect it to raise the exception :) | 11:28 |
| rakhmerov | wait a sec.. maybe I didn't read carefully | 11:29 |
| rakhmerov | so, what do you mean about "finally"? | 11:31 |
| rakhmerov | if you have just "finally" declared in try-except-finally block (w/o 'except') the exception will still be raised | 11:32 |
| rakhmerov | outside | 11:32 |
| rakhmerov | it doesn't prevent from bubbling the exception | 11:32 |
| d0ugal | rakhmerov: true | 11:33 |
| rakhmerov | only "except" does (if it's catches the right exception type) | 11:33 |
| rakhmerov | https://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#direct-workflow-task-attributes | 11:34 |
| rakhmerov | I recently added a paragraph to explain it | 11:34 |
| d0ugal | right | 11:37 |
| d0ugal | rakhmerov: okay, I understand now I think | 11:37 |
| d0ugal | I'm not sure why I got confused :) | 11:37 |
| rakhmerov | ok | 11:38 |
| *** zhurong has joined #openstack-mistral | 12:01 | |
| rakhmerov | d0ugal: just a small thing (syncing with 'mistral' changes): https://review.openstack.org/#/c/461986/ | 12:01 |
| d0ugal | rakhmerov: thanks | 12:02 |
| *** Qiming has quit IRC | 12:06 | |
| *** dprince has joined #openstack-mistral | 12:09 | |
| *** Qiming has joined #openstack-mistral | 12:20 | |
| *** catintheroof has joined #openstack-mistral | 12:30 | |
| *** dprince has quit IRC | 12:43 | |
| *** tung_doan has joined #openstack-mistral | 12:50 | |
| *** zhurong has quit IRC | 13:28 | |
| *** chlong has quit IRC | 13:28 | |
| thrash | rakhmerov: I filed a bug | 13:30 |
| thrash | rakhmerov: so if you think the behavior is correct then we can just close it | 13:30 |
| thrash | rakhmerov: https://bugs.launchpad.net/mistral/+bug/1687630 | 13:31 |
| openstack | Launchpad bug 1687630 in Mistral "Failed action with on-complete marks entire workflow as failed" [Undecided,New] | 13:32 |
| d0ugal | thrash: I think it is correct :) do you still not? | 13:34 |
| thrash | d0ugal: what I don't understand is why it is inconsistent between on-success/on-error and on-complete | 13:35 |
| thrash | d0ugal: I would expect the behavior to be the same regardless | 13:35 |
| *** sharat has quit IRC | 13:38 | |
| *** sharat has joined #openstack-mistral | 13:38 | |
| *** jaosorior is now known as jaosorior_away | 13:41 | |
| thrash | d0ugal: rakhmerov AAHHHHH NOW I understand. Reading that paragraph makes a LOT more sense. | 13:47 |
| thrash | d0ugal: rakhmerov I'll close my bug. | 13:47 |
| d0ugal | :) | 13:47 |
| d0ugal | thrash: it is confusing, but I'm not sure why it is confusing. I think we both made the same incorrect assumption | 13:47 |
| thrash | d0ugal: yep... on-error is essentially the same as if we added an 'ignore-errors' to on-complete | 13:48 |
| *** dprince has joined #openstack-mistral | 13:49 | |
| thrash | d0ugal: I guess the one thing I'm left wanting is not having to repeat the same task in on-success/on-error | 13:49 |
| d0ugal | thrash: agreed | 13:50 |
| d0ugal | on-anything :P | 13:50 |
| thrash | on-whatever | 13:50 |
| thrash | lol | 13:50 |
| *** zhurong has joined #openstack-mistral | 14:02 | |
| *** sharat has quit IRC | 14:05 | |
| *** bobh has joined #openstack-mistral | 14:06 | |
| *** brunograz has quit IRC | 14:13 | |
| *** brunograz has joined #openstack-mistral | 14:17 | |
| *** openstackgerrit has quit IRC | 14:18 | |
| *** zhurong has quit IRC | 14:52 | |
| rakhmerov | thrash: ok :) | 15:04 |
| rakhmerov | on-whatever sounds cool! | 15:05 |
| rakhmerov | we may want to consider adding it ) | 15:05 |
| rakhmerov | thrash, rbrady: so, I'm here, we can discuss something on the summit preparations | 15:06 |
| rakhmerov | if needed | 15:06 |
| rbrady | rakhmerov: which 3 pike features do you want me to highlight in the talk? I don't know if there is any vision published in the mistral community for Queens or "R" Release, but the presentation asks for it | 15:08 |
| rakhmerov | rbrady: well, mostly I think we can talk about what's in the end if README (https://github.com/openstack/mistral) | 15:09 |
| rakhmerov | we set up the goals for 2017, main goals | 15:09 |
| rakhmerov | in addition, let me see what else it is worth talking about.. | 15:09 |
| rakhmerov | * Workflow error analysis (what toure is working on). And in general, the goal is to make Mistral more usable so that it allows to find root causes easier | 15:11 |
| rakhmerov | * Mistra GUI (the demo for the Mistral team will be on May 25th, I'll send out the link) | 15:11 |
| rakhmerov | the main reason to implement it: GUI is crucially important if we're dealing with big workflows that run long and it's hard to see the whole picture clearly so visualization is very important, and so on and so forth | 15:13 |
| *** chlong has joined #openstack-mistral | 15:15 | |
| rakhmerov | * Reworking OpenStack actions. We need to have much better test automation for them, easier ways to install them (only those that are needed) and maintain them (e.g. delete or update them). Possibly multi-versioning (supporting OpenStack APIs of different versions at the same time) | 15:16 |
| rakhmerov | * Multi-region support for OpenStack actions (in progress). So that we could define in what region an OpenStack action should run | 15:16 |
| rakhmerov | and I think this: https://blueprints.launchpad.net/mistral/+spec/mistral-execution-event-subscription | 15:17 |
| rakhmerov | this is probably even too much | 15:17 |
| rakhmerov | there's also a bunch of other things but they are smaller and don't have noticeable user impact probably | 15:18 |
| rakhmerov | rbrady: ^ | 15:23 |
| rbrady | rakhmerov: thanks. has there been any discussion to Queens work yet? | 15:24 |
| rakhmerov | nope, but I think part of these things will be scoped to Queens | 15:25 |
| rakhmerov | rbrady: do you need some clarifications on some of these bullets? | 15:29 |
| rakhmerov | I'll be here for another 20 mins or so | 15:29 |
| rbrady | rakhmerov: reading/processing | 15:29 |
| rakhmerov | :) | 15:29 |
| rakhmerov | ok | 15:29 |
| rbrady | rakhmerov: how about the "development themes" questions for the releases? I guess I can answer pike and skipp the other two | 15:30 |
| rbrady | rakhmerov: or do you just want to skip those altogether? | 15:31 |
| rakhmerov | well | 15:31 |
| rakhmerov | not sure what that means actually | 15:31 |
| rakhmerov | "development themes" | 15:31 |
| rakhmerov | does it mean "important development activities that don't necessarily have serious user impact"? | 15:32 |
| rbrady | it's asking if specific attributes will have a major focus, minor focus, no focus or not applicable | 15:32 |
| rakhmerov | specific attributes? | 15:32 |
| rbrady | and the attributes are Scalability, Resiliency, Manageability, Modularity, Interoperability, Security, User Experience | 15:33 |
| rakhmerov | ok | 15:33 |
| rbrady | rakhmerov: you can see them towards the bottom portion of the form: https://docs.google.com/forms/d/e/1FAIpQLSdM_YsZbvUGk-4ZEeXv7KRLCiTDX2Ct8LJtzB-9ntaceFhYgg/viewform?c=0&w=1 | 15:33 |
| rakhmerov | Scalability, Security, User Experience | 15:33 |
| rakhmerov | aah, I just saw this form in this.. form | 15:34 |
| rakhmerov | Major focus on these three | 15:34 |
| rakhmerov | on the last two questions, I don't know, seems like we don't require anything special | 15:36 |
| rbrady | rakhmerov: the 2nd to last question seems to be soliciting features from users | 15:37 |
| rakhmerov | the last question can be just answered with The Goals 2017 | 15:37 |
| rbrady | rakhmerov: ack | 15:37 |
| rakhmerov | 1. Documentation 2. Actions API 3. Multi-node mode 4. Reduce execution-time (improve performance) | 15:37 |
| rakhmerov | yep | 15:38 |
| rbrady | rakhmerov: ack - from the README :) | 15:38 |
| rakhmerov | right | 15:38 |
| rakhmerov | rbrady: do you have ideas on what you could do for the "Project onboarding session"? | 15:38 |
| rbrady | rakhmerov: how else does mistral solicit for features from the OpenStack community at large? | 15:38 |
| rakhmerov | well.. | 15:39 |
| rakhmerov | OpenStack community I think is pretty happy with Mistral | 15:40 |
| rakhmerov | :) | 15:40 |
| rakhmerov | to be serious, I think "Much much better usability" | 15:40 |
| rakhmerov | which we're moving towards | 15:40 |
| rbrady | rakhmerov: is this something that you get from people pinging you directly? | 15:41 |
| rakhmerov | docs, usability (GUI, Error Analysis, Actions API is also a part of it) | 15:41 |
| rakhmerov | ooh yeah! | 15:41 |
| rakhmerov | especially missing docs and not working OpenStack actions | 15:41 |
| rakhmerov | a bunch of people are complaining on that all the time | 15:41 |
| rbrady | rakhmerov: maybe in the onboarding we can tell them how to queue up or send emails to the list | 15:42 |
| rakhmerov | docs have become better in the last ~6 months (thanks to d0ugal and sharat), so I hear less complaints on it | 15:42 |
| rakhmerov | rbrady: yep, ok | 15:42 |
| rakhmerov | rbrady: I think a good idea would be if you could make a small change and send a patch (explain how reviewing works) | 15:43 |
| rbrady | rakhmerov, thrash: for the onboarding, maybe we can cover mistral IRC meeting, mailing list, mistral specific code conventions and discuss the purpose of each of the repos | 15:43 |
| rakhmerov | together with a person | 15:43 |
| rakhmerov | yes | 15:43 |
| rakhmerov | as far as code conventions, I wouldn't focus on it now because we didn't formalize them really | 15:44 |
| rakhmerov | (it's my technical debt still) | 15:44 |
| rbrady | rakhmerov: ack, guess we can surprise them on their first patch | 15:44 |
| rakhmerov | yeah ) | 15:44 |
| rakhmerov | I'm usually not too picky for newcomers as far as style | 15:44 |
| rakhmerov | so what else... | 15:45 |
| rakhmerov | maybe write a very simple workflow together with them? | 15:45 |
| rakhmerov | 2-3 tasks | 15:45 |
| thrash | rakhmerov: that's a good idea. | 15:45 |
| rakhmerov | demonstrate the most interesting features like: parallel branches, join, with-items | 15:45 |
| rakhmerov | ok | 15:45 |
| thrash | rakhmerov: I will brush up on reverse workflows so we can got through an example of that too. | 15:46 |
| rakhmerov | you can probably use some examples from mistral-extra | 15:46 |
| rakhmerov | not sure though if they are up to date | 15:46 |
| thrash | really depends on what people are looking for... developing workflows or patches to mistral itself. | 15:46 |
| rakhmerov | thrash: yeah, sure. It's kind of an important aspect too (that the system architecturally flexible to allow new workflow types) | 15:46 |
| rakhmerov | but we don't mention it often | 15:47 |
| rakhmerov | thrash: true, we never know who comes | 15:47 |
| rakhmerov | if any ) | 15:47 |
| rakhmerov | at all | 15:47 |
| rakhmerov | if so, that would be the simplest scenario for you though ;) | 15:47 |
| thrash | haha | 15:48 |
| rakhmerov | kidding, hopefully someone will come | 15:48 |
| thrash | I'm sure we will get at least a handful | 15:48 |
| rakhmerov | :) | 15:48 |
| rbrady | rakhmerov: thanks for your help. if we mess anything up or can't answer someone, we will point them in your direction. :) | 15:48 |
| rakhmerov | yeah, no problem | 15:48 |
| rakhmerov | but I think you know it well enough already | 15:49 |
| rakhmerov | thrash, rbrady: ok, so I need to go | 15:49 |
| thrash | rakhmerov: ack. Thanks for the ideas. | 15:49 |
| rakhmerov | if you have anything else I could help with pls let me know (email, irc, whatever) | 15:49 |
| rakhmerov | we still have time | 15:49 |
| rakhmerov | yep, see ya | 15:49 |
| rbrady | rakhmerov: ack, thanks. | 15:49 |
| *** brunograz has quit IRC | 16:06 | |
| *** brunograz has joined #openstack-mistral | 16:23 | |
| *** shardy has quit IRC | 16:28 | |
| *** harlowja has joined #openstack-mistral | 16:48 | |
| *** dprince has quit IRC | 16:48 | |
| breton | i am trying to list all instainces in a project in mistral | 16:59 |
| breton | *instances | 16:59 |
| breton | how do i pass the project id to search_opts? | 16:59 |
| *** clenimar has quit IRC | 17:02 | |
| breton | in python i'd do something like list(search_opts={'project_id': project_id}) | 17:04 |
| *** dprince has joined #openstack-mistral | 17:04 | |
| breton | ok, figured it out | 17:09 |
| breton | next question. Why am i getting this: http://paste.openstack.org/show/608730/ | 17:09 |
| breton | why region_name is None? | 17:15 |
| rakhmerov | hi breton | 17:21 |
| rakhmerov | well, region_name is not handled properly now, this patch should probably fix it: https://review.openstack.org/#/c/460351/ | 17:22 |
| rakhmerov | rbrady: one more complaint about actions ) | 17:22 |
| rakhmerov | breton: do you have more than one region? | 17:22 |
| rakhmerov | kong: if you have time, can you help breton with this? | 17:23 |
| breton | rakhmerov: nope, only 1 region, RegionOne | 20:09 |
| *** toure is now known as toure|gone | 20:18 | |
| *** dprince has quit IRC | 20:19 | |
| *** catinthe_ has joined #openstack-mistral | 20:21 | |
| breton | this seems to happen because region is not in the context | 20:22 |
| *** catintheroof has quit IRC | 20:24 | |
| *** catinthe_ has quit IRC | 20:45 | |
| *** bobh has quit IRC | 21:15 | |
| *** chlong has quit IRC | 21:17 | |
| *** openstackgerrit has joined #openstack-mistral | 22:04 | |
| openstackgerrit | Merged openstack/mistral-lib master: Update serialization from 'mistral' repo with latest changes https://review.openstack.org/461986 | 22:04 |
| *** jkilpatr has quit IRC | 22:05 | |
| kong | hi, breton, still here? | 22:05 |
| kong | breton: i want to know how you create execution? by CLI or call rest api directly? | 22:06 |
| kong | how you defined you credential file? | 22:06 |
| *** apetrich_ has joined #openstack-mistral | 22:27 | |
| *** apetrich has quit IRC | 22:28 | |
| *** harlowja has quit IRC | 22:28 | |
| *** d0ugal has quit IRC | 22:28 | |
| *** jkilpatr has joined #openstack-mistral | 22:39 | |
| *** d0ugal has joined #openstack-mistral | 22:53 | |
| *** bobh has joined #openstack-mistral | 23:04 | |
| *** bobh has quit IRC | 23:11 | |
| *** harlowja has joined #openstack-mistral | 23:31 | |
| openstackgerrit | Lingxian Kong proposed openstack/mistral master: Add "running_region" param for OpenStack actions https://review.openstack.org/460351 | 23:36 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!