| *** bobh has quit IRC | 00:00 | |
| *** zhurong has joined #openstack-mistral | 00:45 | |
| openstackgerrit | Emilien Macchi proposed openstack/mistral master: Add sem-ver flag so pbr generates correct version https://review.openstack.org/453406 | 01:27 |
|---|---|---|
| openstackgerrit | Emilien Macchi proposed openstack/mistral master: Add sem-ver flag so pbr generates correct version https://review.openstack.org/453422 | 01:33 |
| *** zhurong has quit IRC | 01:52 | |
| *** zhurong has joined #openstack-mistral | 01:57 | |
| *** tuan_ has quit IRC | 02:06 | |
| *** jamielennox is now known as jamielennox|away | 02:07 | |
| *** tuan_ has joined #openstack-mistral | 02:07 | |
| *** bobh has joined #openstack-mistral | 02:14 | |
| *** bobh has quit IRC | 02:20 | |
| *** jamielennox|away is now known as jamielennox | 02:21 | |
| *** gongysh has joined #openstack-mistral | 02:27 | |
| *** zhurong has quit IRC | 02:38 | |
| *** bobh has joined #openstack-mistral | 02:46 | |
| *** bobh has quit IRC | 03:10 | |
| *** zhurong has joined #openstack-mistral | 03:12 | |
| *** Kevin_Zheng has quit IRC | 03:13 | |
| openstackgerrit | Lingxian Kong proposed openstack/mistral-specs master: Support openstack context for workflow execution https://review.openstack.org/414508 | 03:39 |
| *** gongysh has quit IRC | 03:46 | |
| *** zhurong has quit IRC | 04:12 | |
| openstackgerrit | Lingxian Kong proposed openstack/mistral-specs master: Support region for openstack actions https://review.openstack.org/414508 | 04:30 |
| *** zhurong has joined #openstack-mistral | 04:35 | |
| *** chlong has quit IRC | 04:49 | |
| *** jaosorior_away is now known as jaosorior | 05:11 | |
| *** sharatss has joined #openstack-mistral | 05:16 | |
| *** gongysh has joined #openstack-mistral | 05:27 | |
| *** warface has joined #openstack-mistral | 05:30 | |
| *** warface has quit IRC | 06:04 | |
| *** warface has joined #openstack-mistral | 06:05 | |
| d0ugal | kong: how about now? :) | 06:24 |
| *** warface has quit IRC | 06:33 | |
| *** warface has joined #openstack-mistral | 06:35 | |
| rakhmerov | d0ugal: hi, sorry, was already off yesterday | 06:41 |
| rakhmerov | d0ugal: still want to discuss something? | 06:41 |
| *** tung_doan has joined #openstack-mistral | 06:49 | |
| d0ugal | rakhmerov: I think we need to do this for mistral-lib | 06:51 |
| d0ugal | https://docs.openstack.org/infra/manual/creators.html#tagging-a-release | 06:51 |
| d0ugal | rakhmerov: I think maybe you or kong needs to do it | 06:51 |
| warface | hey, can anyone please point me to resource on adding a custom action using mistral action-create command. ? All I could find is this: https://docs.openstack.org/developer/mistral/developer/creating_custom_action.html | 06:52 |
| d0ugal | warface: I think that is the best documentation at the moment, it is a bit lacking :( | 06:52 |
| rakhmerov | warface: hey, these two things are not really related | 06:52 |
| rakhmerov | so, let me clarify | 06:52 |
| warface | @rakhmerov thanks a lot :) listening | 06:53 |
| rakhmerov | 'action-create' is for creating so called ad-hoc actions, it's a type of action that you create right in YAML and upload them to mistral | 06:53 |
| rakhmerov | but those actions are limited, you can only just create a wrapper on top of existing actions: you can alter a list of initial action parameters and alter form of its output | 06:54 |
| rakhmerov | I realize that the command name is confusing here.. It is what it is for now, we'll be changing that relatively soon | 06:55 |
| warface | dougal, rakhmerov: thanks a lot for the explanation :) | 06:55 |
| rakhmerov | and the link you provided describes how you can write custom actions in Python and plug them into Mistral under certain names | 06:55 |
| rakhmerov | that latter requires to redeploy Mistral, it's not done via API | 06:56 |
| rakhmerov | warface: np, feel free to ask anything both here and in openstack-dev | 06:56 |
| rakhmerov | d0ugal: looking at your link.. | 06:57 |
| warface | I wanted to create a custom action, since I can't find a way to conditionally fail a standard std.http action, based on whether there is a key present in the response | 06:57 |
| rakhmerov | d0ugal: I have a short meeting now, around 20 mins, then I'll read that | 06:57 |
| d0ugal | rakhmerov: thanks | 06:57 |
| warface | for example, fail the action if the response doesn't contain 'status' key | 06:58 |
| d0ugal | warface: key? is it json? | 06:58 |
| warface | would that be possible without custom actions ? | 06:58 |
| warface | yes, assuming it is | 06:58 |
| d0ugal | warface: it would almost be possible, but I don't think there is a way to parse JSON | 06:59 |
| warface | using YAQL ? | 06:59 |
| d0ugal | so you would need to just check and see if the response content contains the key | 06:59 |
| d0ugal | Yeah, with YAQL - let me try and write a quick example. | 06:59 |
| warface | sure, thanks a ton, really appreciate your time | 07:00 |
| rakhmerov | d0ugal, warface: if I understood the challenge correctly, all that needs to be done is just adding "fail" command either in 'on-success' or 'on-complete' with a condition | 07:04 |
| d0ugal | http://paste.openstack.org/show/605467/ | 07:04 |
| d0ugal | rakhmerov: like that? :) | 07:05 |
| d0ugal | warface: ^ | 07:05 |
| d0ugal | oh, true, I didn't fail - I just showed how you call two different actions if the key is there or not | 07:05 |
| d0ugal | http://paste.openstack.org/show/605468/ | 07:05 |
| rakhmerov | yes except I don't understand what those action_a and action_b are :) | 07:05 |
| d0ugal | rakhmerov: well, I'm not sure either ;) | 07:05 |
| rakhmerov | and a small note: you can do just task() instead of task(make_request) in this case | 07:06 |
| d0ugal | warface: in the first example it will call action_a if the key is there and action_b if it isn't - so you can do something after. In the second example it just fails the workflow if the key isn't there | 07:06 |
| d0ugal | rakhmerov: Yeah, I've had problems with that in the past so I got into the habit of including the name :) | 07:06 |
| rakhmerov | ooh, yeah, good point, 'fail' will fail the entire workflow | 07:07 |
| rakhmerov | d0ugal: yep, understandable, but now it's fixed | 07:07 |
| d0ugal | rakhmerov: btw, the example here should probably be updated. https://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#yaml-example | 07:08 |
| d0ugal | task(create_server) | 07:08 |
| rakhmerov | so, just to avoid a confusion: action_a and action_b here must be task names or command names like "fail", "succeed" etc. | 07:08 |
| rakhmerov | d0ugal: ok | 07:08 |
| warface | d0ugal: 'fail' is a keyword that will fail the entire workflow ? with action being success ? | 07:08 |
| rakhmerov | warface: yep | 07:08 |
| warface | that should really help | 07:08 |
| rakhmerov | there's also succeed, pause and noop | 07:08 |
| * d0ugal is trying to document there | 07:09 | |
| d0ugal | these | 07:09 |
| warface | thanks a ton guys, saved me a lot of time, was stuck at these for quite some time :) | 07:09 |
| rakhmerov | warface: yeah, if you don't need to fail the entire workflow you can have a small subworkflow which will fail | 07:09 |
| rakhmerov | and it will fail the parent task in the parent workflow | 07:09 |
| warface | yes, that would be perfect | 07:09 |
| rakhmerov | warface: or, you can jump to a certain task upon the condition and that task will do something that you need upon error | 07:10 |
| * d0ugal might borrow this example for the docs | 07:12 | |
| warface | nice, will try that out. can't thank you enough today I guess. | 07:12 |
| d0ugal | I'll be around if you have more questions! | 07:13 |
| *** brunograz has quit IRC | 07:15 | |
| rakhmerov | d0ugal: so, just finished reading your link | 07:15 |
| warface | I was going through reverse workflow and couldn't get that started, so I raised a bug, to find out I wasn't writing the command correctly. Please update the docs regarding that whenever you can. Here's the bug that I reported: https://bugs.launchpad.net/mistral/+bug/1679578 | 07:15 |
| openstack | Launchpad bug 1679578 in Mistral "Invalid task name None" [Undecided,Invalid] | 07:15 |
| rakhmerov | so yes, I guess I can do it | 07:15 |
| d0ugal | rakhmerov: great. basically we need an initial release so it can be added to global-requirements. | 07:16 |
| rakhmerov | yes | 07:16 |
| rakhmerov | I used to do that all the time for all mistral subprojects but then our release team took over it | 07:16 |
| *** shardy has joined #openstack-mistral | 07:22 | |
| jenner_ | guys, are there any docs that explain how to configure a distributed mistral setup (N * all components, balanced)? | 07:24 |
| rakhmerov | jenner_: no good docs yet, sorry. But that's pretty simple: mistral-server script has --server option that can be one of the following: api, engine, executor or all | 07:26 |
| rakhmerov | that option is used to specify what component you want to start | 07:26 |
| rakhmerov | 'all' is for all components in one process | 07:26 |
| rakhmerov | so you can start any combination that you'd like | 07:27 |
| rakhmerov | the only thing is that if you start more than one api you'll have to put an LB in front | 07:27 |
| jenner_ | rakhmerov: yeah, but how do the engines know each? you said yesterday that engine can even share WF tasks | 07:28 |
| jenner_ | or do the just need the same rabbit + DB to cooperate? | 07:29 |
| rakhmerov | jenner_: they don't really know about each other, it's all through MQ | 07:29 |
| jenner_ | ok | 07:29 |
| rakhmerov | yes, that's right | 07:29 |
| rakhmerov | same DB and MQ | 07:29 |
| jenner_ | same for executors, right? | 07:29 |
| rakhmerov | yep | 07:29 |
| rakhmerov | executors don't even have DB access, only MQ | 07:29 |
| jenner_ | so basically I'd need a global mistra.conf (except for named executors) and a balancer for APIs | 07:30 |
| rakhmerov | yes | 07:34 |
| rakhmerov | in API you'll have to change hosts | 07:35 |
| rakhmerov | (most likely) | 07:35 |
| rakhmerov | d0ugal: as it turned out my gpg key is expired already, and I'm now in doubts whether we need to use it ourselves or not because as far as I remember there was some problem with handing over release privileges if using different PGP keys | 07:39 |
| rakhmerov | I need to talk to kong first | 07:39 |
| rakhmerov | kong: pls ping me when you have a minute.. | 07:40 |
| d0ugal | rakhmerov: okay, thanks. | 07:40 |
| jenner_ | rakhmerov: what do you mean by change hosts? | 07:40 |
| rakhmerov | jenner_: the host name or IP that a concrete API server instance will be bound to | 07:41 |
| rakhmerov | and potentially port to | 07:41 |
| rakhmerov | by default it's 8989 but you may have to change it depending on your environment constraints | 07:41 |
| jenner_ | rakhmerov: the LB will take care of that :) | 07:42 |
| rakhmerov | ok | 07:43 |
| rakhmerov | yes | 07:43 |
| *** amoralej|off is now known as amoralej | 07:43 | |
| rakhmerov | d0ugal: do you understand this patch? https://review.openstack.org/#/c/453422/1 | 07:55 |
| rakhmerov | it doesn't change anything in the source tree, that's weird | 07:55 |
| *** jpich has joined #openstack-mistral | 07:58 | |
| d0ugal | hah, no, I don't | 08:00 |
| d0ugal | I can check with Emilien later - he wont be around for a few hours yet | 08:00 |
| rakhmerov | d0ugal: I'm not even sure how it's possible to make such a patch | 08:00 |
| rakhmerov | ok | 08:00 |
| d0ugal | They are all like that I see :) https://review.openstack.org/#/q/topic:sem-ver/pike | 08:01 |
| d0ugal | Emilien must have mad git skills :) | 08:01 |
| jenner_ | wow, weird... there's a ChangeId, so the commit-msg hook must've seen a diff to previous commits | 08:04 |
| rakhmerov | aaah, gotcha | 08:05 |
| rakhmerov | yes | 08:05 |
| rakhmerov | d0ugal: so what do you think? I guess he knows what he's doing | 08:05 |
| rakhmerov | we can probably merge | 08:05 |
| rakhmerov | :) | 08:05 |
| d0ugal | rakhmerov: I am inclined to agree, but it would be good to understand and non of the others have merged yet. | 08:06 |
| rakhmerov | d0ugal: reasonable, let's talk to him first may be | 08:06 |
| rakhmerov | I'll also leave a comment in the patch | 08:06 |
| d0ugal | good idea | 08:06 |
| d0ugal | I think "Sem-Ver: api-break" is the relevant part. | 08:07 |
| d0ugal | It must be a new feature in pbr and maybe it needs an initial one in the git history? | 08:07 |
| d0ugal | https://specs.openstack.org/openstack/oslo-specs/specs/juno/pbr-semver.html#proposed-details | 08:08 |
| d0ugal | That is a juno spec, so it isn't new ;) | 08:09 |
| rakhmerov | d0ugal: I left a comment | 08:12 |
| rakhmerov | :) | 08:12 |
| d0ugal | thanks! | 08:12 |
| rakhmerov | I guess you're right but let's check with him | 08:12 |
| d0ugal | rakhmerov: have you ever wanted a syntax highlighter for Mistral workflows? :) | 08:30 |
| rakhmerov | I always have :) | 08:31 |
| d0ugal | rakhmerov: I wrote one for pygments, so we could actually use it in the docs | 08:31 |
| rakhmerov | there's even a POC plugin for sublime | 08:31 |
| d0ugal | rakhmerov: it looks like this: http://www.discode.co/19 | 08:31 |
| d0ugal | it still needs some more work, but I think it makes then a bit easier to read | 08:31 |
| *** jaosorior is now known as jaosorior_lunch | 08:31 | |
| rakhmerov | ooh, cool | 08:32 |
| d0ugal | sphinx uses pygments, so it would be easy to add to the docs | 08:32 |
| rakhmerov | I don't even know what pygments is | 08:32 |
| d0ugal | rakhmerov: Python syntax highlighting library | 08:32 |
| rakhmerov | ok | 08:32 |
| d0ugal | rakhmerov: .. code-block:: yaml | 08:33 |
| rakhmerov | yeaht, that's very cool indeed | 08:33 |
| rakhmerov | yep | 08:33 |
| d0ugal | that tells sphinx to use the pygments syntax for yaml | 08:33 |
| d0ugal | I just spotted your comment - there is a typo in that example. | 08:33 |
| rakhmerov | btw, I noticed that in the thrash's patch for the sensitive data spec these code blocks don't work well | 08:33 |
| d0ugal | so if I were to add my code, then you could do ".. code-block:: mistral" | 08:33 |
| rakhmerov | they are not displayed properly | 08:33 |
| d0ugal | rakhmerov: yeah, only because he got it wrong :) | 08:33 |
| rakhmerov | what exactly? | 08:34 |
| rakhmerov | wrong | 08:34 |
| d0ugal | https://review.openstack.org/#/c/450853/3/specs/pike/approved/secure-sensitive-data.rst | 08:34 |
| d0ugal | I replied to your comment. | 08:34 |
| rakhmerov | d0ugal: that's awesome, really, can you contribute it somewhere? | 08:34 |
| rakhmerov | and then we can modify all our docs to use it | 08:34 |
| d0ugal | rakhmerov: sure. I wrote it a few weeks ago, I don't know why I didn't think of it before now :) | 08:35 |
| rakhmerov | np | 08:35 |
| d0ugal | rakhmerov: where should the code live? Some projects just include it in the main source tree. Mako templates do this for example. | 08:35 |
| d0ugal | https://github.com/zzzeek/mako/blob/master/setup.py#L80-L85 | 08:35 |
| d0ugal | It just needs an entry point. | 08:35 |
| d0ugal | so I could put the code in the mistral repo? I don't mind really. | 08:36 |
| rakhmerov | yes | 08:36 |
| d0ugal | It is only about 20 lines of code (so far) | 08:36 |
| rakhmerov | :) | 08:37 |
| d0ugal | actually, a bit more - ~40. | 08:37 |
| d0ugal | okay, I'll make a patch for that now. | 08:37 |
| rakhmerov | send a patch pls, we'll take a look | 08:37 |
| d0ugal | sure | 08:37 |
| rakhmerov | I want this thing ) | 08:37 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Add support for mistral-lib to Mistral https://review.openstack.org/453517 | 08:38 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Add a Mistral lexer for pygments https://review.openstack.org/453526 | 08:50 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Add a Mistral lexer for pygments https://review.openstack.org/453526 | 08:51 |
| d0ugal | Are the tempest tests Python 2 only? | 08:53 |
| *** jtomasek has quit IRC | 08:54 | |
| tuan_ | Morning guys, | 08:54 |
| tuan_ | i have added a spec for using trust in mistral | 08:54 |
| tuan_ | https://blueprints.launchpad.net/mistral/+spec/mistral-token-expiration | 08:54 |
| tuan_ | please take a look to it | 08:54 |
| d0ugal | rakhmerov: compare https://docs.openstack.org/developer/mistral/quickstart.html#write-a-workflow | 08:55 |
| *** jtomasek has joined #openstack-mistral | 08:55 | |
| d0ugal | with... http://docs-draft.openstack.org/26/453526/2/check/gate-mistral-docs-ubuntu-xenial/b44292d//doc/build/html/quickstart.html#write-a-workflow | 08:55 |
| rakhmerov | d0ugal: on tempest, I thought it's the way around: only for 3 | 08:56 |
| rakhmerov | but not sure | 08:56 |
| rakhmerov | tuan_: hi, yes, thanks. Will do | 08:56 |
| rakhmerov | d0ugal: yeah, really nice! | 08:57 |
| tuan_ | rakhmerov: Thanks renat | 08:57 |
| rakhmerov | d0ugal: let's do it as soon as we can :) | 08:57 |
| rakhmerov | d0ugal: so you're planning to highlight keywords in green, right? | 08:57 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Add a Mistral lexer for pygments https://review.openstack.org/453526 | 08:58 |
| rakhmerov | (I mean rather principle than a concrete color) | 08:58 |
| d0ugal | rakhmerov: yeah, well, I tell them it is a Keyword. The colour comes from the theme css I think - not sure exactly. | 08:58 |
| d0ugal | https://review.openstack.org/#/c/453526/2/mistral/ext/pygmentplugin.py | 08:58 |
| d0ugal | rakhmerov: basically the way it works is with regular expressions identifying different token types. | 08:58 |
| rakhmerov | d0ugal: I'm asking because "type" I guess should also be in green | 08:59 |
| d0ugal | rakhmerov: yeah, that is because I only tested it against TripleO workflows :) | 08:59 |
| rakhmerov | ok, I need to play with it | 08:59 |
| d0ugal | I'll add type | 08:59 |
| rakhmerov | I see :) | 08:59 |
| rakhmerov | we can polish it as we need | 08:59 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Add a Mistral lexer for pygments https://review.openstack.org/453526 | 09:00 |
| d0ugal | ^ type should now work as expected. | 09:00 |
| rakhmerov | ok | 09:00 |
| d0ugal | rakhmerov: I asked about tempest because pep8 fails on temptest when pep8 runs as Python 3 | 09:00 |
| rakhmerov | d0ugal: honestly, I don't remember. I think yes, it's only py 2 | 09:01 |
| rakhmerov | d0ugal: what does "score" mean in analyse_text() ? | 09:04 |
| d0ugal | rakhmerov: We can maybe remove that part. If no language is specified it will ask every registered lexer to score the text and then it will use the lexer with the highest score | 09:05 |
| rakhmerov | hm.. ok | 09:05 |
| d0ugal | rakhmerov: so I gave it a high score if the mistral keywords were present. I could change it to return a score of 0, then it will only be used when we specify it | 09:06 |
| rakhmerov | wait a second.. | 09:07 |
| rakhmerov | so it's just automatic lang detection kind of, right? | 09:07 |
| d0ugal | yeah | 09:07 |
| rakhmerov | I see now | 09:07 |
| d0ugal | I don't think it is even used by Sphinx actually, just checking. | 09:07 |
| rakhmerov | ok | 09:07 |
| rakhmerov | interesting approach | 09:08 |
| d0ugal | my scoring system was very basic :-D | 09:08 |
| rakhmerov | that's fine, for now I can't see anything more advanced | 09:10 |
| rakhmerov | maybe later when I get more familiar with it | 09:10 |
| d0ugal | rakhmerov: it works fine without it, so I removed it - we don't need to score text. | 09:11 |
| rakhmerov | ok | 09:11 |
| d0ugal | I am just adding it to the other workflow samples then I'll push an update | 09:11 |
| rakhmerov | ok, yeah | 09:11 |
| rakhmerov | but no need to change all docs in a single patch ) | 09:12 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Add a Mistral lexer for pygments https://review.openstack.org/453526 | 09:21 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Remove the highlighting choice 'HTTP' https://review.openstack.org/453542 | 09:21 |
| openstackgerrit | Dougal Matthews proposed openstack/mistral master: Use the plain syntax highlighting in the webapi example https://review.openstack.org/453543 | 09:21 |
| *** zhurong has quit IRC | 10:30 | |
| *** jaosorior_lunch is now known as jaosorior | 10:31 | |
| *** gongysh has quit IRC | 10:35 | |
| *** jkilpatr has quit IRC | 10:37 | |
| *** gongysh has joined #openstack-mistral | 10:41 | |
| *** shardy is now known as shardy_lunch | 10:45 | |
| openstackgerrit | Sharat Sharma proposed openstack/mistral-dashboard master: Fix "Workflow" section of "Action Execution Details" view https://review.openstack.org/453573 | 11:01 |
| *** jkilpatr has joined #openstack-mistral | 11:12 | |
| kong | rakhmerov, d0ugal, hi guys :) | 11:17 |
| d0ugal | Hey | 11:17 |
| * kong is reading the irc log | 11:17 | |
| rakhmerov | kong: yep, https://docs.openstack.org/infra/manual/creators.html#tagging-a-release | 11:17 |
| d0ugal | kong: tl;dr - we want to make the initial release of mistral-lib | 11:17 |
| rakhmerov | yes | 11:17 |
| kong | hmm...i never did that but deserves a try | 11:18 |
| kong | d0ugal: you wanna release mistral-lib now? | 11:19 |
| d0ugal | yes | 11:19 |
| d0ugal | so we can add it to global-requirements | 11:19 |
| kong | ok, leave it to me | 11:19 |
| EmilienM | d0ugal: o/ | 11:27 |
| d0ugal | EmilienM: Hey, we were trying to understand the sem-ver thing. | 11:28 |
| kong | d0ugal: not sure i have permission to push a new tag to mistral-lib | 11:28 |
| kong | ! [remote rejected] 0.1.0 -> 0.1.0 (prohibited by Gerrit) | 11:28 |
| kong | error: failed to push some refs to 'ssh://kong@review.openstack.org:29418/openstack/mistral-lib.git' | 11:28 |
| d0ugal | EmilienM: is the goal just to have that in the git history? | 11:28 |
| d0ugal | EmilienM: rakhmerov commented on the mistral patch too: https://review.openstack.org/#/c/453422/ | 11:29 |
| d0ugal | kong: oh :( | 11:29 |
| kong | is it necessary to add me some group? | 11:29 |
| EmilienM | d0ugal: https://docs.openstack.org/developer/pbr/#version | 11:29 |
| EmilienM | d0ugal: it allows to bump pbr without tagging | 11:29 |
| EmilienM | d0ugal: because projects use to wait m1 to tag the first pike version, packages (rdo here), are sill on the ocata version | 11:30 |
| EmilienM | d0ugal: and it's problematic for us since we want to test upgrades to pike | 11:30 |
| d0ugal | right | 11:30 |
| d0ugal | rakhmerov: ^ | 11:30 |
| EmilienM | so Sem-Ver: api-break will bump X in the X.Y.Z semver | 11:31 |
| EmilienM | if you want to bump Y, Sem-Ver: feature | 11:31 |
| EmilienM | but I think for you it makes sense to bump X | 11:31 |
| EmilienM | note: there is no impact for you and it doesn't change anything | 11:31 |
| d0ugal | okay, cool | 11:31 |
| EmilienM | it's only for us when we build packages | 11:31 |
| d0ugal | EmilienM: Thanks for the info. | 11:32 |
| EmilienM | I can update the commit message | 11:32 |
| d0ugal | EmilienM: it's fine I think, we almost trusted you are merged it earlier but I wanted to make sure I learned what was going on first :) | 11:32 |
| openstackgerrit | Emilien Macchi proposed openstack/mistral master: Add sem-ver flag so pbr generates correct version https://review.openstack.org/453422 | 11:34 |
| EmilienM | done | 11:34 |
| kong | d0ugal: did we do the steps according to the creator's guide? | 11:34 |
| kong | what's the configuration of the section '[access "refs/tags/*"]' for mistral-lib? | 11:34 |
| kong | i think i need to be in that group to push tags | 11:35 |
| *** rbrady has quit IRC | 11:35 | |
| d0ugal | kong: good question. I'm not sure, I think rakhmerov made it originally. | 11:36 |
| kong | i didn't find acl file for mistral-lib in https://github.com/openstack-infra/project-config/tree/master/gerrit/acls/openstack | 11:36 |
| kong | rakhmerov? | 11:36 |
| *** gongysh has quit IRC | 11:37 | |
| kong | and there are no groups in gerrit for mistral-lib neither | 11:38 |
| rakhmerov | kong: at the meeting now, will be back in ~20 mins | 11:40 |
| kong | rakhmerov: ok, you can just leave message to me in case I will be on the bed then :) | 11:40 |
| *** gongysh has joined #openstack-mistral | 11:41 | |
| *** gongysh has quit IRC | 11:47 | |
| *** dprince has joined #openstack-mistral | 11:59 | |
| *** gongysh has joined #openstack-mistral | 12:00 | |
| *** gongysh has quit IRC | 12:05 | |
| *** thrash|g0ne is now known as thrash | 12:06 | |
| *** sharatss has quit IRC | 12:06 | |
| openstackgerrit | Sharat Sharma proposed openstack/mistral master: Replace six.iteritems() with .items() https://review.openstack.org/453610 | 12:07 |
| rakhmerov | EmilienM, d0ugal: ok, thanks for explanations | 12:13 |
| rakhmerov | kong: yeah, I probably need to add you into mistral release team | 12:14 |
| rakhmerov | let me check.. | 12:14 |
| rakhmerov | kong: ok, I added you into mistral-release group, you can try again | 12:16 |
| rakhmerov | kong: here's a couple of links on using GPG to sign tags: http://fedoraproject.org/wiki/Creating_GPG_Keys#Creating_GPG_Keys_Using_the_Command_Line, http://openpgpblog.tumblr.com/post/288011255/using-gpg-to-sign-git-tags | 12:17 |
| *** dprince has quit IRC | 12:59 | |
| *** tuan_ has quit IRC | 13:03 | |
| *** shardy_lunch is now known as shardy | 13:08 | |
| *** 21WAA0340 has joined #openstack-mistral | 13:08 | |
| *** catintheroof has joined #openstack-mistral | 13:10 | |
| *** catintheroof has quit IRC | 13:10 | |
| *** catintheroof has joined #openstack-mistral | 13:11 | |
| *** amoralej is now known as amoralej|lunch | 13:17 | |
| *** chlong has joined #openstack-mistral | 13:17 | |
| thrash | rakhmerov: think these are related: https://bugs.launchpad.net/mistral/+bug/1671505 and https://bugs.launchpad.net/mistral/+bug/1654555 | 13:36 |
| openstack | Launchpad bug 1671505 in Mistral "Tempest errors running mistral-api as wsgi in apache" [Undecided,New] | 13:36 |
| openstack | Launchpad bug 1654555 in Mistral "test_get_list_executions_with_pagination fails in Puppet CI" [Undecided,In progress] - Assigned to Brad P. Crochet (brad-9) | 13:36 |
| thrash | rakhmerov: I believe them to be related to concurrency | 13:36 |
| thrash | rakhmerov: but I haven't been able to get a consistent enough result to get any useful insights | 13:38 |
| thrash | if anyone has any ideas on the above, I'm all ears. :) | 13:38 |
| thrash | Or eyes, as it were. | 13:38 |
| 21WAA0340 | thrash: you mean two patches you have posted | 13:39 |
| *** 21WAA0340 has quit IRC | 13:39 | |
| *** tuan_ has joined #openstack-mistral | 13:39 | |
| d0ugal | thrash: silly question, how do you run tempest tsts? | 13:46 |
| toure | d0ugal which test would you like to run | 13:51 |
| toure | just the mistral test? | 13:51 |
| d0ugal | toure: yeah, all Mistral tests | 13:51 |
| * toure grabs doc | 13:51 | |
| toure | only some much I can keep in the brain | 13:52 |
| d0ugal | I should probably try and look it up :-D | 13:52 |
| d0ugal | but it turns out I am lazy | 13:52 |
| toure | hehe, same here | 13:52 |
| toure | d0ugal do you have the configuration partially setup? | 13:53 |
| toure | or do you need to start from scratch? | 13:53 |
| d0ugal | toure: from scratch | 13:53 |
| toure | d0ugal https://docs.openstack.org/developer/tempest/configuration.html | 13:54 |
| toure | that is the first stop, I am trying to find the shortcut file I have | 13:54 |
| thrash | d0ugal: couple of ways... either via devstack or via puppet-openstack-integration | 13:55 |
| d0ugal | aha | 13:56 |
| d0ugal | I think I did it once before with devstack, this is ringing a bell. | 13:56 |
| thrash | I'm using puppet-openstack-integration now, because it sets up mistral via apache wsgi | 13:56 |
| thrash | devstack does not | 13:56 |
| d0ugal | right | 13:57 |
| d0ugal | which is why it passes in mistral CI I guess. | 13:57 |
| *** amoralej|lunch is now known as amoralej | 13:57 | |
| thrash | why devstack does? | 13:57 |
| thrash | we should probabaly add the puppet integration scenario003 to mistral gating | 13:58 |
| *** warface has quit IRC | 14:04 | |
| *** jistr is now known as jistr|mtg | 14:07 | |
| *** shardy is now known as shardy_mtg | 14:07 | |
| *** bobh has joined #openstack-mistral | 14:13 | |
| *** rbrady has joined #openstack-mistral | 14:15 | |
| *** rbrady has quit IRC | 14:15 | |
| *** rbrady has joined #openstack-mistral | 14:15 | |
| openstackgerrit | Sharat Sharma proposed openstack/mistral-dashboard master: Added link to Create Action form Edit https://review.openstack.org/453656 | 14:20 |
| d0ugal | thrash: +1 | 14:22 |
| openstackgerrit | Dougal Matthews proposed openstack/python-mistralclient master: Add a missing space to the help message for execution-create https://review.openstack.org/453666 | 14:27 |
| *** dprince has joined #openstack-mistral | 14:34 | |
| d0ugal | I wonder if anyone finds this useful: https://docs.openstack.org/developer/mistral/guides/cli_guide.html | 14:38 |
| d0ugal | The formatting is partially broken, there is invalid rst in there too. | 14:38 |
| d0ugal | I don't think it is updated | 14:38 |
| d0ugal | I am wondering if it should be re-done or deleted :) | 14:38 |
| *** tung_doan has quit IRC | 14:52 | |
| thrash | d0ugal: My vote would be either delete or rework to use OSC | 14:58 |
| d0ugal | thrash: that might not be all that popular as we have so many non-openstack users. | 14:58 |
| d0ugal | does python-openstackclient work without keystone? | 14:58 |
| *** chlong has quit IRC | 15:03 | |
| *** chlong has joined #openstack-mistral | 15:04 | |
| thrash | d0ugal: That's a good question, and good point. I don't think so. | 15:06 |
| thrash | d0ugal: is that auto-generated from the sources? If not, it should be. :) | 15:06 |
| d0ugal | thrash: I'm not sure, it sort-of looks like it was - and that would explain the bad syntax. | 15:07 |
| thrash | hehe | 15:07 |
| *** chlong has quit IRC | 15:21 | |
| *** shardy_mtg is now known as shardy | 15:21 | |
| *** tung_doan has joined #openstack-mistral | 15:30 | |
| *** chlong has joined #openstack-mistral | 15:35 | |
| *** jistr|mtg is now known as jistr | 15:40 | |
| *** shardy is now known as shardy_afk | 16:02 | |
| *** jkilpatr_ has joined #openstack-mistral | 16:04 | |
| *** jkilpatr has quit IRC | 16:06 | |
| *** jpich has quit IRC | 16:28 | |
| *** shardy_afk is now known as shardy | 16:31 | |
| *** shardy has quit IRC | 17:03 | |
| *** jamielennox has quit IRC | 17:04 | |
| *** jamielennox has joined #openstack-mistral | 17:07 | |
| *** jaosorior is now known as jaosorior_away | 17:08 | |
| *** jtomasek has quit IRC | 17:38 | |
| *** bobh has quit IRC | 17:42 | |
| *** dprince has quit IRC | 17:53 | |
| *** jkilpatr_ has quit IRC | 17:54 | |
| *** tuan_ has quit IRC | 17:57 | |
| *** dprince has joined #openstack-mistral | 18:06 | |
| *** jkilpatr_ has joined #openstack-mistral | 18:08 | |
| *** harlowja has quit IRC | 18:33 | |
| *** amoralej is now known as amoralej|off | 18:41 | |
| *** bobh has joined #openstack-mistral | 18:42 | |
| *** bobh has quit IRC | 18:47 | |
| *** bobh has joined #openstack-mistral | 19:10 | |
| *** harlowja has joined #openstack-mistral | 19:58 | |
| *** jamielennox is now known as jamielennox|away | 20:12 | |
| *** dprince has quit IRC | 21:00 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/mistral master: Updated from global requirements https://review.openstack.org/453883 | 21:03 |
| kong | d0ugal: re 'I wonder if anyone finds this useful: https://docs.openstack.org/developer/mistral/guides/cli_guide.html' | 21:28 |
| kong | no, it's totally useless IMO. The content is the same with when you run 'mistral help <action>' | 21:29 |
| *** jkilpatr_ has quit IRC | 21:42 | |
| *** catintheroof has quit IRC | 21:54 | |
| *** chlong has quit IRC | 22:02 | |
| *** harlowja has quit IRC | 22:05 | |
| *** jamielennox|away is now known as jamielennox | 22:13 | |
| *** rbrady has quit IRC | 22:14 | |
| *** gongysh has joined #openstack-mistral | 22:19 | |
| *** jkilpatr_ has joined #openstack-mistral | 22:20 | |
| thrash | kong: I agree there... Doubt anyone is going to go web searching for cli args. :) | 23:02 |
| *** bobh has quit IRC | 23:09 | |
| *** gongysh has quit IRC | 23:20 | |
| *** harlowja has joined #openstack-mistral | 23:25 | |
| *** jamielennox is now known as jamielennox|away | 23:42 | |
| *** jamielennox|away is now known as jamielennox | 23:45 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!