<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Oooh, ok! Yeah, additional tests for that would help us clearly see that solved.<div class=""><br class=""></div><div class="">Thanks!<br class=""><div class=""><br class="webkit-block-placeholder"></div><div class="">
<div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 03 Mar 2015, at 18:03, Peter Razumovsky <<a href="mailto:prazumovsky@mirantis.com" class="">prazumovsky@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Hi Renat,<br class=""><br class=""></div>We solved problem with referencing. I'll add more tests for understanding, how Mistral Workflow resource look like in Heat template. <br class=""><br class=""></div><br class=""><div class="gmail_extra"><div class="gmail_quote">2015-03-03 14:35 GMT+03:00 Renat Akhmerov <span dir="ltr" class=""><<a href="mailto:rakhmerov@mirantis.com" target="_blank" class="">rakhmerov@mirantis.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class="">Hi Peter,<div class=""><br class=""></div><div class="">Thanks for sharing this.. Overall it looks good to me, I just left a couple of comments/questions in <a href="https://review.openstack.org/#/c/147645/17/contrib/heat_mistral/heat_mistral/tests/test_workflow.py" target="_blank" class="">https://review.openstack.org/#/c/147645/17/contrib/heat_mistral/heat_mistral/tests/test_workflow.py</a> Could you please take a look?</div><div class=""><br class=""></div><div class="">We keep in mind that one thing is still not implemented: workflow references get broken if we upload a workflow which calls another workflow. We need to discuss the best way to deal with that. Either we need to do in Heat itself to restore those references accounting for stack name etc.. Or we need to provide some facility in Mistral itself.</div><div class=""><br class=""></div><div class="">Other than that it looks to be ready to start gathering Heat folks’ feedback.</div><div class=""><br class=""></div><div class=""><div class="">
<div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div><div class=""><br class=""></div><br class="">
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="h5"><div class="">On 26 Feb 2015, at 17:49, Peter Razumovsky <<a href="mailto:prazumovsky@mirantis.com" target="_blank" class="">prazumovsky@mirantis.com</a>> wrote:</div><br class=""></div></div><div class=""><div class=""><div class="h5"><div dir="ltr" class=""><div class=""><span lang="en" class="">In anticipation of Mistral supporting in Heat, let's introduce using Mistral in Heat.<br class=""></span></div><div class=""><span lang="en" class="">1. For using Mistral resources workflow and cron-trigger in Heat, Mistral must be installed to DevStack. </span><span lang="en" class=""><span lang="en" class=""><span class="">Installation guide for DevStack on <a href="https://github.com/stackforge/mistral/tree/master/contrib/devstack" target="_blank" class="">https://github.com/stackforge/mistral/tree/master/contrib/devstack</a> </span></span>Detailed information about Workflow and CronTrigger you can find on <a href="https://wiki.openstack.org/wiki/Mistral" target="_blank" class="">https://wiki.openstack.org/wiki/Mistral</a> Note, that currently Mistral use DSLv2 (<a href="https://wiki.openstack.org/wiki/Mistral/DSLv2" target="_blank" class="">https://wiki.openstack.org/wiki/Mistral/DSLv2</a>) and Rest API v2 (<a href="https://wiki.openstack.org/wiki/Mistral/RestAPIv2" target="_blank" class="">https://wiki.openstack.org/wiki/Mistral/RestAPIv2</a>).<br class=""></span></div><div class=""><span lang="en" class="">2. When Mistral will be installed, check it accessibility - in screen or using command 'mistral --help' (list of commands). You can test Mistral resources creating workflow resources with DSLv2-formatted definitions, cron-triggers and executions.<br class=""></span></div><div class=""><span lang="en" class="">For example, command 'mistral workflow-list' gives the table:<br class="">Starting new HTTP connection (1): 192.168.122.104<br class="">Starting new HTTP connection (1): localhost<br class="">+---------------------+--------+------------------------------+---------------------+------------+<br class="">| Name | Tags | Input | Created at | Updated at |<br class="">+---------------------+--------+------------------------------+---------------------+------------+<br class="">| std.create_instance | <none> | name, image_id, flavor_id... | 2015-01-27 14:16:21 | None |<br class="">| std.delete_instance | <none> | instance_id | 2015-01-27 14:16:21 | None |<br class="">+---------------------+--------+------------------------------+---------------------+------------+<br class=""><br class=""></span></div><div class=""><span lang="en" class="">3. Mistral resources for Heat you can find there: <br class=""><a href="https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:master+topic:bp/mistral-resources-for-heat,n,z" target="_blank" class="">https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:master+topic:bp/mistral-resources-for-heat,n,z</a><br class=""></span></div><div class=""><span lang="en" class="">4. Simple templates using Mistral resources in Heat templates you can find there:<br class=""> <a href="https://wiki.openstack.org/wiki/Heat_Mistral_resources_usage_examples" target="_blank" class="">https://wiki.openstack.org/wiki/Heat_Mistral_resources_usage_examples</a><br class=""></span></div><span lang="en" class=""><span class=""></span></span></div></div></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></div><br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>