Re: [openstack-dev] [mistral] [fuel] Executor task affinity
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. Renat Akhmerov @ Mirantis Inc. On 02 Oct 2014, at 16:11, Dmitriy Shulyak wrote: > Hi, > > As i understood you want to store some mappings of tags to hosts in database, > but then you need to sort out api > for registering hosts and/or discovery mechanism for such hosts. It is quite > complex. > It maybe be usefull, in my opinion it would be better to have simpler/more > flexible variant. > > For example: > > 1. Provide targets in workbook description, like: > > task: > targets: [nova, cinder, etc] > > 2. Get targets from execution contexts by using yaql: > > task: > targets: $.uids > > task: > targets: [$.role, $.uid] > > In this case all simple relations will be covered by amqp routing > configuration > What do you think about such approach? > > On Thu, Oct 2, 2014 at 11:35 AM, Nikolay Makhotkin > wrote: > Hi, folks! > > I drafted the document where we can see how task affinity will be applied to > Mistral: > > https://docs.google.com/a/mirantis.com/document/d/17O51J1822G9KY_Fkn66Ul2fc56yt9T4NunnSgmaehmg/edit > > -- > Best Regards, > Nikolay > @Mirantis Inc. > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [mistral] [fuel] Executor task affinity
Hi, As i understood you want to store some mappings of tags to hosts in database, but then you need to sort out api for registering hosts and/or discovery mechanism for such hosts. It is quite complex. It maybe be usefull, in my opinion it would be better to have simpler/more flexible variant. For example: 1. Provide targets in workbook description, like: task: targets: [nova, cinder, etc] 2. Get targets from execution contexts by using yaql: task: targets: $.uids task: targets: [$.role, $.uid] In this case all simple relations will be covered by amqp routing configuration What do you think about such approach? On Thu, Oct 2, 2014 at 11:35 AM, Nikolay Makhotkin wrote: > Hi, folks! > > I drafted the document where we can see how task affinity will be applied > to Mistral: > > > https://docs.google.com/a/mirantis.com/document/d/17O51J1822G9KY_Fkn66Ul2fc56yt9T4NunnSgmaehmg/edit > > -- > Best Regards, > Nikolay > @Mirantis Inc. > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [mistral] [fuel] Executor task affinity
Hi, folks! I drafted the document where we can see how task affinity will be applied to Mistral: https://docs.google.com/a/mirantis.com/document/d/17O51J1822G9KY_Fkn66Ul2fc56yt9T4NunnSgmaehmg/edit -- Best Regards, Nikolay @Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
