3386 Commits

Author SHA1 Message Date
Vitalii Solodilov
9ba81eb6c6 Replaced the deprecated options in the configuration guide
Change-Id: If59cb3c1011bc26174f1ebb98626960d22e190a8
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
2018-02-25 15:17:40 +04:00
Winson Chan
3f48e24dc4 Implement notification of execution events
Introduce execution events and notification server and plugins for
publishing these events for consumers. Event notification is defined per
workflow execution and can be configured to notify on all the events or
only for specific events.

Change-Id: I9820bdc4792a374dad9ad5310f84cd7aaddab8ca
Implements: blueprint mistral-execution-event-subscription
2018-02-24 07:25:55 +00:00
Andras Kovi
ce454f5f26 Hard code top package name
Using the package name to identify the top module name can cause issues
if the package is renamed for any reasons. Hard coding the top module
ensures more resiliency towards these types of accidental failures
and provides an obvious mapping for the file names.

Change-Id: I9542ba8f01f57b1b3473185c42d95d99ad1e8435
2018-02-22 15:17:47 +01:00
Renat Akhmerov
7423a58365 Explain better combinations of task names and engine commands in docs
Closes-Bug: #1682377
Change-Id: I6c53fc6b3debaf27b01a03b5180f3ef56ddf3e8f
2018-02-20 10:31:30 +02:00
OpenStack Proposal Bot
1f1463adf1 Updated from global requirements
Change-Id: I96b5c43e2ef666e69afcb8ed3c6188e995da0670
2018-02-16 02:14:20 +00:00
Zuul
1f83e5d5a2 Merge "Cache action definitions" 2018-02-15 10:14:19 +00:00
Zuul
aec1193fd3 Merge "Updated from global requirements" 2018-02-15 07:41:37 +00:00
2de17cb760 Update reno for stable/queens
Change-Id: Ic780f945537ed07b0ba58bd58eaddf5a1a1693a3
2018-02-14 13:42:32 +00:00
OpenStack Proposal Bot
5410533bb8 Updated from global requirements
Change-Id: Ibdfd269d450deeae40260985cb71b9b9b62e499b
2018-02-14 12:10:17 +00:00
Mike Fedosin
1ae082794a Cache action definitions
Now to perform some action mistral gets its definition from
the database first. It's not really optimal, because if there are
a lot of similar action calls, mistral will reread the same data
from db. It increases the whole execution time and the load on the
database.

To improve the performance it's suggested to cache read definitions
and take them from the cache instead of the database in the subsequent
times.

Cache ttl can be configured with ``action_definition_cache_time``
option from [engine] group. The default value is 60 seconds.

Change-Id: I330b7cde982821d4f0a06cdd2954499ac0b7be37
2018-02-12 16:16:54 +01:00
Zuul
90d2a94dd8 Merge "Correction of comments for the #539039 review" 2018-02-12 13:08:11 +00:00
Zuul
d5dfa2e242 Merge "Fix error sql about privileges in doc" 2018-02-12 11:03:36 +00:00
Zuul
d8b4db82af Merge "Update mysql connection in doc" 2018-02-12 11:03:03 +00:00
Vitalii Solodilov
e8d6c382c5 Correction of comments for the #539039 review
Change-Id: Id76c20d2da20c362ca94727e5c5dea2e19ed6b6d
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
2018-02-12 04:09:12 +04:00
Zuul
82d5d10f89 Merge "Tags in workflows were not being properly checked" 2018-02-09 14:51:58 +00:00
Zuul
0727c35bc1 Merge "Really make the cron trigger execution interval configurable" 2018-02-09 11:42:01 +00:00
Zuul
e3e8dda43f Merge "Consider size of output_on_error" 2018-02-09 08:29:36 +00:00
Zuul
1d4ff0ab40 Merge "Adding Keycloak authorization support." 2018-02-09 08:25:50 +00:00
Dougal Matthews
24be74635a Really make the cron trigger execution interval configurable
Note: This is an update to I9060253bc416be28af4ef81f3edf694059d92066,
      which almost worked but due to a race condition with config loading
      the default value may have been used. This delays the decorator
      execution to allow the config to be fully loaded.

