openstack/mistral
Code Issues Proposed changes

Add "Project Goals 2017" to README.rst

Browse Source 
Change-Id: I03df44f9779a643ae89514101f457990cd28bab4
This commit is contained in:
Renat Akhmerov 2017-04-13 18:11:09 +07:00
parent 5a3099765d
commit ddc80dea81
1 changed files with 41 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
README.rst
View File

@ -212,6 +212,47 @@ defined in the configuration file should only be used if ``all`` Mistral
servers are launched on the same process. Otherwise, messages do not get
delivered because the ``fake`` transport is using an in-process queue.
Project Goals 2017
------------------
#. **Complete Mistral documentation**.
Mistral documentation should be more usable. It requires focused work to
make it well structured, eliminate gaps in API/DSL specifications, add more
examples and tutorials.
*Definition of done*:
All capabilities are covered, all documentation topics are written using
the same style and structure principles. The obvious sub-goal of this goal
is to establish these principles.
#. **Complete Mistral Custom Actions API**.
There has been the initiative in Mistral team since April of 2016 to
refactor Mistral actions subsystem in order to make the process of
developing Mistral actions easier and clearer. In 2017 we need to complete
this effort and make sure that all APIs are stable and it’s well-documented.
*Definition of done*:
All API interfaces are stable, existing actions are rewritten using this new
API, OpenStack actions are also rewritten based on the new API and moved to
mistral-extra repo. Everything is well documented and the doc has enough
examples.
#. **Finish Mistral multi-node mode**.
Mistral needs to be proven to work reliably in multi-node mode. In order
to achieve it we need to make a number of engine, executor and RPC
changes and configure a CI gate to run stress tests on multi-node Mistral.
*Definition of done*:
CI gate supports MySQL, all critically important functionality (join,
with-items, parallel workflows, sequential workflows) is covered by tests.
#. **Reduce workflow execution time**.
*Definition of done*: Average workflow execution time reduced by 30%.
Project Resources
-----------------