<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Yes, Dmitri, thank you for your comments. We basically came to the same conclusion. For now DB is not going to be involved and it will be possible to fill ‘targets’ from workflow input using YAQL expressions to be able to assign tasks to executors dynamically.<div><br></div><div><div>
<div>Renat Akhmerov</div><div>@ Mirantis Inc.</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On 02 Oct 2014, at 16:11, Dmitriy Shulyak <<a href="mailto:dshulyak@mirantis.com">dshulyak@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>As i understood you want to store some mappings of tags to hosts in database, but then you need to sort out api</div><div>for registering hosts and/or discovery mechanism for such hosts. It is quite complex.</div><div>It maybe be usefull, in my opinion it would be better to have simpler/more flexible variant. </div><div><br></div><div>For example:</div><div><br></div><div>1. Provide targets in workbook description, like:</div><div><br></div><div>task:</div><div> targets: [nova, cinder, etc]</div><div><br></div><div>2. Get targets from execution contexts by using yaql:</div><div><br></div><div>task:</div><div> targets: $.uids</div><div><br></div><div>task:</div><div> targets: [$.role, $.uid]</div><div><br></div><div>In this case all simple relations will be covered by amqp routing configuration</div><div>What do you think about such approach?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 2, 2014 at 11:35 AM, Nikolay Makhotkin <span dir="ltr"><<a href="mailto:nmakhotkin@mirantis.com" target="_blank">nmakhotkin@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, folks! <br><br>I drafted the document where we can see how task affinity will be applied to Mistral:<div><br></div><div><a href="https://docs.google.com/a/mirantis.com/document/d/17O51J1822G9KY_Fkn66Ul2fc56yt9T4NunnSgmaehmg/edit" target="_blank">https://docs.google.com/a/mirantis.com/document/d/17O51J1822G9KY_Fkn66Ul2fc56yt9T4NunnSgmaehmg/edit</a><span class="HOEnZb"><font color="#888888"><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><font>Best Regards,</font></div><div><font>Nikolay</font></div><div><font>@Mirantis Inc.</font></div></div>
</font></span></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></body></html>