The cron_trigger subsystem in Mistral queries the database every second
to look for triggers that require execution. This can be very wasteful
if your deployment only has cron triggers that run infrequently (every
hour or day etc.). Letting operators configure this value reduces the
load and allows the cron triggers to be useful in more scenarios.

Operators do need to be aware that this configuration would limit the
frequency of execution. For example, if the value is set to 600 then cron
triggers configured to run every minute will only run every 10 minutes.

Related-Bug: #1747386
Change-Id: Ia12dcf7fa6b1784be226d223eb89b114c8e4b4f5
2018-02-08 14:29:58 +00:00
rsritesh
5691ddf94a Consider size of output_on_error
While printing the output of a execution
size of output_on_error is not considered
with the field_size_limit_kb

This patch udpates the function to include
the logical calculation of total size limit

Closes-Bug: #1690316
Change-Id: Icab63d147f580b8d72d8c02b3d9261fd64d3438a
2018-02-08 05:55:29 +00:00
Brad P. Crochet
7c807d3d82 Tags in workflows were not being properly checked
If an invalid tag section was specified, Mistral would throw a 500,
with no useful error message. This makes the tags get checked and
throws a proper error if so.

Change-Id: If2ae69ef76a857bcafe1e4b3d72956c6deeeea09
Closes-Bug: #1747950
2018-02-07 13:33:59 -05:00
Zuul
7da5b880c9 Merge "Make the cron trigger execution interval configurable" 2018-02-07 14:57:55 +00:00
Zuul
23828f6a33 Merge "Propagated a task timeout to a action execution" 2018-02-07 10:57:04 +00:00
Zuul
d535b13f4f Merge "Remove achieved goals from the lis of annual goals" 2018-02-07 09:35:06 +00:00
Zuul
ec0219b0bd Merge "Fix how a cron trigger starts a workflow" 2018-02-07 09:35:05 +00:00
Dougal Matthews
a1ab5d85cc Make the cron trigger execution interval configurable
The cron_trigger subsystem in Mistral queries the database every second
to look for triggers that require execution. This can be very wasteful
if your deployment only has cron triggers that run infrequently (every
hour or day etc.). Letting operators configure this value reduces the
load and allows the cron triggers to be useful in more scenarios.

Operators do need to be aware that this configuration would limit the
frequency of execution. For example, if the value is set to 600 then cron
triggers configured to run every minute will only run every 10 minutes.

Related-Bug: #1747386
Change-Id: I9060253bc416be28af4ef81f3edf694059d92066
2018-02-07 09:16:52 +00:00
Chen Eilat
760fb914f0 Adding Keycloak authorization support.
Change-Id: I6e3cd86ecee9f666502076f82b0be935a2228892
2018-02-07 09:01:08 +00:00
Renat Akhmerov
7fac88cce5 Fix how a cron trigger starts a workflow
* It was broken when we were adding the "wf_ex_id" parameter to
  Engine.start_workflow()
* Fixed the test that checks how triggers start workflows
* Other minor changes

Change-Id: Ida361a53ffdb5426a39d276d567391d25261fb7f
2018-02-07 11:10:47 +07:00
Zuul
5dba6c77ed Merge "Fixes mistral-server --version command" 2018-02-07 00:28:58 +00:00
Zuul
3e886c6827 Merge "More tests for running workflows based on existing." 2018-02-06 19:41:28 +00:00
Ryan Brady
897364400e Fixes mistral-server --version command
This patch changes the call into oslo_config to pass the string
containing the version instead of passing the version module.

Change-Id: I698d7206c195f1762dfbadb78c599c60be7f310b
Fixes-bug: 1717869
2018-02-06 08:48:25 -05:00
Toure Dunnon
79028f2760 More tests for running workflows based on existing.
This proposal will add a couple more scenarios to the unit
test for the source_execution option.

