* This module was always a weird entity in the system having just
one function that essentially creates a dynamic class. It was
created just because we didn't understand where else to put this
function. But now after the action provider refactoring we don't
need it anymore. Action instantiation is now a responsibility of
action descriptor classes.
Change-Id: Ic4b6a9a7ca2784a892d2998359edb220ff8c8911
* Some ".. image:" RST directives changed to ".. figure:" where
it's more suitable.
* All images moved to subfolder where they're used
* Fixed indentation in the Workflow Language specification
* Other minor changes in docs
Change-Id: If2f206a5191d1eecdcf95e1f7b44a87968432876
* Grouped documentation articles into several main parts: user docs,
admin docs, developer docs.
* Changed the index page so that it contains links to the index pages
of the main documentation parts like user docs, admin docs etc.
* Fixed all the broken links
* Removed index generation since it's not informative at all in its
current form and it exposes code internals (REST controller class
names)
* Removed obsolete properties that are no longer used by the
"openstackdocstheme" project
* Removed obsolete static html files
* Moved part of the images to the folders where they are used
Further work:
* Refactor main chapters (user, admin, developer) one by one and
make them look consistent. For example, there are several pages
that provide similar kind of information: overview, quick start,
main features etc. It is a mess that's been accumulated throughout
the last 4-5 years.
* Fill the gaps. Add all missing pages like: event notifications,
workflow environment, etc.
* Move cookbooks from Wiki to this doc.
Partially implements: blueprint mistral-restructure-docs
Change-Id: Ia722a6885ad2fb97d63a34285b0a5b1a23da79e8
Fail-on policy allows to fail success tasks by condition. It is useful
in cases we have to fail task if its result is unacceptable and it makes
workflow definition more readable.
Change-Id: I57b4f3d1533982d3b9b7063925f8d70f044aefea
Implements: blueprint fail-on-policy
Signed-off-by: Oleg Ovcharuk <vgvoleg@gmail.com>
A not obvious point for users is the task does not retry after a
timeout is triggered. Added clarification in the retry section.
The documentation contains enough example with Jinja usage. Improved
only the create_vm workflow definition.
Added global publishing to the doc. It is brash copy-paste from
https://specs.openstack.org/openstack/mistral-specs/specs/pike/approved/advanced_publishing.html without mention of atomic publish.
Move Docker guides to the installation section.
Change-Id: I149b2e1dff7f86bd356f4dd2f758659469e6a4a8
Closes-Bug: #1789384
Closes-Bug: #1690156
Closes-Bug: #1779244
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
Reply to address is useful when sending email from an unmonitored email
address and to give user a place to respond in order to contact us.
Add Reply-to as described in section 3.6.2 of RFC5222
https://tools.ietf.org/html/rfc5322#section-3.6.2
Change-Id: Ib6b2bdc130e4f9e5170eb88760d69c3e08d2a1c7
Adds support for cc and bcc addresses to send mails as copy to
administrators and also html formatting. If the html body is specified
the mail will be sent as multipart.
Closes-Bug: #1783349
Change-Id: I2b90354c33052c4b7ae3a98a08e7df1055524a25
A change for disabling some task names has introduced a massively
backward incompatible behavior. E.g. even though there is a 'noop' engine
command, the usual way of handling noop is in many cases is to create a
task called the same. The other commands are not used that often but
noop is massively present in currently deployed workflows and it is
not possible to mitigate the error if the workflows are coming from
3rd parties.
This change re-enables the usage of the engine commands as task names
and adds documentation on why this is a useful feature.
Change-Id: If90ee5f787e4587a25c156d12c7750407081bf0d
Related-Change: https://review.openstack.org/#/c/535297
* Added new JavaScript evaluator py_mini_racer. Advantages:
* is distributed as wheel package
* supports differences platforms
* live project
* BUILD_V8EVAL was removed because it was replaced by py_mini_racer in
Mistral Docker image
* Added stevedore integration to javascript evaluators
* Refreshed javascript tests. Add test for py_mini_racer evaluator
* Install py_mini_racer library in during mistral test
* Refreshed javascript action doc
Change-Id: Id9d558b9b8374a2c2639e10cb1868f4e67f96e86
Implements: blueprint mistral-add-py-mini-racer-javascript-evaluator
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
The 'join' example for using a number did not have a proper workflow.
It looks like it was copied from the 'all' example and not completely
changed. Also, disambiguate the wording of the description for that
example. It used the word 'once' in a place where it looked as though
it meant 'one time' instead of 'as soon as'.
Change-Id: I9b89768c0f0b7d325db08ea9345965a9263a64c8
Closes-Bug: #1761827
Fixes the bug where calling std.ssh action without "password" input was resulting in error.
Closes-bug: #1756272
Change-Id: I5f7af13326933658014a9c42c495d779bec7f14f
Usage of break-on and continue-on are not very clear. This hopefully
gives some pointers on their usage.
Change-Id: Ide237a23ab85fac7342a8fc9bf748fd0b78bf41d
* verified the length of task name while creating a workflow
* fixed bug when join task has a long name
* added the length limitation to the spec docs
Change-Id: I233e6b0f30d42b939757e9c1caf4965ecc375aee
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
This may be useful for a testing purpose if you want to emulate a
action error with data for timeout, retry and the rest of task policies
Change-Id: I679b8338dade284817000670e96ab108481372ae
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
Renat Akhmerov