<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">
<div>Hi,</div>
<div><br /></div>
<div>I'm Renat Akhmerov. I'm running for PTL of Mistral in Rocky.</div>
<div><br /></div>
<div>Mistral is a workflow service developed within the OpenStack community from</div>
<div>the ground up.</div>
<div><br /></div>
<div>In queens we mainly focused on bugfixing, improving performance and</div>
<div>documentation. Performance was again significantly improved (~100%)</div>
<div>by optimizing DB operations and data schema (mostly additional indexex)</div>
<div>and using caching technics. We also made Mistral more robust in various</div>
<div>failure situations. To achieve that we came up with a number of protection</div>
<div>mechanisms.</div>
<div><br /></div>
<div>The two other noticeable features we added are:</div>
<div><br /></div>
<div>* We can now start a Mistral workflow based on an existing workflow</div>
<div> execution, no matter if it's still running or finished. Given an ID of</div>
<div> an execution Mistral copies all needed parameters (input, env etc.) and</div>
<div> creates a new execution.</div>
<div>* When creating a workflow execution, we can now pass an ID of the new</div>
<div> execution. If an execution with this ID already exists the REST endpoint</div>
<div> just returns details of this execution as if it was GET operation. If</div>
<div> not, it create a execution with this ID. Thus creation of workflow</div>
<div> execution can be idempotent.</div>
<div><br /></div>
<div><br /></div>
<div>For the next cycle I'd like to propose the following roadmap:</div>
<div><br /></div>
<div>* Keep improving multi-node mode and HA</div>
<div>* Rearchitect Mistral Scheduler, make it more suitable for HA</div>
<div>* Optimize ‘join’ tasks</div>
<div>* Close all the gaps in the documentation and restructure it so it is more</div>
<div> convenient to read and navigate</div>
<div>* Usability</div>
<div> * New CLI/API (more consistent and human friendly interface)</div>
<div> * Debugging workflows</div>
<div> * Workflow failure analysis (error messages, navigate through nested</div>
<div> workflows etc.)</div>
<div>* Refactor Actions subsystem</div>
<div> * Actions testability</div>
<div> * Move OpenStack actions into mistral-extra and with better test coverage</div>
<div> and usability</div>
<div><br /></div>
<div>Some of those items have now been in progress for a few months. We keep</div>
<div>working on them and I hope most of them will be completed in the next</div>
<div>cycle.</div>
<div><br /></div>
<div>Should you have any ideas on these points we're always happy to discuss and</div>
<div>correct our plans.</div>
<div><br /></div>
<div>We're always happy to get new contributors on the project and always ready</div>
<div>to help people interested in Mistral development get up to speed. The best</div>
<div>way to get in touch with us is IRC channel #openstack-mistral.</div>
<div><br /></div>
<div><br /></div>
<div>The corresponding patch to openstack/election:</div>
<div><a href="https://review.openstack.org/#/c/540720/">https://review.openstack.org/#/c/540720/</a></div>
</div>
<div name="messageSignatureSection"><br />
<div class="matchFont">Thanks</div>
<div class="matchFont"><br style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;" />
Renat Akhmerov<br style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;" />
@Nokia</div>
</div>
</body>
</html>