Related-Bug: #1745962
Change-Id: If5b846c8e45df9e20c2d5da099bddcbf9432d797
2018-02-05 13:53:17 -05:00
Zuul
9b4badd14f Merge "Fixing grammar mistake" 2018-02-05 13:48:28 +00:00
Zuul
3746ff47b6 Merge "Using oslo_log instead of logging" 2018-02-05 13:22:14 +00:00
Renat Akhmerov
0b28e30436 Remove achieved goals from the lis of annual goals
Change-Id: Ie2a308e139a81c65943114a563569b44fd04b6f9
2018-02-05 18:09:57 +07:00
Zuul
e6a7ba2af4 Merge "Fix docs to better reflect Jinja and YAQL usage" 2018-02-05 09:37:29 +00:00
chenxiangui
e0951c110f Fixing grammar mistake
The description of the param 'content_type' doesn't read well,
I think 'Content-Type of the response' is better.

Change-Id: Idfdedf2cfc1abf6ab6f6980114c6d7d00c557afc
2018-02-05 08:47:20 +00:00
chenxiangui
c55eaba612 Using oslo_log instead of logging
The oslo.log (logging) configuration library provides standardized
configuration for all openstack projects. It also provides custom
formatters, handlers and support for context specific logging (like
resource id's etc).

I think it's better to use the common logging module.

Change-Id: I3baefd043a557417e8317a80d57cc5a4a48ccc08
2018-02-02 04:29:06 +00:00
pengdake
79d1f87980 Update mysql connection in doc
Change-Id: If7f5eea5f87ada7c6bc4783b04e9a792bb5cd6f3
2018-02-02 02:31:13 +08:00
pengdake
0ca36b2819 Fix error sql about privileges in doc
Change-Id: I4893e1415a6e0820900353270b62e20279d5bf1c
2018-02-02 00:29:00 +08:00
Zuul
b991844679 Merge "Fix some reST field lists in docstrings" 2018-02-01 07:31:20 +00:00
Zuul
5d5e6c777c Merge "modify the import order" 2018-01-31 17:22:37 +00:00
Zuul
ff9584168a Merge "change import order" 2018-01-31 14:40:40 +00:00
Zuul
9b10790745 Merge "the word arguements should be arguments" 2018-01-31 14:40:39 +00:00
Zuul
5634ba68a8 Merge "TrivialFix: remove redundant import alias" 2018-01-31 14:40:38 +00:00
Vitalii Solodilov
b79f91e9ec Propagated a task timeout to a action execution
It shall be possible to specify timeout for Mistral actions in order
to cancel some long-performed action so that to provide predictable
execution time for client service.
Currently Mistral allows configure timeout on task and automatically
changes task status to error. However mistral don't interrupt action
execution.
We need Mistral to terminate timed out action execution, because there
might be the following issues:
* several the same action executions can run at the same time breaking
data consistency
* stale action executions may lead to the massive resources
consumption (memory, cpu..)

Change-Id: I2a960110663627a54b8150917fd01eec68e8933d
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
2018-01-31 17:40:52 +04:00
Zuul
93ec9fbbe8 Merge "Modify error spelling word" 2018-01-31 12:24:43 +00:00
Zuul
fb3c6f9d4a Merge "Use the latest policy-json-file reference" 2018-01-31 12:10:43 +00:00
chenjiao
49bdc31f93 modify the import order
Alphabetically order your imports by the full module path.
Organize your imports according to the Import order template and
Real-world Import Order Examples below.

{{stdlib imports in human alphabetical order}}
\n
{{third-party lib imports in human alphabetical order}}
\n
{{project imports in human alphabetical order}}
\n
{{begin your code}}

Change-Id: I16e97549a7ae6ddedc07e76dba72236460060650
2018-01-31 11:38:29 +00:00
Zuul
6e75cc3486 Merge "Add claim_messages and delete_messages zaqar actions" 2018-01-31 11:13:14 +00:00